Foundation Devices 'Passport Batch 2' hardware wallet review

[dkbit98]

To be fair, most hardware wallets somewhat resemble either those metal wallets you put your credit cards in or PDA devices. So, it shouldn't draw too much attention. However, I'm not one for carrying hardware wallets out in the open, so I guess it's not much of an issue. At least, not the main one. I guess having a hot wallet in a hardware wallet could potentially work, and draw attention.

Nobody should carry hardware wallets with themselves everywhere, like keychain or phones, except in some special cases.
However, I consider portability to be very important when you are traveling and you need to have funds available with you all the time.
There are many cases of people being able to survive and escape war zones thanks to Bitcoin and hardware wallets.

Although, I step out every day with a wallet, debit card, and all that. So, I'm just as at risk. As long as you aren't carrying your hardware wallet with all your Bitcoin in it, and you take one that's got a small amount meant for spending or emergencies, it's the same as carrying fiat with you. Every day people see you carry fiat, and for the most part it remains safe.

It's funny how people don't care what happens with their cards, and we literally know they are stolen every day  
Even worse for smartphones, they can hold virtual cards and many sensitive information, this can certainly be used to harm you.
If we look at percentages there is much higher chance of someone get stolen wallet with cash and smartphones, than hardware wallets.
I bet that thief would not stole old Nokia-like phone from anyone

Just wanted to let you know that we've created an official Foundation account and topic for Batch 2 here:

https://bitcointalk.org/index.php?topic=5441422.0

Welcome to bitcoitnalk!
I hope you can be active here in forum and post regular updates.

[1714475601]

1714475601

[1714475601]

1714475601

[1714475601]

1714475601

[1714475601]

1714475601

[1714475601]

1714475601

[foundationdvcs]

Just wanted to let you know that we've created an official Foundation account and topic for Batch 2 here:

https://bitcointalk.org/index.php?topic=5441422.0

Welcome to bitcoitnalk!
I hope you can be active here in forum and post regular updates.

Thank you for the kind welcome!

Excited to better support our users (both current and potential) here on Bitcoin Talk, this will be a priority for us moving forward and we'll be monitoring the key threads around Foundation devices.

Expect to see software releases dropped here at the same time as publishing to Github, and any important company news etc. around Passport (+ future devices/products in their own threads!)

[n0nce]

Hello everyone,

Just wanted to let you know that we've created an official Foundation account and topic for Batch 2 here:

https://bitcointalk.org/index.php?topic=5441422.0

Thank you so much for the detailed and in-depth review, n0nce, and for driving such high-signal discussion in this thread!

Awesome, welcome to Bitcointalk! Hopefully we can also ping it at @foundationdvcs if there is something important to know directly from the 'source' in a discussion. Sure, you are welcome.

Expect to see software releases dropped here at the same time as publishing to Github, and any important company news etc. around Passport (+ future devices/products in their own threads!)

That sounds great. The official thread looks very nice, I can see your guys put some time into getting into BBCode and making it all look pretty. As well as reserving a post for firmware updates / release notes. I'm putting it right into my bookmarks!

[satscraper]

Hi, I've almost made up my mind to order Passport for myself.

I am intended to use it with Sparrow wallet connected to net via Bitcoin Core node.

In this respect, I wonder whether Bitcoin Core can  run with flag that disables its wallet?

Sparrow docs states that Bitcoin Core should not  have  disablewallet=1 flag  but I think that in the case when it used as light-weight client for Passport such flag might be a valid thing.

Is this correct?

And one more question.

Is this true that Passport does not allow for the  second PIN allocated for addresses batch generated by  SEED + password and there is a need for manual input of that password each single time  in order to have access to those addresses?

[hZti]

Thank you for the kind welcome!

Excited to better support our users (both current and potential) here on Bitcoin Talk, this will be a priority for us moving forward and we'll be monitoring the key threads around Foundation devices.

Expect to see software releases dropped here at the same time as publishing to Github, and any important company news etc. around Passport (+ future devices/products in their own threads!)

Welcome to Bitcointalk! Very awesome that you decided to join the original bitcoin community and I feel that this will only benefit your company and reputation!


Your devices are very promising and have a lot of great features. They somehow look a little bit like an old phone, which I can not decide if it is a good thing or a bad thing Is there a specific reason for that design choice?

[n0nce]

I am intended to use it with Sparrow wallet connected to net via Bitcoin Core node.
In this respect, I wonder whether Bitcoin Core can  run with flag that disables its wallet?

Sparrow docs states that Bitcoin Core should not  have  disablewallet=1 flag  but I think that in the case when it used as light-weight client for Passport such flag might be a valid thing.

If Sparrow states that it can't connect to Bitcoin Core when the flag is set to 1, they probably have a good reason to do so. I haven't looked into that myself, but I believe that if you disable Bitcoin Core's internal wallet, that disables a lot of functionality which is also required for connecting a different wallet (e.g. Sparrow) to it.

Anyway, I don't get why you'd want to disable the Bitcoin Core wallet in the first place. As long as you don't send funds to it, turning it off won't really make you any more or less secure.

And one more question.

Is this true that Passport does not allow for the  second PIN allocated for addresses batch generated by  SEED + password and there is a need for manual input of that password each single time  in order to have access to those addresses?

If you use a mnemonic passphrase, you have to enter it every time you reboot, but otherwise you don't need to enter it when using the device.

Here you can see the official Foundation Devices documentation of this feature, which includes a video:
https://docs.foundationdevices.com/passport/more#enter-passphrase

[satscraper]

I am intended to use it with Sparrow wallet connected to net via Bitcoin Core node.
In this respect, I wonder whether Bitcoin Core can  run with flag that disables its wallet?

Sparrow docs states that Bitcoin Core should not  have  disablewallet=1 flag  but I think that in the case when it used as light-weight client for Passport such flag might be a valid thing.

If Sparrow states that it can't connect to Bitcoin Core when the flag is set to 1, they probably have a good reason to do so. I haven't looked into that myself, but I believe that if you disable Bitcoin Core's internal wallet, that disables a lot of functionality which is also required for connecting a different wallet (e.g. Sparrow) to it.

Yeah, you are correct.

Sparrow refuses to connect to Core with that flag.

I have already checked this

[
If you use a mnemonic passphrase, you have to enter it every time you reboot, but otherwise you don't need to enter it when using the device.

Here you can see the official Foundation Devices documentation of this feature, which includes a video:
https://docs.foundationdevices.com/passport/more#enter-passphrase

I have 20 characters password that serves as extension to my SEED and  in my view it s very inconvenience to enter password every time when rebooting.  

I need this password as a second layer of security to my funds.

If it is not top secret, what software wallet do you personally use with Passport?

[foundationdvcs]

Thank you for the kind welcome!

Excited to better support our users (both current and potential) here on Bitcoin Talk, this will be a priority for us moving forward and we'll be monitoring the key threads around Foundation devices.

Expect to see software releases dropped here at the same time as publishing to Github, and any important company news etc. around Passport (+ future devices/products in their own threads!)

Welcome to Bitcointalk! Very awesome that you decided to join the original bitcoin community and I feel that this will only benefit your company and reputation!


Your devices are very promising and have a lot of great features. They somehow look a little bit like an old phone, which I can not decide if it is a good thing or a bad thing Is there a specific reason for that design choice?

The main reason is to make it a much more approachable and familiar device to people new to Bitcoin hardware wallets than the other options out there. We want people to pick it up and immediately understand the basics of typing, navigation, etc. through familiarity with old cell phones.

Very much an intentional design choice  


Sharing this from the official Passport thread as it's a massive new update and wanted to be sure everyone saw it! If you're not following that thread yet, you can do so here:

https://bitcointalk.org/index.php?topic=5441422.0

The latest version of Passport firmware, v2.1.0, has been released!

Please note that this is our largest release in some time and also brings Founder's Edition up to date with Batch 2 devices, unifying our firmware. As this is such a large update, we'd love for you all to test it as much as you can before we announce it more widely.

Highlights of this release:

- Backporting v2.1.0 firmware to Founder’s Edition
- Sending to Taproot addresses
- A new Key Manager Extension for BIP 85 and Nostr key support and export
- BIP 85 SeedQR exports

For the full release notes, browse Github or read our blog post below:

https://foundationdevices.com/2023/05/passport-version-2-1-0-is-now-live/

NOTE: Since we are now releasing both firmware files from the same repo, the file naming has changed slightly. "Batch 2" devices use the same naming scheme for firmware as before:

Code:

v2.1.0-passport.bin

but Founder's Edition is now named explicitly to avoid confusion:

Code:

v2.1.0-founders-passport.bin

[satscraper]

A few questions:

1)  What does "Erase Passport" do, erases SEED, nothing else?

