Topic: Foundation Passport Official Thread - page 4. (Read 4649 times)

I usually take my time with any upgrade but this bout I was itching to test v. 2.3.0

I did it today after downloading, verifying


and installing  the relevant .bin   file on my Passport 2.  I never  commented  on the  microSD card slot in Passport 2. This time I should highlight the fact of its  very well-weighed  design which prevents SD card from  being placed in a wrong way.

The upgrade from 2.2.0 to 2.3.0 has took less a minute and went smoothly.

Being upgraded,  I decided to examine how my SEED came across SeedQR: Advanced -->View Seed Words --> Click left button on  QR icon located in the  bottom  left corner on display --> choose either Compact SeedQR or SeedQR.

I should say Compact SeedQR,  as it name implies.   looks ..... more  compact.  (Now I should ponder a bit of the best way  to transfer it to the steel plate. The first stuff came to my head was the transparent film to be used as a mediator.  )

Then I proceeded to exploration of my addresses by Passport 2: Manage Account -->Explore Addresses --> Single sig (I have two types of addresses Single-sig and 2/2 multisig) -->Following screen offers four options: Segwit, Wrapped Segwit, Legacy and Taproot  --> Receive or Change--> Right button on "> " ---> Again 2 times by Right button on "> "  after some warning messages on the screen and
shazam, address is here. Now I may use the directional pad to navigate addresses: Up: -10, Down: +10, Left: -1, Right: +1.

Test of v. 2.3.0 on my Passport 2 to be continued.

Thanks so much for sharing this, Rick! We're thrilled to release this, and as you can see from the blog post it's a massive release and likely our largest to date! If any of you have questions on the release, I'm happy to answer them, and will be sure to stay on top of this thread more moving forward  

Edit: I've updated the version OP, and here is the quick summary for those looking for the tl;dr on v2.3.0:

The moment that we have been waiting has arrived - Passport version 2.3.0 is LIVE[1][2] (paging @satscraper). I'll just highlight a couple of great additions:

• Full Taproot support in Passport;
• Address explorer;
• Support for verifying and displaying OP_Return;
• Creation of 12 word seed phrases (defaults to 12 word seed phrases during onboarding);
• Improved address display

The team over at Foundation keeps transmitting me a sense of responsibility and transparency within the hardware space that I find very appealing. Congratulations to everybody on the team once again.

---

[1]https://foundationdevices.com/2024/02/passport-version-2-3-0-is-now-live/
[2]https://github.com/Foundation-Devices/passport2/releases/tag/v2.3.0

We will be doing a cool halving collab with some other great companies in the space (stay tuned!) but we don't usually do any kind of discounts. I'll see if we can do something special, maybe some kind of bundle.

I am very excited that in the next few weeks we will bring back our customer referral program, the Ambassador Program. Will give an opportunity to refer Passport and get exclusive swag alongside Bitcoin rewards!

Very nice mister Contributor 

Can we expect anything special coming from Foundations around Bitcoin Halving date?

I know few other hardware wallet manufacturers are working on releasing special bitcoin only editions, and maybe there will be some discounts available.

We read everything posted here and take any feature requests into consideration. We appreciate your input! This next release is pretty massive.

Ha ha, my request on adding the master seed SeedQR-export into future release didn't    leave Foundation  hanging. The coming v.2.3.0 will implement it  as it is evidenced by beta variant  already dangling on the official github. Among other noticeable features is long expected (at least by me) " native OP_RETURN message viewing and signing". What a release!

Same feeling here. While the official account is mostly active here from time to time, their Telegram channel is way more active and they always have staff there that interact with many suggestions and ideas. Perhaps you could stop by there and share that idea to gather feedback?

Yeah, I knew about possibility to export  the BIP85 child seeds (one by one) via SeedQR when Key Manager is enabled . The official video ( which shows  how to do this)  exists for a long time. But unfortunately Key Manager doesn't offer the option to export master SEED via  SeedQR and I don't understand why. In my view adding this option  could cover what I want. They could add it even without requiring to create child seeds.

