Foundation Passport Official Thread

[foundationdvcs]

Thanks for the report of this issue!

This is the default behavior when signing PSBTs but for those who look closely can be confusing. Note that it doesn't prevent them from being transmitted in any way, but we've created an internal issue to remedy this by simply not changing the timestamp when signing as Passport does not have a way to keep its internal clock in sync.

[Pmalek]

A bug is a bug. It may not look serious for experienced user like you or me but    put someone, less experienced, in my place. He/she may suspect that if wallet is corrupting the simple thing  then it is capable to corrupt other valuable data relevant to transaction. Such kind of bugs are nonallowable and should be fixed ASAP.

I understand what you are saying and I agree that it needs to be fixed, especially since it shouldn't be difficult for their developers to change that workflow. But I repeat that it isn't a bug that hinders you from using the signing device with all its current capabilities. Foundation should just leave the name alone and not add any timestamps to the signed transactions because the device is missing an internal clock.   

[satscraper]

Thanks for the report of this issue!
we've created an internal issue to remedy this by simply not changing the timestamp when signing

Thanks, this is the wise decision from Foundation part.

Could you consider the adding BIP47 support to Passport?

[foundationdvcs]

Thanks for the report of this issue!
we've created an internal issue to remedy this by simply not changing the timestamp when signing

Thanks, this is the wise decision from Foundation part.

Could you consider the adding BIP47 support to Passport?

BIP 47 has A LOT of complexity when integrating with a hardware wallet as you can't even scan for incoming notifications without the private key.

What we will eventually add in, however, is Silent Payments (BIP 352). First with Envoy, and then with Passport somewhere down the line.

More info on Silent Payments here: https://silentpayments.xyz

[satscraper]

