SeedSigner Fork on Luckfox Pico: Pi Alternative & Secure Boot

Raspberry Pi Zero stock has become a real problem for people wanting to build SeedSigner-style air-gapped signing devices. If you have been trying to buy boards recently, you will know that even big distributors look empty for a long time. That is why I have been working on a SeedSigner fork that supports Luckfox Pico boards, including the Mini, Max and Pi variants.

This article is the written version of my live build video, so it should still be useful if the video is unavailable later. In the video, I assemble several builds, flash firmware to MicroSD, NAND and eMMC, verify secure boot, and show how to re-sign a release on device using BIP85-derived RSA and ED25519 keys.

Watch the video

Build your own hardware wallet

Kits, smartcard hats, cases and parts for SeedSigner, ShieldSigner, Specter DIY and Satochip builds, tested with the firmware shown in these videos and shipped from Canada.

Why use Luckfox Pico instead of Raspberry Pi Zero?

The main reason is availability. The Luckfox Pico Mini is a very small, cheap board that can be sourced when Raspberry Pi boards are not. It has no radios, which fits the air-gapped signing model well. It can boot from MicroSD or onboard flash where supported, and it supports secure-boot-style verification of the bootloader and root filesystem.

For ShieldSigner builds, I am mostly focused on the Pico Mini because it is small enough to make a low-profile device with an integrated smartcard reader. The Max and Pi variants are also supported, but they are bigger and more expensive. In practice, for standard SeedSigner/ShieldSigner use, the CPU performance difference between the Mini, Max and Pi does not matter much. The 64 MB of RAM on the Mini is enough for what we care about here.

The Pico Pi has more RAM, which helps with some on-device workflows such as re-signing firmware in one pass. The smaller boards may need a slightly more air-gapped file-handling approach depending on the workflow, but the core idea is the same: keep signing keys tied to your seed and avoid keeping them on a computer.

Finished builds overview

I built several versions so you can see what is possible:

  1. A low-profile Pico Mini build with the board soldered directly to the Plus Hat.
  2. A no-solder variant using pin headers or an adapter, which works but makes the device thicker.
  3. A larger development-style build based on the Pico Max or Pi, useful for testing and easier access to ports.

The soldered Mini build is the one I think most people will want because it stays compact while still supporting the smartcard reader, camera, display and buttons. The no-solder option is convenient if you do not want to solder, but the trade-off is size.

Three SeedSigner-style Luckfox Pico builds in different cases
Finished builds shown together: low-profile, smartcard and larger development variants

Parts used for a typical build

For a basic ShieldSigner-style Pico Mini build, you will generally need:

If you are building a Raspberry Pi-based version instead, the store also has items like the SeedSigner + Smartcard Kit, the Smartcard Hat for Raspberry Pi with USB-C Input power, and the Raspberry Pi Zero 1.3 when available.

Assembling a Pico Mini Plus Hat build

This is the main build I recommend for people who want a compact, low-profile device.

Step 1: Solder the Pico Mini to the hat

The Plus Hat has castellated vias on the edge. You align the Luckfox Pico Mini with those contacts and solder them down. Newer boards include orientation markings, such as which way the USB should face.

This is not a difficult job if you have basic soldering skills. In my experience, it can be easier than soldering pin headers onto a Raspberry Pi board. If you do not want to solder at all, there are plug-in or adapter options, but they add height.

Step 2: Fit the low-profile camera

The case does not fit the thicker stock camera module nicely, so I use a low-profile camera instead. Place it in the camera slot and secure it with small screws or a 3D-printed backer piece. The goal is to keep it square and stable so the image stays aligned.

Low-profile camera being positioned in the case
Positioning a low-profile camera module into the case

Step 3: Fit the display, MicroSD cavity and buttons

Insert the display with the contacts facing the white connector area. Slide it down until it is seated. You can tape it during assembly if you like, but once the case is clipped together, the tape is usually not necessary.

Add the small MicroSD cavity piece so the card has room to sit correctly. Place the buttons into the lid and clip the case shut. The D-pad area should line up with its cutout.

Assembled orange 3D-printed ShieldSigner-style case
Closed low-profile build in a 3D-printed case

One thing to watch: there are board revisions where the button layout and screen position differ slightly. The front face plate needs to match your revision because one version moved the screen away from solder joints that could short against the 5 V rail.

Assembling a larger Max or Pi development build

