Here I have a couple of different Raspberry Pis running piTrezor. This is a Raspberry Pi 4 connecting using a USB-C port. This is actually a 2012 Raspberry Pi Model A running piTrezor. And this is a Pi Zero, actually using the same hardware configuration that I ran through on my SeedSigner video.

All of these devices will work using the standard Trezor software, as well as anything else that a Trezor One would normally work with. piTrezor is a neat little project that allows you to make a DIY Trezor One using a Raspberry Pi. In this article, I’ll run through how to use a standard Raspberry Pi 4 with no hardware modifications whatsoever, how to run it just using a sort of standard LCD hat, and how to use the SeedSigner hardware to run piTrezor.
You can also follow along in Watch the video. If you are new to DIY crypto setups, be careful: this is an advanced-user project. You need to understand Raspberry Pi setup, SD card flashing, and self-custody security tradeoffs before you put any meaningful funds on a device like this.
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.
What piTrezor actually is
piTrezor is a modified version of the official Trezor One emulator that is maintained and distributed by Satoshi Labs. It has modifications that allow it to run over a USB port on a Raspberry Pi, rather than just being software you run on your PC.
It also includes changes that let it use a variety of different LCD displays, plus some small security improvements around how the emulator runs. One important change is that it can use the hardware random number generator on the Raspberry Pi. The core wallet functionality itself is untouched. Like all things with the Trezor One, this is based on some of the most battle-tested code in the ecosystem, and it works with anything that would normally work with a standard Trezor One: Trezor Suite, other software wallets, and compatible tools.
In terms of hardware, you will need either:
- Raspberry Pi Zero
- Raspberry Pi A or A+
- Raspberry Pi 4B
Basically, any Raspberry Pi that supports USB gadget mode can be used. I have also added some of my own modifications to piTrezor so it can run on the standard SeedSigner hardware, and I have added functionality to choose Bitcoin-only firmware.

Downloading and verifying builds
Just like with SeedSigner, you need to download the software and flash it to a microSD card. I have also pushed some of my improvements to the official repository, but I had not heard back from the author about whether they would be incorporated at the time of recording.
For the official build, the main integrity check is that the MD5SUM matches what is listed on the piTrezor website over at pytrezor.com. You can also make sure these match the releases on their official GitHub.

For my modified build that runs on standard SeedSigner hardware, I did not want to get into the long-term mess of supporting and distributing trusted GPG keys. Instead, I signed a Bitcoin message containing the SHA-256 sums of the binaries I distributed for my fork of piTrezor.
So if you are using one of my released builds, go to my GitHub fork of piTrezor and open the releases page. You will see the three binaries you can download, along with:
- The SHA-256 sums of those binaries
- A Bitcoin message signature
- The address to verify against
That address is the standard tip address I use for Bitcoin stuff on various videos and on my website. You can verify this using Electrum, Sparrow, or even a web-based Bitcoin verification tool. Put in the Bitcoin address, paste the message, paste the signature, click verify, and it will tell you whether the signature is valid.

Once you have verified that, you can save the files to your desktop. If you have something like 7-Zip installed, you can right-click the file on Windows. On Windows 11, you may need to choose “Show more options” first. Then you can get the SHA-256 sum of that file and compare it with the value in the verified message.
That gives you a reasonable level of confidence that the binary matches what I distributed. That said, if you are looking to store a decent amount of funds on this, I would recommend building it yourself. That way, you do not have to place trust in me or anyone else. You can actually verify the code and make sure there is nothing nasty or malicious in there.
Building from source for higher trust
The whole process of building will take a few hours. It will require a few gigabytes of RAM and about 50 gigabytes of hard drive space.
Once you have installed all the requirements for Docker, clone the repository, paste it into your terminal, and go into that folder. You will see a few files. Then run:
sudo build-pitrezor.sh
You can then type in the build you want. If you want one for SeedSigner, you can just type seedsigner. That will pre-configure everything you need for SeedSigner, including latest firmware, Bitcoin-only firmware, and configuration to use the SeedSigner display hat. Then choose your Raspberry Pi model, such as raspberrypi0, hit enter, and walk away.
Come back in five or six hours and it should be finished. It will have produced a file similar to what you get from the official GitHub binary releases, which you can then feed into something like Balena Etcher.

Flashing the microSD card
Select the file you want to flash, connect your microSD card in a standard USB card reader, and hit flash. If you have any issues with that on Windows, often a reboot will be all you need, or maybe try a different PC.

HDMI plus keyboard setup
The first setup I want to look at is running piTrezor using an HDMI monitor plus a keyboard. This is the simplest way to run piTrezor. There are no hardware modifications or extra hardware required at all. It is also the most discreet of all these options, because a stock Raspberry Pi is all you need.
This can be a standard Raspberry Pi 4, but any of the different supported models will do. The amount of RAM does not matter for this basic setup. I do have an LCD hat on mine in some shots, but ignore that for now; it does not actually need to be there.
Steps for HDMI plus keyboard mode
- Connect a micro HDMI adapter so you can connect the Raspberry Pi to a standard HDMI monitor or TV.
- Add any USB keyboard. In my example, I am using a wireless USB receiver so I can use a wireless keyboard.
- Use a standard USB-C cable to connect from the Raspberry Pi 4 to your PC.
- Boot the device and let it start normally.
- Open Trezor Suite on your computer.
You should see the standard Raspberry Pi boot process happen on the screen, then piTrezor running and outputting its display over HDMI. Once connected, Trezor Suite detects the piTrezor just as a standard Trezor.

