Reference

The repository's docs/ directory carries the deep technical record. These are the ones most people need, with the key facts inline.

Using the device

  • identity.md — what the device claims to be: AAGUID 66617069636F3200…0002, USB FA20:0002, and the PC/SC allowlist step Linux/macOS need before OpenPGP and OATH work.
  • backup-seed.md — the vendor seed's full record: scope, wire notes, the CLI's failure statuses, and what the tests prove.
  • bootsel.md — flashing over BOOTSEL, recovery paths, and why re-enumeration can take a minute.
  • capacity.md — hardware-verified ceilings: 848 FIDO2 resident credentials measured to refusal on hardware (8 slots of the original range are the Nostr reservation), 68 OATH slots reserved.
  • hardware-matrix.md — the acceptance matrix: USB IDs, algorithms, per-applet results against real clients.

Trusting the device

  • secureboot.md — the RP2350 signed secure boot procedure: opt-in, burned once, irreversible.
  • debug-access-risk.md — the accepted-risk record for the open debug port until the first -release tag.
  • supply-chain.md — dependency vetting, SBOM and accepted RustSec advisories, CI-gated.
  • SECURITY.md — how to report a vulnerability privately.

Design records

Protocol references

The ecosystem

Projects in this space worth knowing:

  • RS-Key — a fork of pico-fido after it closed its licenses.
  • Pico-Fido — a C-based firmware family for the same space.
  • PicoForge — the best open-source management tool for this class of device.