2) As I got it if I setup my password and do after that backup on microSD the relevant encrypted 7-zip file will hold solely the SEED but not SEED+password, is this correct?

3) If I create a few accounts how can I move between them on Passport?

4) On default Passport creates accounts with native Segwit addrs. How account with nested Sefwit addrs can be created?


P.S.Pairing device  with 3rd parties  wallets via animated QR is still pain in the ass. I have tried it with both Spectre and Sparrow and neither  attempt succeeded. Pairing via micro SD works as it should be.

[n0nce]

~

I would honestly recommend you to ask these questions in the official Foundation Devices Passport thread, now that it exists.

[1] As far as I know, yes. There is not much more that one may want to delete. The main difference from a fresh, new Passport is that you don't get the original 'walkthrough' again with the supply chain validation and whatnot. To the best of my knowledge, this is intentional to give users the ability to tell whether their Passport had been set up and reset before, or whether it comes untouched from the factory.
[2] I don't think the SD backups contain BIP-39 passphrases.
[3] Where did you create those accounts? Are you talking about an imported seed? I'd highly advise against importing a seed and recommend creating a new one, on-device and transfering funds on-chain.
If you still decide to import a seed which has different funded accounts (derivation paths) on it, they will reappear by 'creating' them on Passport again.
What wallets do when you 'create new accounts' is just calculating the deterministic wallet at the next (or chosen) index and displaying its addresses (and balances). Nothing is actually 'created' in that sense, think of it more as 'displaying' a certain (hidden) account.
[4] I don't think nested SegWit is supported.

Regarding pairing: are you running the latest firmware?

[satscraper]

I would honestly recommend you to ask these questions in the official Foundation Devices Passport thread, now that it exists.

Sorry for bothering you.
In my eyes you are a one to whom I may trust largely because of your experience and every your response has a value for me.
As a matter of fact my decision to have  Passport was due to your reviews.

Regarding pairing: are you running the latest firmware?

Yes, The latest one, 2.1.0

[3] Where did you create those accounts?

What wallets do when you 'create new accounts' is just calculating the deterministic wallet at the next (or chosen) index and displaying its addresses (and balances). Nothing is actually 'created' in that sense, think of it more as 'displaying' a certain (hidden) account.

I understand that.  I was asking about moving between those  "(hidden) account's.  Say my primary is .../0' Then there is an option to create  .../1'  Suppose I have created that one. How to move between .../0'  and ../1' ? Only via software?

[n0nce]

I would honestly recommend you to ask these questions in the official Foundation Devices Passport thread, now that it exists.

Sorry for bothering you.
In my eyes you are a one to whom I may trust largely because of your experience and every your response has a value for me.
As a matter of fact my decision to have  Passport was due to your reviews.

Sorry if that came across wrong; it's not bothering me and I appreciate your words. It's just that I watch both threads anyway and if you expect a reponse by Foundation, the other thread may be better suited.

Regarding pairing: are you running the latest firmware?

Yes, The latest one, 2.1.0

Interesting; I just installed it on my Founders Edition and it recognizes addresses as soon as the QR code enters the camera field of view. I've yet to try that firmware version on the Batch 2.

[3] Where did you create those accounts?

What wallets do when you 'create new accounts' is just calculating the deterministic wallet at the next (or chosen) index and displaying its addresses (and balances). Nothing is actually 'created' in that sense, think of it more as 'displaying' a certain (hidden) account.

I understand that.  I was asking about moving between those  "(hidden) account's.  Say my primary is .../0' Then there is an option to create  .../1'  Suppose I have created that one. How to move between .../0'  and ../1' ? Only via software?

You just move between them using the device's arrow keys / keypad (left and right).
Depending on the wallet software, you may need to pair each 'account' individually (using the 'Connect Wallet' menu entry on Passport) or it may support multiple accounts in a concise user interface.

https://docs.foundationdevices.com/passport/account

[satscraper]

You just move between them using the device's arrow keys / keypad (left and right).

Oh, didn't realize that.

Interesting; I just installed it on my Founders Edition and it recognizes addresses as soon as the QR code enters the camera field of view. I've yet to try that firmware version on the Batch 2.

