Argot Collective

30 June

We are pleased to announce that the Argot Collective and the @ethereum.foundation have completed the final phase of our original five-year funding commitment. Approximately 4,938 stETH will be transferred into a multi-sig wallet, with phased unlocks on 1 July 2026 and 1 July 2027.

13h

New blog post out! ethdebug is an open format for compilers to explain their output in a developer's own language. Our first post about it on the Argot blog covers this year's progress, with interactive visuals that run on actual compiler output.

Next it follows a variable's bytes, from its storage slot down to packed fields and strings. And finally, it covers some harder cases for debugging, too: locals that move between stack and memory as code runs, and bytes the optimizer reuses for multiple variables.

argot.orgethdebug: a shared language for debug data, in use across projects todayMore compilers now write ethdebug data, and tools have started to read it. This post shows what that data does today, how you can build on it, and what comes next for the ethdebug format.

13h

Read the full post here and try solc's ethdebug output today: www.argot.org/blog/2026-1...

Tools are reading it too now: • Walnut's soldb reads ethdebug, and • Runtime Verification started a Python library for it. soldb was designed for Solidity, yet it also works with Fe's ethdebug output out of the box.

13h

The second half of the post runs you through interactive visuals. It starts with how ethdebug enables tools to stop guessing at compiler rules, because the compiler now writes them down. From there, it shows how a debugger can read this to step through compiled code.

These compilers now produce ethdebug data: • solc has produced ethdebug source ranges since 0.8.29, with storage variables coming soon • Fe outputs ethdebug source ranges for most instructions, even with the optimizer on • Solar produces ethdebug source ranges, even with the optimizer on

14h

A single contract interaction quietly trusts half a dozen remote services: an RPC, an explorer’s “verified” badge, a served ABI, a simulation API, a wallet’s decoder. Manuel shows how to verify each layer on your own device with Onay, an open-source prototype, instead! Nov 4, 15:30 IST,@devcon.org

docs.sourcify.devOnay: 2FA for Signing | Sourcify DocsIf you've signed anything on Ethereum you know this feeling. The wallet pops up: an address, some hex, a function name... Where are these coming from? Am I even talking to the correct contract? What am I even signing? What is this action going to do?

14h

Learn more about Onay: docs.sourcify.dev/blog/onay-l...

🫣 ✍️ Blind signing is still one of Ethereum's biggest UX and security problems! @kaanuzdogan.bsky.social of Sourcify shows how ERC-7730 turns transactions into something people can read, and how wallets can add it with Sourcify's clear signing SDK. Nov 4, 16:00 IST, @devcon.org

Want to try Core Solidity hands-on? Jacob will run a code-along workshop at @Devcon. You leave with a working Core Solidity smart contract and a direct line to the people building the language. Nov 5, 12:00 to 12:50 IST, Workshop 1. Bring a laptop.

New frontend, same backend Core Solidity is a new frontend for solc. It lowers to Yul and shares the optimizer and code generator with Solidity today, so backend work on stack-too-deep and compile times helps both. Link to the playground in the comment below.

Explore some code examples now and compile and call contracts in the browser: playground.solcore.soliditylang.org

How "anonymous" can you really be? To whom, and to what extend? At @devcon.org , msooseth brings the LINDDUN privacy threat taxonomy to Ethereum, pairs each harm with an attack seen in crypto, and takes Tornado Cash apart flow by flow. Nov 3, 14:30 IST, Lotus 1

We're getting ready for @devcon.org 8 in Mumbai 🇮🇳 ✨ This is where you can find us throughout the week ↓

x.comSolidity (@solidity_lang) on XWe published a status update on Core Solidity: what the language can do today, what is still missing, what the community told us, and what comes next.

Where is Core Solidity at today? The Solidity team's new post covers what works in the prototype, what is still missing, and what 18 interviews with developers, auditors and tool builders taught us. Give it a read now! x.com/solidity_la...

We have 2FA for email and banking but not for signing crypto transactions, the most sensitive step of all. Onay by Sourcify, featured in theDAO fund's second round, adds a local sanity check to every signing request.

Read more and help build it here: initiatives.thedao.fund/initiative/...

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.

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.

youtube.comGoodbye YOLO Signing | Kaan Uzdogan (Berlin Ethereum Day, June 2026)Blind signing has long been one of Ethereum’s biggest UX and securi...

If you want to get more insight into the work they've been doing on Clear Signing watch the full talk from BBW 2026 here ↓ www.youtube.com/watch?v=hM4...

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 on making ecosystem value flow easily visible, and (...) uick Slots' would impact deployed contracts.

