Foundation Passport Official Thread | Bitcointalksearch.org

dkbit98

legendary

Activity: 2212

Merit: 7064

Quote from: foundationdvcs on Today at 11:37:34 AM

✨Beyond the Hardware Wallet

I saw this yesterday and it seriously got me interested.
Can you reveal something or give as a small hint, is it new device related with Bitcoin or not?
Some people think it's a new phone, but please don't use the word CLOCK for it or you can get served by ''someone'' Wink

foundationdvcs

copper member

Activity: 96

Merit: 253

✨Beyond the Hardware Wallet

Stay ahead of the curve - something new is coming to Foundation. 12.16.24

Be the first to know and sign up here for updates: https://foundation.xyz/beyond/

zherbert

member

Activity: 63

Merit: 119

Quote from: satscraper on November 14, 2024, 11:25:24 AM

Quote from: foundationdvcs on November 14, 2024, 10:17:51 AM

Fix is here for you.

https://docs.foundation.xyz/firmware-update-fix/

Thanks, I did it. Everything vent like a charm and my Passport 2 is on the latest 2.3.5. ^{Good that I was not hasty with the update and discovered from foundationdvcs that the problem was buried into version 2.3.2}.

May I ask ^{just of my curiosity} what could do in this case those users who have experienced frozen device . Instruction ^{you have referred to}says users should install developer key preliminary to avoid freeze but they will not be able to this if their devices are already stuck. Is there any workaround for such case?

We had an obscure bug that we missed when QAing v2.3.2. Essentially all of the developers and team who QAs Passport has developer pubkeys installed so we can install internal betas and public betas. The bug checked to see if there was a developer pubkey in the slot in the secure element – if the slot was empty, the firmware update froze.

We all missed the bug, as well as all external beta testers too, since to test the beta you needed to have the developer pubkey added!

The firmware update process didn't care what pubkey was in the slot, only that the slot was not empty. If it was empty it got stuck at 98%.

Was very hard to reproduce this, but once we did we quickly understood what happened and fixed it. Sincere apologies for the inconvenience.

zherbert

member

Activity: 63

Merit: 119

Quote from: Pmalek on November 14, 2024, 08:26:14 AM

I see that foundationdvcs hasn't mentioned yet that in about one month time they are releasing some new type of device or tool.
There isn't much information available at this stage except a mysterious text saying, "Beyond the Hardware Wallet". Based on that, I don't think they will release a new hardware wallet. Could it be something for backing up seeds? Maybe a physical 2FA device?

You can follow Foundation's new page for this update here: https://foundation.xyz/beyond/

They have released an image of the product on X: https://x.com/FOUNDATIONdvcs/status/1856386242805674223
Talkimg is in maintenance mode, so I can't share it here.

You might want to start a new post for this one Wink

satscraper

hero member

Activity: 714

Merit: 1298

Quote from: foundationdvcs on November 14, 2024, 10:17:51 AM

Fix is here for you.

https://docs.foundation.xyz/firmware-update-fix/

Thanks, I did it. Everything vent like a charm and my Passport 2 is on the latest 2.3.5. ^{Good that I was not hasty with the update and discovered from foundationdvcs that the problem was buried into version 2.3.2}.

May I ask ^{just of my curiosity} what could do in this case those users who have experienced frozen device . Instruction ^{you have referred to}says users should install developer key preliminary to avoid freeze but they will not be able to this if their devices are already stuck. Is there any workaround for such case?

foundationdvcs

copper member

Activity: 96

Merit: 253

Fix is here for you.

https://docs.foundation.xyz/firmware-update-fix/

satscraper

hero member

Activity: 714

Merit: 1298

Quote from: foundationdvcs on November 14, 2024, 07:42:08 AM

That was the unintended bug introduced in 2.3.2, which is also still present in 2.3.4. The device is looking for a key to be present in the developer slot. Most users do not have this present, causing the freeze.

