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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@exmulti.com>) id 1SIPf5-0003EV-Up
for bitcoin-development@lists.sourceforge.net;
Thu, 12 Apr 2012 19:26:31 +0000
X-ACL-Warn:
Received: from mail-vx0-f175.google.com ([209.85.220.175])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1SIPf5-000078-9m
for bitcoin-development@lists.sourceforge.net;
Thu, 12 Apr 2012 19:26:31 +0000
Received: by vcbfl13 with SMTP id fl13so2510161vcb.34
for <bitcoin-development@lists.sourceforge.net>;
Thu, 12 Apr 2012 12:26:25 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=mime-version:x-originating-ip:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type
:content-transfer-encoding:x-gm-message-state;
bh=Zx44q3BrDLv7ekDG5su1iFXNBaHNj++4IWpTbTpGaGc=;
b=QGdNbkTlMFxiNL30o8W0TIaTDwdVFE2ZdGp0dIjEHxGkqVZwp5K6rGruWLeAXHEGJO
Hmk2SiKkSvFrZ6JQbRWQp8lhf7La5AvTdQlNRU4djyH2bNtG6oyHIzcm2x8CGIDsrQnJ
dasHS+3bK/Qy53En+ylATeWgyrWIuJZdBUDHyvTiFWF/X6oOkSDRPYZil0BQpxjzTGIZ
D2VU8Vig5FcxKX2GUegAx9jdEAE6wBjb9hQoqTXERFDOOK1lGYSutcqvux33NKbhy7gh
gvd2OPqH9lRasmHxtfg/zZIY247WTH4De1B34GWZYO7IfiQdjiKGoKRady2nwVgF4kfo
cEhg==
MIME-Version: 1.0
Received: by 10.52.178.225 with SMTP id db1mr1564364vdc.26.1334258785746; Thu,
12 Apr 2012 12:26:25 -0700 (PDT)
Received: by 10.52.109.33 with HTTP; Thu, 12 Apr 2012 12:26:25 -0700 (PDT)
X-Originating-IP: [99.43.178.25]
In-Reply-To: <CALf2ePzvwW6VU0YA+6WNCBHzK2rGc5p1uXGvbYG2uS__S-bjoQ@mail.gmail.com>
References: <CA+8xBpc5CZ9Sx4MwPdeS0-5frnV9B+mJ5OwcPoUVrygTawiJBg@mail.gmail.com>
<CALf2ePzvwW6VU0YA+6WNCBHzK2rGc5p1uXGvbYG2uS__S-bjoQ@mail.gmail.com>
Date: Thu, 12 Apr 2012 15:26:25 -0400
Message-ID: <CA+8xBpctyu=VHQJMUiENY7q82hsP5Eti7gc9r4QT6aRwWsNE+A@mail.gmail.com>
From: Jeff Garzik <jgarzik@exmulti.com>
To: Alan Reiner <etotheipi@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQnS4xoYo9c8q6EExRGWRD/IpXwiC1NVY43oGkjYxiVdlsFBbWCngslwJED/5mHG5BTANRhH
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1SIPf5-000078-9m
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin TX fill-or-kill deterministic
behavior
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: Thu, 12 Apr 2012 19:26:32 -0000
On Thu, Apr 12, 2012 at 3:19 PM, Alan Reiner <etotheipi@gmail.com> wrote:
> My one big concern about this that users find a way to exploit this behav=
ior
> for themselves. =A0If it's too easy for users to create tx they know will=
get
> stuck and expire, it's no different than letting them cancel their zero-c=
onf
> transactions. =A0i.e. I pay 0.5 BTC in a store for a candy bar, so I send=
it
> using a combination of inputs and fees that I know will lead to it being
> stuck and expire.
>
> On the other hand, if such conditions are deterministic enough, it could =
be
> detected by the recipient and flagged.
>
> It's not a huge deal, but it's something to consider.
Do you have a -specific- concern that you feel may be exploited?
Expiration already occurs at random, as nodes shut down and restart,
log on and log off the network.
--=20
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com
|
