ERA Wallet Unbox, Setup Guide, Demo & Review

ERA Wallet Unbox, Setup Guide, Demo & Review

In this post, I’ll walk through the ERA Wallet in detail: what’s in the box, how to set it up, how the air-gapped workflow feels in practice, and where you need to be careful. If you’d rather watch the full walkthrough, Watch the video.

Full transparency: this device was sent to me for review. I did not know what to expect before opening it, so I’m reporting what actually happened during testing, including one issue that could seriously affect how you back up your wallet if you use SLIP39 and a BIP39 passphrase.

What’s in the box?

The ERA Wallet comes with:

  • The ERA hardware wallet
  • A wireless charging pad with USB-C
  • Three NFC recovery cards
  • Paper recovery sheets for writing down a 24-word seed phrase
  • An instruction manual / paperwork booklet
ERA Wallet unboxing layout showing device, recovery cards, charger, box and manual
Unboxed contents: ERA wallet, three NFC recovery cards, wireless charger, packaging, and documentation

The hardware itself is very minimal. It has an e-ink display, one button, no visible ports, and a tiny pinhole camera at the top edge for scanning QR codes. That last part matters because this is an air-gapped device: it does not connect to your computer or phone over USB/Bluetooth for signing. Communication happens through QR codes on screen.

ERA Wallet front showing e-ink display and single button
Front of the ERA wallet with e-ink screen and one physical button

First power-on: use the charger correctly

Because there are no ports, you have to place the device on the wireless charging pad to turn it on. I initially had trouble because the device was not aligned properly. The key is that it needs to sit fully on the correct magnetic contact point at the top of the pad. If it only clicks into a lower position, it may not charge or wake up reliably.

ERA Wallet being placed onto wireless charging pad
Placing the ERA wallet onto the wireless charging pad to power it on

Once aligned correctly, the device powers on and you can begin setup.

Setup: app install, firmware update, authenticity check

The first on-device step is to scan a QR code with your phone and install the ERA Wallet companion app. After installing the app, I was prompted that an update was available.

Phone next to ERA wallet showing QR code for downloading companion app
Scanning the device QR code to download the ERA Wallet companion app

Firmware update experience: mixed results

This is where my first real frustration came in. On iPhone, the NFC firmware update was painful. The progress advanced very slowly and required a lot of repeated tapping. In that moment, it felt like one of the worst firmware update experiences I’ve seen on any hardware wallet.

I then tried Android, and it worked much better. Once the phone was positioned correctly over the NFC zone, the update progressed normally. If you’re doing this setup, I would strongly recommend using an Android device for the initial firmware update if possible.

Android phone showing ERA Wallet app firmware update progress
Android companion app updating the ERA wallet over NFC

Authenticity check

After the update, the next important step is the authenticity check. The workflow is:

  1. Open the ERA app on your phone.
  2. Select Authenticity Check.
  3. Scan the QR code shown by the device with your phone.
  4. Then scan the phone-generated QR code back onto the device using the device camera.

This step verifies that you are talking to a legitimate device before continuing setup. It is a good security practice, but it did depend on ERA’s online verification infrastructure being available. During my testing, I hit a period where the authentication server was down and I had to wait for it to be restored before continuing. That is not ideal, especially during first-time setup, but the team responded quickly when I reached out.

ERA app authenticity check screen next to device showing camera prompt
Running the ERA Wallet authenticity check using the companion app

PIN setup and analog entropy collection

Next, you create a device PIN. In my test, the default PIN layout was not scrambled at first. You can later enable Dynamic PIN, which randomizes the button positions to make shoulder surfing harder. That is off by default, but I would recommend turning it on if you care about physical security.

After setting the device PIN, ERA asks you to collect analog entropy before generating private keys. The process includes:

  1. Swiping on the touch area
  2. Shaking the device
  3. Moving the camera around

This is a practical way of adding extra randomness from human motion and environmental input rather than relying only on an internal RNG. It adds friction, but it also makes sense for a security-focused device.

Backup options: paper BIP39 and encrypted NFC cards

ERA supports multiple backup styles. In the standard setup, you can write down your 24-word BIP39 seed phrase on the included paper recovery sheet. You can also create encrypted backups on the included NFC recovery cards.

ERA wallet prompting user to prepare recovery cards for first backup
Setup prompt asking you to prepare the included recovery cards

Each NFC card has its own PIN, and that PIN does not have to match your device PIN. In my test, I created two encrypted card backups with different PINs and left one card blank. The device also lets you verify the backup after writing it, which is a good habit.

Phone using NFC tools next to three ERA recovery cards while device confirms backup
Checking the NFC recovery cards with an NFC reader app

