The console in your browser
The same console, with your passkey as its key.
A Pico's firmware, file for file, running here. It shows what a transaction does, works out its hash itself, and has your passkey sign only that.
worked out in your browser, over the files it runs
D0 D1 D2 are 123, or Esc ↓ Enter. Hold D2 to open or to sign. D1 held is back.
Move ←↑↓→ or WASD · press Enter or Space · A B X Y are 963.
What you approve is this screen. Your browser draws it, and Touch ID won't show the transaction. On a computer you don't trust, use a hardware key, and keep passkey owners below the Safe's threshold.
- 1
Your passkey
— - 2
A Safe to watch
— - 3
Your passkey as its owner
Console output
One folder you can read
This page loads nothing from the rest of the site. Everything it runs sits in one folder, and the firmware in it is the console image a Pico runs, as plain files. Save a copy, check it, and sign from your own.
| In the folder | Size |
|---|---|
firmware/The console image: the same 54 files a Pico runs, in MicroPython. They hash to the release fingerprint. | 13,232 lines, and 10 data files |
shims/Python in place of the Pico's hardware: its pins, screen and Wi-Fi, and your passkey as its key. | 641 lines |
console.js, worker.js, web/, core/, shared/, coi.js, sw.jsThe page's JavaScript: the buttons, your passkey, and the worker MicroPython runs in. | 1,157 lines |
vendor/micropython/MicroPython 1.26.0 for WebAssembly, the one part built elsewhere: by the MicroPython project, from npm, pinned by its hash. | 522 KB |
index.html, console.css, fonts/, brand/This page: its words, its look, the site's typeface and mark. |
- 1
Save a copy
SHA256SUMSlists every file. Fetch them, thensha256sum -c SHA256SUMS. No build step: these are the files that run. - 2
Hold it up to the README
Hash
firmware/the way a release is hashed. It gives the fingerprint above, the one in the README's build table and on a Pico's Device screen. - 3
Run your copy
python3 -m http.serverin the folder, then openlocalhost:8000. A site can change its page on any visit. Your copy changes only when you change it. - 4
Make its own passkey
A passkey belongs to the site that made it. One made on your copy can be asked to sign by your copy, on
localhost, and never by this site.