software developer. 1X hackathon winner •Failed at so many things and constantly improving.

Blockchain
Joined January 2021
My goal is to win, and not in a small way.
1
1
1
7
1,060
Einstein explains his formula E=mc².
41
278
31
1,190
76,928
Update: you can claim tesnet RUSD to test the community market app on fibernut It’s also my birthday : Link 👇
Hello fellow CKB builders I just shared a post on the CKB Forum about FiberNuts Community Market, a testnet app for Cashu on Fiber. The post explains the project, what I'm building, and how it connects Cashu with Fiber Network. link to project below👇
2
2
6
111
Another reason to avoid relying on an ever-growing list of cryptographic precompiles is that each one embeds a cryptographic operation in the protocol’s consensus rules. Introducing a new signature scheme this way requires the network to reach social consensus around a fork. There is a consistent direction in Vitalik’s proposals, from exploring RISC-V as a replacement for the EVM to now advocating “EIP-8288 maximalism”: give Ethereum room to support new cryptography without continually expanding the protocol. EIP-8288 would open a path to supporting different signature schemes without a dedicated precompile for each. Signature verification would be proven off-chain, and those proofs aggregated for the chain to check, reducing the associated data and verification costs. The broader idea is one we've discussed extensively: blockchains are for verification, not computation. Vitalik is reframing the "world computer" along precisely these lines: "any data/computation that does not need to be in the 'main thread' of data/execution should not be put into the main thread." This is the reasoning CKB was built around from the beginning. Its accounting model (the Cell model, which is a generalized version of the UTXO model) separates off-chain state generation from on-chain verification. CKB also launched without cryptographic precompiles. Signature verification runs as ordinary software on its RISC-V VM, so developers can introduce new schemes as Lock Scripts and users can adopt them without waiting for a protocol upgrade. That's how an audited post-quantum lock, SPHINCS+, is already live on mainnet. The idea is simple: keep the base layer simple and stable while giving the cryptography and applications built on it room to evolve. It's the essence of crypto-agility, and it's becoming more appreciated amid the looming threat of cryptographically relevant quantum computers and AI.
Ultimately, precompiles and EVM are both the wrong place to put most cryptography support into Ethereum. The reason is that precompiles and EVM both operate on data that has to be included into the ethereum chain somehow, which realistically means included in a block as calldata. That space is limited - even with PeerDAS and blocks-in-blobs, there's a practical cap of ~8 MB/s before it starts getting uncomfortable. Remember: it's not a blockchain. It's a cryptographic world computer. Any data/computation that does not need to be in the "main thread" of data/execution should not be put into the main thread. Instead, the correct solution is... EIP-8288 maximalism. If you have any heavy computation that's self-contained, compute it and STARK it client-side (this is quickly getting faster and faster, even on phones), and push the STARK through the EIP-8288 recursive aggregation mechanism. The chain sees the fact that the computation was done and what the result is; it never needs to see the actual data and computation. This way everyone can use whatever cryptography they want, the Ethereum chain can be lean, and we never need to add more precompiles again.
1
13
2
54
1,048
Congratulations @Hanssen0
All credit goes to @c_hongzhou! I couldn't possibly have finished this paper without him. 感谢舟舟,我不会踌躇。
7
201
Code3ks retweeted
Elon did it all in one life
289
2,365
207
29,368
506,286
You can swap native CKB for native USDC right now using Perun atomic swaps 🙀
7
33
8
108
4,101
Code3ks retweeted
1999. ELON MUSK GETS HIS FIRST MILLIONS AND A $1M SUPERCAR... BUT HIS BIGGEST FEAR THAT DAY WASN'T LOSING THE MONEY 7am. a truck stops outside a small apartment and a 27-year-old Musk watches a McLaren F1 roll off the back "there are 62 McLarens in the world and i will own one of them" "it's a million dollars for a car. it's decadent" he'd just sold Zip2 to Compaq for ~$307M. his cut: ~$22M then he says the line that tells you who he is: "just 3 years ago i was showering at the Y and sleeping on the office floor" his fiancée Justine is standing right next to him. a new millionaire with a new supercar. and this is what he's worried about: "my fear is that we become spoiled brats. that we lose a sense of appreciation and perspective" he knew exactly what the money could buy: "i could go and buy one of the islands in the bahamas and turn it into my personal fiefdom" "i'm much more interested in trying to build and create a new company" and he meant it. he put "the great majority" of his net worth into x.com, an online bank almost nobody believed in his own words: "it's sort of like a series of poker games" "i haven't gone and taken my winnings... i've just put almost all of it back into the new game" x.com became paypal. paypal turned into ~$180M. the $180M went into spacex and tesla. you know the rest and the car? a year later, Peter Thiel in the passenger seat, on the way to pitch Sequoia. Musk floors it. the F1 spins and goes airborne. no insurance. both walk away napkin math: the toy: $1M in 1999. F1s now sell for $20M+. ~20x the chips he pushed back on the table: ~$22M. today: hundreds of billions. four more zeros the island: still just an island the only time he ever cashed out, he bought a car. everything else went back into the game 26 years later the richest man alive sleeps in an airstream. the 27-year-old who was scared of becoming a spoiled brat never let it happen
Turns out the future does have flying cars
70
635
38
4,535
1,063,299
CKB has been crypto-agile by design since its mainnet launch in 2019. On many blockchains, a new signature scheme needs a protocol upgrade, and getting a whole network to agree is slow and contentious. On CKB, signature checks run as lock scripts rather than as part of the protocol, so a post-quantum scheme can be deployed as a new lock with no network-wide vote. One is already live on mainnet and three are on testnet. Each scheme below is measured against secp256k1, the signature scheme used today by Bitcoin and Ethereum, as well as by CKB's “default” lock. On CKB it takes up 65 bytes and about 3.5 million computing cycles to check. 1. SPHINCS+ (live on CKB mainnet, audited) Instead of relying on the arcane mathematical problems behind today's signatures, SPHINCS+ uses layers of cryptographic hashes to show that a transaction was authorized by the rightful owner. Its security depends on the hash function and nothing else. Jan Xie, our Chief Architect, calls it the most conservative option. It is also stateless: the wallet does not have to keep count of how many times it has signed, so a seed phrase restores everything. ⦿ Size: about 120 to 770 times larger than a secp256k1 signature ⦿ Checking: about 3 to 14 times longer ⦿ Space: about 12 to 70 transactions per block, against about 1,000 with secp256k1 ⦿ Standard and audit: NIST's SLH-DSA (FIPS 205); ScaleBit audited the lock in 2025 In plain terms: the most conservative choice on the list. It is standardized, audited and built on hash functions alone, at the price of taking up the most space on the chain. 2. SHRINCS (testnet, unaudited) SHRINCS also relies only on hash functions. It is a design from @Blockstream, and the CKB lock on testnet was written by Jiandong Xu. It is built to be small. In normal use the signatures are very short, but the wallet has to keep count of them, because signing twice with the same count would expose the key. If the count is lost, or the wallet would rather not rely on it, it can use a larger signature that works from the seed phrase alone. ⦿ Size: about 5 times larger (324 bytes at the start, growing slightly with each signature), or about 40 times larger on the fallback ⦿ Checking: about 3 times longer at the start, or about 5.5 times on the fallback ⦿ Space: about 370 transactions per block with a fresh counter, against about 1,000 with secp256k1 ⦿ Maturity: a young design, with no independent audit or security proof so far In plain terms: SHRINCS signatures have the smallest footprint of the four at first, but the wallet has to keep careful count, and the design is young and unproven. 3. ML-DSA (testnet, unaudited) ML-DSA is NIST's main general-purpose standard (FIPS 204). It rests on a different kind of mathematical problem, called a lattice problem, which is newer than hash functions. Like SPHINCS+, it needs no counter. The CKB locks were written by community developer toastmanAu. ⦿ Size: about 57 to 81 times larger at its two smaller settings ⦿ Checking: about 1 to 2 times longer ⦿ Space: about 100 to 140 transactions per block, against about 1,000 with secp256k1 ⦿ Standard: final (NIST, 2024) In plain terms: the standard all-rounder. It is reasonably quick to check, but bigger than today's signatures and built on a newer mathematical assumption than the hash-based options. 4. Falcon (testnet, unaudited) Falcon is also lattice-based, and NIST is standardizing it. It produces the smallest signatures of the lattice schemes. Its weak spot is signing, which is complex to implement. Checking a signature, the part the chain does, is simple. The CKB locks are also by toastmanAu. ⦿ Size: about 24 times larger for Falcon-512 ⦿ Checking: about a third of secp256k1's cost, the cheapest of the four ⦿ Space: about 280 transactions per block, against about 1,000 with secp256k1 ⦿ Standard: still a draft (NIST's FN-DSA, FIPS 206) In plain terms: the quickest to check, and small for a lattice scheme, but harder to implement on the signing side. So is there a best one? No. Each wins on one measure and pays for it on another: ⦿ SHRINCS: the smallest signatures at first, provided the wallet keeps its count ⦿ Falcon: the cheapest to check, though signing is hard to implement ⦿ ML-DSA: the most established standard and the simplest to build, but bigger than today's signatures ⦿ SPHINCS+: the most conservative foundation, paid for in space Which matters most depends on what a chain is protecting and what it can afford: block space, checking cost, how much it trusts newer mathematics, and how much it can ask wallets to look after. On October 7, @VitalikButerin said hash-based signatures beat lattice-based ones wherever hash-based is possible at all. Ethereum's roadmap already excludes ML-DSA and Falcon. SPHINCS+ and SHRINCS are hash-based; ML-DSA and Falcon are lattice-based. No break of any of the four has been shown. CKB does not have to choose. Each scheme is a lock script, so anyone can deploy one without a network-wide vote, and each user decides which to trust. If research or a standard points somewhere new, a new lock can join them the same way.
2
23
3
74
1,813
Code3ks retweeted
BREAKING: Today, we just watched the future of agents. Introducing Superintelligence Startups A teenager can now reach +$4M/month by giving Claude full access to his Mac. 12 months ago this was straight out of a scifi horror movie. This is too much.
96
82
19
562
133,684
Code3ks retweeted
THE DIFFERENCE??😭
3,350
31,026
3,328
310,086
7,847,676
Code3ks retweeted
Two quantum-safe chains both under $100M, split 4-4 👇 ⚪ Post-quantum on mainnet since → $QRL : June 2018 → $CKB : January 2026 ⚪ Protected by default → QRL : every user → CKB : opt-in only ⚪ Fixed supply cap → QRL : 105M → CKB : none ⚪ Price as % of ATH → QRL : 29.5% → CKB : 3.74% ⚪ Key reuse safe → CKB : yes, stateless SPHINCS+ → QRL : no, stateful XMSS ⚪ PQ contracts on mainnet → CKB : opt-in → QRL : testnet only ⚪ CertiK Skynet → CKB : 86.40 → QRL : 78.83 ⚪ Volume as % of mcap → CKB : 19.8% → QRL : 0.20% QRL got there first and kept its value. CKB got there late and kept its traders.
20
32
5
152
9,294
While Fiber and Lightning are two separate payment channel networks, we figured there doesn’t need to be a hard boundary between them. Fiber’s Cross-Chain Hub can connect the two and let payments move atomically across both networks. Here’s how it works 👇 A hub operator runs a node on Fiber and a node on Lightning, maintaining liquidity on both sides. If you want to pay a Lightning invoice from Fiber, you send a conditional payment to the hub. The hub then uses its own BTC liquidity to pay the recipient over Lightning. The same process works in reverse for payments coming from Lightning into Fiber. Crucially, these are not two unrelated payments. Both sides are tied to the same payment hash. Lightning uses an HTLC, while Fiber uses its own time-locked contract. When the recipient claims the outgoing payment, they reveal a secret preimage that also allows the hub to claim the incoming payment. So the hub can’t simply take your payment and fail to settle the other side. Its ability to collect is cryptographically linked to successful settlement of the outgoing payment. If the payment never completes, the timelocks provide a recovery path for the locked funds. Currently, the Cross-Chain Hub supports one configured pairing: a wrapped-BTC token on Fiber ↔ BTC on Lightning. Support for native CKB and other user-defined tokens is in the works :) 👉 fiber.world/
1
19
2
65
1,231
CKB Off-Chain Hanoi concluded yesterday, and it was an event that brought together CKBuilders, external developers and students. There was a wealth of information and experiences shared, which shows just how far the CKB developer community in Vietnam has come, and reflects the continuing surge in developer activity on CKB in 2026. Many thanks to our partners at @bps_club and @texlabsorg for helping it come together! Read more here talk.nervos.org/t/ckb-off-ch…
3
25
3
102
2,622
Code3ks retweeted
$CKB : Review 📜 What if the signature scheme Vitalik Buterin spent this week arguing crypto should move toward had already been sitting on another chain for a year? Meet Nervos CKB, a proof-of-work Layer 1 where SPHINCS+ hash-based locks have been live as an option since late 2025. Its RGB++ protocol binds Bitcoin UTXOs without a bridge, and its Fiber payment layer just cleared every milestone on its build. Let's explore the chain that keeps being early. 👇 ⚪ CKB at a Glance Marketplace Insight: CKB occupies an awkward and interesting position. The engineering is genuinely ahead of the market's attention, with a Bitcoin-native asset protocol that needs no bridge, a payment-channel layer doing atomic swaps with Lightning, and post-quantum locks that were deployed before the current debate about them started. The token tells a different story, down 69% on the year and sitting near a market cap most people would class as microcap. The all-time high from March 2021 is now a distant number. What the past month shows is a project shipping steadily on Fiber and tooling while the L1 itself stayed deliberately still. ⚪ Mission Nervos CKB exists to be the layer that stores and verifies, not the layer that executes. The architecture separates concerns on purpose: CKB handles state, security, and settlement through its Cell Model, while computation happens above it. The longer-term bet is that Bitcoin will need an asset and payments layer that does not require trusting a bridge, and that a proof-of-work chain with a generalised UTXO design is the honest way to build one. 🔵 A Brief History Nervos launched its mainnet in November 2019, raising around $72 million across its token sales, with a proof-of-work chain running the Eaglesong hash function and a 25-year primary issuance halving schedule. The Cell Model, a generalisation of Bitcoin's UTXO design capable of holding arbitrary state, was the core architectural claim from the start. The chain spent its early years relatively quiet. The turn came with RGB++, which binds asset issuance and ownership to Bitcoin UTXOs through isomorphic mapping, letting assets settle against Bitcoin without a bridge contract holding custody. That removed the single largest attack surface in cross-chain design, which matters given the project's own history. The security record is where the honest reading gets uncomfortable. Force Bridge, the cross-chain bridge infrastructure, suffered exploits that cost the ecosystem real money, including a $3.9 million incident in June 2025 that drew a warning from DAXA, the South Korean exchange consortium. The response was architectural: RGB++ exists partly because bridges keep failing, and the project moved toward a design that does not need one. CKB Edition Meepo activated on mainnet on 1 July 2025 at epoch 12,293, and remains the current ruleset. Late 2025 brought the quantum-resistant lock work, deploying an optional SPHINCS+ lock script on mainnet. Governance restructured when CKBA, a Swiss Verein, replaced the Foundation as the coordination body, with the chain itself remaining permissionless proof-of-work. The past month has been a Fiber month. Version 0.9.1 landed on 11 September with force-close settlement fixes, on-chain TLC reconciliation using verified settlement snapshots, configurable peer-message rate limits, and improved funding-failure diagnostics. Version 0.10.0-rc1 followed on 25 September with backup-RPC authorization fixes. Fiber Studio filed its completion report with all milestones done and signed builds for all three desktop platforms. Node v0.210.0 shipped 17 September carrying dependency and security updates with no protocol change, alongside CKB-VM v0.24.15 and a transaction-pool architecture review. On the ecosystem side, the Gone in 60ms Fiber infrastructure hackathon returned results, with Fiber Forge taking a category and FiberNuts, a Cashu ecash implementation backed by Fiber RUSD, placing first in another. CKB Off-Chain Aba ran in Abia State, Nigeria on 3 October with sessions on the Cell Model, RGB++, and Fiber, and a Vietnam meetup followed on 8 October. Dular wrapped a Fiber payments pilot with around 30 users in Kenya. Not everything went up. UTXOSwap announced it is shutting down on 10 to 11 October, with liquidity providers told to withdraw before 16:00 UTC on the 10th. CKBA does not operate it and only amplified the notice, but a DEX closing is a real signal about ecosystem depth. 🔵 Ecosystem Narrative The through-line across the past month is Bitcoin-adjacent payments, built out while the base layer stayed still. ➛ The Cell Model. A generalisation of Bitcoin's UTXO design where each cell holds arbitrary data and a lock script, giving the chain programmable state without abandoning the UTXO security model. ➛ RGB++. Asset issuance and ownership bound to Bitcoin UTXOs through isomorphic mapping, with no bridge contract and no wrapped token holding custody between the two chains. ➛ Fiber Network. Payment channels on CKB with atomic swaps into Bitcoin Lightning through the Cross-Chain Hub, shipped 18 August. Multi-tenant hosted LSP for mobile wallets, Loop In and Out, and full payment-hash settlement remain in progress. ➛ SPHINCS+ locks. Optional hash-based post-quantum lock scripts live on mainnet since the late 2025 quantum-resistant lock work, the same signature family now being pushed as the conservative path for Ethereum's lean roadmap. ➛ Mobile and tooling. Pocket Node Android v1.8.4 on Google Play with the iOS build verified on hardware at the M1 stage, Khie merged as a P2P wallet-connect protocol, Omiga v1.2.0 expanding on-chain asset management with CCC wallet integration, and CKB Script Port experimenting with moving synced script state between light clients. ➛ Real-world pilots. Dular's Kenya payments pilot, Blackbox POS adding a receive-only Bitcoin rail where keys never touch the device, and FreightOnNervos and RIVET demoed at the Nigeria event. ⚪ Token Utilities $CKB is the state-rent asset of the network, which is an unusual design. ➛ State storage: holding one CKB entitles you to store one byte of state on chain, making the token a claim on blockspace rather than only a gas asset. ➛ Transaction fees: paid in CKB for computation and state changes. ➛ Nervos DAO: locking CKB earns secondary issuance back, offsetting the dilution that uncapped issuance would otherwise impose on holders. ➛ Mining: proof-of-work issuance through Eaglesong, on a 25-year primary halving schedule. ⚪ Key Features ➛ Proof-of-work Layer 1 with a generalised UTXO architecture through the Cell Model. ➛ RGB++ binds assets to Bitcoin UTXOs with no bridge and no wrapped token. ➛ Fiber brings payment channels with atomic swaps into Bitcoin Lightning. ➛ Optional SPHINCS+ hash-based locks live on mainnet since late 2025. ➛ State rent model where token holdings translate directly into storage rights. ➛ Nervos DAO lets holders neutralise secondary-issuance dilution by locking. 🔵 Meet the Team Nervos runs on a three-person founding bench that has stayed intact since 2018, through the 2019 mainnet launch and the long stretch of low attention that followed. For a project this old, nobody leaving is itself a data point. ▶️ Core Members: ➛ Terry Tai - CEO & Director | Leads the company and sits on the board, having moved from the founding team into the executive seat. He has carried the project through the Foundation-to-CKBA restructure and the post-exploit pivot toward bridgeless architecture. ➛ Kevin Wang - Co-Founder | The most visible outward-facing voice on architecture, particularly on the case for separating storage and verification from execution, which is the thesis the entire Cell Model rests on. ➛ Daniel Lv - Co-Founder | Came out of the Ethereum ecosystem engineering side and has focused on the protocol and VM layer, the part of the stack that produced CKB-VM and the Cell Model implementation. ➛ CKBA (Common Knowledge Base Association) | The Swiss Verein that replaced the Foundation as the coordination body, which closed membership applications on 15 September with five applications queued for the General Assembly. It does not control the chain, which stays permissionless proof-of-work. ➛ Nervos DAO and Community Fund DAO | Ecosystem funding and governance, with a community dashboard launched in late September, FiberLatch Access completed and paid, and Vellum passed in the recent cycle. 🔵 Ratings ➛ Use Case: ★★★★ (4/5). CKB is solving a problem that keeps proving itself real. Bridges fail repeatedly, and RGB++ binds assets to Bitcoin UTXOs without one, which is a structurally better answer than most of the industry has. The Cell Model is a serious architectural idea, Fiber extends it into payment channels with working atomic swaps into Lightning, and the SPHINCS+ locks mean the post-quantum conversation reaching Ethereum this week is one CKB already acted on. The 1-point deduction is adoption. The pilots are small, with roughly 30 users in the Kenya test, UTXOSwap is closing this week, and a market cap near $62M after seven years on mainnet reflects a chain whose engineering has consistently outrun its usage. ➛ Tokenomics: ★★★⯪ (3.5/5). The state rent design is genuinely original, tying token holdings to storage rights so that demand for blockspace translates into demand for CKB rather than only into fee burn. The Nervos DAO gives holders a mechanism to lock and recapture secondary issuance, neutralising dilution for anyone willing to commit, and primary issuance follows a predictable 25-year halving schedule. The 1.5-point deduction is that issuance is uncapped, with roughly 49.7 billion CKB circulating and the dilution offset available only to holders who actively lock. The token is down about 69% year on year and hit an all-time low in August, which is a long way from the March 2021 high and indicates the state rent demand loop has not yet reached the scale the design assumes. ➛ Audits: ★★★★ (4/5). Nervos holds a verified CertiK Skynet Score of 85.77, grade A, with eight passed security checks against a single informational flag and zero warnings or alerts. The architecture adds genuine weight on its own: proof-of-work consensus, a UTXO-derived model carrying narrower state assumptions than account-based chains, optional SPHINCS+ post-quantum locks live on mainnet since late 2025, and an RGB++ design that removes bridge custody entirely rather than attempting to secure it. Node and light-client security hardening shipped in the September cycle alongside CKB-VM v0.24.15 and a transaction-pool architecture review. The 1-point deduction is the exploit record and the scope of the rating. Force Bridge suffered multiple incidents including a $3.9 million exploit in June 2025 that prompted a DAXA warning, and the Skynet listing carries a partial rating badge with governance left unscored, so the A grade rests on fewer completed dimensions than a full panel. ➛ Community: ★★★★ (4/5). The community is small but unusually durable, having stayed through a 69% annual drawdown and years of limited attention. The activity is real rather than performative: the Gone in 60ms hackathon produced working infrastructure including FiberNuts and Fiber Forge, Off-Chain events ran in Nigeria on 3 October and Vietnam on 8 October with technical sessions rather than marketing, the Build on CKB campaign closed with 20 participants, and a Dev Rel AMA ran on 28 September with the CCC maintainer. Governance is participatory through the Community Fund DAO with a public dashboard. The 1-point deduction is scale and attrition, with twenty-participant campaigns and thirty-user pilots pointing to a committed core rather than a growing base, and UTXOSwap closing this week shows the ecosystem losing pieces as well as adding them. 🔵 Conclusion CKB is a chain that keeps arriving early and waiting. The Cell Model predated the current interest in UTXO-based programmability, RGB++ solved bridgeless Bitcoin assets before the latest round of bridge failures, and the optional SPHINCS+ locks went live on mainnet roughly a year before the Ethereum research community started arguing publicly for hash-based signatures. The engineering has been consistent and the past month shows it continuing, with Fiber reaching release-candidate stage, Fiber Studio completing every milestone with signed builds, and mobile tooling progressing on both Android and iOS. The gap is everything downstream of the engineering. A $62M market cap after seven years on mainnet, an all-time low set in August, pilots measured in dozens of users, campaigns closing with twenty participants, and a DEX shutting down this week all describe a project whose technical output has not converted into usage or value. The Force Bridge exploit history sits on the record, and the Skynet rating that offsets it is still only partial. What makes it worth watching is the specificity of the bet. If Bitcoin needs an asset layer that does not require trusting a bridge, and if the post-quantum conversation now reaching Ethereum pushes chains toward hash-based signatures, CKB has already built both. Being right early only counts if the market eventually arrives, and that is the thing CKB has been waiting on for seven years.
11
51
4
140
9,080
My closest spider shot, rate it?
2
54
Code3ks retweeted
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.
1
12
45
747
Recommend more news like these, for the sake of the people, our industry (and your business). Jokes aside, crypto-agility is becoming one of the hottest engineering topics of this cycle. Good to see Eli, @VitalikButerin, and others pushing this lately. ⦿ Cryptography ages; every algorithm has a shelf-life ⦿ Quantum is the first threat on the list, and there will be others ⦿ Chains that can swap out their cryptography without rebuilding everything underneath will come out ahead We've been talking about this for ages, and we're glad to see the industry catching on. CKB was built with crypto-agility in mind from day one. Protocol-level account abstraction with no signature schemes baked into consensus. And the consensus layer is already quantum-safe because it's hash-based Proof-of-Work 😉 A NIST-standardised hash-based lock (SPHINCS+) is already running on mainnet. ML-DSA, Falcon, and @Blockstream's SHRINCS on testnet. But the most important part is: the community can add any post-quantum option at the application layer, at any time, without waiting for protocol upgrades. This is the future.
One of the most important features a blockchain needs to have: Crypto agility. Crypto agility means your chain can upgrade when needed, and it can do so without tearing down its foundations or requiring users to go through a difficult and lengthy journey for that. Chains will need crypto agility to migrate to quantum-safety, they will need it to upgrade because of AI threats, and they'll need it for the threats we'll need only a few years from now. This is becoming increasingly important.
9
41
738