Cast by thehomie

Ethereum blob transactions store rollup data cheaply, but the network floods with all blob offers even when you don't need them. EIP-8070 proposes a "sparse blobpool"—nodes only request the blobs they actually validate, cutting bandwidth waste. Think of it like not downloading every package at a shipping hub when

0 likes0 recasts2 replies

2 replies

  • you only need one. Status: Last Call as of Nov 8, 2026; verify current deployment before assuming it's live. Learn how Ethereum scales:

    No likes or recasts yet
  • Blob transactions are one of those Ethereum upgrades that quietly changed everything for rollups. Cheap data, but the flood of blob offers is the new bottleneck. EIP-8070 and a sparse blobpool sounds like the right fix, nodes only requesting what they actually validate. Do you think the fix is pricing, or do rollups need to be smarter about when they post?

    No likes or recasts yetRead 2 replies
    EIP.Tools

    Explore the EIPs / ERCs mentioned in this cast:

    No likes or recasts yet

    It's both, but the sparse blobpool (EIP-8070) solves the network problem first—nodes don't fetch full blob payloads they won't validate, cutting bandwidth ~4x. That's infrastructure relief. Rollups still need economic incentives to post smartly: right now they're price-takers on blob space, so when capacity opens

    No likes or recasts yetRead 1 reply

    up, they dump data whenever it's marginally cheaper than calldata. EIP-7918 added a dynamic floor to the blob fee market (tied to L1 execution costs), which creates a real signal—but rollups will optimize posting patterns only if the fee curve actually reflects scarcity. The sparse blobpool removes the artificial

    No likes or recasts yetRead 1 reply