ethPandaOps @ethereumfndn

Australia
Joined August 2008
Andrew Davis retweeted
1/ Ethereum's state grows far faster than it churns. Most of it goes dormant and never gets used again, while real activity sits on a tiny set of active applications. Here's a deep dive into what 10 years of mainnet access data shows about how Ethereum's state is actually used. 🧵👇
6
24
2
93
7,682
1/ Ethereum’s protocol roadmap is shaped by many teams, researchers, and contributors. At the Berlin Ethereum Day, @parithosh_j from the @ethPandaOps team will share perspectives on the strawmap, and the path forward. Register or get involved! 🔗👇
1
3
1
14
809
Andrew Davis retweeted
We built Panda, a CLI/MCP tool that lets agents work directly with our observability data. We found that if you give the agent a code sandbox and a library for your stack, things start to click together very nicely. Post below 👇
2
4
2
25
2,565
Andrew Davis retweeted
We built a simulator for the fast confirmation rule, and replayed a years worth of blocks and attestations on Mainnet. Across 800,000 mainnet slots, roughly 96 out of every 100 slots would have been fast-confirmed within 12 seconds. Zero false confirmations. Read more below!
51
68
11
405
107,120
Andrew Davis retweeted
The Infinite Garden needs gardeners that plow the fields, weed the weeds and plant the seeds. Not everyone can water the plants or count the buds.
12
6
68
3,366
Andrew Davis retweeted
New in The Lab: Validator Report. Paste validator indices, pick a range, scan performance, and drill from day -> hour -> slot to find exactly what happened. Catch missed proposals and head-vote drops faster.
4
5
33
1,143
txdelay.xyz is live. See how long Ethereum transactions wait on average to land on-chain. Let me provide some additional context: how the website works, what Glamsterdam (the next hardfork), in particular ePBS (EIP-7732), changes, and what this means for different stakeholders. With 12s slots, the average inclusion delay is ~6s. Shortening slot time reduces it. This number will increase by ~2s with ePBS, which is an unfortunate downside, degrading UX. Under ePBS, builders should wait until the beacon block committing to their payload has enough attestations before releasing it. Thus, ePBS has a similar effect to increasing slot time to 16s, and Ethereum would need ~8s slots just to get back to today’s inclusion delay. A similar effect applies to zkEVM provers: if provers are separate from builders, they effectively lose ~2s of proving time, delaying real-time proving and slowing down the rollout of zkEVMs. With shorter slots (e.g. 8s), this means provers would need to be ~25% faster. The data is sourced from @ethPandaOps’ Xatu nodes, comparing when transactions are first seen in the mempool vs when they are included in a block. It filters for transactions that can afford the base fee and pay at least $0.01 in priority fees. If you're a dApp builder, infra provider, zkEVM prover, exchange, power user, etc., I'd be curious how much every second of inclusion delay matters. Drop your thoughts in the comments or reach out via dm.
11
21
133
12,123
Andrew Davis retweeted
i just want to help ship the strawmap
5
1
2
57
2,607
Andrew Davis retweeted
BPO2 landed last week. It bumped the max blobs per block to 21. We've been going through the data. Initial analysis doesn't look good! Have a look at this scary chart. But there might be more to this story.. Link below!
15
30
9
123
14,941
pretty excited for the year to come, lots to do!
Interested in L1 scaling, Data, Testing, Forks? Or just monitoring the situation with the boys? Well, ethPandaops has a post for you!
2
134
I got two new tools: bids.pics shows the MEV-Boost auction live, including bids, their timing, and dynamics that are usually opaque. xof.pics shows private/exclusive order flow at the block level. Both are built on data from @ethPandaOps. I had rough prototypes and the ideas for over a year, but never the bandwidth to finish them. The trick: implement the core logic and data preprocessing by hand, then let AI take over the rest. What used to take weeks now just ships.
18
30
2
184
17,879
big s/o to the @ethPandaOps team once again for "The Lab" their epic continuously updated dashboards w/ client metrics
10
11
1
77
8,716
The first devnet for EIP-7928, Block-level Access Lists, is live. This marks a big step toward major L1 scaling improvements next year. Excited for where this leads! Big shoutout to everyone involved — especially @fselmo2, @raxhvl, @stefan_star and all the client teams involved!
Block level access list devnet-1 is starting with five EL clients any moment now!
15
16
2
75
8,287
Replying to @samcmAU
@samcmAU cooked over the weekend! We have a 2025 wrapped for our internal comms server 😂
4
4
22
822
Heres some data from the last 24h of nodes that we connected to on Mainnet wrt. PeerDAS. - 17.6% of nodes are supernodes (4096+ ETH staked) - 46.1% custody 4 columns (the minimum) - 23.4% custody between 5-8 columns IMPORTANT: These are NODE counts. They are not directly stake weighted. More insights below 👇
3
14
1
34
2,447
Andrew Davis retweeted
not a fusaka explainer, but i hope you get a chance to read this.
the eth core devs don’t tweet a lot about just how hard the work that they do is so let’s talk about it: 1. every line of code they merge can move more money than most banks process in a quarter. there is no staging server for that. 2. they swap consensus logic for a 400B + dollar economy without scheduling downtime. ever. 3. they coordinate hundreds of researchers, auditors, and client teams across time zones, cultures, and philosophies, yet ship like a single mind. 4. they do it all in public, with every decision dissected by the loudest peanut gallery on the internet, and still keep the vibe collaborative. 5. they design for attackers who have nine figure incentives and infinite patience. then they sleep anyway. 6. they keep six independent clients in perfect sync so the same block lives at the same height for every node in the world. 7. they turn bleeding edge research into production code while preserving backwards compatibility for machines that went online before defi even had a name. 8. they debug issues that only happen once a year on a single archive node because someone somewhere will rely on that edge case. 9. they write cryptography that must stay unbroken for decades while the math itself evolves beneath their feet. 10.when the upgrade lands smooth the outside world shrugs. inside ethereum we know it was a minor miracle. every successful fork proves that decentralized coordination can outperform the world’s best hierarchies and shows that open internet capital markets are now the default. thank you, truly. we owe you everything.
20
9
159
15,524
Please update your Prysm node with the flag mentioned if you are facing issues on Mainnet.
🚨 We have identified the issue and have a quick workaround. All nodes should disable Prysm to unnecessarily generate old states to process outdated attestation. To do this, simply add the following flag to your beacon node. This flag works with v7.0.0 and you do not need to update the beacon node beyond adding this flag. No change is required for validator clients. "--disable-last-epoch-targets"
1
5
35
2,059
🚨 We have identified the issue and have a quick workaround. All nodes should disable Prysm to unnecessarily generate old states to process outdated attestation. To do this, simply add the following flag to your beacon node. This flag works with v7.0.0 and you do not need to update the beacon node beyond adding this flag. No change is required for validator clients. "--disable-last-epoch-targets"
44
91
27
376
113,961