The larger builds are easier if you want access to ports or do not want to solder the Pico Mini directly onto the hat. The case is bigger, and some versions have an Ethernet port sticking out the side, which is annoying but workable for testing.

For these builds:

  1. Insert the display with the contacts facing the white area.
  2. Position the smartcard hat so the pins line up without crushing the flat ribbon cable.
  3. Fold the case over and secure it.
  4. Add buttons to the lid where required.

The important point is not to pinch or crush the FPC ribbon cable. If you damage that connection, the display will stop working.

Larger development build with main PCB and smartcard hat
Seating the main board and ribbon cable while aligning the smartcard hat

First boot and secure boot status

When you power up a device, it may show that secure boot is not enabled. That is normal for an unlocked board. If secure boot is enabled, the device will verify the bootloader and root filesystem before continuing. You are looking for a passed result, such as “rootfs signature valid” or similar wording depending on the firmware build.

If the firmware was signed with the public developer key, you may see a warning that it is using a dev key. That is expected during beta testing because releases are initially signed with a developer key so users can later re-sign them with their own BIP85-derived keys.

Secure boot verification screen showing PASSED
Device shows secure boot passed and rootfs signature valid

Choosing the right release file

The firmware files are device-specific. You need to choose the correct one for your hardware:

  • Pico Mini MicroSD
  • Pico Mini NAND
  • Pico Max variants
  • Pico Pi eMMC or SD depending on the board

Do not flash a Mini image onto a Pico Pi, and do not use a NAND bundle when you are trying to write to eMMC. The partition layout is different, and the device may reject it or fail to boot correctly.

I download the release files from my SeedSigner fork repository. The releases include bundles for the supported Luckfox Pico variants. You should also check that your file matches the hardware you have in front of you.

Flashing MicroSD with Balena Etcher

The easiest workflow is flashing a MicroSD image if your board supports it. This is similar to normal SeedSigner flashing, but there is one difference: Luckfox Pico images may not look like standard bootable Raspberry Pi images.

  1. Insert a MicroSD card into your computer.
  2. Open Balena Etcher or another flashing tool you trust.
  3. Select the correct Pico Mini SD release file.
  4. Accept the warning about a missing partition table. That is normal for these Luckfox Pico images.
  5. Flash the image to the card.
  6. Insert the card into the device and power it on.

MicroSD has boot priority over onboard NAND or eMMC on supported devices. That means you can leave test firmware, recovery firmware or even a decoy image on the internal storage, then insert a signed MicroSD card to boot the real signer. This is useful for shipping assembled units with validation firmware and letting the user install their own final image later.

Device booting from MicroSD with secure boot not enabled
MicroSD inserted into the device while it boots

Flashing NAND with SocToolkit

For boards that use onboard NAND, you need a different workflow. On Windows, I use Rockchip’s SocToolkit. On Linux, there are command-line tools, and you can also do an offline SD-based update by putting the right files on a MicroSD card, but the USB tool is easier to demonstrate.

  1. Connect the device to a data-enabled USB port using the data port.
  2. Put the board into mask ROM / flash mode. You can do this from the firmware menu if available, or by pressing the boot button while powering on. On some cases, you may need a paper clip to reach the button.
  3. Open SocToolkit and select RV1106. Even though some Pico Mini boards are based on an RV1103, the tooling often treats them as RV1106 for this workflow.
  4. Extract the correct NAND bundle from the release download.
  5. In SocToolkit, choose search path and select the extracted folder.
  6. Confirm that it reloads all files.
  7. Select all listed firmware files and start the download.

Once flashing completes, the device should reboot automatically into the new firmware. If secure boot is enabled later, SocToolkit will reject firmware that is not signed with the accepted key.

SocToolkit showing partition list during NAND flash
Rockchip SD ToolKit partition list and download progress

Flashing Pico Pi eMMC

The Pico Pi workflow is similar, but you must use the correct Pico Pi firmware bundle because the partition layout differs.

  1. Hold the boot button while connecting the board to a data-enabled USB port so it appears as a mask ROM device.
  2. Open SocToolkit and select the supported chip option used by the tooling.
  3. Select the extracted Pico Pi firmware folder, not the Mini folder.
  4. Confirm that the files reload with the correct addresses.
  5. Start the download.

The Pico Pi is plug-and-play in terms of assembly because it does not require soldering the small board onto a custom hat. However, I have not been able to get MicroSD hot-swapping working reliably on this variant, so plan for full reboots when changing cards during testing.

Re-signing firmware with BIP85-derived keys

