Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 74.125.82.53 as permitted sender)
	client-ip=74.125.82.53; envelope-from=andyparkins@gmail.com;
	helo=mail-wg0-f53.google.com; 
From: Andy Parkins <andyparkins@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Date: Fri, 13 Apr 2012 09:35:28 +0100
User-Agent: KMail/1.13.6 (Linux/3.0.0-1-686-pae; KDE/4.6.3; i686; ; )
References: <CA+8xBpc5CZ9Sx4MwPdeS0-5frnV9B+mJ5OwcPoUVrygTawiJBg@mail.gmail.com>
In-Reply-To: <CA+8xBpc5CZ9Sx4MwPdeS0-5frnV9B+mJ5OwcPoUVrygTawiJBg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart1982315.vsJSpkDXUD";
	protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <201204130935.35227.andyparkins@gmail.com>
Subject: Re: [Bitcoin-development] Bitcoin TX fill-or-kill deterministic
	behavior
Precedence: list

--nextPart1982315.vsJSpkDXUD
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

On 2012 April 12 Thursday, Jeff Garzik wrote:
=20
> One of my From-Day-One complaints about bitcoin is that transactions
> behavior could be far more deterministic (predictable), from a user
> standpoint.  Transactions in the current system can easily remain in
> limbo forever.
>=20
> One big step in making transactions behave more predictably would be
> to remove transactions from the memory pool, if they have not made it
> into a block for a couple days.  i.e.

A change I've wished for for a while (but I suspect it is too big a change =
to=20
ever make it) is that a transaction announcement include the block the user=
=20
wants to base on.  It would only be in the protocol message, not the=20
transaction stored in the blockchain.

The advantage is that (1) it protects against double spends without needing=
 a=20
confirmation period; as a merchant I can instantly spend a 1-confirmation=20
transaction by creating my transaction with that 1-confirm as its "base".  =
(2)=20
your expiry from memory pool becomes easy -- if the "base" is more than N=20
blocks below the current head, then that transaction won't be included.

Retransmission is possible with the base updated.


Andy

=2D-=20
Dr Andy Parkins
andyparkins@gmail.com

--nextPart1982315.vsJSpkDXUD
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEABECAAYFAk+H5VAACgkQwQJ9gE9xL21KWQCfQXw3NX9z80QUgBrvQ7U9kOZe
jcIAn3pJKQVZhFLkwOtcsuRrLWq0nq6d
=0j8T
-----END PGP SIGNATURE-----

--nextPart1982315.vsJSpkDXUD--