Foundation Passport Official Thread

[foundationdvcs]

Foundation Passport Official Thread

Hi all, and welcome to the official thread for Foundation's Passport "Batch 2"! We'll use this thread to drop updates, stay on topic of questions and comments, and get feedback from all of you on your usage of Passport.

What is Passport?

Passport is the new standard for Bitcoin hardware wallets, built from the ground up to make Bitcoin self-custody more approachable without sacrificing security or features.

Passport brings best-in-class user experience via QR code scanning and microSD transaction signing, making it easy to use Passport at home or on the go with the wallet of your choice. We've also built an easy-to-use companion app for Passport in Envoy, a mobile app that helps you manage Passport, perform firmware updates, watch your wallets, and send and receive Bitcoin transactions easily.

Images



Key Features

• Airgapped security with both microSD and camera for QR code scanning
• Full T9 keyboard + directional pad to make PIN entry, passphrase entry, and navigation of the UI simple and fast
• Stunning color, IPS glass display makes it so much easier to navigate, confirm transaction details, and handle QR codes
• Envoy, our mobile companion app that lets you send and receive Bitcoin, manage, and update Passport from anywhere, anytime
• Power-only USB-C to ensure you can charge up easily without fear of compromising device security
• Rechargeable battery, with replacements available widely online in a standard form factor

Links

• Foundation's Website
• Passport, the new standard for Bitcoin hardware wallets
• Envoy, the simple Bitcoin wallet and mobile companion app for Passport
• Passport and Envoy documentation and tutorials

Reviews

• A fantastic and detailed review thread by forum member n0nce
• Reviews Megathread (Twitter)

Where you can find us

• Twitter: @FOUNDATIONdvcs
• Nostr: @Foundation
• Telegram Group Chat
• Email: hello@foundation.xyz

We look forward to hearing more of your feedback and answering any questions you have in this topic as well.

[1715252678]

1715252678

[1715252678]

1715252678

[1715252678]

1715252678

[foundationdvcs]

Firmware Updates

Most recent version: v2.3.0
Blog post: Passport version 2.3.0 is now live!
GitHub release: https://github.com/Foundation-Devices/passport2/releases/tag/v2.3.0

Release Summary:

We’re beyond thrilled to be able to release Passport firmware v2.3.0, including full Taproot support, revamped passphrase behavior, an all-new address explorer, master seed SeedQR export, 12-word seed phrase support, 12th/24th word generation for advanced users, and native OP_RETURN message viewing and signing.

This release is one of our largest to date and includes a massive amount of new features, improvements, and bug fixes.

[zherbert]

Confirming this is our official account 

[dkbit98]

Quick question - Did you test how durable Passport wallet is, and what happens if it drops on ground?
I am doing some research about this and I want to see how many hardware wallet manufacturers are stress testing their devices for durabllity.

Unrelated with my previous question, if there are roadmap plans and ideas for Future of Passport device please post it here.

PS
I think it's time for Passport to release accessories like skins, cases and other stuff.

[bitmover]

Images

I quoted your image original links but the forum security breaks them

I hosted the images in a different server with a few modifications so they can be seen here:




you can update the original post with the imafes once you have ranked up your account or paid for a Copper Account.
details here

[foundationdvcs]

Quick question - Did you test how durable Passport wallet is, and what happens if it drops on ground?
I am doing some research about this and I want to see how many hardware wallet manufacturers are stress testing their devices for durabllity.

Unrelated with my previous question, if there are roadmap plans and ideas for Future of Passport device please post it here.

PS
I think it's time for Passport to release accessories like skins, cases and other stuff.

We've tested extensively for durability in-house, and one of the reasons we went with the metal frame was to provide drop resistance. The combination of plastic shell + metal frame protect the screen/keys/camera module very well from their functionality being harmed.

We like to play our cards pretty close to the chest for new products until we're ready to announce, but rest assured that we're working hard on another product that is going to break the mold  

We're also working on accessories for our next device for these very reasons. Excited to announce it all when the time is right

