Architectural Note: The "10-Minute Mempool Window" & Why Genesis-Level PQC MattersRecent multi-billion-dollar security breaches across global crypto infrastructure reinforce a basic law in cybersecurity:
adversaries rehearse in the dark and never send advance notice before executing an exploit. While centralized issuers can step in to freeze compromised tokens, native assets moved on L1 with valid signatures are permanently gone. On a true decentralized ledger, there is no "freeze button." Once a valid signature is broadcast, finality is absolute.
Yet legacy blockchains still operate under the illusion of a "graceful migration window," assuming there will be years of public warning to coordinate soft forks and let users safely migrate their funds before fault-tolerant quantum hardware arrives. In reality, once quantum hardware reaches an adversarial threshold, legacy elliptic-curve networks (ECDSA / Schnorr) face an immediate dual-vector trap with zero warning:
1. At-Rest Vulnerability (Exposed On-Chain Public Keys): Legacy P2PK outputs, Taproot (P2TR) outputs, and any previously reused addresses already have their raw elliptic-curve public keys permanently exposed on the ledger. An adversary can derive these private keys silently offline, leaving zero on-chain footprints until the exact millisecond forged signatures are broadcast to drain liquidity.
2. In-Transit Mempool Hijacking (The 10-Minute Confirmation Window): Even if a user protects an un-reused address behind a cryptographic hash (P2PKH / P2WPKH), those funds are only safe while static. The instant a user attempts to spend or panic-migrate those funds to a new address, the transaction must be broadcast to the public mempool. Entering the mempool requires revealing the raw public key in plaintext within the witness payload so peers can verify the signature. During the ~10-minute block confirmation window, a quantum adversary monitoring the mempool can run Shor's algorithm against the newly exposed public key in real time and broadcast a higher-fee replacement transaction (exploiting Replace-By-Fee / RBF) to hijack the funds before the block is mined.
This creates a fatal
"Migration Catch-22" for legacy chains: exposed keys are drained silently at rest, while hash-protected keys are hijacked in mid-air during the 10-minute mempool window the moment holders attempt to flee.
Security cannot rely on reactive migration after an attack begins. That is why
QBTC enforced
NIST FIPS 204 (ML-DSA-65) and
PQ-SegWit strictly from Block 0, ensuring public keys and transactions (whether static, reused, or in-flight in the mempool) remain mathematically immune to quantum key derivation.
The code speaks for itself.
GitHub: https://github.com/Q-Jack-core/quantum-btc
