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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gmaxwell@gmail.com>) id 1XD2Zy-0000sJ-Am
for bitcoin-development@lists.sourceforge.net;
Fri, 01 Aug 2014 02:28:22 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.220.176 as permitted sender)
client-ip=209.85.220.176; envelope-from=gmaxwell@gmail.com;
helo=mail-vc0-f176.google.com;
Received: from mail-vc0-f176.google.com ([209.85.220.176])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1XD2Zx-0001st-IV
for bitcoin-development@lists.sourceforge.net;
Fri, 01 Aug 2014 02:28:22 +0000
Received: by mail-vc0-f176.google.com with SMTP id id10so5668970vcb.7
for <bitcoin-development@lists.sourceforge.net>;
Thu, 31 Jul 2014 19:28:15 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.220.74.10 with SMTP id s10mr2839095vcj.61.1406860095900;
Thu, 31 Jul 2014 19:28:15 -0700 (PDT)
Received: by 10.52.187.132 with HTTP; Thu, 31 Jul 2014 19:28:15 -0700 (PDT)
In-Reply-To: <3826251.5rGb1MfKOu@crushinator>
References: <CA+iPb=HkxeVPF0SynxCPgUkq4msrdfayFrVNFjzg29rFwqXv1w@mail.gmail.com>
<3826251.5rGb1MfKOu@crushinator>
Date: Thu, 31 Jul 2014 19:28:15 -0700
Message-ID: <CAAS2fgQPVwMzHBWmbRLBHZcm+YEbioqUHoL_a-SLr9yWDmguiw@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Matt Whitlock <bip@mattwhitlock.name>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(gmaxwell[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1XD2Zx-0001st-IV
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] deterministic transaction expiration
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 01 Aug 2014 02:28:22 -0000
On Thu, Jul 31, 2014 at 6:38 PM, Matt Whitlock <bip@mattwhitlock.name> wrot=
e:
> It would make more sense to introduce a new script opcode that pushes the=
current block height onto the operand stack. Then you could implement arbi=
trary logic about which blocks the transaction can be valid in. This would =
require that the client revalidate all transactions in its mempool (really,=
only those making use of this opcode) whenever the chain tip changes.
Transactions that become invalid later are have pretty severe
consequences because they might mean that completely in an absence of
fraud transactions are forever precluded due to a otherwise harmless
reorg.
While there may be uses for that, the resulting outputs should be
considered differently fungible=E2=80=94 like coinbases which are immature=
=E2=80=94
and should probably be only used with great caution... not as a
mechanism for ordinary transactions.
|
