New @SeedSigner experiment: initial support for BIP-352 Silent Payments!
- Generate your shareable, reusable payment addr
- Export the signing key's pubkey
- Export the scanning key's privkey
#bip352
Quick overview: #bip352 requires TWO private keys:
- The scanning key. Must be loaded into a hot wallet in order to scan utxos to find incoming payments.
- The signing key. Obviously you want to keep this offline and airgapped (hello, @seeker!).
BIP-352 specifies derivation paths for generating each key as a child of a common root key.
That means: load a single seed into @SeedSigner as usual and use it to generate the #bip352 scanning AND signing child keys.
I only built support for SETTING UP an airgapped #bip352 silent payments wallet.
I still have to dig into how the SPENDING side works and what specific support @SeedSigner might need in order to sign those txs.
And here's my work-in-progress dev branch: https://github.com/kdmukai/seedsigner/tree/bip352_silent_payments_basic_support
If anyone want to add more information about Silent Payments is free to do... I'm still trying to understand what it means completely. Even the experiment is not complete by the author, but the path it's going seems fruitful.