Websites that outlast us: dependency minimalism and the walkaway test applied to the frontend stack
Duration: NaN:NaN:NaN
Speaker: Darryl Yeo
Type: Lightning Talk
Expertise: Some familiarity with the topic
Event: Devcon
Date: Nov 2026
Walletbeat’s stack decisions treat browser-native behavior as a transfer of responsibility: shift implementation away from frameworks toward shared platform primitives, and accept progressive enhancement as an interim tradeoff for newer capabilities. Compilers sidestep the traditional server-client runtime model: Svelte bridges missing state, Astro produces static files, and subresource integrity ensures output is self-consistent.
Publication is designed around recovery: reject wallet-controlled services whose email recovery restores unilateral control, build once, then send artifacts through independent storage paths and checked browser access before updating ENS. IPFS content addresses are rollback targets, not promises of retention; ENS keeps automated updates revocable without granting ownership of the name. Conventional static hosts (Vercel, Cloudflare) remain the baseline; extra machinery earns its place only when it adds a verifiable or recoverable property the project values.