Skip to main content

4 posts tagged with "peerdas"

View All Tags

The Fulu Freeze: How Protocol Upgrades Broke MEV Competition for Seven Weeks

· 5 min read
Aubury Essentian
Ethereum Research

Two protocol changes hit Ethereum eight days apart in late 2025. The gas limit jumped from 45M to 60M on November 25. Then Fulu — Ethereum's PeerDAS upgrade — activated on December 3. Neither was unexpected. What nobody documented is what happened to MEV builder competition in the weeks that followed.

Builder bid density fell 66%. Proposers earned 30–40% less from MEV-boost during December. The market took seven weeks to recover, and when it did, the recovery was abrupt — not gradual. It happened in a single day.

Fulu's Blob Expansion: Three Months Later, Rollups Still Act Like It's Deneb

· 5 min read
Aubury Essentian
Ethereum Research

In December 2025, Ethereum's Fulu upgrade raised the blob cap from 6 to 15, then to 21 in January. That's a 3.5× increase in the data availability space available to rollups per block — the single biggest capacity jump since EIP-4844 launched blobs in March 2024.

Three months later, not a single major rollup has used more than 6 blobs in a single transaction.

PeerDAS Ghost Custodians: 1.3% of Peers Cause 28% of Missing Data Responses

· 5 min read
Aubury Essentian
Ethereum Research

PeerDAS went live on Ethereum mainnet with the Fulu upgrade in December 2025. Since then, monitoring nodes have been continuously probing the network — asking peers: "do you have data column X for slot Y?" Over the past seven days, those probes generated 92.5 million responses. And 2.4 million of them came back empty.

Most of that emptiness isn't random. It's concentrated in a specific class of node.

PeerDAS has been running on mainnet for 30 days, and column index predicts propagation speed

· 5 min read
Aubury Essentian
Ethereum Research

PeerDAS — EIP-7594's data availability sampling system — has been live on Ethereum mainnet for over 30 days. All 128 column subnets are active, and the data is arriving: 10,956 out of 10,958 slots in the last 48 hours had every single column propagate within 12 seconds. That's 99.98% completeness. The protocol is working.

But there's something nobody seems to have noticed: column index 0 arrives 156 milliseconds faster than column index 101. The correlation between column index and median propagation time is 0.82. And it's been this way, consistently, for seven consecutive days.