Well ^{the problem is buried into 2.3.2}. My Passport2 is still on 2.3.2 and I want to update it to 2.3.5. What exactly should I do to avoid any freezing? I mean how to add that developer pubkey into developer slot if I prefer to update via relevant firmware file downloaded to my miroSD card? ^{I don't like to use Envoy for update purpose.}

Pmalek

legendary

Activity: 2730

Merit: 7065

I see that foundationdvcs hasn't mentioned yet that in about one month time they are releasing some new type of device or tool.
There isn't much information available at this stage except a mysterious text saying, "Beyond the Hardware Wallet". Based on that, I don't think they will release a new hardware wallet. Could it be something for backing up seeds? Maybe a physical 2FA device?

You can follow Foundation's new page for this update here: https://foundation.xyz/beyond/

They have released an image of the product on X: https://x.com/FOUNDATIONdvcs/status/1856386242805674223
Talkimg is in maintenance mode, so I can't share it here.

foundationdvcs

copper member

Activity: 96

Merit: 253

That was the unintended bug introduced in 2.3.2, which is also still present in 2.3.4. The device is looking for a key to be present in the developer slot. Most users do not have this present, causing the freeze.

> nope, user clearly said that he was trying to update to 2.3.5 but his device has stuck, so problem do persists when updated to 2.3.5.

That's right, he is trying to update to 2.3.5 from his current version, but failing. This user is not currently running 2.3.5. Once they carry out the recovery steps correctly and successfully install 2.3.5, the issue does not persist and subsequent updates can be applied using the typical method.

satscraper

hero member

Activity: 714

Merit: 1298

Quote from: foundationdvcs on November 14, 2024, 02:03:42 AM

Quote from: satscraper on November 14, 2024, 01:38:51 AM

Quote from: foundationdvcs on November 12, 2024, 10:36:05 AM

and answering.

Doubt this. I noticed that you prefer to not answer the tough questions^{like mine above ^{that is not alone in this thread}} which leads me to think.... Regarding you new communication channel i.e. community.foundation.xyz it is factually empty and ^{being such} is useless^{at this point}, sorry to say this, ^{anyway it is true}.

Please read the comments under the post you linked. It has been answered and the problem does not persist when updated to 2.3.5.

I have read that comment. It states that there is a need to add either the developer pubkey or user's one to avoid this problem, But why on Earth I have to add any key to update my device to 2.3.5.^pfft. Previous updates don't require this.

Quote from: foundationdvcs on November 14, 2024, 02:03:42 AM

the problem does not persist when updated to 2.3.5.

nope, user clearly said that he was trying to update to 2.3.5 but his device has stuck, so problem do persists when updated to 2.3.5.

foundationdvcs

copper member

Activity: 96

Merit: 253

Quote from: satscraper on November 14, 2024, 01:38:51 AM

Quote from: foundationdvcs on November 12, 2024, 10:36:05 AM

and answering.

Doubt this. I noticed that you prefer to not answer the tough questions^{like mine above ^{that is not alone in this thread}} which leads me to think.... Regarding you new communication channel i.e. community.foundation.xyz it is factually empty and ^{being such} is useless^{at this point}, sorry to say this, ^{anyway it is true}.

Please read the comments under the post you linked. It has been answered and the problem does not persist when updated to 2.3.5.

satscraper

hero member

Activity: 714

Merit: 1298

Quote from: foundationdvcs on November 12, 2024, 10:36:05 AM

and answering.

Doubt this. I noticed that you prefer to not answer the tough questions^{like mine above ^{that is not alone in this thread}} which leads me to think.... Regarding you new communication channel i.e. community.foundation.xyz it is factually empty and ^{being such} is useless^{at this point}, sorry to say this, ^{anyway it is true}.

foundationdvcs

copper member

Activity: 96

Merit: 253

Quote from: JayJuanGee on November 11, 2024, 11:40:47 AM

Quote from: foundationdvcs on November 11, 2024, 09:33:31 AM

OUR COMMUNITY IS MOVING!

Due to the proliferation of scammers on Telegram, we have taken the decision to migrate our community. All future community discussions should be now held at community.foundation.xyz. Our Telegram group will soon become read-only, with admins posting company updates.

Need support? Want to stay up to date? Got some product feedback? Head over to our new space to join the conversation!

Learn more in our blog post here.

NO ADMIN FROM OUR TELEGRAM ROOM WILL EVER DM YOU OFFERING SUPPORT. STAY VIGILANT!

Many of us stay in this forum for a reason, so we might not want to join other communities. Hopefully you will still be answering here.

We will be staying here too and answering.

satscraper

hero member

Activity: 714

Merit: 1298

Quote from: foundationdvcs on November 11, 2024, 09:33:31 AM

OUR COMMUNITY IS MOVING!

Due to the proliferation of scammers on Telegram, we have taken the decision to migrate our community. All future community discussions should be now held at community.foundation.xyz.

I have read over there that update to v.2.3.5 remains risky for someones as it was with 2.3.4. Why does such problem persist? ^{(My Passport 2 still sticks to v.2.3.2 and such complains abut stuck devices at the end of update prevent me from its elevating to the higher version, ^{(one cannot be too careful)})}.

Quote from: https://community.foundation.xyz/t/firmware-stuck-work-around-question/75

JayJuanGee

legendary

Activity: 3892

Merit: 11105

Self-Custody is a right. Say no to"Non-custodial"

Quote from: foundationdvcs on November 11, 2024, 09:33:31 AM

OUR COMMUNITY IS MOVING!

Due to the proliferation of scammers on Telegram, we have taken the decision to migrate our community. All future community discussions should be now held at community.foundation.xyz. Our Telegram group will soon become read-only, with admins posting company updates.

Need support? Want to stay up to date? Got some product feedback? Head over to our new space to join the conversation!

Learn more in our blog post here.

NO ADMIN FROM OUR TELEGRAM ROOM WILL EVER DM YOU OFFERING SUPPORT. STAY VIGILANT!

Many of us stay in this forum for a reason, so we might not want to join other communities. Hopefully you will still be answering here.

foundationdvcs

copper member

Activity: 96

Merit: 253

OUR COMMUNITY IS MOVING!

Due to the proliferation of scammers on Telegram, we have taken the decision to migrate our community. All future community discussions should be now held at community.foundation.xyz. Our Telegram group will soon become read-only, with admins posting company updates.

Need support? Want to stay up to date? Got some product feedback? Head over to our new space to join the conversation!

Learn more in our blog post here.

NO ADMIN FROM OUR TELEGRAM ROOM WILL EVER DM YOU OFFERING SUPPORT. STAY VIGILANT!

foundationdvcs

copper member

Activity: 96

Merit: 253

Envoy v1.8.3 & Envoy v1.8.4 has been released.

v1.8.4 has fixed a problem from the previous v1.8.3 release affecting some users related to not being able to send to legacy type addresses.

You can read more on both blog posts about each release below.

https://foundation.xyz/2024/10/envoy-version-1-8-3-is-now-available/

https://foundation.xyz/2024/10/envoy-version-1-8-4-is-now-available/

satscraper

hero member

Activity: 714

Merit: 1298

Probably it is worth to notify those who use Passport that this wallet has been elevated to v. 2.3.5 which "Fixed an issue where some users were unable to update their firmware". This bug din't touch me as my Passport2 is still running on 2.3.2^{(as I'm commonly reactant to go fast with updates and favor a go-slow approach)}. BTW, their firmware numbering is a bit strange for me as 2.3.3 got out of set.

Quote from: https://github.com/Foundation-Devices/passport2/releases/

Pmalek

legendary

Activity: 2730

Merit: 7065

Quote from: dkbit98 on October 22, 2024, 03:48:29 PM

Price is a bit more expensive when ordered from BitcoinBrabant but delivery should be faster and fees lower.

That's no surprise. It's expected, considering it's an American product that has to be shipped from the United States. Then, you have to account for customs and import fees. Hence the more expensive price for non-US customers. The cheapest way to get a Foundation Passport is to buy it the US and smuggle it in into the EU or have someone else bring it for you.

dkbit98

legendary

Activity: 2212

Merit: 7064

Quote from: Pmalek on October 22, 2024, 07:32:52 AM

Good news from Foundation for EU users. EU purchases will now be distributed in a partnership with Bitcoin Brabant. I assume they will ship from The Netherlands.
This means faster deliveries, lower shipping costs, and no customs fees and import taxes. This is now in effect for all orders placed in the EU.

Price is a bit more expensive when ordered from BitcoinBrabant but delivery should be faster and fees lower.
I don't know who did it first but I saw c0ldcard did the something similar and opened their shop in EU.
Cold-War continues

Topic: Foundation Passport Official Thread (Read 5939 times)