summaryrefslogtreecommitdiff
path: root/f4/95968fd87fe527a64f76f8696947f287882186
blob: e88887c3bec63df29ceff0b5d18df315334f13b0 (plain)
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
Return-Path: <falke.marco@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id EB71AACA
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu,  3 Mar 2016 15:55:26 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-io0-f169.google.com (mail-io0-f169.google.com
	[209.85.223.169])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id A64EB18C
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu,  3 Mar 2016 15:55:25 +0000 (UTC)
Received: by mail-io0-f169.google.com with SMTP id g203so31724080iof.2
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu, 03 Mar 2016 07:55:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:cc; 
	bh=nwzkUQEqjedeOQvRkPbewib4jkOt82+VO9EjuxHJQkA=;
	b=K5IjTOO7ZnuOv+6P/qWU8THoACX79SRkxywdzKe/q1/Y95vPPtsOELteQgExQ430Hn
	UFXUuR5l5UEyybajw1mkd9lPlEvvYvo4nRFpsE0ciyPMMVhlCcO0KwbMz1UcQZLn+aWH
	ZHkMMJAvbhknOFPvdF/YzWCXNJWEqZz1EFdlpw1Reqa/qDV/kshG6ixIqdCRKda7CW+3
	Lz4IUiuKDSmQpz6/E4K2lcH95PePa772sRajUFwTWzHJKsvspuuJrdsbYUpeX269eqCy
	qXt46r3JM1mXGnKdlcCaXKy8Lgo7EvCGjc9hsoSEXDPVmzeobqNcg6oI38BTN9p40FHV
	v3Gg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:in-reply-to:references:date
	:message-id:subject:from:cc;
	bh=nwzkUQEqjedeOQvRkPbewib4jkOt82+VO9EjuxHJQkA=;
	b=dV4K7LI/Of9lH7YsJi0nlOCwPkiE2VJQ5JQIt3Qw/o4Z06t4Cvbxr9nUrqyqm8/m+S
	qwdUySslMyStgZ0aJrJ1fNa+0hc6KWPgmdbF6Vya4u5hMaUXVz1rC1kWGgU79Ni8SPew
	r7YudsxS6d4JtavLDQVG5Nl6J3GllL9V0js/IWB5g/E3GV9E/Aa1frjIBATkQU1wB1O+
	4R+550gWce8OGcRlVKlqCfqhNFTKjAYbVt7MKKnFs03W5j3kOmBAk3ONrXMbmd7SBB5L
	2G7fG+ktLx5XlJNXDkIGIi/WifPHDUaImqoRtQIRTJtYfq1ORMMKtaqlAoac4MuHU9VJ
	OWhw==
X-Gm-Message-State: AD7BkJLZH2zrS5eB6EnPYxpJIKHiruA9F9/6sJHe9YPO8C7My6UypqcIKJgUoXxGNVtYXGON6KHkPozCiM5xCA==
MIME-Version: 1.0
X-Received: by 10.107.137.146 with SMTP id t18mr4352555ioi.147.1457020525148; 
	Thu, 03 Mar 2016 07:55:25 -0800 (PST)
Received: by 10.64.136.11 with HTTP; Thu, 3 Mar 2016 07:55:25 -0800 (PST)
In-Reply-To: <20160303152836.GA27932@savin.petertodd.org>
References: <56D835D3.9070902@librelamp.com>
	<20160303150418.GA2341@banane.informatik.uni-ulm.de>
	<20160303152836.GA27932@savin.petertodd.org>
Date: Thu, 3 Mar 2016 16:55:25 +0100
Message-ID: <CAKJqnrFc0i_eoG4gfU5zM_b4xbZrHqnR9-ajfB8=JAWJ4xAnaQ@mail.gmail.com>
From: Marco Falke <falke.marco@gmail.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Content-Type: text/plain; charset=UTF-8
X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, MISSING_HEADERS,
	RCVD_IN_DNSWL_LOW autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
X-Mailman-Approved-At: Thu, 03 Mar 2016 18:20:44 +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:55:27 -0000

2016-03-03 16:28 GMT+01:00 Peter Todd via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org>:
> Bitcoin Core already implements this safety limit with the "absurd fee"
> limit of 10000 * the minimum relay fee. This limit is active in both the
> wallet and the sendrawtransaction RPC call. Additionally for the wallet
> there is a user configurable -maxtxfee option to limit fees set by the
> wallet which currently defaults to 0.1 BTC.


It is planned for Bitcoin Core 0.13 to use -maxtxfee for both, the
wallet and the RPC interface (sendrawtransaction). (c.f.
https://github.com/bitcoin/bitcoin/pull/7084)

In regard to the issue, I agree with Jonas. Such large transaction
fees were historically caused by no or insufficient warnings from the
wallet software. And it's the responsibility of the operators to make
the wallet user friendly.

Apart from that, there are legit use cases where one would want to
"pay" a large transaction fee: It may be convenient for the miner to
just collect the fees instead of sending back the change on their own
transactions. Of course making sure to mine the high-fee tx themself.
Moreover, it could increase privacy if another party decides to "wash"
their bitcoins by letting the miner claim the "fee" and then have the
miner send back a fraction of the fee to a fresh address. Though, this
probably works best if a lot of participants are doing this.

Marco