The 2.8-inch panel
- A Raspberry Pi 3 Model B or B+
- Waveshare 2.8inch DPI LCD
- A microSD card of 256 MB or more, and a power supply
- A USB webcam that offers uncompressed (YUYV) frames, or a Raspberry Pi Camera Module v1 or v2
Where Faraday runs, and what the build of each platform carries and leaves out. Every fact here is from Faraday's documents; each section names its source.
Supported hardware Platforms Screens and layout One build per platform The boards Left out Cameras and input Help test Considered
One card for each piece of hardware the download page offers. Its page says what it needs, its screen and its builds.
The Pi has one image. It finds the screen attached when it starts, so the same card runs either setup.
Where Faraday runs, and the state of each.
| Platform | Runs on | State |
|---|---|---|
| The stick | A 64-bit PC with UEFI firmware (one build, with efi=disable_early_pci_dma on its command line); Intel Macs planned | Released; booted in QEMU with OVMF and on a laptop (the kernel with efi=disable_early_pci_dma, 2026-10-31) |
| The Pi, the 2.8-inch screen | A Raspberry Pi 3B, 3B+ or Zero 2 W with the Waveshare 2.8-inch DPI panel, with USB keyboards, mice and sticks | Built, not tried on the one image: looking for testers (the earlier 2.8-inch image was tried on the panel) |
| The Pi, HDMI screen | A Raspberry Pi 3B, 3B+ or Zero 2 W with an HDMI monitor and a USB keyboard and mouse, or Waveshare's 10.1-inch HDMI LCD (B) with its USB touch | Built, not tried: looking for testers |
| The Pi Zero 2 W | A Raspberry Pi Zero 2 W with the same screens | Built, not tried: the Pi image carries its device tree; nobody has booted it on a Zero 2 W |
| The Apple Silicon stick | Macs with M1 or M2 | Planned: its Spec is docs/MAC.md |
| Faraday Demo | Linux and Windows, x86_64 | Released, for trying Faraday: not air-gapped |
| The Starter | Linux and Windows, x86_64; macOS specified | Released on Linux and Windows |
The Starter writes sticks and Pi cards and holds no keys. Faraday Demo runs on a computer that is on a network. It is a simulator with Practice's samples, not a signing device.
The network stack is not compiled in: no Ethernet, Wi-Fi, Bluetooth or USB network driver, and no socket layer. A Pi 3's Wi-Fi and Bluetooth chip is never given its firmware, so it never runs. A PC's own disks are invisible.
Faraday Demo and the Starter run on a computer that may be on a network. Neither is a place for real keys.
Faraday lays every screen out again at its own size. Its size class comes from its width in dp at its density, divided by the text size: a larger text steps the layout down.
| Class | Width | Navigation | Typical screen |
|---|---|---|---|
| Compact | under 600 dp | The navigation bar at the foot | The Pi panel (268 × 358), a narrow window, a 7-inch panel in portrait (565 × 964 at its 170 dpi) |
| Medium | 600 to 839 dp | The navigation rail | A half-screen window |
| Expanded | 840 to 1199 dp | The navigation rail | A 7-inch panel in landscape (964 × 565), a 10-inch panel in portrait (853 × 1365 at its 150 dpi), a small laptop window |
| Large | 1200 to 1599 dp | The expanded navigation rail | The desktop app's default window (1280 × 800), a 10-inch panel in landscape |
| Extra-large | 1600 dp and over | The expanded navigation rail | A full monitor at 1×: 1920 × 1080, 2560 × 1440 |
Height counts where it is short. A screen under 480 dp tall is short, as the Pi's 2.8-inch panel is: there Home is the menu. One under 600 dp tall is low, as a 7-inch panel in landscape is. docs/LAYOUT.md says what each class lays out.
| Screen | Pixels | Density | dp | Class, navigation |
|---|---|---|---|---|
| Waveshare 2.8-inch DPI panel (the Pi) | 480 × 640, portrait natively | 286 dpi | 268 × 358 | Compact and short: Home is the menu, every other page has its bar with a back chevron; no Rotation |
| A 7-inch panel, landscape (a small tablet, a panel PC or a portable monitor on the stick) | 1024 × 600 | 170 dpi, from its EDID | 964 × 565 | Expanded and low: the navigation rail |
| A 7-inch panel, portrait | 600 × 1024 | 170 dpi | 565 × 964 | Compact: the navigation bar at the foot |
| A 10-inch panel, portrait | 800 × 1280 | 150 dpi | 853 × 1365 | Expanded: the rail |
| A 10-inch panel, landscape | 1280 × 800 | 150 dpi | 1365 × 853 | Large: the expanded rail |
| A PC monitor or laptop screen on the stick | Its firmware mode | faraday.dpi=160, doubled at 2800 pixels wide or more | Its pixels, or half | Expanded to extra-large: the rail or the expanded rail |
| An HDMI screen on the Pi | The mode the kernel chose from its EDID | Its EDID's on a screen of 11 inches or less, faraday.dpi=160 otherwise | By its mode | By its width, as on the stick |
| Faraday Demo's window | 1280 × 800 at first, any size | The system's scale | Its size | Any class, laid out again at every size; the Size menu shows the panels above |
A 7-inch or 10-inch panel starts in landscape, and Settings › Display › Rotation turns it and its touch. A screen of 11 inches or less takes its density from its EDID. The app lays out every one of these sizes. The Pi image is built for the 2.8-inch panel and for an HDMI screen, one image that finds its screen at boot: faraday/image/panels/any holds the two screens' values and overlays, and faraday/image/panels/ the PC's firmware framebuffer. A 7-inch screen is the stick's, on a small PC or tablet, or an HDMI one on the Pi.
The layout follows the screen's width in each orientation: a 7-inch panel is expanded and low in landscape, with the rail, and compact in portrait, with the navigation bar at the foot. The Pi's 2.8-inch panel stays in portrait: it has no Rotation.
Every platform starts with full motion. Reduce motion (Settings › Appearance) is off on a first start. Where frames are slow, the automatic gate turns fades off by itself: it does so when the steps are more than 55 ms apart, and brings them back after 24 fast frames in a row.
The PC stick is one image, and the Pi has one image for every screen. There is no build to choose between.
| Platform | The kernel |
|---|---|
| The Pi | DRM for HDMI and the 2.8-inch DPI panel; USB keyboards, mice and touchscreens; USB storage |
| The PC stick | efi=disable_early_pci_dma on its built-in command line, so no PCI device the firmware left running can write to memory before the kernel has set up the IOMMU; kernel.cmdline makes the kernel check require it |
The PC's kernel is the EFI program itself, with its root filesystem inside it and the firmware's framebuffer, so nothing it runs needs the devices that flag cuts off. KCMP is forbidden on the PC (its own kernel.forbidden) and allowed on the Pi, where DRM selects it.
efi=disable_early_pci_dma on its built-in command line, and a kernel check that requires it.The root filesystem, the app and its checks are the same on both platforms; the kernel and its command line are each board's own.
Each board has its own list of forbidden kernel options, and the build fails if one is on.
What starts before Faraday, and where it is kept, differs from board to board.
Everything they start from is on the card: the firmware, and the kernel with the system linked into it. A fresh card is a clean start.
The chip's one-time-programmable memory is out of the app's reach: its mailbox driver is not built. The Wi-Fi and Bluetooth chip is never given its firmware, so it never runs.
One card starts the 3B, 3B+ and Zero 2 W: it carries each board's device tree, and the firmware loads the one for the board it starts on. Nobody has started a Zero 2 W with it yet. The Zero 2 W has no DSI connector, so a screen on the DSI connector does not fit it.
The Pi 4 starts from a boot loader kept in an EEPROM on the board, not on the card. A card carrying recovery.bin can rewrite it, so on a Pi 4 a fresh card is not a clean start. Its security is close to a PC's: its boot code is on the board. Its USB sits behind PCIe.
It will run the same images as the Pi 3: its 32-bit kernel, firmware and device tree beside the Pi 3's, the system the same. No Faraday card carries a boot loader update, and its kernel leaves out SPI_SPIDEV and SPI_BCM2835.
Before first use, restore Raspberry Pi's boot loader with Raspberry Pi Imager. A wire to test point TP5 locks the boot loader in hardware.
Its firmware runs before Faraday, and Faraday does not defend against compromised firmware. Nor against the management processors below the operating system, Intel's Management Engine and AMD's Platform Security Processor: What else runs on this computer says which computers have them and what to do.
Between the firmware and the kernel's IOMMU there is a window in which a PCI device the firmware left running could write to memory. The stick closes it: its kernel's built-in command line carries efi=disable_early_pci_dma, and its kernel check requires it. The stick has been tried on a laptop with it. The IOMMU is on from boot in strict mode.
Thunderbolt is left out. A Thunderbolt or USB4 port is a PCIe slot on the outside of the case; without the Thunderbolt driver it carries USB and DisplayPort and nothing that speaks PCIe. The computer's own SATA, NVMe and eMMC disks are invisible: their drivers are not built.
The Pi 5 comes after the Pi 4.
On the PC and the Pi. Each kernel is built with a fixed list of drivers.
su, sudo or passwd, and root's password is locked. Every process that handles input runs as an unprivileged user.Faraday reads QR codes through a camera, and files from sticks and cards.
| The PC stick | The Pi | |
|---|---|---|
| Touch, keyboard, pointer | Built-in keyboard, touchpad and touchscreen; USB ones once approved | The panel's touch, or the HDMI panel's USB touch once approved by a tap on the target; other USB keyboards, mice and touchscreens once approved, as on the stick |
| Camera, for QR codes | A USB webcam, plugged in or built in, that offers uncompressed frames; not a MIPI camera | A USB webcam that offers uncompressed frames; a Camera Module v1 or v2, tried with the earlier 2.8-inch image, and on the one image beside the 2.8-inch panel and an HDMI screen to be tried; not Camera Module 3 |
| Files | USB sticks; an SD card only in a USB reader | Its own SD slot and USB sticks |
A USB webcam that offers uncompressed frames (YUYV) works, plugged in or built in. A webcam that sends only MJPEG frames does not work yet.
On a Pi, the camera is a Raspberry Pi Camera Module v1 or v2 on the board's ribbon connector, or a USB webcam. Camera Module 3 is not supported. For a housing, a bare USB camera board with screw holes and an adjustable (M12) lens also fits well: screw it in place and set its focus once at the distance a QR code is held.
Not working yet: a MIPI camera. Most laptop webcams made after about 2020 are sensors on a MIPI lane behind an image processor, and Faraday carries neither their driver nor its firmware. Such a computer shows the scanner's file path and no viewfinder; a USB webcam in a port works. A webcam plugged in after the system starts is not picked up.
On a PC: a built-in touchscreen, and a USB one once approved.
On the Pi: the panel's own touch, and USB touchscreens once approved; the one the screen's profile names, such as the 10-inch HDMI panel's, is trusted input and needs no approval.
A keyboard other than the computer's built-in one is ignored until it types a random code shown on the screen, and until it is unplugged if it types three codes' worth of letters without it. After three such keyboards, new ones are ignored until Faraday starts again.
A new pointer is ignored until a person approves it with trusted input. USB interfaces are authorised one at a time: a stick that also claims to be a keyboard types nothing.
FAT only, read and written by Faraday's own disk process in Rust, not by the kernel. A partition holding anything else is left alone.
On a PC: USB sticks, and an SD card in a USB reader. On the Pi: its own card slot and USB sticks.
An image is published before it has been tried on its hardware, marked Looking for testers. Once it has been tried there, its screen's settings are confirmed and its page marks it Tested. The pages never say whose hardware it was tried on.
Not yet tried: the Pi card on a Pi 3B or a Zero 2 W.
Open an issue on github.com/bitcoinpasada/faraday with the make and model of the computer or board, the screen, the image's file name, and what happened.
Where it does not start, When the stick does not start goes first.
Built from the source with dev=1, it shows the kernel's messages on the screen and writes faraday-boot-report.txt every 30 seconds: the kernel log, the screen and devices found, and no secret. Send that file, and the build ID (uname -r on its console), with the report. Never use the dev image for keys that matter.
DEVELOPING §6.2 says how to build it.
Boards studied. Faraday does not run on them yet.
A 7-inch 1024 × 600 IPS board with GT911 capacitive touch, MIPI-DSI and MIPI-CSI. It has an ESP32-P4 (two RISC-V cores, up to 400 MHz, 768 KB SRAM, 32 MB PSRAM, 32 MB flash) and an ESP32-C6 module for Wi-Fi 6 and Bluetooth 5. It costs about US $50. Studied without a board on 2026-10-28. Not supported, and not being ported.
Vault memory. Faraday makes vaults of at least 64 MiB of Argon2 memory, and the board has 32 MB in all. A vault it could open would be made at 16 MiB or less, below Light. That is the owner's decision, not taken.
The radio. The C6 boots its own flash at power-on, whatever the P4 runs. Without a radio means the C6 module desoldered, or its flash erased and the erase checked. No ESP32-P4 board without a C6 was found. ESP32-S3 boards carry the radio in the chip and are not candidates.
The security model. docs/SECURITY-MODEL.md rests on Linux:
One ESP-IDF image in one address space would need a model of its own.
Secure boot. Espressif's advisory AR2026-006 says the P4's ROM ECDSA check may accept invalid signatures, so RSA-3072 secure boot would be used. ESP-IDF is a large body of C that Faraday has not reviewed.
Help is welcome. Before any port, these would be measured on the board:
faraday-draw