(...) more recently they've been supplying Ethlabs with data to assess how 'Quick Slots' would impact deployed contracts.

x.comCryptoCanal - Common S3nse (@CryptoCanal) on XWhat's next for Solidity? @_czepluch from @solidity_lang, joins the Common S3nse stage to walk us through where the language has been and what's coming next. Privacy • Security • DeFi 📍 Amsterdam 📅 September 4-5 (during Cypherpunk Week)

17 Aug

Who will we meet in Amsterdam? Jacob will talk all things Solidity during Cypherpunk Week in Amsterdam in September and hopes to see many of you there! ↓ x.com/CryptoCanal...

github.comRelease v26.2.0 · argotorg/fe26.2.0 (2026-06-23) Features Contract fields are now immutable by default unless declared with mut. Immutable fields must be initialized before every successful init exit and are embedded into co...

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.

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...

Two problems found across two compilers, both fixed and shipped. Formal verification catching issues that testing alone could miss. 🤝

github.comEnforce payable vs non-payable constructors by axic · Pull Request #458 · argotorg/solcoreConstructors can now be marked payable. A non-payable constructor (the default) rejects any incoming value transfer at deploy time, reverting with the same NonPayableReceivedValue error (0xb5988ea3...

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.

The bug was reported to the team & fixed. 🔗 github.com/argotorg/so...

Example 2: Fe Since Fe encodes storage similarly to Solidity, act can verify Fe compiled bytecode directly. We wrote a simple contract containing mappings & wanted to verify it against its act spec. act flagged a discrepancy in how Fe handled those mappings:

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.

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 and Fe show what that looks like in practice.

Example 1: Core Solidity  We wrote a simple contract in solcore along with its act specification & tried to prove they were equivalent. act said they weren't. After some digging we discovered that constructors were payable by default, which was unintended.

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.

30 July

Excited to announce the first release of EquiVM! ✨ EquiVM is a Lean 4 framework for formally verifying that deployed EVM bytecode faithfully implements a formal, human-readable specification, with machine-checked proofs guaranteeing the two behave the same.

We'd genuinely value your input at this stage. If you work on verification, security, or tooling, take a look at the examples and the trusted-base section of the README. Tell us what’s unclear, what do you think is missing, or what you’d implement differently. Link to the release below ↓

github.comGitHub - argotorg/EquiVM: Refinement proofs in Lean for EVM bytecodeRefinement proofs in Lean for EVM bytecode. Contribute to argotorg/EquiVM development by creating an account on GitHub.

30 July

Github: EquiVM 0.1.0 github.com/argotorg/Eq...

The proofs are generated by autonomous LLM agents & checked by the Lean kernel, so nothing about the agent has to be trusted. The important part: you can audit a contract by reading the spec instead of the bytecode, and reason formally about its behavior through the high-level representation alone.

30 July

This research direction grew directly out of community feedback on act, and we're excited to see it take shape. The 0.1.0 release ships proofs for real deployed contracts: WETH9, MakerDAO Dss contracts, OpenZeppelin contracts, and more, across a range of solc versions and optimizer settings.

Our second bi-annual transparency report is live, covering all spending from January 16 to July 2, 2026. As a collective committed to public-goods stewardship, we believe financial and organizational transparency is essential to accountability.

Three Argot projects were also selected for the inaugural theDAO Ethereum Security QF Round on Giveth: Sourcify, act, and hevm. The fund allocates yield from funds recovered from TheDAO hack toward projects strengthening Ethereum security. We are honored to have been part of its first round.

argot.orgTransparency Report 2026 (H1) | Argot CollectiveOur second bi-annual transparency report, detailing all spending from January 16 to July 2, 2026.

Transparency is a continuous effort. We hope this report gives the community a clear view of how resources are being used and where support is going. Read the full report: www.argot.org/reports/tra...

We have finalized the terms and governance of the remaining 2 years of the @ethereum.foundation's 5 year funding commitment, with the first unlock this July. This continued support gives Argot the stability to maintain and develop core infrastructure for Ethereum long term. See: sl1nk.com/ey3k87g

Solidity was fortunate to be selected for three Octant rounds in the first half of the year across Epoch 10, StreamVote, and the first v2 round. Octant continues to be a driving force in public goods funding innovation and we are grateful for the continued support.

The Budget & Expense section breaks down spending into categories including salaries, infrastructure, and legal costs. Click the toggle to see the salary breakdown per project across teams. As with our previous report, the majority of expenses are contributor salaries.