Useful sources: where to verify an answer
Use primary documentation for the part, platform and software revision you actually have. This is a reviewed starting list, not an endorsement of every fork, release or linked product. Checked 2026-10-17.
| Source | Useful for | Scope |
|---|---|---|
| Official SeedSigner | Baseline signing model and original project | Official Raspberry Pi hardware instructions are not our Luckfox assembly guide |
| ShieldSigner application | Smartcards and added application features | Pinned to our application revision |
| Hardware platform profiles | Display types, GPIO profiles and supported platforms | Match model and profile, not only screen size |
| QR formats | Recognizing wallet exports, transaction and seed payloads | Avoid exposing secret QR contents to online decoders |
| Descriptor handling | Loading, using and clearing multisig policy | Application behavior at the pinned revision |
| SeedSigner recovery | Script types, derivation paths and key encoding | Match network, account and any custom path |
| BIP383 | Multisig descriptor threshold/key semantics | Specification, not a complete recovery procedure |
| SeedKeeper applet guide | Persistent secret storage workflows | Card version, PIN and export policy matter |
| Satochip guide | On-card signing workflows | Distinct from SeedKeeper storage |
| Bundled JavaCard applets | Applet identities and versions | Does not prove an arbitrary JavaCard is compatible |
For physical design, use the saved manufacturer PDFs, current carrier BOM, and electrical review. For firmware provenance and reproducibility, use our OS build record; the original project and fork use different platform build paths.
Reading historical advice
Check date, hardware variant, release and whether a post describes a proposal, a patch, or a successful test. A pull request can be useful without being merged or present in your image. Stock, discounts and shipping estimates need a current supplier quotation. An old missing-feature report can become obsolete after a release.
Public guide additions cite public primary sources and project evidence. Community discussions help identify questions worth investigating; they are not substituted for measurements or a verified recovery test.
Source: docs/USEFUL-SOURCES.md ↗. Documentation describes reviewed evidence; it does not replace physical testing.