You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It may be interesting to have, on the stax and flex, when you open an app on the device, the receiving addresses.
The UI may be a bit similar to the Keystone pro one, with the QR code, the address, the number of the address and the derivation path, and a button to get a new address (see screenshot of a youtube video here below).
This may be interesting to have to receive tokens on a device, without having to have the ledger app or ledger live application open on an other device.
(Obviously, no check is possible to know if this address has already been used or not, but it's not part of the usecase).
Hi,
thanks for the issue. It is a good idea and it has been discussed internally, however:
it would be somewhat disappointing if the feature only works for singlesig, since the app supports multisig & miniscript via BIP-388 wallet poiicies; therefore, it would require persisting some amount of state in the app storage (feasible, but it adds complexity)
I would like to not encourage address reuse, so a mechanism to sync from a software wallet (e.g. to at least keep track of the 'first free address') seems necessary.
If at some point we manage to integrate silent payments support, than showing the SP address in that way becomes a no-brainer as it doesn't have the above issues (but no ETA for that, yet!).
Hi,
Small idea regarding the apps.
It may be interesting to have, on the stax and flex, when you open an app on the device, the receiving addresses.
The UI may be a bit similar to the Keystone pro one, with the QR code, the address, the number of the address and the derivation path, and a button to get a new address (see screenshot of a youtube video here below).
This may be interesting to have to receive tokens on a device, without having to have the ledger app or ledger live application open on an other device.
(Obviously, no check is possible to know if this address has already been used or not, but it's not part of the usecase).
https://www.youtube.com/watch?v=KevCBnuuYGE
The text was updated successfully, but these errors were encountered: