3 commits

Author	SHA1	Message	Date
SomberNight	73cf007048	transaction: allow PSBT input to have both UTXO and WITNESS_UTXO ... - make sure they are consistent - only keep one of them internally (UTXO), and only serialise with UTXO (not both) fixes #6429	2020-07-22 02:44:33 +02:00
SomberNight	aa518c0ea5	psbt: allow insecure signing of legacy UTXOs without full previous tx ... When "importing" a psbt, we accept witness utxos even for legacy inputs (warning shown to user in gui). When "exporting" a psbt, we follow the spec; except when exporting as a QR code, in which case we include witness utxos for all inputs. This makes QR codes for psbts with legacy inputs feasible, just like they were before, with our custom tx serialization format (with the same risk, of burning coins as miner fees).	2019-11-07 02:40:10 +01:00
SomberNight	bafe8a2fff	integrate PSBT support natively. WIP	2019-11-04 22:24:36 +01:00