Work

Live Layer Protocol: Streaming Signed, Verified WebAssembly Layers into Running Applications

Year: 2026
Type: preprint
Abstract: Shipping a code change today means running it through a build-test-release-deploy pipeline and then restarting the program that runs it. The pipeline is where safety checks live, so it cannot simply be removed. We describe the Live Layer Protocol (LLP), which moves those checks to the moment a change arrives at a running application. Code is delivered as a stream of small, signed, content-addressed WebAssembly modules (layers). A Live Host owns all application state, verifies each signed manifest, rehearses the new layers against a copy-on-write shadow of the real state, commits all of them atomically or none, and reverts a layer that traps or exceeds its time or memory limit. The same manifest stream drives client devices and server or edge nodes, and a fleet layer adds channels, percentage rollouts with health gates, convergence tracking and key rotation. We report a reference host in JavaScript, an independent second host in Go written from the specification, and a conformance suite of 161 language-neutral checks that both pass. On one 4-core machine, a warm swap takes 2.3 ms (p50), a change reaches 1,000 simulated hosts 0.58 s after the file is saved, and a layer that crashes after going live is reverted with state restored in 2.3 ms. A red-team review produced 39 findings, of which 29 are fixed (several only partly or opt-in) and 10 remain open. We replay the failure mechanisms of four public outages in simulation and state where the protocol contains the failure and where it does not. LLP v0 is experimental: it catches crashes and hangs, not wrong answers, and several results come from single-machine simulation.
Language: English
Open Access status: green
OpenAlex ID: W7236208336
Cites:
Cited by:
Related to: 10