I checked the cards with an NFC reader app and could see that a blank card changed state after being written to. That is useful from a transparency perspective: you can tell whether a card has been programmed or not.

The device also supports reading seeds back off the cards, erasing them, and cloning them in the recovery manager. That gives you more flexibility than a single paper backup, but it also means you need to be disciplined about where those cards are stored.

Pairing with Blue Wallet for Bitcoin

ERA does not come with its own full consumer wallet app in the same way some vendors do. Instead, you pair it with third-party wallet software. For my main Bitcoin test, I used Blue Wallet.

The pairing flow was straightforward:

  1. Open Blue Wallet.
  2. Add a new wallet.
  3. Choose import / scan.
  4. Scan the QR code shown by the ERA device.
  5. Select the derivation path you want to use.
  6. Confirm that the imported watch-only address matches on both devices.
Blue Wallet add wallet screen next to ERA pairing instructions
Pairing ERA with Blue Wallet using QR code import

After importing, I verified the receive address on the phone and again on the ERA device. This is not optional if you want a secure setup. With an air-gapped wallet, your security depends heavily on checking that the address you are sending funds to is really the one displayed on the hardware device itself. If you skip this step, you lose a major advantage of using an air-gapped signer in the first place.

Receiving Bitcoin

Once paired, receiving worked as expected. I checked the receive address in Blue Wallet and confirmed it matched what was shown on the ERA screen. The default derivation path used in my test produced standard native Segwit bc1 addresses. If you choose a different script type or derivation path, make sure both sides match.

Phone showing received Bitcoin balance next to locked ERA device
Received Bitcoin shown in the mobile wallet after address verification

Sending Bitcoin with PSBT signing

Sending also worked well for single-sig Bitcoin. The flow was:

  1. Start a send in Blue Wallet.
  2. Create the unsigned transaction / PSBT.
  3. Scan the QR code onto the ERA device using its camera.
  4. Review the transaction details on the device.
  5. Approve and sign.
  6. Scan the signed transaction back to the phone.
  7. Broadcast from Blue Wallet.
Phone showing signed transaction approval next to ERA QR prompt
Completing a PSBT-based Bitcoin send using QR code signing

This is exactly the kind of workflow air-gapped devices are supposed to be good at, and in this basic single-sig case, it worked reasonably well.

Multi-wallet support and SLIP39 backups

One useful feature is that ERA can hold multiple wallets on one device. In my test, I created a wallet with its own name, icon, and separate wallet PIN. That means you have both:

  • A device PIN
  • One or more wallet PINs

If you forget the wallet PIN, you can still recover through your backup, but that is exactly why backups need to be done carefully.

In expert mode, ERA also offers a Shamir-style SLIP39 backup option. In my test, it created multi-share backups using 20-word shares. On the surface, this looks powerful: you could split recovery across multiple cards or paper sheets and use a threshold like “any 2 of 3.”

ERA wallet showing SLIP39-related backup workflow
Backup prompt offering to save an ERA recovery card backup

But here is where things get important.

Major warning: the SLIP39 implementation is not fully standard

I found a serious issue in how ERA handles certain SLIP39 workflows, especially when combined with a BIP39 passphrase.

To put it plainly: ERA’s SLIP39 behavior does not behave exactly like current Trezor-style extendable SLIP39 in all cases. It appears to use an older or non-extendable style of Shamir backup in some paths. That matters because SLIP39 has subtle rules around how passphrase-derived seeds should be handled, and if a device does not follow the spec carefully, it can create backups that do not behave the way you expect.

What I tested

I imported a Trezor SLIP39 share into ERA. For the base seed with no passphrase active, the addresses matched between Trezor Suite and ERA. That part looked fine at first glance.

Trezor Suite next to ERA and Trezor devices for address comparison
Comparing a Trezor-backed wallet against ERA after importing SLIP39

Then I enabled the same BIP39 passphrase on both sides. That is where it broke down. The passphrase-derived addresses did not match between Trezor Suite and ERA, even though the no-passphrase addresses had matched earlier.

Side-by-side receive address comparison showing mismatch after enabling passphrase
Comparing receive addresses after enabling a BIP39 passphrase

Why this is dangerous

The real problem is not just that you may see different addresses in the moment. The bigger risk is what happens if you then create or overwrite an ERA multi-share backup based on that imported seed. In my testing, ERA offered to save a new multi-share backup after importing the Trezor share. If you accept that offer and write down or store those shares, you may be baking the wrong derivation behavior into your backups.

