We could add a --bip388-policy (or just --policy) option to the signtx and displayaddress commands.
For devices that support it, e.g. Ledger, these commands would first register the policy if needed. Since displaying an address is a good idea anyway before sending money to it, I don't think we need a separate register command.
Ledger returns an HMAC after registration. Afaik this isn't documented in any BIP. I also don't know if other devices do this. We could add a --ledger-hmac argument for the time being and replace it with something more generic later?
Combined with #783 this should enable MuSig2 support, at least for the manual flow, since Bitcoin Core doesn't pass these fields (yet). The policy can be manually derived from a descriptor, though bitcoin/bitcoin#32659 would make that easier.
We could add a
--bip388-policy(or just--policy) option to thesigntxanddisplayaddresscommands.For devices that support it, e.g. Ledger, these commands would first register the policy if needed. Since displaying an address is a good idea anyway before sending money to it, I don't think we need a separate
registercommand.Ledger returns an HMAC after registration. Afaik this isn't documented in any BIP. I also don't know if other devices do this. We could add a
--ledger-hmacargument for the time being and replace it with something more generic later?Combined with #783 this should enable MuSig2 support, at least for the manual flow, since Bitcoin Core doesn't pass these fields (yet). The policy can be manually derived from a descriptor, though bitcoin/bitcoin#32659 would make that easier.