From: Murch <murch@murch.one>
To: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] What if we let Quantum Hunters get Bitcoin rewards ?
Date: Thu, 21 May 2026 12:46:51 -0700 [thread overview]
Message-ID: <6469ae87-7225-41a2-bc67-3f3e46e6a279@murch.one> (raw)
In-Reply-To: <46a49975-dbaa-48d5-b50f-36c649041933n@googlegroups.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 2743 bytes --]
Hello Amon,
Your document’s formatting is broken, because you use MediaWiki syntax
in a Markdown file.
IMHO, any proposal that calls for Bitcoin to issue a substantial quantum
bounty should make the case why this would be in the interest of the
Bitcoin ecosystem. Your proposal treats this as obvious, but it’s not
clear to me why the Bitcoin ecosystem should involve itself in this
manner in Quantum research.
-Murch
On 2026-05-07 08:37, Amon BAZONGO 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/6469ae87-7225-41a2-bc67-3f3e46e6a279%40murch.one.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 56263 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-05-22 12:40 UTC|newest]
Thread overview: 7+ 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
2026-05-21 19:46 ` Murch [this message]
2026-05-22 17:41 ` Amon BAZONGO
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=6469ae87-7225-41a2-bc67-3f3e46e6a279@murch.one \
--to=murch@murch.one \
--cc=bitcoindev@googlegroups.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