From: Alice Wonder <alice@librelamp.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] consensus rule change for TX fee safety
Date: Thu, 3 Mar 2016 05:02:11 -0800 [thread overview]
Message-ID: <56D835D3.9070902@librelamp.com> (raw)
I think the next hard fork should require a safety rule for TX fees.
https://blockchain.info/tx/6fe69404e6c12b25b60fcd56cc6dc9fb169b24608943def6dbe1eb0a9388ed08
15 BTC TX fee for < 7 BTC of outputs.
Probably either a typo or client bug.
My guess is the user was using a client that does not adjust TX fee, and
needed to manually set it in order to get the TX in the block sooner,
and meant 15 mBTC or something.
I suggest that either :
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
Either of those would have prevented this TX from going into a block.
Many people I know are scared of bitcoin, that they will make a TX and
make a mistake they can't undo.
Adding protections may help give confidence and there is precedence to
doing things to prevent typo blunders - a public address has a four byte
checksum to reduce the odds of a typo.
This kind of mistake is rare, so a fix could be included in the coming
HF for the possible July 2017 block increase.
Thank you for your time.
Alice Wonder
next reply other threads:[~2016-03-03 13:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 13:02 Alice Wonder [this message]
2016-03-03 15:04 ` [bitcoin-dev] consensus rule change for TX fee safety Henning Kopp
2016-03-03 15:28 ` Peter Todd
2016-03-03 15:55 ` Marco Falke
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=56D835D3.9070902@librelamp.com \
--to=alice@librelamp.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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