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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1VZrqF-0008Be-Jj
for bitcoin-development@lists.sourceforge.net;
Sat, 26 Oct 2013 00:34:59 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.175 as permitted sender)
client-ip=74.125.82.175; envelope-from=gavinandresen@gmail.com;
helo=mail-we0-f175.google.com;
Received: from mail-we0-f175.google.com ([74.125.82.175])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VZrqD-00077I-LB
for bitcoin-development@lists.sourceforge.net;
Sat, 26 Oct 2013 00:34:59 +0000
Received: by mail-we0-f175.google.com with SMTP id t61so4435904wes.6
for <bitcoin-development@lists.sourceforge.net>;
Fri, 25 Oct 2013 17:34:51 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.180.211.237 with SMTP id nf13mr565629wic.55.1382747691437;
Fri, 25 Oct 2013 17:34:51 -0700 (PDT)
Received: by 10.194.156.163 with HTTP; Fri, 25 Oct 2013 17:34:51 -0700 (PDT)
Date: Sat, 26 Oct 2013 10:34:51 +1000
Message-ID: <CABsx9T2UfGNiCuCzw00Tgk8aZQ=ZcnT=bDFqrsrYC7r355QRmw@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=001a11c25f42f6573804e99a08b3
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information. [URIs: github.com]
-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
(gavinandresen[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-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: 1VZrqD-00077I-LB
Subject: [Bitcoin-development] Feedback requested: "reject" p2p message
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: Sat, 26 Oct 2013 00:34:59 -0000
--001a11c25f42f6573804e99a08b3
Content-Type: text/plain; charset=ISO-8859-1
Mike Hearn has been lobbying for an "error" message in the Bitcoin p2p
protocol for years (at least since the "ban peers if they send us garbage"
denial-of-service mitigation code was pull-requested). This came up again
with my proposed "smartfee" changes, which would drop low-priority or
low-fee transactions.
In short, giving peers feedback about why their blocks or transactions are
dropped or why they are being banned should help interoperability between
different implementations, and will give SPV (simplified payment
verification) clients feedback when their transactions are rejected due to
insufficient priority or fees.
See the gist for details, I'm looking for feedback and planning on
implementing this before circling back to finish the 'smart fee' work:
https://gist.github.com/gavinandresen/7079034
--
--
Gavin Andresen
--001a11c25f42f6573804e99a08b3
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Mike Hearn has been lobbying for an "error" mess=
age in the Bitcoin p2p protocol for years (at least since the "ban pee=
rs if they send us garbage" denial-of-service mitigation code was pull=
-requested). This came up again with my proposed "smartfee" chang=
es, which would drop low-priority or low-fee transactions.<br>
<br>In short, giving peers feedback about why their blocks or transactions =
are dropped or why they are being banned should help interoperability betwe=
en different implementations, and will give SPV (simplified payment verific=
ation) clients feedback when their transactions are rejected due to insuffi=
cient priority or fees.<div>
<br></div><div>See the gist for details, I'm looking for feedback and p=
lanning on implementing this before circling back to finish the 'smart =
fee' work:</div><div><br></div><div>=A0 =A0<a href=3D"https://gist.gith=
ub.com/gavinandresen/7079034">https://gist.github.com/gavinandresen/7079034=
</a><br>
</div><div><br></div><div>-- <br>--<br>Gavin Andresen<br>
</div><div><br></div></div>
--001a11c25f42f6573804e99a08b3--
|
