diff options
author | Glenn Willen <gwillen@nerdnet.org> | 2018-10-26 15:31:41 -0700 |
---|---|---|
committer | Pieter Wuille <pieter.wuille@gmail.com> | 2018-12-03 10:37:08 -0800 |
commit | db445d4e5a25ff13de014dbbf43bb99cde8b8769 (patch) | |
tree | 133cfa34c9677e5d5c2554c0283164c4fa2fea50 /src/policy/rbf.cpp | |
parent | ad94165db91c0416634459e18f173c5cd063dc55 (diff) | |
download | bitcoin-db445d4e5a25ff13de014dbbf43bb99cde8b8769.tar.xz |
Refactor PSBTInput signing to enforce invariant
Refactor the process of PSBTInput signing to enforce the invariant that
a PSBTInput always has _either_ a witness_utxo or a non_witness_utxo,
never both.
This simplifies the logic of SignPSBTInput slightly, since it no longer
has to deal with the "both" case. When calling it, we now give it, in
order of preference: (1) whichever of the utxo fields was already
present in the PSBT we received, or (2) if neither, the
non_witness_utxo field, which is just a copy of the input transaction,
which we get from the wallet.
SignPSBTInput no longer has to remove one of the two fields; instead, it
will check if we have a witness signature, and if so, it will replace
the non_witness_utxo with the witness_utxo (which is smaller, as it is
just a copy of the output being spent.)
Add PSBTInput::IsSane checks in two more places, which checks for
both utxo fields being present; we will now give an RPC error early on
if we are supplied such a malformed PSBT to fill in.
Also add a check to FillPSBT, to avoid touching any input that is
already signed. (This is now redundant, since we should no longer
potentially harm an already-signed input, but it's harmless.)
fixes #14473
Github-Pull: #14588
Diffstat (limited to 'src/policy/rbf.cpp')
0 files changed, 0 insertions, 0 deletions