Blockchain security will always be a battle
The Cellframe advantage is that our code is built from scratch (native post quantum) without the crazy bloat that makes older systems vulnerable
To defend blockchain we need a tactical retreat to the safety of the Cellframe ecosystem!
soon, you will find out that *all software* handling funds is prone to AI finding vulnerabilities. all of it
that's why you also saw tons of defi exploits already this year
open source, L1, L2, DeFi, mutable, immutable, private, transparent, cross-chain. if it's software, it is at risk. in fact, it has always been at risk, but now AI changes the math.
so what does one do about this? is the idea of crypto over?
in theory, the main difference for privacy contracts vs regular contracts is detectability
in practice, we've seen countless times in defi where the hackers got away fast even after detection (happened at least 7 times this year that I can count)
it is not an accident that you've seen so many in recent times
the safest way against this is self-custodying the native asset itself on the native chain. because even in the worst case, the validators could roll it back if the exploit is large and core enough. so there is some lower bound there
but as vitalik, toly, and many others have pointed out, the main improvement to defend against this going forward will be formal verification
this is a rigorous, mathematically-based method to formally prove that software behaves exactly as intended
this is also why open source will be critical. because you will have countless others also trying to help you collectively improve security (for rewards) whereas with closed source the math is fundamentally skewed because only the core team can defend
the next zcash upgrade, some defi protocols, and some chains are already in the process of doing this, aggressively
the result will be that crypto emerges stronger than ever before and in fact safer than centralized counterparts. there will be no stopping crypto.
Exciting look into the fallout of Google's splash quantum/cryptography paper
tl/dr: Their attempt to keep their methods secret backfired monstrously, and classical cryptography is f***ed
Time to go post-quantum
CELLFRAME
Today a crazy quantum story just got wilder.
On March 31, the Google Quantum AI team published a landmark result on Shor's algorithm for elliptic curve cryptography. Technically, the paper was a bombshell: a dramatic 10x improvement over the state-of-the-art. As a stunt and wakeup call to the blockchain space, those optimisations were illustrated on secp256k1, the elliptic curve underlying Bitcoin and Ethereum signatures.
But perhaps the most striking part of the paper was sociological, not technical. Instead of following standard academic process, the optimisations were kept secret, hidden behind a zero-knowledge (ZK) proof. Google's accompanying blog post mentions they "engaged with the U.S. government". The ZK proof demonstrates the existence of algorithmic improvements without leaking details. Academic censorship with ZK, a historic first!
As a co-author of the Google paper I witnessed some of the context surrounding this censorship. To be honest, multiple aspects of that context don't sit well with me. As much as I believe the general public ought to know more, I am limited in my ability to whistleblow. Though let me be clear about one thing: the Google team's professionalism has been absolutely exemplary, and they deserve nothing but praise.
Censorship has a way of backfiring. The Streisand effect, where an attempt to bury something only draws more attention to it, is exactly what's unfolding today. First, Google's key optimisation has been rediscovered by the French. And in a thrilling turn of events, a collaborative Shor-at-home challenge just launched. The initiative, available at ecdsa[.]fail, breached a new Shor world record in a matter of hours.
Let's start with the rediscovery. Just two months after Google's paper, French quantum expert André Schrottenloher cracks the main secret optimisation. His paper, titled "Optimized Point Addition Circuits for Elliptic Curve Discrete Logarithms", landed on the arXiv today. Big congrats to André, who beat several other nerdsnipped experts to it. In a blog post also published today, Craig Gidney, the world expert on Shor optimisations, revealed that he'd been sitting on this very optimisation for a whole year under censorship pressure.
Interestingly, André missed a handful of minor optimisations, both from Google's original publication and from improvements found since. It's plausible there's still plenty of juice left to squeeze out of Shor, and this is exactly what the ecdsa[.]fail challenge is about. The verifier program developed for the ZK proof does double duty, automatically filtering for valid submissions. Dozens of compounding small and micro improvements are rolling in. As of the time of writing there's an 8.4% improvement to Google's circuit, as measured by the product of logical qubit count and Toffoli gate count. Nice!
The nerdsnipping ran deeper than anyone expected. Over the last few weeks it became clear it extended well beyond André and other quantum experts. Behind the scenes, a small army of amateurs quietly got to work. Inspired by Karpathy-style autoresearch, they turned AI on Shor. Ironically, the verifier program for the ZK proof makes an ideal reward function for AIs. The barrier to entry for this modern style of research is refreshingly low, with several non-experts, even a teenager, finding nice optimisations. Get in touch if you'd like to join a Telegram group with fellow autoresearchers :)
Part 2: neutral atoms and qday
The story doesn't end with Google. On the same day Google went public, a stealthy startup called Oratomic published its own Shor paper in a coordinated release. It made a splash, ultimately becoming the most upvoted paper on scirate[.]com, a website ranking arXiv papers.
Oratomic's claim was wild. By building on Google's logical optimisations and applying custom physical optimisations for neutral atoms, they claimed just 10K physical qubits were sufficient to run Shor's algorithm on secp256k1. That number is mind-bogglingly low.
Knowing essentially nothing about neutral atoms when Oratomic's paper landed, I was intrigued and decided to learn more about the tech. I fell straight down the rabbit hole and spent a couple hundred hours on the topic. I got a little obsessed and watched every YouTube video I could find and spoke to a bunch of experts.
My conclusion? The tech is real, very real. Even Google recently decided to start a neutral atom lab, a notable pivot from their sole focus on superconducting qubits. If you care about qday, i.e. the day a quantum computer will break the first piece of cryptography in production, neutral atoms demand your attention. I shared some of my learnings on Shor and neutral atoms in a 30min talk at the ZKProof cryptography conference. You can find it on YouTube by searching "zkproof neutral atom".
Here's an interesting observation about this duo of breakthrough papers: neither Google nor Oratomic say a word about what their results mean for qday. No timelines. Zero. Nada. That is especially baffling given that the whole point of whitehat quantum cryptanalysis is to inform qday estimations and help the general public make good decisions.
So let me attempt to partially fill the silence, similarly to what Scott Aaronson did in his April 29 post. Given everything I know, including scary non-public information, I now put the odds of qday by 2032 at 50%. 10% by 2030.
Anecdotally, the US government has its own date: 2035. Originating at the NSA and later adopted by NIST, it's when branches of the US government will be disallowed from using quantum-vulnerable cryptography. In plain language: with hindsight, that date is a joke and should be discounted entirely. I don't see how NIST avoids being forced to pull it forward by years.
Part 3: post-quantum cryptography
There are good reasons to sound the alarm today, but please do not panic. Rushing carelessly towards immature post-quantum cryptography is a recipe for disaster. IMO a good target date for migration is 2029, roughly 3.5 years out. 2029 happens to be the date selected by Google, Cloudflare, and the Ethereum Foundation.
These days most of my time goes to safely migrating Ethereum towards post-quantum cryptography as part of the broader lean Ethereum effort. There's a lot to do. We need to rip out and replace BLS signatures at the consensus layer, KZG commitments at the data layer, and ECDSA signatures at the execution layer.
The plan to get there is compelling, and is based on hash-based cryptography. Within the Ethereum Foundation we've developed a Swiss army knife called leanVM (github[.]com/leanEthereum/leanVM) powered by the magic of hash-based SNARKs. Thanks to truly exceptional work by Emile, Thomas, and others, its performance is derisked. Regarding security, leanVM is a jewel, a minimal zkVM crafted for end-to-end formal verification and maximum security.
Want to help? There are two $1M initiatives. First, the Proximity Prize (proximityprize[.]org). Solve a long-standing mathematical conjecture in coding theory, improve hash-based SNARKs, and go home a millionaire. Second, the Poseidon Initiative (poseidon-initiative[.]info), offers $1M for breaking Poseidon, the SNARK-friendly hash function.
While everyone argues about narratives, $CELL is becoming infrastructure. Quietly. Product by product. Fee by fee.
DEX, live. Web version is close. The rest is in today's AMA.
You should probably watch it. @cellframenet
Traditional VPNs = centralized risk❌
Built on @cellframenet, @KelVPN delivers a decentralized, censorship-resistant, and quantum-resistant future for online privacy.🛡️
This is what the real #DePIN utility looks like in the #Web3 era.🚀
#Cellframe#KelVPN#Privacy
The Trump administration just committed $2 billion to quantum computing
How they're distributing the money:
• $IBM: $1 billion
• $GFS: $375 million
• $QBTS, $RGTI, and Infleqtion: ~$100 million each
• Diraq: $38 million
• And 3 private companies Atom Computing, PsiQuantum, Quantinuum
In return, the government is taking equity stakes in every company
Amazing to see @cz_binance company post that they are just *now* in 2026 discovering the basic factors of post-quantum blockchain (that the PQ signatures require much more data) when we have been working on this for nearly a *decade* @BNBChainDevs
The text version of the AMA session from May 7 with Dmitry Gerasimov — CEO of Demlabs and project lead of Cellframe — is now available!
Key takeaways from the AMA:
- Current status of the investigation into the illegal m-token situation
- Infrastructure updates and enhancements following the Cellframe bridge hack
- Project tokenomics and team funding questions
- Order book synchronization and launch of the web version of Cellframe DEX
- Operating principles and development plans for the bitcoin quantum hedge — cBTC
- Expansion of the Cellframe ecosystem and launch of new services
Read the text version in the blog on the project's website: https://t.co/fDHv74B4MO
Uniswap and other DEXs are actually not very decentralized, since they depend on smart contracts
Cellframe solves this with a new generation of P2P architecture
One of the most overlooked risks in crypto is infrastructure dependency.
Most users think decentralization only means custody.
But real decentralization also means:
• communication layers
• networking layers
• execution layers
• security layers
If critical infrastructure remains centralized underneath, the ecosystem still inherits centralized points of failure.
That’s part of what makes @cellframenet interesting.
The ecosystem is not only focused on blockchain architecture, but also on surrounding infrastructure like decentralized networking and post-quantum security.
The next evolution of Web3 may not be about adding more chains.
It may be about reducing hidden dependencies.
#Cellframe #QuantumSafe