Closes: #30294
Looking for approach (N)ACK.
Previously setting the bip32derivs
flag to false with the walletprocesspsbt
RPC correctly does not include bip32_derivs
for inputs in the PSBT, but does include bip32_derivs
for outputs.
User may want to actively strip all bip32 derivation paths from a PSBT for privacy reasons however. It may make sense to do this after signing your inputs and outputs during a manual coinjoin as demonstrated in the BIP174 example.
To me, this makes more sense to include in the Combiner
PSBT role. It’s then separated from signing done by the Signers
.
Therefore add functionality to combinepsbt
permitting stripping of all bip32_derivation
paths found in all provided psbts’ inputs and outputs.
As this RPC can be called with a single PSBT, it can be used to strip derivation paths from a PSBT with any number of participants.