Who Can Turn Off Your Ethereum App? A Full-Stack Walk-Away Test
Duration: NaN:NaN:NaN
Speaker: James Carnley
Type: Talk
Expertise: Some familiarity with the topic
Event: Devcon
Date: Nov 2026
Ethereum apps have centralized off switches throughout the stack. Upgrade keys change contracts. Domains and web servers remove interfaces. RPCs and indexers control what users see. A content hash proves integrity, not availability, discovery, authority, or an exit path.
I built Ethereum File System around a cypherpunk requirement: the maintainer should be optional. Its public web client uses ENS and IPFS. Path, provenance, and mirror records are on Sepolia. I will retrieve the same file from IPFS and Arweave, verify it against public records, and show how to distinguish corruption from unavailability. EFS shows how the same questions apply to any Ethereum app.
The talk goes layer by layer through contract control and immutability, naming, frontend distribution, RPCs, indexers, storage, gateways, provenance, and verification. Developers will leave knowing why each layer matters, what to check in their own apps, and how to test what still works when a team or service disappears.