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
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
|
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 <andyparkins@gmail.com>) 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 <bitcoin-development@lists.sourceforge.net>;
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 <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>
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: <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, 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--
|
