From: Damian Williamson <willtech@live•com.au>
To: "bitcoin-dev@lists•linuxfoundation.org"
<bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] BIP 177: UTPFOTIB - Use Transaction Priority For Ordering Transactions In Blocks
Date: Sun, 24 Dec 2017 02:57:38 +0000 [thread overview]
Message-ID: <PS2P216MB0179FE1CAF04AB860A5F36719D000@PS2P216MB0179.KORP216.PROD.OUTLOOK.COM> (raw)
[-- Attachment #1: Type: text/plain, Size: 1269 bytes --]
BIP 177: UTPFOTIB - Use Transaction Priority For Ordering Transactions In Blocks
This BIP proposes to address the issue of transactional reliability in Bitcoin, where valid transactions may be stuck in the mempool for extended periods.
There are two key issues to be resolved:
1. The current transaction bandwidth limit.
2. The current ad-hoc methods of including transactions in blocks resulting in variable and confusing confirmation times for valid transactions, including transactions with a valid fee that may never confirm.
It is important with any change to protect the value of fees as these will eventually be the only payment that miners receive. Rather than an auction model for limited bandwidth, the proposal results in a stable fee for priority service auction model.
I will post the full proposal up on to my blog in the coming days and, re-review incorporating feedback that I have received on and off thread. It would not be true to suggest that all feedback received has been entirely positive although, most of it has been constructive.
The previous threads for this BIP are available here:
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-December/subject.html
Regards,
Damian Williamson
[-- Attachment #2: Type: text/html, Size: 2490 bytes --]
next reply other threads:[~2017-12-24 2:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-24 2:57 Damian Williamson [this message]
2017-12-24 7:21 ` Luke Dashjr
2017-12-24 22:20 ` Damian Williamson
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=PS2P216MB0179FE1CAF04AB860A5F36719D000@PS2P216MB0179.KORP216.PROD.OUTLOOK.COM \
--to=willtech@live$(echo .)com.au \
--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