This is one of the most important parts of the project. The release files are signed by default with a developer key. That makes them easy to test, but it also means anyone who knows that public dev key could produce firmware that an unlocked or dev-key-locked device would accept. To make your own device more secure, you can re-sign the firmware using keys derived from your own BIP85 seed.

The good news is that this can be done on device. You do not need to keep signing keys on a computer. The workflow uses two key types:

  • An RSA key for release-level signing.
  • An ED25519 key for root filesystem signing.

Both can be derived from BIP85 paths on your seed. In the demo, I use index 0 for both, but they do not have to be the same path if you prefer separate derivation indices.

Step-by-step re-signing workflow

  1. Put a MicroSD card with the release bundle into the device.
  2. Boot the signer.
  3. Enter or select your seed in the appropriate signing context. Do not use a public or well-known test seed for a real locked-down device.
  4. Enable Luckfox build tools if it is off by default.
  5. Open the re-sign release option.
  6. Choose to derive keys from BIP85.
  7. Select the RSA key index and ED25519 key index you want to use.
  8. Run the re-sign process.
  9. Wait for key derivation and signing to complete. On Luckfox Pico devices, this is much faster than on a Raspberry Pi Zero.

You can also check a release before re-signing it. The check screen tells you what hardware the bundle is for, whether signatures are valid, and whether it was signed with a published dev key. That is useful if you want to verify a download before trusting it further.

Device showing release signature verification
Signature verification screen identifying the boot key

What secure boot actually protects against

Secure boot does not make your device magically safe from every attack. It solves a specific problem: after you have verified firmware, you want confidence that the software on the device has not been tampered with while it was unattended.

A standard Raspberry Pi-based SeedSigner gives you very little protection if someone swaps or modifies the MicroSD card after you leave it alone. With secure boot enabled, the board verifies signed components at startup and rejects firmware that is unsigned or signed by a key it does not accept.

If you lock the device to your own BIP85-derived keys, an attacker would need your seed to produce firmware your device will accept. If they already have your seed, the situation is much worse anyway, so secure boot is not a substitute for protecting your recovery words. It just raises the bar against casual or physical tampering with the firmware image.

There is also an important operational point: re-signing firmware and arming e-fuses are separate steps. You can test re-signing before permanently locking the board down. That matters because once secure boot is locked to a key, flashing incompatible firmware will fail.

Smartcard support and ShieldSigner hats

The builds in this video include smartcard reader support through ShieldSigner-style hats. Flashing existing Java applets works, as do uninstall and related GPG/smartcard tooling. However, building Java applets on Luckfox Pico is not supported yet because the environment needed to compile them does not work there at this stage.

If you are using a thin integrated smartcard reader, pay attention to card orientation. The contacts need to face the same direction as the visible contacts on the reader. On some hats, that means the card goes in one way; on others, it goes in the opposite way. If in doubt, line up the gold contacts visually before inserting the card.

Smartcard hat connected for ShieldSigner testing
ShieldSigner smartcard hat mounted on a Luckfox Pico build

Beta status and what to expect

This is still beta hardware and firmware. The goal of the beta period is to let people test builds, report issues and confirm that the workflows are stable before I roll a proper release. If you want to participate, check my GitHub repository for the current pre-release assets, KiCad files, case files and build notes.

If you order parts from the store, please do not rush into ordering large quantities just because the boards are available. The point of beta testing is that other people should use it before I scale production. If you want a cheap test setup now, this may be a good time to try one or two units and report what you find.

Conclusion

The Luckfox Pico gives SeedSigner-style builders a practical alternative when Raspberry Pi Zero boards are unavailable. The Mini is small enough for a low-profile ShieldSigner build, the Max and Pi variants give more room for development, and secure boot adds real value by verifying firmware at startup. With BIP85-derived signing keys, you can re-sign releases on device and lock your board to only accept firmware tied to your own seed.

For advanced DIY users who are comfortable with beta hardware, this is a useful path forward: build it, test the normal workflow first, verify signatures, then decide whether you want to permanently arm secure boot.

Build your own hardware wallet

Kits, smartcard hats, cases and parts for SeedSigner, ShieldSigner, Specter DIY and Satochip builds, tested with the firmware shown in these videos and shipped from Canada.

Found this useful?

These guides are free and ad-free. You can support them by sharing them, subscribing on YouTube, or sending a tip.

Stuck on this?

Book a one-hour session and I’ll walk you through it, or ask about a trusted recovery.

Recovery guides

More guides