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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <pete@petertodd.org>) id 1Z32GA-0004ZJ-Ex
for bitcoin-development@lists.sourceforge.net;
Thu, 11 Jun 2015 13:11:06 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of petertodd.org
designates 62.13.148.100 as permitted sender)
client-ip=62.13.148.100; envelope-from=pete@petertodd.org;
helo=outmail148100.authsmtp.co.uk;
Received: from outmail148100.authsmtp.co.uk ([62.13.148.100])
by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1Z32G8-0001BV-8p for bitcoin-development@lists.sourceforge.net;
Thu, 11 Jun 2015 13:11:06 +0000
Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235])
by punt15.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t5BDAusc023291;
Thu, 11 Jun 2015 14:10:56 +0100 (BST)
Received: from savin.petertodd.org (75-119-251-161.dsl.teksavvy.com
[75.119.251.161]) (authenticated bits=128)
by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t5BDAnkd053989
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
Thu, 11 Jun 2015 14:10:51 +0100 (BST)
Date: Thu, 11 Jun 2015 09:10:48 -0400
From: Peter Todd <pete@petertodd.org>
To: Aaron Voisine <voisine@gmail.com>
Message-ID: <20150611131048.GA24053@savin.petertodd.org>
References: <CAFdHNGgtgWGu8gnnJfM0EcVn2m_Wff5HPwAe-9FBvjR++q0Q-Q@mail.gmail.com>
<CANEZrP3+jW3BO=Zv41CGubJL7bSZ==o=Wp83K6Q0xL4PP+0ZUQ@mail.gmail.com>
<CACq0ZD6Qr7F7_20Nfd0a8TTHEVMR0fxu-T5bO4FfN1Lp9PcGDQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature"; boundary="uAKRQypu60I7Lcqm"
Content-Disposition: inline
In-Reply-To: <CACq0ZD6Qr7F7_20Nfd0a8TTHEVMR0fxu-T5bO4FfN1Lp9PcGDQ@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Server-Quench: 4914aa26-103b-11e5-b396-002590a15da7
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aQdMdwMUEkAaAgsB AmMbWlBeUV17XGI7 bA9PbARUfEhLXhtr
VklWR1pVCwQmRRlz cm9ACU1ycgZPcHc+ ZEZmXXYVWE17cRcs
QEhJFG0FN3phaTUa TRJbfgVJcANIexZF O1F6ACIKLwdSbGoL
NQ4vNDcwO3BTJTpY RgYVKF8UXXNDJiQ7 XxcZFDF9VXY9eW0d
IhFuBl8HF0EPP18j eV4sUlIRNR4JD2UA
X-Authentic-SMTP: 61633532353630.1023:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 75.119.251.161/587
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
anti-virus system.
X-Spam-Score: -1.5 (-)
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 SPF_PASS SPF: sender matches SPF record
X-Headers-End: 1Z32G8-0001BV-8p
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Proposal: SPV Fee Discovery mechanism
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, 11 Jun 2015 13:11:06 -0000
--uAKRQypu60I7Lcqm
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Jun 10, 2015 at 02:18:30PM -0700, Aaron Voisine wrote:
> The other complication is that this will tend to be a lagging indicator
> based on network congestion from the last time you connected. If we assume
> that transactions are being dropped in an unpredictable way when blocks a=
re
> full, knowing the network congestion *right now* is critical, and even th=
en
> you just have to hope that someone who wants that space more than you do
> doesn't show up after you disconnect.
Hence the need for ways to increase fees on transactions after initial
broadcast like replace-by-fee and child-pays-for-parent.
Re: "dropped in an unpredictable way" - transactions would be dropped
lowest fee/KB first, a completely predictable way.
--=20
'peter'[:-1]@petertodd.org
0000000000000000124bae79afdcee9267b4e6f8137758b8b4135455cd8e3bfd
--uAKRQypu60I7Lcqm
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
iQGrBAEBCACVBQJVeYjTXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDAxMjRiYWU3OWFmZGNlZTkyNjdiNGU2ZjgxMzc3NThiOGI0
MTM1NDU1Y2Q4ZTNiZmQvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkftQzggAiAeRliTQzvvKL8mALd7Z66K7
hjQJv2M56U2t575fV/uvx+dcBH51Vtg1SAL6/qecguWmexJnu6bOLC8VVGkyXcU5
DRIzLbe7XrhSCVXzInjDz1W3WrIPlTGlN5rJVt99GPe4Nw0Auxx/KdJrgHs41Fi2
lnw/D55P2xBav6++KxkT452zccD3tB7i23Apy2J+zsYtHgtojmZSAg6asuZHAaLK
IZ5w104IXW51S7qpRQCEfqMfH01pPdmWiYGD0dbK5EQGo8NwCueGaYmBzjQuR2Si
avgKbiMFiHEgagBm/v42BHzjifipjuAio3J4PcnR68Z1kaKGv8o3Th6xn1IQZQ==
=Z5It
-----END PGP SIGNATURE-----
--uAKRQypu60I7Lcqm--
|