you can update the original post with the imafes once you have ranked up your account or paid for a Copper Account.
details here

Ah, thank you bitmover! Just paid for Copper to enable us to post images, will get that updated using another image host that's allowed here!

[hugeblack]

It looks great, I will read more about it, especially since it looks like an old phone, but through a quick review of the evaluation in the forum, I hoped that this would be stainless steel, or at least waterproof and fireproof, so that it could be relied upon.


Since the device looks like a phone, is it possible to hide the logo (make it inside) and an update on the interface so that it looks like it works as an old broken phone (in case of theft)

[foundationdvcs]

It looks great, I will read more about it, especially since it looks like an old phone, but through a quick review of the evaluation in the forum, I hoped that this would be stainless steel, or at least waterproof and fireproof, so that it could be relied upon.

Hey hugeblack, definitely understand the desire for a steel backup, but that would definitely raise price for everyone when not everyone want's to backup on steel.

Thankfully, as it's just a standard 20-digit PIN or 24 seed words, you can easily back it up onto your favorite steel backup system without issues.

Since the device looks like a phone, is it possible to hide the logo (make it inside) and an update on the interface so that it looks like it works as an old broken phone (in case of theft)

We actually had a "Snake" game mode as a pseudo-phone mode on the original Passport, but when we rebuilt the firmware for Batch 2 we didn't add it back in. A dummy phone mode is definitely on our to-do list still, though, and we'll explore bringing that to our users in future versions!

[dkbit98]

We've tested extensively for durability in-house, and one of the reasons we went with the metal frame was to provide drop resistance. The combination of plastic shell + metal frame protect the screen/keys/camera module very well from their functionality being harmed.

So you didn't experience any serious damage to screen or vital parts of devices during this durability testing?
It would be cool if you could reveal more information about that, but I understand if it's only for internal use.
I think we need to have some guy like JerryRigEverything ^{(check out his youtube channel)} but only for testing hardware wallets  

We're also working on accessories for our next device for these very reasons. Excited to announce it all when the time is right

Now you got me interested, just don't go with BlackBerry style device please  

[sad-error]

Any ideas why I'd be getting a "memory allocation failed" exception when signing a transaction imported from the qr code - importing from the sd card works fine.

Traceback looks something like this

Code:

File "flows/flow.py", line 139, in run File "flows/sign_psdbt_qr_flow.py", line 95 in show_signed_transaction MemoryError: memory allocation failed, allocating 5859 bytes

[foundationdvcs]

Any ideas why I'd be getting a "memory allocation failed" exception when signing a transaction imported from the qr code - importing from the sd card works fine.

That usually happens when the PSBT you're trying to sign is quite large/complex. What version firmware are you running? If less than v2.0.6, please update to that as we've made quite a few quality of life improvements in it.

We're also about to release a beta for v2.0.7 that has a completely reworked transaction parsing memory approach that will allow for signing *much* larger transactions via QR, but we do still recommend microSD for larger transactions as the process is much faster and easier that way.

[sad-error]

Any ideas why I'd be getting a "memory allocation failed" exception when signing a transaction imported from the qr code - importing from the sd card works fine.

That usually happens when the PSBT you're trying to sign is quite large/complex. What version firmware are you running? If less than v2.0.6, please update to that as we've made quite a few quality of life improvements in it.

We're also about to release a beta for v2.0.7 that has a completely reworked transaction parsing memory approach that will allow for signing *much* larger transactions via QR, but we do still recommend microSD for larger transactions as the process is much faster and easier that way.

it's 2.0.6. Yes, the psbt is likely quite big as it's 3/6 multisig, but coldcard has absolutely no problems with it so I would expect passport to be the same.

[foundationdvcs]

We've tested extensively for durability in-house, and one of the reasons we went with the metal frame was to provide drop resistance. The combination of plastic shell + metal frame protect the screen/keys/camera module very well from their functionality being harmed.

