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.