From: Marco Falke <falke.marco@gmail•com>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] consensus rule change for TX fee safety
Date: Thu, 3 Mar 2016 16:55:25 +0100 [thread overview]
Message-ID: <CAKJqnrFc0i_eoG4gfU5zM_b4xbZrHqnR9-ajfB8=JAWJ4xAnaQ@mail.gmail.com> (raw)
In-Reply-To: <20160303152836.GA27932@savin.petertodd.org>
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
next prev parent reply other threads:[~2016-03-03 15:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 13:02 Alice Wonder
2016-03-03 15:04 ` Henning Kopp
2016-03-03 15:28 ` Peter Todd
2016-03-03 15:55 ` Marco Falke [this message]
2016-03-03 15:36 ` Jorge Timón
2016-03-03 16:38 ` Dave Scotese
2016-03-03 15:29 ` Jonas Schnelli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKJqnrFc0i_eoG4gfU5zM_b4xbZrHqnR9-ajfB8=JAWJ4xAnaQ@mail.gmail.com' \
--to=falke.marco@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox