Companion app.
The side that talks to the network never holds a spending key.
- A viewing key only: it can see your payments, not sign them.
- Builds the payment, proves it, broadcasts what the signer signed.
- Shows the same address rows as the device, so you can compare.
Case.
Made to be opened, not sealed shut.
- Held together with screws, not glue.
E-ink panel.
What you approve is drawn here, not on your computer.
- A 3.7″ touch e-paper panel, 240 × 416. Amount, fee, memo and network are drawn before you sign, the recipient in numbered rows of four-character groups, matching the app.
- Tap to choose; “Reject” cancels a payment. To sign, hold “Hold to sign” for 1.5 s; a hold lifted sooner never signs.
- The PIN keypad starts at a random digit for every digit you enter.
Firmware.
It checks the payment itself instead of taking your computer’s word.
- Checks every amount and output against its commitments, then computes the ZIP-244 sighash itself.
- For a payment, only signatures go back over USB. No command sends the seed.
- Updates over USB are signed by the project, and the device checks the signature.
Schematic.
Every part and every connection, to be published.
- The next board starts in KiCad from the open Dabao board files.
- Chip, the touch e-paper panel with its boost circuit, and USB-C. No battery: it runs on USB power.
- To be published with the board layout, so the two can be checked against each other.
PCB.
A layout you can hold up against the board itself.
- Layout files and photos of the inside, to be published for comparison.
- Until that board exists, the Baochip-1x work runs on a Dabao, its development board.
Chip.
It runs on the Baochip-1x.
- Mostly open RTL, with a TRNG, glitch sensors, a security mesh and a key store on the die. Its protections still have to be proven.
- The signer has already signed a shielded transaction on a Dabao board.
- Build it yourself from the published files, or get it as a kit from the project.
Seven layers. None of them should be hidden.