1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
|
Return-Path: <pete@petertodd.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 5EDEDD3B
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 15 Aug 2018 21:46:26 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from outmail149056.authsmtp.com (outmail149056.authsmtp.com
[62.13.149.56])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id B9222774
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 15 Aug 2018 21:46:25 +0000 (UTC)
Received: from mail-c245.authsmtp.com (mail-c245.authsmtp.com [62.13.128.245])
by punt24.authsmtp.com. (8.15.2/8.15.2) with ESMTP id w7FLkMUG096093;
Wed, 15 Aug 2018 22:46:22 +0100 (BST)
(envelope-from pete@petertodd.org)
Received: from petertodd.org (ec2-52-5-185-120.compute-1.amazonaws.com
[52.5.185.120]) (authenticated bits=0)
by mail.authsmtp.com (8.15.2/8.15.2) with ESMTPSA id w7FLkK80006011
(version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
Wed, 15 Aug 2018 22:46:21 +0100 (BST)
(envelope-from pete@petertodd.org)
Received: from [127.0.0.1] (localhost [127.0.0.1])
by petertodd.org (Postfix) with ESMTPSA id 404D740007;
Wed, 15 Aug 2018 21:46:20 +0000 (UTC)
Date: Wed, 15 Aug 2018 21:46:18 +0000
In-Reply-To: <CABm2gDpOvXg7_Yv9jkX=+a7ALXHgA5-4Oh4ZQnzp=pw5-0bZPA@mail.gmail.com>
References: <CACrqygD_5jpkTvvcFo7eHxZfiH4evzZQc=YB=opBo6M_0EsZTQ@mail.gmail.com>
<CABm2gDpOvXg7_Yv9jkX=+a7ALXHgA5-4Oh4ZQnzp=pw5-0bZPA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset=utf-8
Content-Transfer-Encoding: quoted-printable
Autocrypt: addr=pete@petertodd.org; keydata=mQENBE+Xo6MBCACpPhm2zLk6G65vB8Of
G04VyBus9Ht9jHhI0rMQ6Orai9luo0FbCPZGljnpi9GSrm6nG15aDtG84cjTVatJ3wmoAPDmcq/Q
PTaeEAY28us9QN4Fsqw0emJqiaQez9pd/5BYtOSG8vLZpAxXfnOgDH/YK6u9WdoX7/RgTAltcoGa
zmyJHZHjVzB5OoZzakuWDALdHAw40i3RO5KpjS+BetQPRH0nV8dW/56aZWFk8scIhhMWTEFM5GZ2
d0qz4lyfxqoGdpsDYqh9iakWz8ppFy19BC/XYxQhAaGb4abdQlw/CZ0ShWzW1RnlLJpAp7cC31mR
541x+EJjPW9o9+JrUBlVABEBAAG0H1BldGVyIFRvZGQgPHBldGVAcGV0ZXJ0b2RkLm9yZz6JAZkE
EwEIAIMCGwMCHgECF4BeFIAAAAAAFQBAYmxvY2toYXNoQGJpdGNvaW4ub3JnMDAwMDAwMDAwMDAw
MDAwMDExZDlmNjkzMWU2NWY4MTRjNmYzYjIyMTczNmIwYzQ1ZjI1ZTAzNjVhM2QxNTZmYQULCQgH
AwUVCAoJCwIWAAUCWcs3RwUJDBTHEAAKCRB/qxFCZ+T6BLuQB/9rNzkX9+tFAHg5o+e0LIqQe26d
KhZQiB5GF6uJKiDGzna8HeZqg83diIpjo4it6espMLDpwE5nKhlBFyAnZZBF44u/5+Y6Ilu4qDAF
S8vBQ1ls86a+Ai+q4ZArLaPnuQOwB4eTg8xc8SgUv+8oRHnoti4RCGQZuh1AkYU+w9tV03C1HKww
i9Ennv95kb49M+71wLJYuqCMiyLQ9NDtoLpxugqXhmWu9XZL+sS1ecb6xnxoxrM1FW7LkBw4XQxF
aEuHowv26KNGkINRjrfLKOZM988+c2E/wmYlbzi7Ondjw/92ooWRH+aHY3mnI1Ij4Fy0DFL6xwys
AtNBbzefoZyzuQENBE+Xo6MBCADB0197HdK48SqvipyPB49vlzfP6KHfcACZCg1JTqOt8KRJFwTP
3PTi/GJuUvt4io1UVG29+3e2X8eDbrxufP0YPr+0IbTE/EMgXizNN28Zf/VIR7bEv9oFXfn/4L3B
2L8rf61vw/W/u2b+z6MROC1qgWg3nOG6FwgiEeiBTlaLWhuwqgIdp6mdoOled50ym409o5kD6nXM
0MkqLOTMJTKwrYipoo0D0acLtiBLzxXdYgrqxT30eIxvMdkaj3mC5mNd7pHYSf3jQ7/BWAVkccRm
3o2e5F8oDEe6dkWYODjbKAAKkn2B9GoHsROaqeYdANd5VNiFJIzGWTCGkN8GjNEVABEBAAGJASUE
GAECAA8CGwwFAlTbOU4FCQ6plyMACgkQf6sRQmfk+gQO4gf/QpBTrZWPm1XOk8/gdnNqb2feqnRO
AQRqtIOxAlsETDAQdP2HlU9mTeJuJ0YfzrFjTAGKj3fw9YNnynu32BZVD2ueIhGg8bWyhIrJtMYB
wSKQ5/hojGlzU91qXd/VAxTsOmeIXgYyL7siRhNRCyHYZevRHZ8GLJ7XklYxRAj8o2dtO/wmhUTx
jax5GRMhMkJUtOhjhPqmAfE+l7HF/TD/CCWyL5Uj2ILeWHSetSOlAqFj0ApcDvZlJtHMmfAiCjGY
0FSxNcaOYb2aUKrC7LnsfnvAPxd5XZS7LPuLmZ+GGm+kmxuIh8a0xykxw2eCGCnlWVgnZUCMYrUd
Wy93HBYT8g==
To: =?ISO-8859-1?Q?Jorge_Tim=F3n?= <jtimon@jtimon.cc>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
=?ISO-8859-1?Q?Jorge_Tim=F3n_via_bitcoin-dev?=
<bitcoin-dev@lists.linuxfoundation.org>,
Christopher Allen <ChristopherA@lifewithalacrity.com>
From: Peter Todd <pete@petertodd.org>
Message-ID: <367FF84A-219E-4735-B9F7-09CEFEB20587@petertodd.org>
X-Server-Quench: a6629720-a0d4-11e8-8e1a-9cb654bb2504
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aQdMdwcUGUATAgsB Am4bWVZeVFt7W2I7 bghPaBtcak9QXgdq
T0pMXVMcUwIefUd6 Dh4eUh9ydgQIeX9x ZE4sD3ZdXk19d0Zg
E04AEXAHZDJodWhK URFFflAGdgZOLE1H b1B7GhFYa3VsNCMk
FAgyOXU9MCtqYA9R SwAILFQdCU8NVhkE cCovIQgVOwU9XSg9 LgxO
X-Authentic-SMTP: 61633532353630.1039:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 52.5.185.120/25
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
anti-virus system.
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW
autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] Claiming an OP_RETURN Prefix
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Aug 2018 21:46:26 -0000
On August 15, 2018 8:33:43 PM UTC, "Jorge Tim=C3=B3n via bitcoin-dev" <bit=
coin-dev@lists=2Elinuxfoundation=2Eorg> wrote:
>op_return outputs can be pruned because they are not spendable=2E
>putting a hash on in the witness script data won't make things better
>(it would actually make them worse) and it definitely doesn't help
>"block size bloat"=2E
>I think I'm missing some context, but if you're using op_return purely
>for timestamping I would recommend using pay 2 contract instead=2E
If you're *actually* just doing timestamping you're better off using OpenT=
imestamps=2E But many times people think they're just doing timestamping in=
reality mere timestamps are insufficient for the task=2E
Notably, this is something the Satoshi Bitcoin white paper gets wrong, inc=
orrectly describing Bitcoin as a timestamping system: timestamping is insuf=
ficient to prevent double-spends=2E
--=20
https://petertodd=2Eorg 'peter'[:-1]@petertodd=2Eorg
|
