bitcoin/doc/release-notes-16525.md

RPC changes
-----------

Exposed transaction version numbers are now treated as unsigned 32-bit integers
instead of signed 32-bit integers. This matches their treatment in consensus
logic. Versions greater than 2 continue to be non-standard (matching previous
behavior of smaller than 1 or greater than 2 being non-standard). Note that
this includes the joinpsbt command, which combines partially-signed
transactions by selecting the highest version number.
Dump transaction version as an unsigned integer in RPC/TxToUniv Consensus-wise we already treat it as an unsigned integer (the only rules around it are in CSV/locktime handling), but changing the underlying data type means touching consensus code for a simple cleanup change, which isn't really worth it. See-also, https://github.com/rust-bitcoin/rust-bitcoin/pull/299 2019-08-01 17:54:48 -04:00			`RPC changes`
			`-----------`

			`Exposed transaction version numbers are now treated as unsigned 32-bit integers`
			`instead of signed 32-bit integers. This matches their treatment in consensus`
			`logic. Versions greater than 2 continue to be non-standard (matching previous`
Additionally treat Tx.nVersion as unsigned in joinpsbts This gets its own release note callout, though doesn't appear to violate the BIP as the BIP appears to be underspecified. We probably want to update BIP 174 to mention how version numbers are combined. 2019-09-03 10:53:45 -04:00			`behavior of smaller than 1 or greater than 2 being non-standard). Note that`
			`this includes the joinpsbt command, which combines partially-signed`
			`transactions by selecting the highest version number.`