From there, you can set it up like any other Trezor. If I say “Setup Trezor,” it detects the firmware. In this example, it is running universal firmware at the moment. Continue, create a new wallet, choose standard wallet, and back up. You get the standard Trezor output on the screen.
If you are also running an LCD hat, you can see the same input on both displays. That is very useful if you are trying to debug something. The left and right buttons correspond to the standard left and right buttons on a Trezor One. If we want to create a new wallet over here on our piTrezor, pressing the right arrow confirms it.

One important warning: you need to make really, really, really sure that you are doing this in a place where no one can see the screen or monitor. It is quite different from having your Trezor seed words displayed on a small hardware wallet screen compared to a full-size monitor or TV. Be very careful about who is watching, what cameras might be watching, and whether anyone could photograph the display while you are backing up or restoring.
Native OLED/LCD hat configuration
Native LCD hats are good if you have some SPI or I2C screens kicking around, along with digital push buttons. You can either make your own setup using breadboard-style hat adapters, or use a retail LCD hat that sits nicely on top of a Raspberry Pi.

The funny thing with these Raspberry Pi A boards is you will actually need a USB-A to USB-A connection lead to connect them up. You might have some of these kicking around, or you can pick one up from Amazon. That just goes in.
With these LCD hats, you will need to edit the piTrezor.config file on the microSD card. In my examples, both devices are using an SH1106 SPI display. For both of them, I had to edit the config to change the OLED type to number 5.
When using native OLED hats, also make sure that the mirror HDMI function is set to zero.
For buttons, my preference for these style of displays is to set up your yes and no buttons as:
- Press the joystick on one side
- Press down on the button on the other side
I mapped this to GPIO functions 20 and 13. These numbers do not actually relate to the pin number; they relate to the GPIO function for those pins. You can check whether the buttons are correct based on the create wallet screen. It will ask you yes or no. If your two buttons are backwards, or either of them does not work, you should find out at this point. For example, if you cancel, it should go back.

Once the buttons are working and the screen is working, this will behave just like a standard Trezor from there.
SeedSigner hardware setup
The last setup I want to look at is using SeedSigner hardware. That is basically a Raspberry Pi Zero plus a Waveshare color LCD hat. You can use the Raspberry Pi Zero 1.3 and the Waveshare 240×240 1.3inch LCD Hat for Raspberry Pi.
By default, the SeedSigner branch uses Bitcoin-only firmware. But if you want things like altcoin support for Ethereum or other chains, or U2F, you will need to run universal firmware.
The SeedSigner build is a little bit different from the others because I added modifications that mirror the HDMI output onto the LCD screen. Once you have flashed one of the SeedSigner builds onto the microSD card, connect your SeedSigner with a standard micro USB cable.
When using SeedSigner normally, you will usually use the top micro USB port, because the other one is power only. If you want to run your SeedSigner totally air-gapped, that is the best one to use. However, for piTrezor, we actually need to use the middle micro USB port, because it not only delivers power but also has the data lines connected that piTrezor needs to communicate with your PC.

I disconnected the other Raspberry Pis, then went into Trezor Suite and plugged in the Raspberry Pi Trezor with the SeedSigner hat. Once it booted, Trezor Suite detected it without issue. It also detected the Bitcoin-only firmware, because that is the default for the SeedSigner build. Just like the others, you can create a new wallet or restore an existing seed.
For this setup, I went with left joystick press-down for cancel and the right middle button for yes. So we can confirm actions as normal. You end up with all four of these Trezor devices connected, and Trezor Suite happily detects all of them. As far as Trezor Suite is concerned, they are functionally the same.

Advantages of using piTrezor
A big advantage of piTrezor, just like SeedSigner, is that it is very easy to use totally discreetly. If you are happy to use HDMI plus keyboard mode, then it is just a totally stock Raspberry Pi. That makes it a fantastic way to have something more secure than just a software wallet without having to punch in your address and name and order some crypto-specific hardware that gets shipped to your house or workplace.
piTrezor is also a lot more forgiving than SeedSigner, because you can use all of the documentation and software already supplied by Trezor. This lets you do things like verifying seed derivation and address derivation between different implementations to make sure everything is doing what it should. It also gives you an option to perhaps recover your seed phrase from your SeedSigner in a more secure environment than just shoving it into a software wallet if, for whatever reason, you run into trouble and are trying to debug it.
piTrezor can also make use of existing hardware you already have, especially if you already own a SeedSigner. Being able to reuse the hardware makes the SeedSigner a more attractive proposition, given that Raspberry Pis are still quite expensive at the moment.
Perhaps the most powerful feature of piTrezor is that it allows you to easily create a multi-signature Bitcoin wallet where you are mixing software and implementations from entirely different vendors with entirely different codebases. If there is something underlying that is malicious or buggy in either device, such as SeedSigner or piTrezor, your multisig wallet can still be secure.

