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 / paying nodes that actually execute proofs a free rider cannot copy from a peer

  • YouTube
Paying Nodes That Actually Execute: Proofs a Free-Rider Cannot Copy From a Peer preview
  • Details

Paying Nodes That Actually Execute: Proofs a Free-Rider Cannot Copy From a Peer

Duration: NaN:NaN:NaN

Speaker: Pranay Anchuri

Type: Talk

Expertise: Some familiarity with the topic

Event: Devcon

Date: Nov 2026

Outside the consensus committee, nobody pays a node to execute blocks. Lottery rewards are the natural fix, but a state root is a public output of the state transition function, exposed by every API. A node can copy a peer's root and claim the reward without running the block. Signing the output does not close the attack. A signature proves who is claiming, not that the claimant did the work. A signature attached to a separately produced proof is separable too, so only the cheap half is bound to the node's secret. The proof itself has to require the secret and the computation at the same time. TRACE binds both in one argument over the in-memory execution trace, a vector that is never serialized and cannot be fetched from an API. The verifier stays logarithmic, so the claim is checkable without redoing the execution. I will also cover the transferable tension: hiding the node's secret wants fresh randomness, but prover-chosen randomness lets nodes grind the lottery.

Categories

DecentralizationCryptographyProving SystemsCensorship Resistance