What does it take to trust a transaction end to end?

Duration: NaN:NaN:NaN

Speaker: Manuel Wedler

Type: Talk

Expertise: Some familiarity with the topic

Event: Devcon

Date: Nov 2026

Using a contract today means trusting a stack of services: an RPC for chain state, an explorer database for "verified" sources and the ABI it serves, a simulation API for effects, a decoding service for human readability, the same explorer for what happened. None of it is proof. We split the pipeline into layers and show each made verifiable on the user's device: - Chain state through an embedded light client - Sources by local recompilation matched against proven bytecode - Simulation from a local EVM that reads only proven state - Decoding via ERC-7730 descriptors with attestations verified locally - Post-mining re-verification of what you signed vs. what actually happened The proof is an open prototype, called Onay, that brings existing local verification tools together into one app. We close with what limits local verification, and with what still runs on trust: the screen-to-device gap, the light client checkpoint, compiler binaries, ERC-7730 attesters, and the device itself.