sourcify.eth

Source code verification for Ethereum smart contracts: open-source, open-data, open-standards.

An @argotorg project and a member of @verifalliance

[sourcify.eth @SourcifyEth]

https://t.co/ptwX453PRD

[Ethlabs @ethlabs_org]

https://t.co/NVpqHq6dCX

[Fe Language @official_fe]

Fe 26.3 is here! 🧵

First-class memory pointers, new array and ERC-20 helpers, important compiler fixes, and foundations for source-level debugging.

Here’s what’s new 👇

[sourcify.eth @SourcifyEth]

Welcome to the 50M club 🏆

Notice the Parquet size is even smaller now, that's 40GBs saved with metadata.json deduplications!

[Solidity @solidity_lang]

Solidity 0.8.37 is out.

[Blaine Malone @blainemalone]

shoutout to the folks on the Clear Signing Working Group (@kaanuzdogan) who merged our PR for @staycloakedxyz !

https://t.co/eWKw9QH04x

knowing what you sign is extremely important and we're trying to make that as easy as possible.

[Kaan @kaanuzdogan]

🫡 one by one we are increasing the ERC7730 clear signing coverage

[Trezor @Trezor]

Smart contract transactions can be complex. 

Clear Signing makes them easier to understand. Your Trezor decodes supported EVM transactions and shows the action, tokens, amounts, and destination on its trusted screen.

See it. Verify it. Sign with confidence.

[Barnabé Monnot | barnabé.eth @barnabemonnot]

EF Protocol teams have ranked Quick Slots, a proposed upgrade to begin making Ethereum L1 faster, as B-tier, clearing their bar for consideration in Hegotá.

https://t.co/pSnI33bdB2

They have listed four concrete requirements to increase their level of confidence in delivering better UX, better markets and better censorship-resistance for Ethereum all at once in Hegotá. Work is now fully underway to close all four requirements:

1. Specifications covering all expected changes to the core protocol are proposed and actively discussed here https://t.co/H1tgsmB0yv I appreciate @JustinTraglia for his valuable input here.

2. Two individual core developers from two distinct client teams have started the work of prototyping the change, including @terencechain from Prysm. There is more to do here, and I thank both of them for their time.

3. An in-depth assessment of downstream effects is in progress, with the support of @SourcifyEth. A preliminary write-up was shared here: https://t.co/HgG7mFknMx and the analysis is currently being expanded to cover more sources of dependencies, including EIP-4788.

4. @fradamt in our team is an integral part of the effort of specifying decoupled consensus, working in closest collaboration with the EF Protocol Finality team. On our side, we are confident that Quick Slots do not complicate decoupled consensus.
In fact, since one of the objectives of decoupled consensus is to deliver shorter slots via decoupling block production and finality, doing Quick Slots in Hegotá means that decoupled consensus delivers maximum value once it fully ships. This is on top of faster blocks providing an additional latency reduction to finality, close to 20%.

Job is not done 🫡 and we will keep raising our efforts to derisk Quick Slots and ensure its inclusion. The opportunity is to make Ethereum meaningfully faster in its next major upgrades, rather than waiting for two or more cycles.

If you want to know more about why we think it's important and are committed to pushing it forward, check out our Hegotá view on the topic: https://t.co/sKp23UHnnh

[Kaan @kaanuzdogan]

I'm speaking at @EFDevcon 8!

"Goodbye YOLO Signing"

Join me in Mumbai 🇮🇳 November 3-6, 2026. https://t.co/uEmn9JH6xi

[sourcify.eth @SourcifyEth]

It's been a while and we're growing non-stop.

DB past 1TB
>47M contracts

[sourcify.eth @SourcifyEth]

Our hearts beat together 💙❤️

[L2BEAT 💗 @l2beat]

L2BEAT has verified ~1000 smart contracts on @SourcifyEth 🤝 The biggest Solidity contract open database just became richer with actual contracts used in L2 projects and bridges.