Another advantage is that it gives you a U2F device: a hardware security key that you can use to boost the security of your logins for online websites and other services. On a Trezor One, however, U2F is not protected by a PIN or passphrase. That is an important limitation to understand before using it this way.

Disadvantages and security limits
We need to say straight out of the gate that the physical security on piTrezor is not good at all. Your wallet data simply lives on the microSD card. That is really different from SeedSigner, because one reason SeedSigner can be secure on a Raspberry Pi is that it is stateless and wipes itself every time you turn the device off. piTrezor is not like that.
The data on the microSD card is protected by your device PIN, but it is probably a really good idea to add a BIP39 passphrase to your wallet. That means even if someone fully decrypted the information on the microSD card for your Trezor, they would still not be able to access your funds.
Running piTrezor will still provide excellent protection against malware and remote attacks, such as phishing websites. It gives you a second trusted screen on which you can verify transactions and so on. But be really clear: you do not want to leave it lying around. It is not tamper-proof, and it is not tamper-evident at all. This is primarily protecting you against remote attacks.
Trezor also issues warnings for their emulators saying that this is code they do not deliberately harden the same way as physical Trezor hardware. It should also be clear that there is a much larger attack surface with a device like this running as a USB gadget than there is with a standard Trezor. The sky is the limit in terms of what a device like this could actually do if you downloaded some really malicious software and flashed it to the microSD card, something that initially looked like piTrezor but then did something very malicious afterwards, or if the device was tampered with without your knowledge.

Another disadvantage is that firmware updates cannot happen automatically. piTrezor is not running a normal bootloader in the same way. You will see this when you try to run a firmware update: the device may just restart. For piTrezor, you need to manually reflash your microSD card using updated software and restore your wallet from your recovery seed. Just be really sure that you run a full recovery check to make sure your seed is valid before doing that.

The final limitation is that you are depending on volunteer work to push updates from Satoshi Labs. When new firmware comes out for Trezor, it might take a while before updated firmware arrives for piTrezor. The developer and maintainer for piTrezor is normally pretty quick about this, but if you are using this software, definitely take time to send a tip to support continued development of the tool.
Summary and conclusion
piTrezor is a really great illustration of the power of open source software. Even if you lost your physical Trezor One, Satoshi Labs had gone out of business, and you could no longer source yourself a physical Trezor One, you could easily spin up piTrezor on something like a Raspberry Pi to access your funds as though nothing happened.
It is also really handy in situations where you might not want to, or be able to get, the retail hardware. That said, using any kind of DIY hardware wallet is certainly something for advanced users. For the vast majority of users, you are far better off ordering a retail hardware wallet and using that with vendor-supplied software. It is really important that open source and DIY things like this exist, but they are things you need to take time to understand and do securely and properly.
For me, I do a lot of recoveries, so it is always handy to have some spare Trezors on hand that I can wipe. I will certainly be using this quite a bit. If you are someone who has done a DIY build for piTrezor, I would love to hear about what you did in the comments. Likewise, if you are trying to get it working and run into trouble, leave a question and I will do my best to reply to everything.
If your situation is more about lost access, damaged backups, or complicated recovery work rather than building a DIY wallet, see recovery services and consultations. Best of luck, stay safe, and I’ll see you later.
Questions from viewers
Common questions from the comments on this video, with my answers.
Can I use a generic, cheap OLED or LCD screen instead of the official HATs?
Yes, you can. If you are using the 'Universal Firmware,' it should work with standard displays like 0.96-inch OLEDs (1306 controller) connected via I2C or SPI. You just need to wire up a few buttons for navigation. It’s a great way to build a prototype without buying specific hardware.
Which piTrezor build should I use if I have a Raspberry Pi 3A+?
You should test the 'Pi1A' build first, as it is designed for that board. The 'SeedSigner' build is specifically for the color Waveshare hat and likely won't be the right fit for a standard Pi 3A+ setup unless you are using that specific display. Keep in mind that the Yocto-based builds are very stripped down, so they don't include networking features like Bluetooth by default.
Does the Raspberry Pi 400 support USB OTG for this project?
The Pi 400 does support OTG via its USB-C port, similar to a standard Pi 4. However, because it runs a CM4 module under the hood, it requires a targeted build to work correctly. I haven't released a specific build for it yet, but it is technically possible. (Apps and tools change, so check the current version if something looks different.)
How can I make the wallet more secure against physical theft or border searches?
The biggest advantage here is discretion. You can split the device into two parts: the Raspberry Pi and the SD card. If someone finds the Pi, it's useless without the SD card. You can hide the SD card separately or carry it on your person while leaving the Pi behind. This makes it much harder for anyone to perform a quick 'wrench attack' compared to carrying a single, obvious hardware wallet. Full OS encryption is also an option to mitigate risks further, though it is a bit messier to set up on a Pi than on a standard Linux system.
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.







