We're cooking something for @EFDevcon 2025... 😋

We’re thrilled to share a major milestone: Argot has secured foundational funding from the @ethereumfndn! This significant support ensures we can sustain and advance critical open-source infrastructure for @ethereum. Find all details on our blog or follow the tl;dr here👇

🗣 Call for Feedback: In order to reduce maintenance burden, Solidity is considering the deprecation of some niche distribution channels for compiler binaries. Read the full forum post: →

This is the chart you've been waiting for 👀 Where's @solidity_lang, @SourcifyEth, @official_fe and Formal Verification though? We're in @argotorg :)

Solidity v0.8.30 just landed! This latest version is a maintenance release in light of the Pectra Ethereum network upgrade and changes the default EVM version from cancun to prague. 📝 Blog: 💾 GitHub: Some important things to know in the thread 🧵↓

✨ APIv2 for verification is here! Following contract lookup, now you can verify contracts using APIv2 - Std JSON as default, instead of metadata.json (still supported) - Ticketing with verification jobs, no hanging requests - Minimal, lean API Legacy API is being deprecated

As Ethereum prepares for the Fusaka upgrade, the debate around the Ethereum Object Format (EOF) is heating up. One question stands out: Is statically analyzable code really that valuable? Let's talk about it 👇🏻

With the Interop Testing call happening over the next hour, which will (yet again) decide the fate of EOF, we would like to address a few misconceptions. [🗣Call agenda:]

The team prepared valuable input to the discussion on @solidity_lang libraries "compilation to EOF" issues. It's worth reading and decide if it's complicated or easy.

There has been a lot of talk about the promise of RISC-V for Ethereum execution lately, but I don't think there has been sufficient thought about _how_ we get to that place. Here are my thoughts about how the transition could work and how EOF fits in.