📅 Original date posted:2014-08-06 📝 Original message:-----BEGIN PGP SIGNED ...

Peter Todd [ARCHIVE] /

npub1m23…2np2

2023-06-07 15:24:47

in reply to nevent1q…zmj2

📅 Original date posted:2014-08-06
📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

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

iQFQBAEBCAA6BQJT4mgPMxxQZXRlciBUb2RkIChsb3cgc2VjdXJpdHkga2V5KSA8
cGV0ZUBwZXRlcnRvZGQub3JnPgAKCRAZnIM7qOfwhSYlCAC1ncAGQt53HKS+8/rq
OG0RGrqE2l2/qCM/ybd9M8TkwxaI3NB5bqfIus8dB5MnyiTBFS3ooN54kNNOHtSX
2rEzPJphtOj46tk3nqe1QO3cbFJPjBCtxZff51DWZckhCiO2Iy1Br3fK3v55iscp
1jxyZnpfgUG/Ivfx+h6vkisucBXgXJ82d5vzvMIMxixh4v2+4/SAcSY6HCLIpxmV
Z3l0NcGllnmWe5B6eftpWYUAREuoCNk/671jHmwu0cqk2u/Egrp776zxkEO1xivH
d0EWjJmlDLmQ2hEhkpBq46ji/2m4EWPLqTW/EXf3RzwU8uCEldbxEe2tyZ0d6oBt
NnTE
=AhV7
-----END PGP SIGNATURE-----

Author Public Key

npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2

Seen on

wss://relay.noswhere.com wss://relay.nostr.band

Show more details

Published at

2023-06-07 15:24:47

Kind type

1 Short Text Note

Event JSON

{ "id": "4ce9c337a08a61625d4b4dde2fc9bf41bed576f599ba772214f1e6146bf0e28c", "pubkey": "daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa", "created_at": 1686151487, "kind": 1, "tags": [ [ "e", "862ea3dc96b72bff70fc377e79d0d6efd56d14bf0babb9aa995ab55fc1b92d18", "", "root" ], [ "e", "ba34a3ad7986936876fe668f34bf7562c651733f95d1cb0b206b4c7a3fc5d7eb", "", "reply" ], [ "p", "1c61d995949cbfaf14f767784e166bde865c7b8783d7aa3bf0a1d014b70c0069" ] ], "content": "📅 Original date posted:2014-08-06\n📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA256\n\n\n\nOn 6 August 2014 10:30:11 GMT-07:00, Mark Friedenbach \u003cmark at monetize.io\u003e wrote:\n\u003eOn 08/06/2014 01:20 PM, Peter Todd wrote:\n\u003e\u003e The general case doesn't require transmission of any merkle data; it\n\u003e\u003e is derived from the tx data.\n\u003e\n\u003eHow can that possibly be the case? The information is hidden behind the\n\u003eMerkle root in the transaction. The validator needs to know whether\n\u003ethere is an expiry and what it is. What's it supposed to do, guess?\n\nThe 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.\n\nYou should read more about soft-forks; see the BIP. Remember that Bitcoin protocol development and deployment is not a centrally controlled activity.\n-----BEGIN PGP SIGNATURE-----\nVersion: APG v1.1.1\n\niQFQBAEBCAA6BQJT4mgPMxxQZXRlciBUb2RkIChsb3cgc2VjdXJpdHkga2V5KSA8\ncGV0ZUBwZXRlcnRvZGQub3JnPgAKCRAZnIM7qOfwhSYlCAC1ncAGQt53HKS+8/rq\nOG0RGrqE2l2/qCM/ybd9M8TkwxaI3NB5bqfIus8dB5MnyiTBFS3ooN54kNNOHtSX\n2rEzPJphtOj46tk3nqe1QO3cbFJPjBCtxZff51DWZckhCiO2Iy1Br3fK3v55iscp\n1jxyZnpfgUG/Ivfx+h6vkisucBXgXJ82d5vzvMIMxixh4v2+4/SAcSY6HCLIpxmV\nZ3l0NcGllnmWe5B6eftpWYUAREuoCNk/671jHmwu0cqk2u/Egrp776zxkEO1xivH\nd0EWjJmlDLmQ2hEhkpBq46ji/2m4EWPLqTW/EXf3RzwU8uCEldbxEe2tyZ0d6oBt\nNnTE\n=AhV7\n-----END PGP SIGNATURE-----", "sig": "886bd46c460034498b2739e82401e51b3b6a14dc878a40d9bd8312452de3ad40999501e4c45b6ead98734ee33fed7e4f27c505b930795a9c9d1256916cd5f3d8" }