This page is for checking the design system. It is not in the sidebar or the search index, and it asks search engines not to index it. Switch the theme with the toggle in the header to see both palettes.
Body text is Inter 400. Headings are Inter 700, with page titles and section headings at 800. Code, pin names and GPIO labels use JetBrains Mono, for example GPIO14 and 3V3. Bold text uses 600–700. A link looks like this.
The page title above is the only level 1 heading. Every other level follows.
A long paragraph shows the prose measure. Lines stop at about 70 characters, so they stay easy to read on a wide screen. This sentence is here only to make the paragraph long enough to wrap across more than one line.
Sketch uses 1234567 bytes (37%) of program storage space.
The tools and libraries are installed and checked. Nothing is wired yet.
Phase 1Display✓Done
The touch shield shows graphics, driven by the ESP32 DevKit.
Phase 2Touch input and on-screen controls✓Done
Accurate touch, plus reusable on-screen buttons and a keyboard.
Phase 3QR scanner on the camera board✓Done
The ESP32-CAM decodes QR codes and sends them out on one pin. Two test criteria were waived, not passed: a QR code of 300 or more characters, and 2 minutes of continuous scanning.
Phase 4One-way camera link✓Done
The signer receives what the camera scans over a single one-way wire, and survives a flood of random data without crashing.
Phase 5Keys (stateless seed)✓Done
Generate, back up, load and use a seed without ever storing it, and export a watch-only wallet to Sparrow.
Phase 6Address check screen✓Done
You can check receive and change addresses on the device itself.
Phase 7Reading and checking transactions✓Done
The device receives an unsigned transaction by animated QR, checks it independently and shows it for approval.
Phase 8Signing and returning the transaction◐In progress
The device signs after approval and shows the signed transaction as a QR code for Sparrow to broadcast. Two signet transactions have confirmed, one with two inputs. The exit criterion asks for three.
Phase 9Hardening○Planned
Close the obvious prototype gaps and write down the threat model.
Phase 10Path to the final hardware○Planned
A written plan for moving to a security-oriented chip with a secure element. Planning only, not building.
Without summaries:
8 of 11 phases done.
Phase 0Setup and baseline✓Done
Phase 1Display✓Done
Phase 2Touch input and on-screen controls✓Done
Phase 3QR scanner on the camera board✓Done
Phase 4One-way camera link✓Done
Phase 5Keys (stateless seed)✓Done
Phase 6Address check screen✓Done
Phase 7Reading and checking transactions✓Done
Phase 8Signing and returning the transaction◐In progress
Espressif lists a camera interface, PSRAM, secure boot and flash encryption for the ESP32-S3. The idea to explore is whether one board could do the job of the current two, with protections this prototype doesn't have yet.
Like the current boards, the ESP32-S3 has Wi-Fi and Bluetooth radios.
○PlannedNot built, not yet researched
Raspberry Pi Pico 2 (RP2350)
Raspberry Pi lists boot signing with the key fingerprint in one-time-programmable memory, and Arm TrustZone, for the RP2350. The plain Pico 2 has no radio; only the Pico 2 W does.
Its product page doesn't mention a camera interface, so how it would scan QR codes is an open question.
Every wire in wiring.yaml, with the group filter (it appears when more than one group is shown):
Hover over, focus or tap a wire to see where it goes.
Schematic only: each board shows just the pins in use, not in their physical order. Always match the labels printed on your board. Dashed wires are not yet tested.
Every wire in wiring.yaml
From
To
Signal
Notes
TFT shieldLCD_D0 (D8)
ESP32 DevKitGPIO22
Data bit 0 / touch YM
Moved from GPIO12, a strapping pin that caused boot loops. Needs library patch 3.
TFT shieldLCD_D1 (D9)
ESP32 DevKitGPIO13
Data bit 1 / touch XP
TFT shieldLCD_D2 (D2)
ESP32 DevKitGPIO26
Data bit 2
TFT shieldLCD_D3 (D3)
ESP32 DevKitGPIO25
Data bit 3
TFT shieldLCD_D4 (D4)
ESP32 DevKitGPIO17
Data bit 4
TFT shieldLCD_D5 (D5)
ESP32 DevKitGPIO16
Data bit 5
TFT shieldLCD_D6 (D6)
ESP32 DevKitGPIO27
Data bit 6
TFT shieldLCD_D7 (D7)
ESP32 DevKitGPIO14
Data bit 7
TFT shieldLCD_RD (A0)
ESP32 DevKitGPIO21
Read strobe
Moved from GPIO2, a strapping pin that blocked upload mode. Needs library patch 2.
TFT shieldLCD_WR (A1)
ESP32 DevKitGPIO4
Write strobe
TFT shieldLCD_RS (A2)
ESP32 DevKitGPIO15
Command/data select / touch YP (analog)
An analog-capable pin (ADC2_CH3). Also a strapping pin.
TFT shieldLCD_CS (A3)
ESP32 DevKitGPIO33
Chip select / touch XM (analog)
An analog-capable pin (ADC1_CH5).
TFT shieldLCD_RST (A4)
ESP32 DevKitGPIO32
Reset
TFT shield5V
ESP32 DevKit5V / VIN
Power (5V)
The shield's regulator and backlight need 5V.
TFT shield3V3
ESP32 DevKit3V3
Power (3.3V logic)
TFT shieldGND
ESP32 DevKitGND
Ground
ESP32-CAMGPIO14 (IO14)
ESP32 DevKitGPIO34
One-way data
The only data wire between the boards. GPIO34 is input-only, so the DevKit can't send anything back. There is no wire from the DevKit to the CAM.
ESP32-CAMGND
ESP32 DevKitGND
Common ground
Required. Use the GND next to the CAM's 5V pin, never the pin labelled "GND/R", which is tied to reset on this board.
ESP32 DevKit5V / VIN
ESP32-CAM5V
Power (5V)
Not yet tested. Only for when the USB-TTL adapter is removed for good. Never connect two 5V supplies to the CAM at once. If the CAM browns out, use a separate 5V supply and keep GND shared.
USB-TTL adapter5V
ESP32-CAM5V
Power (5V)
In the tested setup this is the CAM's only power supply. The DevKit's 5V is not connected to the CAM.
USB-TTL adapterGND
ESP32-CAMGND
Ground
USB-TTL adapterTX
ESP32-CAMU0R (GPIO3)
Data to the CAM (uploads and console commands)
With the adapter set to 5V, this line carries 5V logic, above the ESP32's rating. A 1 kΩ / 2 kΩ divider is recommended; not fitted on the tested build.