To scan for cash obtained to Bobs silent cost tackle, he wants to make use of his b_scan personal key because the shared secret is calculated by the sender utilizing a*B_scan.
This query will not be about whether or not host wallets / companion apps for {hardware} wallets will make the most of scanning servers or another method to implement scanning however fairly how they may cope with the personal key b_scan being required to be “on-line”.
- {hardware} wallets usually don’t assist exporting personal keys (and shouldn’t imo.)
- BIP-352 says that wallets MAY use BIP32 derivation paths however this would possibly not be doable for {hardware} wallets that do not export personal keys.
How might doable implementations appear like? The host pockets / scanning server might simply compute all A (sender’s public key a1 + a2 + ... + an for n inputs) after which {hardware} wallets might have an API to calculate the shared secret given the A?
Recovering the pockets steadiness from a sure block top (the block top that the {hardware} pockets rolled out silent cost obtain for instance) can be loads of work, and for all subsequent receives the {hardware} pockets additionally must be related.
Does anybody have an thought how {hardware} wallets might presumably cope with this with out destroying UX / including complexity to the {hardware} pockets firmware?
To scan for cash obtained to Bobs silent cost tackle, he wants to make use of his b_scan personal key because the shared secret is calculated by the sender utilizing a*B_scan.
This query will not be about whether or not host wallets / companion apps for {hardware} wallets will make the most of scanning servers or another method to implement scanning however fairly how they may cope with the personal key b_scan being required to be “on-line”.
- {hardware} wallets usually don’t assist exporting personal keys (and shouldn’t imo.)
- BIP-352 says that wallets MAY use BIP32 derivation paths however this would possibly not be doable for {hardware} wallets that do not export personal keys.
How might doable implementations appear like? The host pockets / scanning server might simply compute all A (sender’s public key a1 + a2 + ... + an for n inputs) after which {hardware} wallets might have an API to calculate the shared secret given the A?
Recovering the pockets steadiness from a sure block top (the block top that the {hardware} pockets rolled out silent cost obtain for instance) can be loads of work, and for all subsequent receives the {hardware} pockets additionally must be related.
Does anybody have an thought how {hardware} wallets might presumably cope with this with out destroying UX / including complexity to the {hardware} pockets firmware?
