Keystone Forgebox Review: Running Specter-DIY on BYO-Firmware Hardware

Keystone Forgebox: A Bring-Your-Own-Firmware Wallet (Running Specter-DIY)

It has certainly been a bit of a rough year for self-custody. The trust that people are asked to place in hardware wallet vendors is more top-of-mind than it has been in quite some time. In response to this climate, I’ve been looking at devices that offer a different approach to security and transparency.

Today, we are looking at the Keystone Forgebox. This is not your standard retail hardware wallet. It is a developer-oriented device that ships with the exact same hardware as the Keystone 3, but without any pre-installed firmware. You have to flash the software yourself, and you are free to run a variety of open-source or custom firmware on the device.

In this article, I will walk you through the full setup process, from unboxing to generating your own signing keys, and finally demonstrate running a community port of Specter-DIY on the hardware. If you prefer watching, you can Watch the video.

What Is the Keystone Forgebox?

The Forgebox is essentially a “bring-your-own-firmware” (BYOF) hardware wallet. While the physical casing, screen, and internal components (MCU and secure elements) match the retail Keystone 3, the bootloader allows users to sign and flash their own code.

This is aimed at advanced users, developers, and those interested in hardware hacking who want the benefits of an integrated hardware stack—like tamper protection capabilities—combined with the freedom of DIY open-source software.

Unboxing and Genuine Check

When you open the box, you get the device and a USB-C cable. Notably, there are no seed backup instructions or standard user manuals included, as this is a developer tool. The device comes with a translucent case, which is a nice touch for visibility.

One important note regarding verification: Keystone recently leaked the verification keys used to verify the genuineness of their devices on their website. They have since fixed this with new hardware batches. However, because my sample was received before the fix, the standard online verification process flagged the device as potentially using old, leaked signing keys.

Despite this warning, the verification process still completed successfully, confirming the bootloader and factory firmware integrity. This highlights a current challenge in the industry: even legitimate devices can trigger warnings due to past vendor errors. Always stay updated on news regarding your specific hardware provider.

Setting Up the Forgebox CLI

To interact with the Forgebox, you need to use the forgebox CLI tool. This is managed via npm.

  1. Install the CLI: Run the installation command via npm. Ensure Node.js and npm are installed on your system.
  2. Verify Connection: Once installed, add the tool to your system path. Connect the device via USB.
    • Tip: If the device isn’t detected (no USB devices found), try a different USB cable. In my testing, a faulty cable was the initial issue.
  3. Check Status: Run forgebox status. This should return the model (KV3A) and hardware serial number, confirming the device is reachable and inspecting its basic information.

Generating and Registering Signing Keys

This is the most critical step for security. The Forgebox uses a key-based system to authorize firmware updates. You must generate a key pair and register the public key on the device. From that point on, the device will only accept firmware signed by this specific private key.

Important Security Note: You must back up this private key file securely. If you lose it, you cannot flash new firmware onto the device. Unlike a standard wallet where you back up a seed phrase, here you are backing up the cryptographic authority to update the device’s operating system.

  1. Generate Keys: Run forgebox keygen. This creates two files: a public key and a private key.
  2. Backup: Immediately copy these files to a secure location. Do not store them on the same machine as your primary trading environment if possible.
  3. Register Public Key: Use the CLI to register the public key on the device.
  4. Confirm on Device: The device will display the public key. Compare it visually with the one on your computer to ensure they match. Slide to confirm on the device screen.

Once this is done, the setup is complete. Any future firmware you flash must be signed with the corresponding private key.

Flashing Firmware: Hello World Example

Before jumping into complex wallets, it’s good practice to test the flashing mechanism with a simple example. Keystone provides a “Hello World” repository to test this workflow.

  1. Clone the Repo: Clone the example repository from GitHub.
  2. Build with Docker: Use Docker to build the firmware binary. This ensures a consistent build environment regardless of your local OS (Linux, Windows, or Mac).
  3. Sign the Binary: Copy the generated .bin file and sign it using your previously generated private key. The output will be a signed firmware file (e.g., forgebox.bin).
  4. Flash via microSD:
    • Copy the signed .bin file to a microSD card.
    • Insert the card into the Forgebox.
    • Hold the power button to enter recovery mode.
    • Select “Update.” The device will detect the new firmware and begin the installation.

After a reboot, you should see the “Hello World” demo running. This proves that your key registration and signing workflow are functioning correctly.

Running Specter-DIY on the Forgebox

Now for the interesting part. I spent a few days working with AI agents to port Specter-DIY to the Forgebox hardware. Specter-DIY is a popular open-source firmware for Bitcoin hardware wallets, known for its modularity and support for various peripherals.

The form factor, screen resolution, and hardware of the Forgebox are a very good match for Specter-DIY. Below is how the experience works.

Fingerprint Biometric Unlock

One of the standout features of the Keystone hardware is the fingerprint reader. In this Specter-DIY port, I enrolled a fingerprint directly onto the device.

  • Startup: Instead of entering a PIN every time, you simply tap your finger on the sensor.
  • Security: The biometric data is processed locally. Once recognized, the wallet unlocks.
  • Seed Storage: The seed is stored across the MCU and the two secure elements, exactly as it would be on a retail Keystone. This distributed storage adds a layer of resilience against single-point failures.

Air-Gapped Signing with Sparrow

For transaction signing, the Forgebox uses the built-in camera rather than a dedicated QR scanner module. This is similar to how many smartphone-based wallets operate.

  1. Pairing: Pair the Forgebox with Sparrow Wallet on your desktop or mobile device. The pairing process is identical to pairing any other Specter-DIY device.
  2. Creating a Transaction: In Sparrow, create a transaction (e.g., sending funds to a receive address).
  3. QR Scanning: On the Forgebox, select “Scan QR Code.” Point the device’s camera at the QR code displayed on Sparrow.
  4. Signing: The transaction details appear on the Forgebox screen. Verify the amount and recipient. Sign the transaction.
  5. Broadcast: Scan the resulting signature QR code back into Sparrow to broadcast the transaction.

Performance Note: The signing process is slightly slower than the standard MCU implementation on some other Specter devices, but it remains very usable for daily transactions. The air-gapped nature means your seed never touches an internet-connected device.

USB Signing with Liana

If you prefer USB connections over QR codes, the Forgebox also supports USB workflows. I tested this with Liana Desktop.

  • Enable USB communication in the Specter-DIY settings on the Forgebox.
  • Connect via USB.
  • The device presents itself as a standard Specter-compatible device.
  • You can sign transactions directly over the USB connection within Liana.

This dual-mode capability (Camera QR + USB) makes the Forgebox versatile for different user preferences.

Important Limitations and Caveats

While this setup is impressive, there are a few things you need to know before diving in:

  1. No Official Tamper Detection: The retail Keystone 3 has a physical tamper detection mechanism that halts the boot process if the device is opened. In this specific Specter-DIY build for the Forgebox, this feature is not currently implemented. If you physically open the device, the software does not automatically wipe secrets or halt execution in the same way the official firmware does. If you require this level of physical security assurance, you may need to implement your own logic or stick to the official firmware.
  2. Not Officially Supported: This is a community port. It is not an officially supported version of Specter-DIY by the main project maintainers, nor is it the official Keystone firmware. It is a proof-of-concept and a useful reference for developers.
  3. Retail Devices Cannot Do This: You cannot take a standard retail Keystone 3 and do this. Retail devices are locked to Keystone-signed updates only. The Forgebox is specifically provisioned differently at the factory to allow third-party key registration.
  4. Supply Chain Considerations: Like all hardware wallets, you are trusting the supply chain. The Forgebox is currently listed as out of stock with a contact email, suggesting it may be produced in limited batches or upon request. Be cautious when purchasing from secondary markets.

Where to Find the Code

If you have a Forgebox and want to try this yourself, I have uploaded the code to a branch of Specter-DIY on my GitHub.

The repository includes: * The modified Specter-DIY source code for the Forgebox. * Instructions on how to build, sign, and install the firmware. * Documentation on how the hardware is configured, including insights gained from analyzing the bootloader.

This documentation is particularly useful if you are using AI coding agents; pointing them at this repo gives them a solid starting point for implementing other projects on the Forgebox platform.

Conclusion

The Keystone Forgebox is a fascinating piece of hardware. It bridges the gap between the polished, closed ecosystem of retail hardware wallets and the flexible, open world of DIY development.

By allowing users to register their own signing keys, Keystone has created a device that empowers advanced users to audit, modify, and run their own software while still benefiting from the robust physical design of the Keystone 3. Running Specter-DIY on it demonstrates that the hardware is capable of supporting rich, modern Bitcoin workflows, including biometric unlock and air-gapped signing.

However, it is crucial to remember that this is a developer tool. It lacks the out-of-the-box physical tamper detection of the retail version, and the software is a community effort. It is not for the average user who wants a plug-and-play experience. But for those who want to understand exactly what is happening under the hood, or who wish to run custom open-source firmware on trusted hardware, the Forgebox is a powerful option.

As always, do your own research, back up your keys (both seed and firmware signing keys), and proceed with caution. Stay safe.

Choosing a hardware wallet?

See how this device stacks up against the others I’ve tested: security model, supported coins, backup options and price.

Some links on this site are affiliate links: if you buy through them I may earn a commission at no extra cost to you. It doesn’t change what I recommend.

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