Devcon Archive logo
Devcon Devconnect Forum Blog
  • Watch
  • Event
    Event: background logo
    • Devcon 7
    • Devcon 6
    • Devcon 5
    • Devcon 4
    • Devcon 3
    • Devcon 2
    • Devcon 1
    • Devcon 0
    • Devconnect ARG
  • Categories
    Categories: background logo
    • Cryptoeconomics
    • Devcon
    • Developer Experience
    • Coordination
    • Core Protocol
    • Layer 2s
    • Real World Ethereum
    • Cypherpunk & Privacy
    • Security
    • Applied Cryptography
    • Usability
  • Playlists

Suggested

Loading results..

View all

About Devcon —

Devcon is the Ethereum conference for developers, researchers, thinkers, and makers.

An intensive introduction for new Ethereum explorers, a global family reunion for those already a part of our ecosystem, and a source of energy and creativity for all.

  • Watch
  • Devcon
  • Devconnect
  • Forum
  • Blog

Get in touch

devcon@ethereum.org

Subscribe to our newsletter

Crafted with passion ❤️ at the Ethereum Foundation

© 2026 — Ethereum Foundation. All Rights Reserved.

devcon8 / blob or chunk which one is cypherpunk infinitely scalable data for smart contracts

  • YouTube
Blob or chunk: which one is cypherpunk? Infinitely scalable data for smart contracts preview
  • Details

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

Duration: NaN:NaN:NaN

Speaker: viktor Tron

Type: Lightning Talk

Expertise: Some familiarity with the topic

Event: Devcon

Date: Nov 2026

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.

Categories

DecentralizationScalabilityEVMCommunication