In practical terms:

  • Your base wallet without a passphrase can still work.
  • You may not see your passphrase-protected funds on ERA if it derives them incorrectly.
  • If you create new SLIP39-style backups from ERA after this happens, those backups may require special recovery steps or future firmware fixes to access the passphrase wallet correctly.

This is a real risk for users who:

  • Already use Trezor with SLIP39
  • Use a BIP39 passphrase
  • Import their seed into ERA
  • Then create new ERA multi-share backups from that imported state

Who is affected?

To be clear, this issue is limited to the SLIP39 Shamir backup path. It is not an issue for standard single-share BIP39 wallets in my testing. If you are using a normal 24-word BIP39 backup without passphrase-related SLIP39 import workflows, that part of the device worked as expected.

If you have already hit this problem and need to regain access quickly, I offer recovery consultations for exactly these kinds of situations: recovery services. If this affects your wallet, do not panic and do not start random experiments on connected machines. The safest path is careful offline analysis with the right tools.

Multisig testing: no support in my Sparrow test

Next I checked whether ERA can be used for multisig by connecting it through Sparrow as an air-gapped hardware wallet. For single-sig, the connection worked and I could see the relevant transactions. But when I tried to use it in a multisig context, it did not work.

Sparrow connect dialog next to ERA pairing screen
Testing ERA as an air-gapped wallet in Sparrow

So based on this test, ERA does not support multisig at least in the workflow I tried. If multisig is a core part of your self-custody plan, that alone may be enough to make you look elsewhere for now.

EVM testing: basic smart contract decoding with MetaMask

I also tested ERA on the Ethereum side using MetaMask. The device can add an EVM wallet and show some transaction details before signing. In my test, I ran a simple swap in MetaMask and ERA was able to provide basic smart contract decoding for that interaction.

MetaMask confirmation next to ERA signing screen
Basic EVM transaction review using MetaMask and ERA

This is useful because it can help you see, at a high level, what kind of action you are approving. However, your experience will depend on whether the specific contract or router is supported by the device’s decoding data. If the contract is not recognized, you may get less helpful information than you would like. In other words: this feature exists and can be useful, but it is not a guarantee that every DeFi interaction will be fully transparent to you.

Recovery manager, display, and other settings

The device also has a recovery manager where you can read seed data back from cards, erase cards, and clone them. That is handy for managing multiple NFC backups over time.

ERA wallet WALLETS menu showing existing wallets and add option
Wallet list on the ERA device

Other settings include:

  • Display brightness / front light
  • Auto lock
  • Auto power off
  • Haptic feedback
  • Dynamic PIN
  • Factory reset
  • Device info / help screens

The e-ink display is good for battery life and readability, and it has a front light option. That is actually useful compared with some other e-ink devices that are hard to read in low-light conditions.

ERA wallet display settings menu
Display settings on the ERA device

Open-source status: partially open, not fully verifiable

One area I always check is how much of the firmware you can actually inspect and build yourself. In this case, ERA’s “pro” series is only partially open source. There are proprietary components included in what is provided, and it cannot be fully compiled or deterministically verified by third parties from the available material.

In plain English: you are still relying on trust in the vendor to a meaningful degree. That may be fine for some users, but if your threat model requires full build verification, this device does not meet that bar today.

Final verdict

The ERA Wallet is a strong first product from a new company. The hardware feels premium, the interface is clean, and the air-gapped QR workflow works well enough for basic single-sig Bitcoin use with Blue Wallet. It also has some genuinely useful features:

  • Multiple wallets on one device
  • Separate device and wallet PINs
  • BIP39 paper backups
  • Encrypted NFC card backups
  • Basic EVM smart contract decoding
  • A front-lit e-ink display

But it is still very much a first-generation product, and that showed in several places:

  1. The firmware update experience was rough on iPhone and far better on Android
  2. I hit an availability issue during the authenticity check process
  3. There is no multisig support in my Sparrow test
  4. The SLIP39 implementation has a serious passphrase-related bug risk
  5. The documentation and responsible disclosure / security reporting materials are thin for a device handling real funds

If you are a beginner, I would be cautious. This device targets people who may not be power users, but it still expects you to understand important concepts like address verification, derivation paths, passphrases, and backup types. If you do not verify receive addresses on the hardware device itself, your setup is less secure than it could be — even with an air-gapped signer.

If you are an experienced user, I would say: it can work for simple single-sig Bitcoin, but do not assume its SLIP39 backups are drop-in compatible with Trezor-style workflows if you use a passphrase. That is the biggest red flag in this review.

Overall, the ERA Wallet is promising and has some nice features, but it is not yet at the level of maturity I would expect from a long-established hardware wallet vendor. It may become much better over time, but for now, you need to understand its limitations clearly before putting meaningful funds on it.

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