From: Amon BAZONGO <amonmoce@gmail.com>
To: RB GAMING <ronakbharadiya180@gmail.com>,
Nikita Karetnikov <nikita@karetnikov.org>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] What if we let Quantum Hunters get Bitcoin rewards ?
Date: Thu, 7 May 2026 23:08:56 +0000 [thread overview]
Message-ID: <CAEsN3a4FNd8+b77CfgbdXxGjK_DhYUCF1Wirwfs5PfSp+505Sg@mail.gmail.com> (raw)
In-Reply-To: <CAJMs1u2RqBZj42+NTHwj3r3Lk1NS_CWtNrn9jUF5RWgPUpiOiA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4889 bytes --]
Hello Ronak and all,
Thanks for the feedback. You are right to be concerned.
Let me add some more lights:
1. First, we suppose BIP-360 is a prerequisite to my proposal. Which means
that all new addresses would be quantum-resistant. Each old-address holder
is responsible to migrate to a new quantum-resistant address.
2. So when a hunter (I prefer this term instead of attacker),
proves quantum capability from a monitored address, vulnerable because it
didn't migrate to a new quantum-resistant address, the transaction can be
redirected to mechanism that splits the transaction in two: 10% to the
winning hunter and 90% to a fund that will distribute the rest following
the bitcoin halving cycle.
3. So in practice, each vulnerable UTXO is a "bitcoin one piece"
opportunity. So we might not even have the same hunter for all the ~6.7M
BTC.
So it diffuses the risks, so we do not break bitcoin's core principles, and
we still allow hunters to deserve their reward the same way miners deserve
their reward.
I don't know if it adds some elements that can help clarify the idea.
Thanks for reading,
Amon
On Thu, May 7, 2026 at 8:32 PM RB GAMING <ronakbharadiya180@gmail.com>
wrote:
> Hi Amon,
>
> I read your BIP draft, and personally I like the “One Piece” concept more
> than freezing Bitcoin because of quantum theft risks. The idea is creative,
> and theoretically it makes sense.
>
> However, from a practical perspective, I am still concerned about the
> ~6.7M BTC that could become quantum-exposed. The main issue is that we
> cannot accurately predict how fast quantum computing will evolve in the
> future. If quantum capabilities become much stronger than expected, the
> reward mechanism could create massive incentives for attackers and
> potentially harm Bitcoin’s long-term stability and value.
>
> I do not think the idea is bad at all in fact, it is one of the more
> interesting approaches to this problem. I just feel the risks may currently
> be higher than we expect, which is why freezing vulnerable coins seems like
> the safer option for now.
>
> Of course, this is only my personal point of view. I may be missing some
> cases or thinking differently from your perspective, so please do not take
> my comments the wrong way. I appreciate the effort and creativity behind
> the proposal, and maybe with further refinement the idea could become even
> stronger.
>
> Best regards,
> Ronak
>
> On Thu, 7 May, 2026, 9:19 pm Amon BAZONGO, <amonmoce@gmail.com> wrote:
>
>> Hi all,
>>
>> I'd like to share a draft Informational BIP as an alternative framework
>> to BIP-361's proposed coin freeze.
>>
>> The core argument: rather than suspending Bitcoin's neutrality to prevent
>> quantum theft, we can structure the inevitable quantum capture of exposed
>> coins as a self-financing prize mechanism — the largest open technological
>> prize in history.
>>
>> The proposal introduces three components:
>>
>> - Genesis Quantum Transaction (GQT): recognition of a successful spend
>> from a quantum-exposed address
>> - Quantum Vault (QV): automatically receives 90% of captured funds,
>> distributes periodically to proven quantum actors synchronized with the
>> halving cycle
>> - Quantum Proof Address (QPA): the on-chain identity of any actor who
>> demonstrates quantum capture capability, forming a public, unfalsifiable
>> register of global quantum capabilities
>>
>> The capturing actor receives 10% immediately as a First Reward, with
>> ongoing distributions from the Vault — creating long-term alignment with
>> ecosystem stability rather than incentivizing immediate liquidation.
>>
>> Draft:
>> https://github.com/amonmoce/Hunting-The-Bitcoin-One-Piece/blob/master/bip-hunting-the-bitcoin-one-piece.md
>>
>> Looking forward to technical and philosophical feedback.
>>
>> Best,
>> Amon
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Bitcoin Development Mailing List" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to bitcoindev+unsubscribe@googlegroups.com.
>> To view this discussion visit
>> https://groups.google.com/d/msgid/bitcoindev/46a49975-dbaa-48d5-b50f-36c649041933n%40googlegroups.com
>> <https://groups.google.com/d/msgid/bitcoindev/46a49975-dbaa-48d5-b50f-36c649041933n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/CAEsN3a4FNd8%2Bb77CfgbdXxGjK_DhYUCF1Wirwfs5PfSp%2B505Sg%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 6142 bytes --]
prev parent reply other threads:[~2026-05-07 23:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 15:37 [bitcoindev] What if we let Quantum Hunters get Bitcoin rewards ? Amon BAZONGO
2026-05-07 16:07 ` Nikita Karetnikov
2026-05-07 17:23 ` Amon BAZONGO
2026-05-07 20:32 ` RB GAMING
2026-05-07 23:08 ` Amon BAZONGO [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEsN3a4FNd8+b77CfgbdXxGjK_DhYUCF1Wirwfs5PfSp+505Sg@mail.gmail.com \
--to=amonmoce@gmail.com \
--cc=bitcoindev@googlegroups.com \
--cc=nikita@karetnikov.org \
--cc=ronakbharadiya180@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox