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
|
Return-Path: <dev@jonasschnelli.ch>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 291D4C98
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 3 Mar 2016 15:29:36 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from server3 (server3.include7.ch [144.76.194.38])
by smtp1.linuxfoundation.org (Postfix) with ESMTP id A3EEA102
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 3 Mar 2016 15:29:35 +0000 (UTC)
Received: by server3 (Postfix, from userid 115)
id 7E6EA2D0078B; Thu, 3 Mar 2016 16:29:34 +0100 (CET)
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Spam-Level:
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00, FSL_HELO_NON_FQDN_1
autolearn=ham version=3.3.1
Received: from Jonass-MacBook-Pro.local (unknown [213.55.184.135])
by server3 (Postfix) with ESMTPSA id CFA122D00144
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 3 Mar 2016 16:29:33 +0100 (CET)
To: bitcoin-dev@lists.linuxfoundation.org
References: <56D835D3.9070902@librelamp.com>
From: Jonas Schnelli <dev@jonasschnelli.ch>
Message-ID: <56D8585A.1070804@jonasschnelli.ch>
Date: Thu, 3 Mar 2016 16:29:30 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0)
Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56D835D3.9070902@librelamp.com>
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature";
boundary="AxOf2jn0TLMbi4KRDOliVm2bEdBxKAEFm"
X-Mailman-Approved-At: Thu, 03 Mar 2016 15:34:04 +0000
Subject: Re: [bitcoin-dev] consensus rule change for TX fee safety
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Mar 2016 15:29:36 -0000
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--AxOf2jn0TLMbi4KRDOliVm2bEdBxKAEFm
Content-Type: multipart/mixed; boundary="sr1k6tsemMXMJK2BmOJoCCcCnkCQxm0mr"
From: Jonas Schnelli <dev@jonasschnelli.ch>
To: bitcoin-dev@lists.linuxfoundation.org
Message-ID: <56D8585A.1070804@jonasschnelli.ch>
Subject: Re: [bitcoin-dev] consensus rule change for TX fee safety
References: <56D835D3.9070902@librelamp.com>
In-Reply-To: <56D835D3.9070902@librelamp.com>
--sr1k6tsemMXMJK2BmOJoCCcCnkCQxm0mr
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Hi
> My guess is the user was using a client that does not adjust TX fee, an=
d
> needed to manually set it in order to get the TX in the block sooner,
> and meant 15 mBTC or something.
>=20
> I suggest that either :
>=20
> A) TX fee may not be larger than sum of outputs
> B) TX fee per byte may not be larger than 4X largest fee per byte in
> previous block
I don't think a such "feature" or lets say protection should be part of
the consensus layer.
Such checks should be done by the tx creation clients (wallets) =96 or =96=
nodes could have an option to not accept transaction with insane fees
into their mempool (policy).
</jonas>
--sr1k6tsemMXMJK2BmOJoCCcCnkCQxm0mr--
--AxOf2jn0TLMbi4KRDOliVm2bEdBxKAEFm
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJW2FhaAAoJECnUvLZBb1PsrXAP/1Kov99rXQsaO9hQKzF48EtI
l9VWHmHSaFno9avHxjEy6b+14X95ba7TOVze6rsLl9EGhOJ/PMJ319jGtdP/SXPs
G6fCGY7wfA/gIlcUNurPnuGZPnEwglpSvXkmMRxBfVFVga4g9CEmMum1fY7fr1LA
oKJpfi5cL0BTkD0QVtsYoof0FSzcpzFAQBdVWcCjRG+lRJLPzoZE7PK/xDAPRUR0
fJil6//QDMWVEI2vIf7ErE6v1ayivWV0lbcXrtTgu4HkmiYlA9V/19Uo+x9V77Qu
jYNByiUwIWqfzNNWNOypMRYeYzadsMc1HJbVMnt+OzWxiZWB35w6ZqQNQgJcaKP/
M3zdyr5FgTFzxq7tk/4SkR3m2lC0s3XfoiOH8zxmAle8Qwg+Wxy7ZnWjNwZvfl87
7t+jRRe0W6UTkRFo2nB/hByz4FZAp8/wgXq/s30pxDAuL1as5f56/gibO+0LRSBA
mJYv5vabXx7BMO6mYlElhr0uDnINBLEFAEUBUCyZrEPp51Lz/v6UeuWFFUg8yls3
YGSkw7+QkFi2OEUvzUSApvnCfZUIh//hJ1+IedEZl3Z1MgrYVemABsm67yOxKXDv
CoD9UPVIFhdM5RpAtVIesab34t2gXUXyHEtj1D9h3+0L304m8YGRWNQNLAnGQwlM
52ITlh4/ZP1Z8TBUMasj
=UB9i
-----END PGP SIGNATURE-----
--AxOf2jn0TLMbi4KRDOliVm2bEdBxKAEFm--
|
