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
|
Return-Path: <jtimon@jtimon.cc>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id E8E9EEDA
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 5 Oct 2015 15:42:58 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com
[209.85.212.172])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 43357170
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 5 Oct 2015 15:42:58 +0000 (UTC)
Received: by wicge5 with SMTP id ge5so126677672wic.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 05 Oct 2015 08:42:57 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type
:content-transfer-encoding;
bh=d9zqtoKI5ob3cd0qW0sjDDSD19NHvl8Lj5F2odbAjIk=;
b=H9R3nwAyxrCMx29V7DVYE+rY5YukrwnqwyY1ogKNc4KhL9oZXzVXGVRPrQ9vV+nLay
Fxxn0ICuvoIq9bIc6nFEXJ5v5mpPAuzIR9CwWYL8M1afT3TfFXv9N76c57RBhnybNpqK
/59Bz+1jaVGltlpQApWIINbWDHQJpwYFP7JcvLXY843XPrRP86NYcb6sDZELcVPEyLE6
fvA9uJ73ayFBI8ZC4l1ZiKKBllt7WtqqDbh9o9sngftHpaYnqJTglCG9pDKNUo/IqqL4
TI2ngF7ROat0BKIsMxLL9ku94Y9tW24S41Ffv01kJaj/qQVSwRcaU17Tz9qY0ulP9D8d
iNsA==
X-Gm-Message-State: ALoCoQlfiILZmWtNRhUb9DT3Z1KY908kM14IpV1D14q0Uhnb19sApR6J1H/jOUwyw8t3Ir9Sg0AW
MIME-Version: 1.0
X-Received: by 10.194.246.161 with SMTP id xx1mr30808149wjc.26.1444059777081;
Mon, 05 Oct 2015 08:42:57 -0700 (PDT)
Received: by 10.194.114.199 with HTTP; Mon, 5 Oct 2015 08:42:56 -0700 (PDT)
In-Reply-To: <CAP63atYmt5zEexcon+-jBTFcc=toAX0Bbn5J+R0Yktb1MbZirQ@mail.gmail.com>
References: <CAKfs=Z_jVKtjeSHM1a6n+ch6WcazkshmDgN4Wi1K_kLBUE4o4w@mail.gmail.com>
<BLU436-SMTP132FA09C343ACB7C82E6C98C64B0@phx.gbl>
<CA+w+GKT0Th4Tpk=cCxfJwsMdB5NLrARACU3_qiRn4Ns7z_PXYQ@mail.gmail.com>
<CADm_WcaVbj98G9acqbwUxYudHhWh01FLpm5KgL3rqHffd5WCXg@mail.gmail.com>
<CA+w+GKTkos5gwZmN_1c7wUFmJgZMJGzZbaZeWO=Rwt3Ta3Zbzw@mail.gmail.com>
<CABm2gDp1r78OtM=MfHqvV17-6N=nCG+hFOwqL0R6DHz9SjLmsg@mail.gmail.com>
<CAP63atY+yH5BinWYAyxkqER5wA9Lj6pFC0LritSDLcDuBVbXrg@mail.gmail.com>
<CABm2gDqi2tHHVN6NqsGwhUka+Scza-UcLe=_UhxZx8hvytt5BQ@mail.gmail.com>
<CAP63atYmt5zEexcon+-jBTFcc=toAX0Bbn5J+R0Yktb1MbZirQ@mail.gmail.com>
Date: Mon, 5 Oct 2015 17:42:56 +0200
Message-ID: <CABm2gDq7woaxPxSCTz6szzQdngjpXiBuT4319tUEQGgyfcEw4A@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
To: =?UTF-8?Q?Cl=C3=A9ment_Elbaz?= <clem.ds@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
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
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Let's deploy BIP65 CHECKLOCKTIMEVERIFY!
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development 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: Mon, 05 Oct 2015 15:42:59 -0000
On Mon, Oct 5, 2015 at 2:29 PM, Cl=C3=A9ment Elbaz <clem.ds@gmail.com> wrot=
e:
> The problem is that some transactions that are meaningless to you are
> actually meaningful to people using an upgraded Bitcoin software.
>
> Therefore during a softfork, while you can not miss the existence of a
> transaction, you can miss its meaning.
Why would you care about payments to other people?
The scriptPubKey's that you give to your payers certainly have meaning to y=
ou.
> But as soon as you try to actually use Bitcoin (that is, calculate the
> accurate balance of a wallet in a very broad sense), you can be led a wro=
ng
> result if you did not upgrade, which is a critical problem for financial
> software.
What is it important that you are able to calculate balances of
wallets that aren't yours?
> And because nothing prevent people to send you transactions of a new type=
,
> you have no way to "opt out" of this problem.
Why would anyone "pay you" to a scriptPubKey you don't understand?
I can "pay" the bill of my internet services by burying cash in a park
nearby my house for my provider to pick up later.
But if I don't tell my provider, it will never know. If I inform it, I
will get an answer: "no, sorry, we won't accept this new 'form of
payment' of yours as payment".
|
