Some users requested support for BIP-322, which allows signing messages on behalf of arbitrary addresses (unlike legacy message signing, that only works for single-signature addresses).
Apart from generalizing message signing to multisig and miniscript wallets, this might also be useful for parties who want to be able to issue a proof of funds.
This feature could probably be implemented entirely inside the SIGN_PSBT flow, by recognizing the specially crafted PSBTs as specified by the BIP.
(Client libraries might implement a bit of syntactic sugar to help craft those special PSBTs)
Some users requested support for BIP-322, which allows signing messages on behalf of arbitrary addresses (unlike legacy message signing, that only works for single-signature addresses).
Apart from generalizing message signing to multisig and miniscript wallets, this might also be useful for parties who want to be able to issue a proof of funds.
This feature could probably be implemented entirely inside the
SIGN_PSBTflow, by recognizing the specially crafted PSBTs as specified by the BIP.(Client libraries might implement a bit of syntactic sugar to help craft those special PSBTs)