Math/CS substack https://xitter.cf/t.co/EQpUjKs3mk tg blog: https://xitter.cf/t.co/p0oMX1YsrO

Joined March 2010
ETH is (maybe) false. Silicon Valley turned out to be almost prophetic: while optimizing data compression, its AI discovers a polynomial-time algorithm for discrete logarithms and starts cracking TLS encryption. youtube.com/watch?v=v4zFwXwb…
53
Mike Voronov retweeted
After OpenAI's math drop a few days ago, I posted soon after, doubting the veracity of all of the included claims. We need people who actually know what they're doing (mathematicians) to verify results. We can't just blindly trust AI (yet). The responses I got to this POV were pretty crazy. It seems as soon as AI touches a field, people's critical thinking skills turn off. Some responses: "it's formalized in lean", "it can't be wrong", "cope", etc. Well, OpenAI just outright withdrew three of their released papers and released many, many corrections to others. And this is only a few days later! Once people actually have some time to go through this, I bet the number gets much higher. Sad that critical thinking skills are coming harder to come by just as we most need them. BTW, I have nothing against OpenAI, they employ many mathematicians on their team to do this work, and props to them for being forthcoming and honest about corrections. github.com/openai/math/blob/…
Why do people act like mathematicians aren’t the happiest people on earth right now? Who’s going to check that all this stuff is right? Some random 20-something software engineer at a big lab who didn’t know what a field was until yesterday? Gimme a break.
9
4
1
35
2,393
Mike Voronov 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.
5,960
6,242
2,292
25,550
6,660,938
🔐 Session Feature: Modern Custody & DVM–MPC Architecture "Key storage does not equal signature control." Join Mike @VMS11 Voronov (Co-Founder, ClusterLodge) at Blockchain Community Day 2026 to dismantle traditional assumptions about HSMs and enclaves. Core focus: ▪️ Locating the real trust boundaries across control, identity, and runtime planes. ▪️ Implementing a dual-circuit DVM–MPC model to completely isolate execution from key material. ▪️ Crypto-agility: Preparing institutional custody platforms for the post-quantum (PQC) migration. 📅 June 8–12, 2026 | 🌍 Online 🔗 Claim your free spot: luma.com/wupxaqku
3
1
4
474
From my pov, no one should really use the GG/CGGMP family of protocols - they are too hard to implement correctly. The DKLS family is a way better and cryptographically simpler.
This morning, THORChain was drained of roughly $10.8m Node operators have freezed the network for nearly 13 hours. The full analysis isn't out yet, but according to @jpthor, this could be a MPC exploit. ECDSA and TSS is hard. THORChain's vaults rely on TSS, a flavor of MPC where a quorum of nodes jointly produces a signature without ever reconstructing the private key. Clean for Schnorr or EdDSA; painful for ECDSA, which Bitcoin and Ethereum require. That's why we saw plenty of protocol attempts (Lindell17, GG18, GG20, CMP, CGGMP21, DKLS, KU23...), each patching flaws in the previous one. GG20 has a track record. THORChain's TSS uses GG20, on a fork of Binance's tss-lib. GG20 has shipped two well-publicized critical bugs: CVE-2023-33241 and TSSHOCK. CGGMP21, now cggmp24, are the latest protocols, but GG20 is still widely deployed. I often hear a misconception when I hear about MPC setup: "The key is split across many nodes, so any single co-signer doesn't really matter". In every published GG18/GG20 attack, one malicious or compromised co-signer is enough to extract everyone else's shard and reconstruct the full key. AI changes the threat model. Compromising a full software node, complex Go stack, exposed P2P, custom signing daemons, a churn protocol that admits new participants on a schedule, has always been difficult and acted as a barrier. With LLM-driven vulnerability discovery and exploit synthesis, the bar to compromise one of N validators is dropping fast. Here, it's a plausible TSSHOCK-style playbook: - compromise one operator - wait for it to churn into an active Asgard vault - send malformed proofs during keygen or signing - reconstruct the key offline - sweep in a single transaction It's unclear yet if the attacker used a known-unpatched GG20 weakness, or a fresh cryptographic flaw. But, in all cases, MPC and TSS are not a substitute for hardening every co-signer. They sit on top of co-signers that must each be treated as critical infrastructure, hardware-isolated enclaves, minimally exposed, continuously audited, and running protocol with security proofs. While the investigation progresses, be careful in your interactions onchain. These TSS setup are used in various protocols.
145
Mike Voronov retweeted
All the best programmers I know are starting to write code by hand again
642
327
233
6,524
1,488,312
Mike Voronov retweeted
The Kelp DAO situation highlights a critical design challenge in institutional DeFi: complex cross-protocol assets back $280M in loans, how much data visibility is enough? It's a question all of us building in this space need to answer.
4
7
1
9
1,135
Fear sells best as usual
Anthropic CEO Dario Amodei: “50% of all tech jobs, entry-level lawyers, consultants, and finance professionals will be completely wiped out within 1–5 years.”
170
Mike Voronov retweeted
Divisible UTXO swaps enable real L1 peer-to-peer order books. No matching engine. Just Bitcoin Script. Multisig protects treasuries with m-of-n approval. Public keys stay hidden until the spend. Multi-party sign-off on every mint and burn. Configurable at issuer-level compliance with a designated authority now able execute regulatory orders directly on-chain. No off-chain detours. No issuers, miners, or foundations/associations in the loop. On-chain script-enforced - no intermediaries. STAS 3.0 script template makes this real 👇 medium.com/@Stas33496115/bit…
3
17
3
73
6,233
I vibe code every day. I have a team of 30+ engineers. We spend F tons of credits. And I will tell you this about AI from my experience. It’s being wildly over hyped. Everyone is drunk. Fucking drunk. All the CEOs and Gen Z’s saying coding is dead are idiots. IDIOTS.
701
348
67
6,907
493,035
Mike Voronov retweeted
1) Hello World 🌍 Meet Diffuse Prime - the Uncustodial Prime Broker. 👉 app.prime.diffuse.fi A new DeFi primitive designed for capital efficiency, verified risk, and transparent yield.
5
12
3
44
3,614
Why do tech giants build everything in-house? It's not NIH syndrome. It's Ontological Gravity - the most underrated force in system architecture. A thread 🧵
1
184
A simple test for your system: Where do your base entities live - in your domain contracts or in a vendor's ontology? If the answer is "vendor" - that's not a library choice. That's a system architecture dependency.
1
112
Distributed infrastructure does not guarantee independence. Independence is determined by who owns the vocabulary your system thinks in. Choose your gravity deliberately. Or it will choose you.
89