Time for a Sourcify update because @SourcifyEth has been busy! Over the past months the team has turned into a true Swiss army knife, touching multiple corners of the Ethereum ecosystem at once. Throughout the first half of the year they have been supporting the Clear Signing working group by building an SDK to help wallets fight blind signing, collaborating with @growthepie_eth on making ecosystem value flow easily visible, and more recently they've been supplying @ethlabs_org with data to assess how 'Quick Slots' would impact deployed contracts. All of this builds on their consistent work of verifying and maintaining an open source database of currently 43.5M+ contracts across 260+ EVM chains.

Formal verification is getting a lot of attention and there are many ways to approach it. Alongside the recent EquiVM release, there's other FV work happening at Argot, including act. act is a formal specification language with a range of capabilities, one of which is proving that EVM bytecode matches a human-readable spec. Think of it as a way to mathematically guarantee that a contract does exactly what it claims to do. Building under one umbrella means our work streams reinforce each other. We collaborate across teams from the start and apply our tools wherever they add value. Two recent cases with @solidity_lang and @official_fe show what that looks like in practice.

Example 2: Fe Since Fe encodes storage similarly to Solidity, act can verify Fe compiled bytecode directly. We wrote a simple contract containing mappings and wanted to verify it against its act spec. act flagged a discrepancy in how Fe handled those mappings: dynamic sized copies were adding unnecessary complexity. The Fe team resolved it in their 26.2 release. Bytecode and spec are now equivalent. 🔗 github.com/argotorg/fe/relea…

🔥 link to EquiVM in comment below ↓ 🔥