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
|
Return-Path: <alex.mizrahi@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id B18AAB2E
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 16 May 2017 12:15:19 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-qk0-f176.google.com (mail-qk0-f176.google.com
[209.85.220.176])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 414CA175
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 16 May 2017 12:15:19 +0000 (UTC)
Received: by mail-qk0-f176.google.com with SMTP id u75so126145396qka.3
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 16 May 2017 05:15:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to;
bh=eT2rM98hzCi6kcngQQHO1mIDgRpeV8/bnCHQt3jus48=;
b=QtMFqBtLCe7bk9OPgzrP9P17tpt5+8K0AYraU/NVo+ESH/vBgSy2DiW6oRAuLSj6os
0y8vGASAO0s1dx0q1YfofwnavKMjxV+pcOWdxluZ7kO024goCsmWjiRAOWmDdXnQKwju
4mJYxkrO53sgumguSEge+JhlH6PSijWZ0nyLsGR4xQ6/YmbA8sS9eozzUUbl4igY7IQ1
x7gefqhVA50Mx0vfEJXUgnkhN+JdNGrQFM842pZhl9J4YHw3SSWR2sEOs9GRAgLw4QGh
+ImeeMKWocE32N4dqJaPMQKZKoGqNFgcVPKzdZIZeunqay4k+lmbfzXKBF7dmsBRVfFh
HQRQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to;
bh=eT2rM98hzCi6kcngQQHO1mIDgRpeV8/bnCHQt3jus48=;
b=pYciTaP2H0r3WL+w/2NUoZ3LjeJiwNMJrfsYHyCTO194+eYwvcqzJs/mKGah1cdpeG
ljmrpzrr1wjkjODxQCwUuCntIN6hdImOtd5KCFbnxmD4tEgHItHizEj6qPEvkIFerrJn
KejBUgNo1NQbuoRUqJWUI6smagHBx0yF2vcY9LVfvFMuG5gQOM7YivuJjF+w3Xb7pAvk
dnSM7TcdLb+Dznm/SSfO+KfAuGOi7MbHSJdkQ973ToGwern4y1I+PRQqtdYcQ3Pxla0e
1nmMB7AZ1Bl95PpcbrMXc5BoGf2W35hZ+C8PcwXnhecW40Ef1ggkdwGpkX4RWvj/NW1O
dBSg==
X-Gm-Message-State: AODbwcDIktqnzgD2ZZBRuAIlhwYZhWt9Ev8rXmxiBHzymcO/qmPNZkaZ
oqD7Kf4Az09U/agy0YNROwB+MeZnHrvMBhI=
X-Received: by 10.55.110.132 with SMTP id j126mr10878178qkc.227.1494936918320;
Tue, 16 May 2017 05:15:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.55.160.143 with HTTP; Tue, 16 May 2017 05:15:17 -0700 (PDT)
In-Reply-To: <20170223011147.GB905@savin.petertodd.org>
References: <20170223011147.GB905@savin.petertodd.org>
From: Alex Mizrahi <alex.mizrahi@gmail.com>
Date: Tue, 16 May 2017 15:15:17 +0300
Message-ID: <CAE28kUTxc4KPvijiaJQ6M=LDPf_Du1pFdehfTtXtqs0hOtyWTw@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="94eb2c05c09cfa6b60054fa31fe9"
X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
RCVD_IN_DNSWL_NONE,
RCVD_IN_SORBS_SPAM autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] TXO commitments do not need a soft-fork to be
useful
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: Tue, 16 May 2017 12:15:19 -0000
--94eb2c05c09cfa6b60054fa31fe9
Content-Type: text/plain; charset="UTF-8"
> Something I've recently realised is that TXO commitments do not need to be
> implemented as a consensus protocol change to be useful.
You're slow, Peter. I figured this out back in 2013:
https://bitcointalk.org/index.php?topic=153662.10
--94eb2c05c09cfa6b60054fa31fe9
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><br>=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">Something I've recent=
ly realised is that TXO commitments do not need to be<br>
implemented as a consensus protocol change to be useful.=C2=A0</blockquote>=
<div><br></div><div>You're slow, Peter. I figured this out back in 2013=
:</div><div><br></div><div><a href=3D"https://bitcointalk.org/index.php?top=
ic=3D153662.10">https://bitcointalk.org/index.php?topic=3D153662.10</a><br>=
</div></div></div></div>
--94eb2c05c09cfa6b60054fa31fe9--
|