Yeah, it recognizes addresses quickly, but I was talking of initial pairing when app reads animated QR from Passport screen.

My Sparrow runs on relatively fastCore i7-7700 HQ, 16 Gb Ram and  today only forth attempt to pair it with Passport via animated QR has succeeded. But my hands were tired to hold Passport around  4-5  minutes in front of camera to get to the end. I can only imagine how it would be at say signing transaction.  

Probably do it via SD card less secure but at the same time more effortless.

[n0nce]

Interesting; I just installed it on my Founders Edition and it recognizes addresses as soon as the QR code enters the camera field of view. I've yet to try that firmware version on the Batch 2.

Yeah, it recognizes addresses quickly, but I was talking of initial pairing when app reads animated QR from Passport screen.

Of course, pairing needs a bit more time, since there is much more data to transmit (much more than addresses or PSBTs).
I just tried it on mine again and it took about half a minute to a minute. I don't think that computer hardware performance has anything to do with it, since the laptop I tried it on is weaker than yours.

Honestly, pairing is something you will do very rarely, so using a microSD card is fine, too, but I'd be interested to hear whether PSBTs are transferred fairly quickly. If not, you may have to open a support case with Foundation.
Over the last months of updates, the recognition speed became faster and faster with every release.

[Peach Bitcoin]

Damn, really cool review!

We just recently chatted with these guys about Peach. 🍑

I'll be sure to pass on the link to this thread as well.

https://open.spotify.com/episode/0PRWM4A2HklUh0yQwZGv9D

If you’ve been hearing the hype around Peach Bitcoin or simply starting to look into acquiring Bitcoin via a P2P exchange, today’s episode is for you! We’ll be diving into why Peach exists, how it’s different from the other P2P exchanges out there, and answering all your questions.

[satscraper]

but I'd be interested to hear whether PSBTs are transferred fairly quickly.

The  PSBTs  are a bit slower than a light.    Moved all my stash from ledger nano s+ to Passport 2.

[RickDeckard]

but I'd be interested to hear whether PSBTs are transferred fairly quickly.

The  PSBTs  are a bit slower than a light.    Moved all my stash from ledger nano s+ to Passport 2.

And it seems that the latest price reduction combined with the Ledger fiasco did wonders for stocking out some suppliers in the EU[1]:

Never expected this to happen. Contacted @Blockstream and @FOUNDATIONdvcs last night to restock ASAP.  Around 01.30 the website went down, came back online at 11.00. We’re very sorry for that. We just delivered almost every signing device we had in stock to the post office. 🙏 🧵

Keep up the nice work @foundationdvcs and @zherbert!
[1]https://nitter.it/BitcoinBrabant/status/1658837864724013063

[satscraper]

Of course, pairing needs a bit more time, since there is much more data to transmit (much more than addresses or PSBTs).

Ha, I've got how to pair Passport via animated QR with a speed of light.

When animated code is shown on Passport display the latter exposes to view  three small squares  located at bottom of the screen  just in the center between left and right arrows. One should use  joystick-button and choose the smallest square. That results in increased QR patterns which are readily perceived  by Web camera. With this trickery I managed to pair Passport with Sparrow in less than 10 secs.

Piece of cake!

[RickDeckard]

Of course, pairing needs a bit more time, since there is much more data to transmit (much more than addresses or PSBTs).

Ha, I've got how to pair Passport via animated QR with a speed of light.

When animated code is shown on Passport display the latter exposes to view  three small squares  located at bottom of the screen  just in the center between left and right arrows. One should use  joystick-button and choose the smallest square. That results in increased QR patterns which are readily perceived  by Web camera. With this trickery I managed to pair Passport with Sparrow in less than 10 secs.

Piece of cake!

That's a great tip! However, I do believe that most users will probably not be that savy regarding knowing it and it would be better to make it available to everyone, straight when the QR codes appears. Perhaps with your tip the developers could figure out what is making the application get slower in that particular menu? Or you're just using the menu correctly and every user has to select a square (I don't own a Passport).

[satscraper]

[Or you're just using the menu correctly and every user has to select a square (I don't own a Passport).

Exactly, there is no need for special menu.

User should select correct square.

Perhaps  their official docs should be more detailed on that when describing how to pair device with the use of animated QR.

All three squares are very small. I noticed them only today and figured out what they are for.

Probably the default should be the smallest one.

UPD. The smallest one is default.