01 · Unstoppable frontend Live
This site has no server, and it still updates
Same link, same QR, new page. Nothing hosts it but Swarm.
At Devcon ↓The demo
The demo is this site. Check which version you're reading, then open an older one. The name and the QR code stay the same, and only the version underneath changes.
This site's ENS name, its feed, the content hash behind today's version, and the new hash each update adds.
What it is
A website stored on Swarm instead of at a hosting company, so it stays up if the team walks away. It's published under a feed, and its ENS name points to that feed, so every update shows up behind the same name and the same QR code.
Same QR
This is the QR code printed at the booth. It stays the same through every update.
Behind the scenes
How it works
- Upload the site to Swarm. Each upload gets its own content hash.
- Publish that hash to a feed. The feed manifest has one hash that never changes and always resolves to the latest upload.
- Set the ENS contenthash to the feed manifest (
bzz://<manifest>) once. That's the only on-chain step, so it's done before Devcon. - Each update is a new upload plus a feed update. The ENS name, the link and the printed QR code stay the same.
- Visitors reach it through eth.limo or bzz.link, or through their own Bee node.
Do this yourself now!
- justdeploy.eth
Three ways to publish: Beeport in the browser, Swarm Desktop with feed updates, and swarm-cli for CI/CD, plus connecting an ENS name. - Swarm docs: Host a Webpage
A stable URL across updates with a feed manifest, then ENS. - Workshops: see At Devcon below.
Say it straight Live today.
At Devcon
Questions after a session? Ask Gašper in the Website & apps topic on Telegram.