So you didn't experience any serious damage to screen or vital parts of devices during this durability testing?
It would be cool if you could reveal more information about that, but I understand if it's only for internal use.
I think we need to have some guy like JerryRigEverything ^{(check out his youtube channel)} but only for testing hardware wallets  

We're also working on accessories for our next device for these very reasons. Excited to announce it all when the time is right

Now you got me interested, just don't go with BlackBerry style device please  

Will double check with the team on what info we can share around that and get back to you!

And yes, don't worry about that

it's 2.0.6. Yes, the psbt is likely quite big as it's 3/6 multisig, but coldcard has absolutely no problems with it so I would expect passport to be the same.

Ah, does make more sense in that case, then. Definitely use microSD (as you would with ColdCard) for now for transactions with that large of a quorum, but we'd love to hear back from you on how v2.0.7 works for you once we release it!

I'll post the release here as soon as it's available with release notes etc.

[Welsh]

We've tested extensively for durability in-house, and one of the reasons we went with the metal frame was to provide drop resistance. The combination of plastic shell + metal frame protect the screen/keys/camera module very well from their functionality being harmed.

Might I ask, whether you're testing to a certain specification, and standard or are you just doing your own tests for durability? For example, certain mobile phone manufactures cater to the MIL-STD-810G specification. I tend to like pretty rugged devices, and I think for a hardware wallet it's definitely something to consider since it protects against certain situations which might arise. For example, a few discussions recently above the earthquakes, and safe guarding your seeds or hardware wallets popped up. While, I'm definitely not expecting it to be that substantial for obvious reasons, it's definitely something that other manufacturers don't seem to be targeting.

[foundationdvcs]

I don't plan to buy Passport. But i have few question about shipping,
1. I found an article which state "free shipping within the USA.", but what's shipping cost for other contry?
2. Does your shipping provider offer service which pay custom/import fee on behalf of the receiver?

1. We can't estimate it for every country in one page, so you'll get the estimate when you're checking out and put in your country/address. It varies widely, of course!
2. It does not, we use standard international shipping. If you want to simplify the customs/import process, using one of our resellers (if there is one local) is usually the best option.

Link to page about Envoy is broken.

Thanks for that, fixed! Getting used to the syntax here 

Might I ask, whether you're testing to a certain specification, and standard or are you just doing your own tests for durability? For example, certain mobile phone manufactures cater to the MIL-STD-810G specification. I tend to like pretty rugged devices, and I think for a hardware wallet it's definitely something to consider since it protects against certain situations which might arise. For example, a few discussions recently above the earthquakes, and safe guarding your seeds or hardware wallets popped up. While, I'm definitely not expecting it to be that substantial for obvious reasons, it's definitely something that other manufacturers don't seem to be targeting.

On current devices we've just been doing our own tests as normally these devices aren't an "every day carry" type of device, but we did want to ensure they were rugged enough to withstand normal use for a HWW. On future devices we'll explore testing to specific standards, will bring this up to the team today as a reference!

[foundationdvcs]

Now that we're active on Bitcoin Talk, we wanted to include the awesome community here in an opportunity to beta test new Passport firmware releases and provide feedback.

We're happy to announce that the public beta for version 2.0.7 is available now on Github:

Passport v2.0.7 Firmware (Beta 7)

NOTE: This is a Beta version of Passport firmware. You must install the beta pubkey (attached in GitHub) using the Settings -> Advanced -> Developer PubKey menu item before you can install this beta. If you are not comfortable with this, please wait for the official release, which should be available shortly. Detailed instructions for this process can be found here.

Mainly usability improvements in this one, full details of which can be found in the GitHub change log. Most notable are:

• Improved memory management when signing via QR codes (sign larger transactions)
• Added the ability to export existing multisig configs via QR or SD card (Passport can now act as an additional backup of the wallet data which can be super useful in disaster recovery scenarios)
• Improved transaction detail display when conducting self spends

