Blob or chunk: which one is cypherpunk? Infinitely scalable data for smart contracts

A chain of reductions: each step removes machinery the previous one needed.

Blobs: data never enters the EVM, type-3 txs are EOA-only, bytes pruned in ~18 days — publication, never storage.

Anchor pattern: a 32-byte content-addressed root; updates O(1) at any payload size; keccak Merkle openings verified natively in Solidity.

Validity vs availability: slashing forces openings but can't punish withholding; availability must be physically produced — broadcast, or a second bonded holder.

Litigable receipts: staked nodes at a derived secondary address pledge "produce on challenge or be slashed", countersigned by the primary storers — withholding needs two colluding neighbourhoods; persistence prepaid via postage stamps.

Reads are EIP-3668 callbacks verifying Merkle paths; writes are gasless signed pointer flips.

Authenticated indexes give query completeness; a censored result is convicted on-chain by two keccak proofs. Close: storage-cost state, consensus-grade trust.

Speakers: viktor Tron

Track: Open & Verifiable Stack