[
What we will eventually add in, however, is Silent Payments (BIP 351). First with Envoy, and then with Passport somewhere down the line.

Thanks, Silent Payments is a decent alternative  to BIP 47, regarding the privacy  it does the same , and even better.

UPD. Didn't pay attention at first. Did you really mean BIP 351 rather than BIP 352?

Silent Payment refers to BIP352 while BIP351 is relevant to different payment scheme which has some trade-offs:

[foundationdvcs]

[
What we will eventually add in, however, is Silent Payments (BIP 351). First with Envoy, and then with Passport somewhere down the line.

Thanks, Silent Payments is a decent alternative  to BIP 47, regarding the privacy  it does the same , and even better.

UPD. Didn't pay attention at first. Did you really mean BIP 351 rather than BIP 352?

Silent Payment refers to BIP352 while BIP351 is relevant to different payment scheme which has some trade-offs:

Yes, I meant 352! Edited my post now.

[foundationdvcs]

Passport v2.3.1 is live now!

Blog post: Passport version 2.3.1 is now live!
GitHub release: https://github.com/Foundation-Devices/passport2/releases/tag/v2.3.1

Release Summary:

With this version of Passport’s firmware we’ve added connections to Theya, Zeus, and Coinbits, updated dependencies, and made reproducible builds more resilient to upstream changes.

[satscraper]

Passport v2.3.1 is live now!

With this version of Passport’s firmware we’ve added connections to Zeus,

Does this mean that Passport is now capable to connect directly to lightning node embedded into ZEOS wallet and thus,  open/close channels?

If yes, how many channels it is capable to support simultaneously?

Would be nice to have the full guide on this matter.

[Pmalek]

Does this mean that Passport is now capable to connect directly to lightning node embedded into ZEOS wallet and thus,  open/close channels?

If yes, how many channels it is capable to support simultaneously?

Would be nice to have the full guide on this matter.

From what I can see on Zeus' Twitter feed, the update is not publicly available yet. It's in a closed alpha stage, nearing an open beta release soon. I am wondering how users will be able to use the lightning network and open and close channels without making transactions from the connected hot wallet that broadcasts everything?

[satscraper]

Does this mean that Passport is now capable to connect directly to lightning node embedded into ZEOS wallet and thus,  open/close channels?

If yes, how many channels it is capable to support simultaneously?

Would be nice to have the full guide on this matter.

From what I can see on Zeus' Twitter feed, the update is not publicly available yet. It's in a closed alpha stage, nearing an open beta release soon. I am wondering how users will be able to use the lightning network and open and close channels without making transactions from the connected hot wallet that broadcasts everything?

Node is in charge for broadcasting transaction rather than a wallet itself. Thus if Passport connected directly to lightning node embedded into Zeus it could have the ability to open/close channels without  topping up Zeus-wallet itself.  Sure, along this line ,Passport must be capable  to control the state of the channel.Hope, Foundation will correct me if I'm wrong.

[foundationdvcs]

Passport v2.3.1 is live now!

With this version of Passport’s firmware we’ve added connections to Zeus,

Does this mean that Passport is now capable to connect directly to lightning node embedded into ZEOS wallet and thus,  open/close channels?

If yes, how many channels it is capable to support simultaneously?

Would be nice to have the full guide on this matter.

At it's core it allows you to sign channel open transactions directly from Passport and have channel closes be automatically sent back to Passport. Since Passport is air-gapped and offline it can't act as the always-on hot wallet portion of a Lightning wallet, but now you can save extra, needless transactions to open and close channels from/to cold storage.

[foundationdvcs]

We just launched Envoy 1.7 - Buy Bitcoin directly into self-custody with a few taps!

Today we release the biggest update yet and mark a new chapter for our Bitcoin mobile wallet, Envoy.

✅ Buy Bitcoin directly to self-custody
✅ Redeem BTCPay and Azte.co vouchers
✅ Discover p2p exchanges & ATMs

Learn more at https://foundation.xyz/2024/06/envoy-1-7-buy-bitcoin-directly/

Full release notes: https://foundation.xyz/2024/06/envoy-version-1-7-0-is-now-live/

[dkbit98]

I don't think that Envoy partnering with Ramp that is asking for kyc verificatioin is a good idea.
There are plenty of options to buy and sell bitcoin without any kyc that you could explored instead.

Learn more at https://foundation.xyz/2024/06/envoy-1-7-buy-bitcoin-directly/

What service are you using for showing map locations with Bitcoin ATM's?
I know there is already one nice open source app called BTC Map for that, so is there any advantage of using Envoy app for this purpose?

[satscraper]

~

As a frequent traveler I could support the using Envoy app for finding the local crypto ATMs as such feature eliminates the need of having extra apps on your mobile.  The less apps on  mobile the more safer it is.

As to partnering with RAMP, probably those who use this service will appreciate this, but I prefer to buy/sell BTC on decentralized p2p exchanges particularly on bisq which is my favorite.  

Probably crazy idea but if Foundation could manage to partner with Visa/MasterCard so that BTC (from Passport/Envoy) could be spend at POS terminals there would be (virtually)  no price at all for their wallets.

[foundationdvcs]

I don't think that Envoy partnering with Ramp that is asking for kyc verificatioin is a good idea.
There are plenty of options to buy and sell bitcoin without any kyc that you could explored instead.

Learn more at https://foundation.xyz/2024/06/envoy-1-7-buy-bitcoin-directly/

What service are you using for showing map locations with Bitcoin ATM's?
I know there is already one nice open source app called BTC Map for that, so is there any advantage of using Envoy app for this purpose?

1. Definitely understand the sentiment, and many on the team are heavy users and advocates of p2p exchanges instead. This is just the first step as it's the lowest lift, with direct p2p exchange integration on the roadmap!
2. We're using this service: https://coinmap.org/

[dkbit98]

1. Definitely understand the sentiment, and many on the team are heavy users and advocates of p2p exchanges instead. This is just the first step as it's the lowest lift, with direct p2p exchange integration on the roadmap!

Good to hear, and having more options is always good.
To give you some ideas, is Robosats for p2p LN to fiat trading and they have a list of compatible wallets, you can consider adding support for Envoy in future:
https://learn.robosats.com/docs/wallets/

PeachBitcoin is also doing a great job with their app, so maybe you can do something similar or make some cooperation with them.

[foundationdvcs]

1. Definitely understand the sentiment, and many on the team are heavy users and advocates of p2p exchanges instead. This is just the first step as it's the lowest lift, with direct p2p exchange integration on the roadmap!

Good to hear, and having more options is always good.
To give you some ideas, is Robosats for p2p LN to fiat trading and they have a list of compatible wallets, you can consider adding support for Envoy in future:
https://learn.robosats.com/docs/wallets/

PeachBitcoin is also doing a great job with their app, so maybe you can do something similar or make some cooperation with them.

Robosats for p2p LN to fiat trading

Once we have Lightning support in Envoy we will absolutely ensure that we are compatible with Robosats, and perhaps even explore a direct integration.

PeachBitcoin is also doing a great job

We agree Unfortunately they don't allow US users, which is by far the largest customer segment for us. Would certainly be interesting to explore some sort of integration in the future, however.