Domain Atlas — Warranty Demo

A two-minute, no-installation demo of a factory-to-retailer-to-owner credential chain.

One certificate, one physical unit: a factory mints it with a real serial number, a retailer stamps the actual sale date onto it when it's sold, and from that moment the warranty clock is running — for however many owners the product passes through next. Selling it secondhand doesn't reset anything or need anyone's permission from the factory: the same certificate, with its original serial number and sale date intact, simply changes hands. In a real deployment, minting and stamping would be authenticated operator actions — a factory login, a retailer login — the way this domain's Admin Panel models them for a real operator. This page plays both parts for you, one click at a time, so you can see the whole chain without needing an operator login of your own — transferring ownership below is the one step a real product owner would actually do themselves.

What this looks like for a real manufacturer

A serial number an operator authenticated at manufacture time, a sale date stamped by whichever authorized retailer actually made the sale, and a warranty status anyone can compute themselves from those two signed facts — no phone call to the factory required to find out if a used appliance is still covered, and no way for a reseller to quietly extend or backdate it, since both facts are signed by the factory's own key.

Your identity

A wallet keypair generated right here in this tab — this is who the factory mints the certificate to first.

Step 1 of 4 — the factory mints a certificate

A real factory authenticates once, at manufacture time, before assigning a serial number. Pick whatever serial you like — this page mints the certificate straight to the identity above, playing the factory's part for you.

Serial number

Full history

A genuine call to GET /atlas/asset/history — walks this certificate's own supersedes chain back through every stamped sale and every resale, one archived link at a time, each one still an independently verifiable signed credential in its own right. Nothing about this is specific to warranties — any class can opt into the same archive, this is just the first one that does.

Step 2 of 4 — the retailer stamps the sale

Fill in a sale date, a warranty length, and the retailer's name — this page stamps them onto the certificate for you, the same generic reissue mechanism the museum exhibit's info card and a mistagged item's tradeScope already use elsewhere on this site, just playing the retailer's part in one click.

Sale date Warranty length (months) Retailer name

Step 3 of 4 — ownership changes hands

A genuine call to POST /atlas/asset/transfer, signed by whoever currently holds the certificate — no factory or retailer involved at all. Click as many times as you like to simulate the product being resold again and again; the serial number, sale date, and warranty status travel with it unchanged every time.

Step 4 of 4 — verify the certificate independently

Runs entirely in your own browser: fetches this domain's public key and revocation list — the same two public files anyone could fetch directly — then checks the signature and looks the id up in the revocation list. Nothing here trusts this page.

Nothing on this page is stored in a database anywhere, and reloading it starts a fresh identity from scratch. Back to the plaza.

A warranty that travels with the product