Seed verifier

Check your seed.

Your KEY draws its seed from two chips that cannot see each other, and shows you both layers before it mixes them. Paste or scan them here and redo the arithmetic yourself — the XOR, the hash, the words. Nothing is sent anywhere.

These bytes are your wallet

Layer A and layer B together reconstruct the seed. Anyone who scans, photographs or copies both can spend your coins and sign as you.

Use a throwaway seed unless you have a specific reason not to. If you are checking a real one, download the offline copy at the bottom of this page and run it on a machine that is not connected to anything.

running self-test…
Step 1

Layer A — the secure element

On the KEY: Settings → Device → Overlay seed. Freeze the SE051 layer and it offers a QR.

Step 2

Layer B — the camera

Cover the lens while it runs and watch the grid freeze. That is the sensor being read, live, in front of you.

What this proves, and what it doesn't

  1. It proves the device hashed what it showed you. The board is the pre-image — no substitution, no grinding for a value the maker likes.
  2. It proves neither chip vendor acted alone. The SE051 never sees a camera frame and the camera never sees the SE051's output, so a backdoor in either part on its own still leaves the board unpredictable to whoever planted it.
  3. It does not prove the bits were unpredictable. A picture of random-looking output is not evidence of randomness — output that came from a counter looks identical. That gap is closed by reproducible builds and secure boot, not by this page.
  4. If you want to trust nobody at all, roll dice. The dice path takes input the device cannot predict, and it is the only one that survives a fully compromised device.

Run it offline instead

One file, no network requests, no dependencies — save it and open it from disk on an air-gapped machine. Same arithmetic, same self-test.

Download the offline verifier
sha256 1b0230070d26176328e2e29b685fd80e4edd900f3aba1d2990f104ee578634d9