Fhenix is live on Ethereum and Arbitrum mainnet.
We're glad to have supported this launch with a security audit of their contracts. Dual-mode confidential tokens are now available.
Congratulations to the @fhenix team on reaching this milestone. Onchain security is shared work.
Full audit report ⬇️
We're glad to have supported @fhenix on the way to mainnet.
This article is the product of the audit work. It covers how FHE contracts work, the mental model needed to review code where standard smart contract assumptions no longer hold, and how to handle operations in an encrypted environment.
Consensys Diligence retweeted
📣 A new patch of updates have landed across SEAL Frameworks!
All of these are community contributions because that's what keeps the Frameworks current and worth using.
Want to contribute? h/u @mattaereal
frameworks.securityalliance.…
Check out all the updates in the thread below.
Consensys Diligence retweeted
Bug bounty industry in Web3 is fully broken; unverified AI slop is making companies leave the platforms that don't verify submissions correctly.
Hopefully these companies will establish their own bug bounties. Feel free to reach out to if you need help with verification
No practical attack on ECDSA is known today. Long-lived privileged keys are still a weak assumption, but teams can start fixing that now through operations.
The discussion on quantum and AI-assisted cryptanalysis has an interesting operational implication for EVM protocols, particularly security councils, treasury multisigs, deployment addresses, and other privileged accounts. Many of them depend on a few long-lived keys whose public keys became public with their first signature, including off-chain ones such as EIP-712 messages and multisig confirmations.
Whatever the timeline, teams don't have to wait for new cryptography, they can start with a map of every privileged role.
EOAs cannot rotate, so the next step is moving that authority into contract accounts. From there, existing tools already support short-lived signers, frequent key rotation (even once per transaction for hot, high-value wallets, retiring each signer in the transaction that reveals its key), limited privileges, less activity per key, stronger separation of duties, and authorization layers that fail independently, such as timelocks with active monitoring. Contract accounts can also add their own verification on top of ECDSA.
Rotating keys also means safely transferring privileges, revoking old ones, and ensuring operational continuity without introducing new attack vectors.
Traditional enterprise security has decades of experience with credential rotation, least privilege, and defense in depth. These principles transfer to onchain operations. The remaining work is to make them part of every security process. The main difference is that onchain there is no recovery path outside the contract’s own permissions. Once an attacker controls the keys at the top, nothing above them can revoke access, so rotation matters most before that point.
This is a substantial engineering and operational challenge. Every rotation is itself a privileged transaction. Signers in different time zones must coordinate. New keys need secure generation and storage. New addresses need verification. Owner changes must stay distinguishable from a takeover. One mistake can break the threshold or lock the team out, so recovery paths need to be in place before the first rotation. The right process depends on how each organization operates.
Still, the cost of these frictions is lower than the cost of long-lived exposed keys.
Onchain keys are also only part of the exposure. SSH keys, TLS certificates, and cloud and CI signing keys rely on the same kinds of public-key cryptography.
In the near term, AI-assisted research may also find ordinary bugs in wallets and signing libraries sooner than it changes the mathematics, which is one more reason to keep privileged keys away from everyday web use.
The current discussion gives the industry a good reason to improve key management, moving it from emergency response to routine practice. Regular rotation also limits damage from leaked keys and compromised devices today, and complements post-quantum cryptography, which remains the long-term 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.
Our @sick_nerdballer at DSS in Mumbai on Certiflai: how to orchestrate swarms of agents for security certifications.
November 1-2
@EFDevcon week
📍Courtyard by Marriott
George Kobakhidze · DSS 2026
“Certiflai: orchestrating swarms for certifications”
Explore the talk and add it to your agenda:
defisecuritysummit.org/2026/…
Tickets: luma.com/9qtxqqxx
Consensys Diligence retweeted
This was quite an educational journey in applying AI for something practical and seemingly bounded.
Come and discuss!
George Kobakhidze · DSS 2026
“Certiflai: orchestrating swarms for certifications”
Explore the talk and add it to your agenda:
defisecuritysummit.org/2026/…
Tickets: luma.com/9qtxqqxx
AI security: attackers and auditors now use the same models. The difference is the judgment and process around them.
Davit at DSS in Mumbai, November 1-2.
@EFDevcon week.
On the DSS 2026 agenda: Davit Kobakhidze
“Sword vs. Shield: Navigating the AI Security Chaos in 2027”
Explore the talk and add it to My agenda:
defisecuritysummit.org/2026/…
Tickets: luma.com/9qtxqqxx
Live now 👇
How to Launch a Mainnet Safely in 2026: Fhenix Audit Breakdown xitter.cf/i/broadcasts/1qJVmyPAE…
We'll be live soon with @fhenix, tune in at 3 PM UTC.
A breakdown of Fhenix's FHE system and its security model, ahead of mainnet 🤝
shipping a mainnet in 2026 means one thing first: security
we're opening up the fhenix audit with @ConsensysAudits and @jack_gk
set your reminders for all the tea
The Fhenix audit, explained live tomorrow with our auditors and their team.
A technical walkthrough of what makes confidential contracts different, how the CoFHE model works, and what "mainnet-ready" means for an FHE system beyond passing an audit.
🔊 Tune in at 3 PM UTC
shipping a mainnet in 2026 means one thing first: security
we're opening up the fhenix audit with @ConsensysAudits and @jack_gk
set your reminders for all the tea
DeFi Security Summit, @EFDevcon week: two talks from our team on protocol security and AI verification.
@DavitBuilderD (Business Development): "Sword vs. Shield: Navigating the AI Security Chaos in 2027"
@sick_nerdballer (Security Researcher): "Certiflai: Orchestrating Swarms for Certifications"
If you're in Mumbai, talk to us after the sessions.
🗓️ November 1–2
📍 Courtyard by Marriott Mumbai International Airport
Full agenda from @summit_defi: defisecuritysummit.org/2026/…
Planning your Mumbai security week?
DSS 2026 runs Nov 1–2, 10am–6pm IST, at Courtyard by Marriott Mumbai International Airport. DSS at Devcon on Nov 3 has separate admission.
@EFDevcon
Agenda: defisecuritysummit.org/2026/…
Tickets: luma.com/9qtxqqxx
Consensys Diligence is at @token2049 Singapore.
We're meeting protocols and institutions to talk about security and privacy for onchain products.
If you're at Marina Bay Sands today, our DMs are open.
How does an AI security agent turn thousands of raw claims into a short list of real bugs?
@kotyasec explains the verification method and the role of local models.
Assumption → Independent review → Attempt to disprove → More evidence → Severity
Where precision and recall meet: each output enters the pipeline as intel and becomes a finding once every step validates it.
Read the full article 🔽
Security is a priority for the whole ecosystem.
Our team will be in Mumbai. See you there 🇮🇳
Consensys Diligence joins the AvengerDAO Security Marketplace as @BNBCHAIN ecosystem partner.
To keep teams safer, we offer comprehensive security reviews, risk assessments, bug hunting through Vulnerability Mining, ZK fuzzing, and formal verification.
👉 avengerdao.org/marketplace
More security support, less friction for builders.
6 new security firms just joined the AvengerDAO Security Marketplace, bringing the total to 17:
→ @QuillAudits_AI
→ @cyfrin
→ @asymmetric_re
→ @MixBytes
→ @ConsensysAudits
→ @PashovAuditGrp
From development to launch and beyond, builders can compare services, contact firms directly, or ask the AvengerDAO admin team where to start.
Explore the marketplace 👇
avengerdao.org/marketplace
We're in town for @Ethereum_JP ETHTokyo week and at @ETHGlobal Pragma Tokyo on Saturday 🇯🇵
With AI in the review loop, security tooling is evolving rapidly. If you're around and want to talk about the latest developments, reach out via DMs.




















