Bitcoin Forum
November 18, 2026, 12:15:32 AM *
News: Latest Bitcoin Core release: 32.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Blazecoin Quantum Bridge: a 2014 coin moved its coins behind post-quantum keys  (Read 5 times)
hyperminer (OP)
Jr. Member
*
Offline

Activity: 161
Merit: 5


View Profile WWW
November 17, 2026, 10:35:49 PM
 #1

Blazecoin Quantum Bridge
How a 2014 coin moved its coins behind post-quantum keys, and a free tool to check yours

Blazecoin is a scrypt proof-of-work coin from 2014. Since block 4,250,000 (16 September 2026) every node on its main network checks a post-quantum signature type, ML-DSA-44 (NIST FIPS 204), next to the classic one. Switching the signature on was the smaller half of the job. The larger half was getting coins across to it, and that is what this topic is about.

I call the wallet side of that move the Blazecoin Quantum Bridge. It is a way across on one chain, not a bridge between chains.



The idea: every coin is in one of three states
    [*]Exposed: the public key is already on the chain. Old pay-to-public-key outputs, and any address that has ever spent. A quantum attacker could take these whenever a capable machine exists.
    [*]Hash-safe: the chain shows only a hash of the key. An address that has received and never spent. Safe until you spend from it.
    [*]Post-quantum: the coin sits behind a post-quantum key (on Blazecoin, a BQ... address).
    [/list]

    The Bridge is a wallet that shows you which of your coins are in which state and moves them across: exposed coins first and at once, hash-safe coins the next time they would move anyway.

    What this chain looked like (every unspent output at block 4,320,675, 9 October 2026, 23 days after activation):

    StateCoinsShare of supply
    Exposed409.9 million48.9%
    Hash-safe320.3 million38.2%
    Post-quantum107.5 million12.8%

    Nearly half the supply sat on keys that were already public. That is the number that made the wallet work matter more than the signature work.



    The five jobs, and where they stand
      [*]1. Triage: show which coins are in which state. Built, in the desktop wallet since 12 September 2026.
      [*]2. Hygiene sweep: move exposed coins to a fresh classic address. Built. This needs no change to the chain at all.
      [*]3. Migration sweep: move classic coins into post-quantum addresses. Built, in the desktop and light wallets since 28 September 2026.
      [*]4. Receive-only custody: migrate using the old key and only the new public key. Not built. It is a proposal.
      [*]5. Import old wallets, keeping both ways of signing. Built.
      [/list]

      Four of the five are built and have been used on the main network.

      The honest part

      They have been used mostly with my own coins. In the first eight weeks, 99.98% of the post-quantum spends on the chain were mine: 37 of 158,441 came from anyone else, and 23 outside addresses received post-quantum coins. Most of the post-quantum share in the table above is the project treasury. So this is a migration that has been run end to end on a live chain by its operator. It is not yet a migration that a community of holders has made, and I have not measured what it does for other users.

      It also has a cost. A post-quantum input is 3,782 bytes where a classic one is 148, about 25.6 times the size, and a standard transaction holds 26 of them.



      Check your own coins (Bitcoin or Blazecoin)

      The first job is also published as a small watch-only script. You give it addresses, an extended public key or a descriptor, and it tells you which coins are exposed, which are hash-safe and which are post-quantum. It is one Python file with no dependencies, and it never sees a private key. On Bitcoin it reads any Esplora explorer.

      Code:
      python pq_triage.py bc1q... 3... 1...
      python pq_triage.py --xpub zpub6r...
      python pq_triage.py --chain blazecoin B... BQ...

      Its limits are written in its README. The main one: it sees one chain. If you have revealed a key somewhere else (a signed message, a shared extended public key, the same key on a fork), treat that coin as exposed whatever the tool says.



      What is and is not being claimed
        [*]This is not "quantum-proof". A coin behind a BQ address is protected as far as ML-DSA-44 holds, which is a newer assumption than the hash functions Bitcoin's drafts lean towards.
        [*]The pieces are not new. BitGo has an exposure checker and a sweep for its custody clients. Project Eleven runs a registry that ties an address to a post-quantum key. What I have not found elsewhere is the whole move as one wallet pattern, run on a live chain with the numbers written down.
        [*]Others have put post-quantum signatures on a network before: Bitcoin Post-Quantum did in 2018 on a chain split from Bitcoin's history, and Marscoin has a post-quantum branch on its test network. If you know of another coin that has added them to its own running main network, tell me and I will add it.
        [*]It was a hard fork by one operator. That part does not transfer to a larger network.
        [/list]

        Everything is free to use

        The field report, the companion note with the Bridge in full (section 8), the defect list, test vectors with an independent verifier, and regtest patches for Bitcoin Core, Litecoin Core and Dogecoin Core are here, under MIT and CC BY, with a written pledge that none of it is or will be patented:

        github.com/AMA-CSharp-Code/blazecoin-pq-toolkit

        Run the script on your own addresses and tell me what it gets wrong. Corrections go into the next version.

        hyperminer
        Pages: [1]
          Print  
         
        Jump to:  

        Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!