[Bitcoin-development] deterministic transaction expiration
pete at petertodd.org
Wed Aug 6 17:38:23 UTC 2014
-----BEGIN PGP SIGNED MESSAGE-----
On 6 August 2014 10:30:11 GMT-07:00, Mark Friedenbach <mark at monetize.io> wrote:
>On 08/06/2014 01:20 PM, Peter Todd wrote:
>> The general case doesn't require transmission of any merkle data; it
>> is derived from the tx data.
>How can that possibly be the case? The information is hidden behind the
>Merkle root in the transaction. The validator needs to know whether
>there is an expiry and what it is. What's it supposed to do, guess?
The general case is all committed information is included in the transaction; the merkle tree is a compatibility path, as well as an optimisation for lite clients and applications.
You should read more about soft-forks; see the BIP. Remember that Bitcoin protocol development and deployment is not a centrally controlled activity.
-----BEGIN PGP SIGNATURE-----
Version: APG v1.1.1
-----END PGP SIGNATURE-----
More information about the bitcoin-dev