Quantum-Proof Wallets Without a Single New Address: AmericanFortress's Claim Is a Narrative, Not Cryptography

An entity called AmericanFortress has emerged from the messenger apps with a promise calibrated to our deepest biases: protect your Bitcoin, Ethereum, and Solana wallets from quantum attack—no migration, no new addresses, no friction. The language is not accidental. It is engineered to press the single emotional lever that keeps most users from adopting security upgrades: the perceived cost of change. Over the past week, the claim has circulated through obscure news wires and trading groups, but it has not survived first contact with the cryptographers who actually build the tools. There is no whitepaper. There is no code. There is no audit. There is no named researcher. There is a press release, a conviction, and a void where evidence should live. To hunt the truth, one must first bury the hype. I buried it once across fifty ICO whitepapers in 2017, and the pattern I found then—utility claims that collapsed under a single question of which problem, exactly, is being solved—is repeating here in a more exotic costume. Let us be precise about the threat, because the threat is real, and that is precisely why this claim is dangerous. Shor's algorithm breaks the discrete logarithm problem that underpins secp256k1, the elliptic curve behind most Bitcoin and Ethereum keys. A sufficiently large quantum computer would recover a private key from a public key in polynomial time. For Bitcoin, the exposure is not merely hypothetical; every address that has ever spent funds has permanently published its public key to the chain. Taproot outputs, after a spend, expose their output keys too. The effective shelf life of those coins is shorter than most users assume, and the clock starts the moment a transaction broadcasts. This is why the cryptographic community took the National Institute of Standards and Technology's post-quantum standardization seriously. The winners—CRYSTALS-Dilithium, Falcon, SPHINCS+—are not incremental tweaks to key lengths. They replace the mathematical foundation of signatures entirely, moving from elliptic-curve groups to lattices or hash-based structures. And here is the contradiction AmericanFortress glosses over. A Bitcoin address is a hash of an elliptic-curve public key. Change the signature scheme, and you change the public key; change the public key, and the address no longer resolves under the old derivation rule. There is no known mechanism that allows a Dilithium public key to verify against an address derived from secp256k1 without some act of translation that is, in every meaningful sense, a migration. The claim of unchanged addresses is not a feature; it is an assertion that the algebraic relationship between address and key can be rewritten without anyone noticing. In my years scanning protocol designs, assertions like that are usually a confession in disguise. What are the plausible workarounds? Option one: keep the old signature on-chain but move the security decision off-chain into trusted hardware or multi-party computation. This preserves addresses but abandons the core property of self-custody; a user's coins now hinge on a vendor's enclave or a coordination game between nodes—exactly the trust model this industry was built to dissolve. Option two: a smart-contract envelope that holds users' public keys and verifies post-quantum signatures before forwarding intents. That is not protection for existing wallets; it is a requirement to adopt a new contract, new transaction flows, and new security assumptions. Option three: a genuine cryptographic discovery that reconciles post-quantum signatures with legacy address derivation. Such a break would be published first in a top-tier venue, surrounded by test vectors and hostile reviewers, not pitched to a press desk. The absence of those artifacts is itself data. I have seen this narrative grammar before. In 2020, while studying Uniswap's evolving social contract during DeFi Summer, I watched dozens of forks promise "drop-in liquidity" and "zero-change yield" before decaying into ghost protocols. The storytelling was identical: remove the user's friction, and adoption will follow; do not burden the crowd with mechanism. That logic works for user experience, but it fails as protocol design, because security is not a preference—it is a dependency chain. AmericanFortress is selling the narrative equivalent of a couch that self-assembles: the pitch removes the pain point of assembly by eliminating the assembly process, and in doing so, it also eliminates the furniture. The incumbents in this corner of the industry, from QANplatform's lattice-based layer-1 to Algorand's post-quantum key types, have all accepted the awkward truth: users must move, and the industry must design migration paths that are safe, tested, and simple. No one has found a way around it. A claim that skips the migration step is not an advance; it is a boundary violation dressed as innovation. Test the announcement against market signals, and the picture darkens. Search attention is near zero; no testnet can be found; no GitHub history exists; no team page contains human names. In the aftermath of the 2022 crash, I spent months in isolation, auditing my own biases before writing what became "The Cost of Belief." That exercise taught me to distinguish between pain that produces artifacts—code, papers, failure reports—and pain that only produces pamphlets. Projects with genuine cryptographic intent behave differently: they publish constants, reference implementations, and interim updates before they make headlines. Even Satoshi, hiding identity, shared code. A security product announced without a single commit is not early; it is pre-evidentiary. In the 2017 ICO boom, I read more than fifty whitepapers and isolated a reliable tell: the riskiest projects spent sentences on the grandeur of their problem and no sentences on the unglamorous specifics of their solution. The AmericanFortress specification, as reported, is one sentence long. The timing of the narrative is also convenient. Credible forecasts place a Shor-capable machine years away, and our industry's collective attention appears to hold only one existential risk per calendar year. That gives a claim of this kind a long runway: it cannot be falsified quickly because the deadline is distant, and the deliverable has no observable artifact. In behavioral terms, the pitch exploits two biases at once—status quo bias, by promising zero migration, and ambiguity aversion, by scaring users away from present tools while offering no verifiable substitute. The output is paralysis. Users delay every quantum-preparedness decision while waiting for a miracle that will not arrive. The cost of that delay is not paid today; it is paid in five years, when migration becomes a panic instead of a plan. And here is the deeper irony. Even if AmericanFortress is pure vaporware—and all available evidence points that way—its existence can still inflict real damage, because it gives the ecosystem a permission structure to ignore the actual problem. When the genuinely difficult upgrades arrive, wallets will change key-derivation methods, new address types will be offered, and users will remember the glowing promises of empty press releases. The dismissal reflex will be immediate: we tried that, and it was nothing. A scam does not simply fail; it contaminates the search space of plausible solutions. I wrote about fragile trust mechanisms in AMMs during the 2020 liquidity craze; the pattern is the same. Trust is the new collateral, and it is scarce—every false promise drains the reservoir that real projects need. That is why I find myself more concerned with what is omitted than with what is claimed. The sober state of quantum preparedness is uneven: unspent P2PKH addresses retain some protection via hash preimage resistance, but spent addresses have already displayed their public keys, and their risk matures faster than the industry admits. The honest migration path is not an overlay; it is a slow re-architecture of how keys are derived, stored, and delegated—multisig layering, updated address formats, and a deliberate acceptance that some coins become unrecoverable. That unglamorous middle-class of cryptographic engineering is where survival is actually decided. It is happening in NIST-adjacent working groups, in wallet research labs, and in the quiet corners of protocol repos, not in press releases. To hunt the truth, one must first bury the hype; what remains after the burial is a to-do list, not a product. The question worth tracking is not whether AmericanFortress succeeds; it is whether the industry, having watched one absurd claim burn out, chooses to do the difficult work anyway. I will set my signals accordingly. A peer-reviewed paper on post-quantum key derivation will catch my attention. A commit in a major wallet repository moving test coverage beyond secp256k1 will catch my attention. A press release will not. In a bear market, survival means distinguishing the real bleeding from the theatrical kind; applied to quantum readiness, it means the same discipline. The next credible signal will not be announced. It will arrive as a hash, a test vector, a subtle revision inside an upgrade proposal. Watch the blocks, not the copy—and ignore anyone who promises you can keep them both unchanged forever.