CEO of @SarsonFunds Blockchain and Web3 Investor. Funding the Decentralized Economy from 2016 till as long as it takes.

United States
Joined December 2019
This
You may have seen @drakefjustin warning that AI-driven math could break ECDSA before a quantum computer does, and that assets should move to addresses whose public keys were never exposed. That migration means new addresses, new UX, and years of users who never get around to it. We published a construction that removes the need for it. ZKPoSP (Zero-Knowledge Proof of Seed Provenance) replaces the elliptic-curve signing step with a zero-knowledge proof that the signer holds the seed and full BIP32 derivation chain behind an existing address. Address format unchanged. Funds do not move. The security proof rests only on SHA-256, SHA-512 and a hash-based proof system. No elliptic-curve, lattice or isogeny assumption. The posture Drake is recommending. QBIP-32, in the same paper, extends it to any prime-order curve with one derivation scheme. secp256k1 and Ed25519, covered the same way. This was the conversation two days ago at Quantum & Privacy Day, @token2049 Singapore with @MehowHacks, @conordeegan (@QuantusNetwork), and @cadillion (@quipnetwork). The question on stage was never whether post-quantum cryptography works. It was what it costs to ship. Not moving every user's funds is a big part of the answer.
1
71
Actually is a boss. Part of @ManifestNetwork
I finally found him the final boss of crypto conferences (not AI)
40
John_Sarson retweeted
I finally found him the final boss of crypto conferences (not AI)
393
52
45
2,023
115,907
Manifest is the answer
Today I call upon the blockchain industry to calmly begin planning for "bunker mode". My personal recommendation is to set in motion a controlled mass migration of assets to fresh addresses, i.e. addresses whose pubkeys remain hidden behind a hash. Holders, starting with large and sophisticated ones, should consider moving the bulk of their funds to addresses that have never signed a transaction. And when they do sign one, they should also move remaining funds to a new address (possibly generated from the same seed phrase). Don't rush. While I believe there is cause for action a rushed migration would do more harm than good. Don't panic either. Moving assets to protected addresses is a simple, preventative step which does not require new cryptography or new wallets. IMO it is now reasonable to brace for the possibility that ECDSA breaks before qday, in the worst case in months not years. By "break" I mean fast private key recovery (e.g. in one week) on available hardware (e.g. a large GPU cluster). Recent days have been humbling for human mathematical intuition. Long-held, unquestioned hypotheses have fallen. This includes the n log(n) bound for integer multiplication and the 3SUM conjecture. In hindsight, May's unexpected disproof of the Erdős unit distance conjecture was our warning shot. Yesterday's OpenAI drop made it clear that mathematical superintelligence is upon us. They say there are weeks where decades happen. We are about to live through weeks where centuries of mathematical progress happen. Could our magic 64-byte ECDSA signatures be too good to be true? Was it just security through obscurity all this time? Elliptic curves feel especially vulnerable to superintelligence. Curves carry rich structure, with room for fancy tricks like Schoof, Frobenius, pairings. (By contrast, hashes are designed to minimise algebraic structure.) Separately, as Ewin Tang can attest, an efficient quantum algorithm sometimes foreshadows an efficient classical one. We should be open to the possibility of a classical counterpart to Shor that breaks elliptic curves and RSA at once. Also noteworthy is the striking under-representation of cryptographic breakthroughs among the 722 mathematical results OpenAI published. I've witnessed first-hand the US government censoring academic quantum cryptanalysis results. Backroom interventionism is my base case. I urge large, sophisticated actors to lead by example. Project11's "risq list" (bitcoin-risq-list.projecteleven[.]com) is a great tracker of exposed BTC pubkeys. Binance, Bitbank, Robinhood, Bitfinex, and Tether have an opportunity to harden their cold storage. Next month I'll address institutions in London in a live Q&A (forum.ethereuminstitutional[.]org/london-2026). Again, please do not rush. Wallets holding under 50 BTC enjoy partial cover from "Satoshi's shield", i.e. his 20K exposed addresses that hold 50 BTC each. Load-bearing signers like oracles and L2 security councils should consider rotating ECDSA pubkeys with every signed message and/or multi-signing with a hash-based schemes like SPHINCS. Exiting bunker mode safely will require post-AI cryptography. My inclination is to go all-in on hash-based cryptography and avoid structured mathematical assumptions entirely, whether from curves, lattices, or isogenies. A single battle-tested hash (e.g. from the SHA or BLAKE families) yields plausible post-AI security. The Ethereum roadmap on strawmap[.]org fully embraces hash-based cryptography with end-to-end formal verification as a response to the quantum threat. Those timelines must now be revisited and accelerated in light of mathematical superintelligence. I'll be pushing for maximum defensive acceleration.
52
John_Sarson retweeted
If an AI agent spends your money, who authorized it? And how would you prove it went beyond what you allowed? Our President and CTO Michael Steuer spoke to Investing.com about building accountability into machine payments. Investing.com/analysis/the-a…
10
30
1
146
7,681
John_Sarson retweeted
I see this narrative a lot... the claim that there is no solution to the AI Alignment problem. We better find one! We believe @ManifestNetwork is working towards a solution with our many partners including @rendernetwork @MorpheusAIs @AskVenice and many others. That solution starts with Sovereignty for the individual over the AI systems they interact with. We invite @a_nnawang @hilbertspaess and all other AI researchers searching for solutions in the AI Alignment and Safety space to join us on the quest for AI that works for humanity, and not towards our destruction.
I worked at Google DeepMind and now at Anthropic. This is a common sentiment amongst my peers. (I write this in personal capacity.) There is not yet a viable scientific plan to solve risks from recursively self-improving AI. Please look up!
1
8
23
2,902
John_Sarson retweeted
A look at how hyperscalers, neoclouds, decentralized networks and physical infrastructure are starting to coexist across the AI stack. 🧐 sarsonfunds.com/sovereign-ai…
2
2
5
272
If you are in Wyoming, dont miss a chance to learn about the "quantum fix" that is American Fortress. No hard forks, every token. They said it couldnt be done, meet the guy who did it. We are happy we did!! @SarsonFunds @scottmelker @MarioNawfal
The industry is debating whether to freeze Satoshi's wallets before quantum computers can crack them. That's the wrong question. What we should be asking is, why aren't wallets quantum-resistant by default? @MehowHacks will be talking about exactly that at the @SALTConference in Wyoming. See you there.
1
2
8
345
The industry is debating whether to freeze Satoshi's wallets before quantum computers can crack them. That's the wrong question. What we should be asking is, why aren't wallets quantum-resistant by default? @MehowHacks will be talking about exactly that at the @SALTConference in Wyoming. See you there.
967
385
7
450
7,571
Up to $470B in Bitcoin could be exposed to future quantum attacks, per Bloomberg. Every migration plan so far asks you to move funds and change addresses. Ours doesn't. @Cointelegraph covered our proposal:
868
426
6
672
65,495
Quick breakdown of how stealth address systems actually work: 1. Someone sends to a human-readable name 2. Their wallet computes a brand new receive address that has never existed before 3. Only the sender and recipient can derive that address 4. The address is never reused 5. It works across every chain and every token To an outside observer, every payment appears to go to a completely different wallet. Because cryptographically, it does.
970
395
7
473
6,102
John_Sarson retweeted
one year ago today, there were 28 x402 transactions today, that's being hit every ~3 seconds
19
12
6
117
13,571
John_Sarson retweeted
John Sarson joins @Macro_Wealth and explores key developments shaping the future of crypto, including the GENIUS Act, growing integration between AI and blockchain technology, and the anticipated passage of the CLARITY Act. Watch🔗youtu.be/cbXUPtCBp0E
5
1
13
1,835
Q2 2026 just became the most hacked quarter in crypto history. 83 incidents. Double the previous record for attack frequency. But the dollar losses weren't record-breaking. The shift is the story: not a few giant exploits anymore. A constant stream of smaller ones. The attack surface didn't shrink as the industry matured. It multiplied.
4,209
869
6
824
17,962
From our data center to yours! The @ManifestNetwork team wishes everyone an amazing 4th of July! We will be here keeping the lights on and working on our cable management. Your data doesn't take holidays off, neither do we.
1
5
8
282
John_Sarson retweeted
HTTP has had a 402 status code since 1991. It means Payment Required. For thirty years, nothing used it — because there was no machine-native way to pay for a web request in real time. That problem is now solved. x402.dial.wtf is the internet's payphone. Walk up. Pay in USDC. Get a real US phone number provisioned in two minutes. Send SMS for $0.05. No account. No API key. No 10DLC registration queue. No carrier paperwork. Your wallet is the credential. The number is yours when the payment settles. This is what HTTP payment infrastructure looks like when it actually works. x402.dial.wtf
1
1
5
139
Most compliant privacy systems have a backdoor. They call it a "viewing key" - a master key that lets a third party see into your transactions. For compliance, supposedly. But a viewing key is God mode. Someone, somewhere, can decide to look at your activity without your consent. The better answer: no viewing key at all. The recipient can reveal their funds to whoever they choose, but no third party can decide for them. Compliance without a backdoor. Disclosure without God mode.
4,944
1,609
3
1,447
20,293
Soon
What "privacy by default" actually means in practice: — Your wallet generates a new address for every transaction automatically — Your balance is never visible to people you haven't transacted with — Your transaction history can't be traced back to a single permanent identifier — Compliance is built in, not bolted on afterward None of this requires a separate privacy coin. None of it requires a mixer. None of it requires the user to do anything differently than they do today. That's what "default" means. It just works. Invisibly.
1
110