MIME-Version: 1.0
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
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin TX fill-or-kill deterministic
	behavior
Precedence: list

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