Author: justusranvier at riseup.net 2015-06-19 17:48:25
Published on: 2015-06-19T17:48:25+00:00
In a message signed on June 19, 2015, Jeff Garzik discussed the need for multiple incompatible versions of a spend as a requirement for various refund contract protocols. A field in a transaction called nSequence is available for indicating when a protocol is in use, and transactions using these protocols can be easily differentiated from those that aren't, which is good from a payment assurance standpoint but bad from a privacy standpoint. The message is signed with a GnuPG v2 signature.
Updated on: 2023-06-09T23:48:05.057474+00:00