Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1SIbys-0000wz-RV for bitcoin-development@lists.sourceforge.net; Fri, 13 Apr 2012 08:35:46 +0000 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; Received: from mail-wg0-f53.google.com ([74.125.82.53]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128) (Exim 4.76) id 1SIbys-0007Nc-33 for bitcoin-development@lists.sourceforge.net; Fri, 13 Apr 2012 08:35:46 +0000 Received: by wgbfm10 with SMTP id fm10so2552687wgb.10 for ; Fri, 13 Apr 2012 01:35:40 -0700 (PDT) Received: by 10.180.24.66 with SMTP id s2mr2602336wif.7.1334306139877; Fri, 13 Apr 2012 01:35:39 -0700 (PDT) Received: from dvr.localnet (mail.360visiontechnology.com. [92.42.121.178]) by mx.google.com with ESMTPS id k6sm3194425wie.9.2012.04.13.01.35.37 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 13 Apr 2012 01:35:37 -0700 (PDT) From: Andy Parkins 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: In-Reply-To: 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> 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 (andyparkins[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: 1SIbys-0007Nc-33 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Apr 2012 08:35:47 -0000 --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--