Perseverance retweeted
Announcing a major milestone achieved by my team @GoogleDeepMind: we have proven key security properties of the machine code underlying the Signal messaging protocol. This is the first time the actual production code of a widely deployed protocol has been formally verified – by any method, with or without AI – and at this depth.
More than a research breakthrough, it’s a prime example of how frontier AI can be a force multiplier to counter the speed and scale of modern cyber threats.
Formal verification offers a higher standard of security; however, it’s extremely complex and time consuming, which is why in many cases it’s considered to be impractical. Similar efforts could take teams decades of combined effort. We did it in a month’s time.
Using AlphaProof Code, Google DeepMind's new agentic framework for formal verification that runs on LLMs including Gemini Carbon, we verified the Signal protocol down to the actual code running on devices. This milestone lays the groundwork for a future in which vital systems, from medical device firmware to power grid software, ship with mathematical proof that their protections work.
Reaching that future will take continued research from our community. In that spirit, we're open-sourcing our formal specifications and verification artifacts so others can build on this work.
On a personal note, this moment is of deep significance to me. I started my own research journey more than two decades ago as an intern working on checking the consistency of complex software systems. Seeing this grand challenge made practical with modern AI is extraordinary.
I'm extremely proud of my team members: Swarat Chaudhuri, Andrew Ferraiuolo, Anton Kovsharov, Tej Chajed, Sam Schlesinger, Karn Seth, Jonathan Katz, and Charles Sutton for taking on this grand challenge and delivering, and grateful to the Signal team for their partnership.
deepmind.google/blog/formal-…
Perseverance retweeted
We've come a long way in a short time for formal verification—one of our strongest tools for putting the S in CROPS—to become a new normal. Here, verity formally verified EIP-8282 and in doing so found real discrepancies for researchers to address.
Thanks for the work @Veritylab
We formally verified EIP-8282 for the @ethereumfndn.
Proved directly on the bytecode, checked by Lean.
veritylabs.dev/our-work/eip-…
Perseverance retweeted
we have tools for FORMAL VERIFICATION
we have decades of experience in FORMAL VERIFICATION
we have PhDs in FORMAL METHODS
we have top notch security researchers who know how to find bugs and PROVE what matters
we are @Certora
Kudos to the @Certora team for the great research and responsible disclosure! The write-up is such an interesting read. It’s an honor to collaborate with such talented security researchers. Thanks @tpiliposian for sharing the behind-the-scenes story!
our team found this nice bug during one of our zero knowledge audits. a very interesting read, and quite a story.
we reported it to Consensys, they confirmed the issue, and we started identifying downstream projects. happy to see everything handled so well.
special kudos to the @Consensys team for their quick responses and responsiveness, and huge thanks to @_SEAL_Org for the super quick response, and to @pcaversaccio for the great advice on how to proceed given the situation
certora.com/blog/take-no-hin…
During my vacation days, I hunted on a big Blockchain project with huge Rust codebase. I found a Medium bug which confirmed quickly, paid just 2 days after confirmation. Time from submission - paid is about 5 days! Awesome experience 🎉😍! @immunefi Thanks the Project a lot!
😀Happy to share an interesting Critical finding that I found in @AftermathFi audit (Sui) with @Certora . This wasn’t an obvious bug, but came from combining several weaknesses. Always satisfying when bugs got fixed before they can cause real damage. Read 👇
Some of the most interesting smart contract vulnerabilities emerge when individually reasonable behaviors interact in unexpected ways.
That’s what we found during our audit of @AftermathFi Perpetuals, an on-chain perpetual-futures exchange on Sui.
We identified a critical order-book liveness issue, which the Aftermath team proactively addressed with layered mitigations.
Here’s what we found, how they fixed it, and what other protocols can learn from it:
certora.com/blog/sui-order-b…
Perseverance retweeted
very happy to see the performance of our AI Auditor and that it helped you find a unique bug that was missed.
we have been using it internally for a long time, and it has been very useful for us. now everyone has access to use it as well.
thanks so much for the exercise you did and for sharing your feedback @SolidityLab
Perseverance retweeted
And here I am, having reported vulnerabilities throughout my career that could have resulted in a total of several billions (yes, with a B, > $2B) being *stolen*, while my total earnings are around $2M.
So what's the lesson the industry is teaching researchers?
That next time we should steal the funds first, then negotiate a "responsible disclosure," return 80–90%, and walk away with 10–20%?
Obviously, no. But it's insane that the incentives can make that rhetorical question even possible.
The bounty world is broken.
Blackhats exploit a protocol and get treated like kings in negotiations. Meanwhile, whitehats disclose the exact same kind of vulnerability privately, prevent any damage from happening, and then spend months arguing with projects that try to downgrade the finding and pay the bare minimum.
I'm fighting several cases like this right now. Millions of dollars protected, vulnerabilities responsibly disclosed, and yet projects still don't want to pay the amounts they themselves advertised.
We should be making responsible disclosure the overwhelmingly obvious choice.
Instead, the current state of Web3 is doing its absolute best to discourage whitehats while creating increasingly attractive incentives for blackhats and "grayhats".
Those incentives are backwards, and eventually the ecosystem pays the price.
Really enjoyed 🙂 contributing to the security review for @umia_finance alongside the @certora team. Big thanks to Tigran (@tpiliposian) and @p_tsanev for great collaboration. Wishing @umia_finance a successful launch and continued growth! 🎉
really enjoyed working with the team, such a highly professional team and a very cool project.
wishing @umia_finance the best of luck with the launch, and big kudos to @p_tsanev and @PerseveranceSu5 for the great work on the review 🫡
Perseverance retweeted
With Umia’s token launch happening tomorrow, we wanted to give one huge shoutout to all the partners that made the Umia launch a reality behind the scenes.
Starting with the first step every user has to do, we want to thank @privy_io for making the onboarding experience smooth and helping us deliver the account abstraction features we always wanted.
For the Early Bid period, we want to thank @reclaimprotocol and @fairscalexyz for their support, helping us with the necessary infrastructure needed for Umia’s zkTLS proofs.
We are also proud to be building with @Uniswap V4, hooks and CCA. Thank you for your technical assistance during these months to setup Umia's treasury and our Tailored Auctions mechanism.
Finally, a huge shoutout to @Certora for being our technical audit partner, to @MetaLeX_Labs for helping bring forward the Umia CyberCorp, and lastly @ChainstackHQ and @envio_indexer for helping us deliver all the chain data we need to our users.
Let’s keep building the token-first vision, we can’t wait to keep building standing on the shoulders of giants 🫡
Perseverance retweeted
Aftermath Perpetuals V2 is live on mainnet.
15 markets on day one: BTC, ETH, SUI, NVDA, TSLA, GOOGL, gold, silver, WTI crude, the S&P 500, and more. Entirely onchain.
af.lol
Perseverance retweeted
.@AftermathFi has completed a second independent audit with @Certora.
Manual review from @osec_io, formal verification from Certora.
This is the bar we want for teams building on Sui.
.@CertoraInc has completed its security assessment of our Perpetuals V2 contracts.
This is the second independent audit of the protocol, conducted by a completely separate firm from @osec_io.
Full report below.
Honored to have contributed to the @AftermathFi Perpetuals V2 Security Assessment with the @certora team. Kudos to the @AftermathFi team for their strong security mindset and practices. Wishing them continued success! 🎉
.@CertoraInc has completed its security assessment of our Perpetuals V2 contracts.
This is the second independent audit of the protocol, conducted by a completely separate firm from @osec_io.
Full report below.
6
468
Honored to have contributed to @AftermathFi Perpetuals V2 Security Assessment with @certora team.
Finding security bugs and making sure they got properly remediated is always rewarding. Glad to have helped make the protocol more secure.
Thanks for the shoutout @tpiliposian 😃
200+ lines in the audit report, 70+ issues found. crazy audit
huge kudos to the @AftermathFi team for the very professional communication throughout the audit, immediately discussing and addressing the issues, and overall for building such a cool protocol
huge thanks to everyone from our side who worked on this one, and a special shoutout to @PerseveranceSu5 for the exceptional work
1
9
700
Perseverance retweeted
.@CertoraInc has completed its security assessment of our Perpetuals V2 contracts.
This is the second independent audit of the protocol, conducted by a completely separate firm from @osec_io.
Full report below.
Perseverance retweeted
.@osec_io has completed its security assessment of our Perpetuals V2 contracts.
12 weeks. 9 repositories. 0 critical. 0 high.
Every advisory resolved.
Perpetuals V2 launches on Mainnet Tuesday.
Full report below.




























