Author: Russell O'Connor 2017-05-13 17:11:27
Published on: 2017-05-13T17:11:27+00:00
On May 13, 2017, Luke Dashjr emailed about the need to specify a timeout for versionbits to avoid losing their meaning after deployment. Users can bundle a pair of similar transactions, one with transaction version bits set and another with a locktime set to add a timeout. Dashjr's formal condition includes a check for block version, but it does not prevent upgrading versionbits. Any txVersion that does not begin with 0b001 is unconditionally acceptable and available for further soft-forking.
Updated on: 2023-06-12T00:46:52.198174+00:00