Please test it out (if you're comfortable with a beta release) and report back with any issues, feedback, or suggestions you have! The official release should go live in about 1wk, pending any issues that are discovered in the public beta testing.

[dkbit98]

Please test it out (if you're comfortable with a beta release) and report back with any issues, feedback, or suggestions you have! The official release should go live in about 1wk, pending any issues that are discovered in the public beta testing.

I am expecting n0nce will be testing this new firmware, but I like new ability to export multisig configs with QR codes or SD cards.

Maybe you can tell us more about new integration with Bitcoinkeeper app, you posted about that with your twitter account.
I was following them for some time and it looks interesting for multisig setup but I never tested it myself, they support many hardware wallets.

[n0nce]

Please test it out (if you're comfortable with a beta release) and report back with any issues, feedback, or suggestions you have! The official release should go live in about 1wk, pending any issues that are discovered in the public beta testing.

I am expecting n0nce will be testing this new firmware, but I like new ability to export multisig configs with QR codes or SD cards.

Yes, I do like to test their firmwares; for instance here I tried the v2.0.5 beta to see whether the camera was working better.
Right now, I'm running the v2.0.6 release version and camera scanning is now amazing + looping through the main menu is quite convenient.
I don't know when I'll have the time to thoroughly test v2.0.7, since it seems more focused on multisig and that takes me more time to test, since I've got to gather my various wallets and such.

[foundationdvcs]

Maybe you can tell us more about new integration with Bitcoinkeeper app, you posted about that with your twitter account.
I was following them for some time and it looks interesting for multisig setup but I never tested it myself, they support many hardware wallets.

Sure! You can find all of our docs on the integration here, but the core of it is that Bitcoin Keeper is a multisig-centric wallet with a focus on helping users setup tiers of Bitcoin storage (including singlesig and multisig) with a proper plan for inheritance long-term. They have a pretty clean UI and UX, and have been great to work with on the integration front. They've also done good work integrating the latest interoperable standards for multisig, which has been helpful for us as well as we're laser-focused on interoperability and embracing emerging standards in the Bitcoin space.

We also did an interview with them on our podcast, Journey to Sovereignty, that you can find here:

EP #5 - Is multisig for everyone?

Edit: Realized I didn't even link their website! Here is their website with plenty more info on their approach and implementation:

Bitcoin Keeper, your private bitcoin vault

[RickDeckard]

1. We can't estimate it for every country in one page, so you'll get the estimate when you're checking out and put in your country/address. It varies widely, of course!
2. It does not, we use standard international shipping. If you want to simplify the customs/import process, using one of our resellers (if there is one local) is usually the best option.
 did want to ensure they were rugged enough to withstand normal use for a HWW. On future devices we'll explore testing to specific standards, will bring this up to the team today as a reference!

Regarding both topics that ETFbitcoin brought up, I would like to highlight[1] my initial discussion with @zherbert regarding the way shipping costs are calculated when talking about other countries besides USA and how (perhaps) it could be improved:

Currently we just display the estimated import tax, but we don't charge the customer. The customer then needs to pay it directly from UPS (or whatever carrier they select) upon package delivery.

I think there is a way where we could pay the import tax on behalf of the customer, and therefore charge them for the estimated tax during checkout. I'll explore if this is possible, because I like your idea. The only downside would be if the estimate is consistently lower than the actual tax; that would eat into our margins and we aren't quite as big as Amazon

So while the client is making the purchase he was to directly pay it to UPS instead to Foundation as a company? I may be thinking this wrong and I would love your input but, from a user perspective, this operation seems like it's a bit confuse - If I'm willing to pay for such a premium for such a device (considering the offers in the market), the least that I would expect is that I would pay whatever had to pay to Foundation and then the order would eventually come to my house - no need to make two separate transactions, one for you and one for UPS. I may be wrong on the following assumption, but doesn't it mean that by paying directly to UPS it makes me the one responsible for the package, thus it would be me who would have to argue with them if something went bad as opposed to being Foundation the ones responsible to care and making sure that the package arrives with no problems?

[1]https://bitcointalk.org/index.php?topic=5421713.msg61764293#msg61764293