[Kaan @kaanuzdogan]

Do I know anyone here working on any Ethereum wallet?

We are working hard on ERC7730 Clear Signing. We need more eyes and feedback on what we are working on and see how it fits your wallet. Software or Hardware.

RTs and interactions appreciated 😇

[Argot Collective @argotorg]

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.

[sourcify.eth @SourcifyEth]

Helloo 👋

- Check out the Dataset Playground on https://t.co/cQobbbF9W7
- Do your queries on a Python notebook, like this one fresh out of the oven: https://t.co/26yxoR7fuy
- Or download the dataset in Parquet https://t.co/Bzsv3s2SrT

We believe it's essential to have the verified contract datasets as whole open and accesible

[sourcify.eth @SourcifyEth]

With @barnabemonnot of @ethlabs_org we ran a preliminary analysis on our open dataset of verified contracts for the "Quick Slots" proposal

A very good example of what open datasets enable

20.6K of 7.7M Mainnet contracts (0.27%) were found relevant

🧵

https://t.co/YP5I6Zge8p

[sourcify.eth @SourcifyEth]

Feedback and ways to improve more than welcome!

The whole Colab notebook available at: https://t.co/yw9zLgTxvy

Check resources on EIP-8198 and Sourcify dataset:
- https://t.co/zod2b4UZ7T
- Magicians thread: https://t.co/kvbTWy8pyz
- Sourcify DB: https://t.co/evDsr0pFuP

[sourcify.eth @SourcifyEth]

With @barnabemonnot of @ethlabs_org we ran a preliminary analysis on our open dataset of verified contracts for the "Quick Slots" proposal

A very good example of what open datasets enable

20.6K of 7.7M Mainnet contracts (0.27%) were found relevant

🧵

https://t.co/YP5I6Zge8p

[Barnabé Monnot | barnabé.eth @barnabemonnot]

Thank you for questions and support expressed during the presentation yesterday! Two points that were highlighted:

1. Identify potential issues with deployed contracts relying on the slot time. We will have more on this soon, doing joint work with @SourcifyEth, currently no strong blocker encountered with a few important contracts that we have surveyed.

2. Understand costs and benefits, as some pointed out that a moderate decrease from 12 to 10 seconds, our Hegotá anchor target, may not be worth the work. I'd reiterate here that getting started with slot time decreases is the hard part, that we need to cross in order to iterate towards shorter and shorter slot times. 12 to 10 seconds remains quite significant, and is immediately beneficial to all users of Ethereum at once.

Hence, it appears most valuable to get started asap, and enjoy a decrease in Hegotá. And then potentially more decreases in subsequent hard forks, as decoupled consensus comes online and zk/pq move forward.

Hegotá may well be the last time before long where we can get started with slot time decreases. Many, myself included, wish to see decoupled consensus deployed in the fork following Hegotá, to obtain faster finality. However, bundling a slot time change with decoupled consensus appears unreasonable.

Meaning: We either commit to staying at 12 seconds for the next two years minimum, or land 10 seconds in ~a year in Hegotá, and possibly less than 10 seconds by the year after. This is why it is in my view critical to move ahead with quick slots in Hegotá.

There is no blocker other than prioritisation, hence the importance of continuing to express support for the value of this EIP.

---

A special shout-out too to @CarlBeek who has authored the quick slots EIP and kept the work of slot time decreases going. We'll be updating the EIP to reflect the new anchor target of 10 seconds, following comments to that effect in the ACD chat.

You can find the presentation and questions on Forkcast. Thank you again to all for the good discussion!

https://t.co/GP1Mf6bdi4

[sourcify.eth @SourcifyEth]

The analysis is preliminary and for demonstration purposes.

Obvious next steps:
- Sort addresses by TVL and transaction count. Address them first, and reach out where necessary.
- Loosen or tighten the filter with false negatives