After some research I have found that if you enable the Key Manager extension in the Foundation devices you are able to generate (and export) in SeedQR and Compact SeedQR BIP 85 child seeds. A glimpse of it can be seen here[1]:
Since this functionality already exists for child seeds I believe that it wouldn't be hard to implement the same system during the process of generating a new master seed.

---

[1]https://foundationdevices.com/2023/05/all-your-wallets-one-backup/

Yeah, I was thinking about the creation of SeedQR directly from device, something like it was implemented in Blockstream Jade.

I would rather  trust  SeedQR module on device  than those generators found on github. Anyway, thanks for your efforts and clarification.

I would appreciate the  implementation of SeedQR generator by the  future releases.

I may have understood in a wrong way your question, but are you asking if Foundation is able to create a SeedQR directly on the device (from your seed words)? If so, that is not the case I believe. When they said in the v.2.20 that you can now "directly import a SeedQR" they were referring to the fact that you are able to scan an existing QR code (based on the SeedQR format specification). This assumes that you need a QR code first. You can see it better explained in their guide[1]:
If you are interested in creating one, I have found an open sourced repository that provides the ability to generate a compact SeedQR[2] but as I never used it I can't vouch for it. Or, considering that the method of creating a SeedQR is openly described[3] you can try to create one by yourself and only rely on an open source tool to generate QR codes (in offline mode) such as this[4].

---

[1]https://docs.foundationdevices.com/en/passport/setup
[2]https://github.com/renkasiyas/seedQR-generator
[3]https://github.com/SeedSigner/seedsigner/blob/dev/docs/seed_qr/README.md
[4]https://github.com/nayuki/QR-Code-generator

@foundationdvcs, as it was stated  the v.2.2.0 release has brought the option of importing "a SeedQR directly into Passport when restoring from seed.".

However, when passing through my Passport 2 (v 2.2.0) menu I failed to find the opt to create such SeedQR.

Does it mean there is a  need for  some 3^rdparty soft to create that  SeedQR from my SEED?

The (soonish) Passport version 2.3.0 release sure brings up a set of interesting features per BitcoinQ_A (Head of Customer Service[1]) recent tweet[2]:
Considering that the release is now on QA, I suppose Passport users will end February with a new set of cool features?  

---

[1]https://foundationdevices.com/about/
[2]https://n.opnxng.com/BitcoinQ_A/status/1755507422771228854

Yesterday, I sent  a transaction with 30 inputs and three outputs (excluding that  one relevant to commission).

I chose to sign it via QR code. After analyzing this code, Passport 2 (v2.2.0) warned that this transaction was large and suggested to continue the signing by using the PSBT file.

But I decided to continue the signing  via QR code.

Passport 2 did the job well. It took less than a minute to scan the dynamic code generated by Sparrow and then sign the transaction.

@foundationdvcs : I just saw that in the latest Envoy release[1], Spanish is listed as a new language to select. Are you planning on adding other languages during 2024?

---

[1]https://foundationdevices.com/2024/01/envoy-version-1-5-1-is-now-live/

In my opinion, if other hardware wallet devs are able to add support for their device to Envoy without additional libraries or security concerns, Foundation could always merge it into their main branch.

But then you run into all these issues like a buggy implementation being blamed on Foundation. Would be totally understandable from a business perspective if Foundation Devices never merged third-party wallet support into the official version of their application.

Wise commitment.

I think that granting to other HW the ability to be paired  with Envoy  would require incorporation of the  third-party connectivity libraries  into app's code. Those libraries may have the flaws and thus, be vulnerable to malware or hacking attempts . Consequently , the security of HW + Envoy tandem would be  liquefied.

We plan on focusing only on Passport (and future devices) in Envoy as that allows the tightest UX pairing possible, and there are other fantastic multi-hardware wallet solutions out there like Sparrow Wallet.

As you mentioned, Envoy is 100% open source so anyone could fork it and make it work with other air-gapped hardware wallets, with those supporting the same UR/animated QR standards being the easiest to implement.

Is there a way for Envoy app to have support for other aigrapped hardware wallets, other than Passport?
Or maybe you have the tools available for other developers to help and work on that, since everything is open source code.