EIP-4844 introduces Shard Blob Transactions.
Blob data would make a big impact to make Ethereum the central place to rollups by taking the first step towards danksharding: a vision where ethereum as L1 can host and attract a diverse set of L2s with much lower fees for ethereum L2 users.
Nov 22 EIP-4844 shanghai candidate update:
- No interactions with Shanghai EVM EIPs: the EIP adds one opcode to push a datahash onto the stack, and a precompile to verify data against the commitment.
- Compatibility with Withdrawals: the EL and CL specs are based on top of the withdrawal work (EL, CL, Engine API)
- EIP-4844 Spec completion:
- We have iterated through EIP changes for 9 months, and the scope of changes reduced significantly over time
- The EIP received review from most client implementer teams
- Complementary CL specs and Engine API specs
- EIP-4844 Testing:
- EIP-4844 KZG-ceremony readiness:
- EIP-4844 KZG library readiness:
- The CL specs define a simple minimal interface, as well as the EIP
- C-KZG-4844 implements this interface, with NodeJS, CSharp and Python bindings. And ongoing Rust bindings.
- Go-KZG implements this interface in Go
- EIP-4844 Devnet readiness:
- Wide client devnet support:
- EL: Erigon, Geth, Nethermind
- CL: Prysm, Lighthouse, Lodestar
- Targetting devnet v3 soon after ACD, on Nov. 30
- Wide client devnet support:
Dec 8 EIP-4844 ACD update: EIP-4844 was confirmed as primary focus for Cancun.