Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
Updating info on high-priority-transactions #1421
Conversation
| -time. The remaining space in each block is typically allocated to transactions | ||
| -based on their fee per byte, with higher-paying transactions being added | ||
| -in sequence until all of the available space is filled. | ||
| +Older versions of Bitcoin Core recognized so-called "[high-priority transactions][/en/glossary/high-priority-transaction]{:#term-high-priority-transactions}{:.term}" which spent satoshis which had not moved for a long time. These transaction were often exempt from the normal fee requirements. Before Bitcoin Core 0.12, 50 KB of each block would be reserved for these high-priority transactions, however this is now set to 0 KB by default. As of Bitcoin Core 0.14, the entire concept of "high priority" / free transactions will be removed, meaning that all transactions will simply be prioritized based on their fee per byte, with higher-paying transactions being added in sequence until all of the available space is filled. |
MarcoFalke
Dec 4, 2016
Contributor
version .14 will have relay disabled by default. (You can still enable most of the priority logic in 0.14)
Removal is targeted for 0.15.
jonathancross
Dec 11, 2016
Contributor
Thanks for the feedback, I've reworded and uploaded a new version.
|
ACK |
wbnns
self-assigned this
Dec 9, 2016
| -time. The remaining space in each block is typically allocated to transactions | ||
| -based on their fee per byte, with higher-paying transactions being added | ||
| -in sequence until all of the available space is filled. | ||
| +Older versions of Bitcoin Core recognized so-called "[high-priority transactions][/en/glossary/high-priority-transaction]{:#term-high-priority-transactions}{:.term}" which spent satoshis which had not moved for a long time. These transaction were often exempt from the normal fee requirements. Before Bitcoin Core 0.12, 50 KB of each block would be reserved for these high-priority transactions, however this is now set to 0 KB by default, meaning that all transactions will simply be prioritized based on their fee per byte, with higher-paying transactions being added in sequence until all of the available space is filled. As of Bitcoin Core 0.14, high-priority-transaction relaying will also be disabled by default and the related code is targeted to be removed in v0.15. |
jonathancross
Dec 11, 2016
Contributor
I reworded this based on feedback from @MarcoFalke and @luke-jr, hopefully this is more accurate.
jonathancross
Dec 12, 2016
Contributor
Hmmm... seems I've unknowingly stepped into contentious territory with this change and misunderstood @luke-jr's concerns. Will work on making the wording more neutral and update here again when ready for another look.
jonathancross
changed the title from
Updating info on deprecated high-priority-transactions
to
Updating info on high-priority-transactions
Dec 13, 2016
| -time. The remaining space in each block is typically allocated to transactions | ||
| -based on their fee per byte, with higher-paying transactions being added | ||
| -in sequence until all of the available space is filled. | ||
| +In the past, these "priority" transaction were often exempt from the normal fee requirements. Before Bitcoin Core 0.12, 50 KB of each block would be reserved for these high-priority transactions, however this is now set to 0 KB by default. After the priority area, all transactions are prioritized based on their fee per byte, with higher-paying transactions being added in sequence until all of the available space is filled. <!-- Consider adding links to blockmaxsize and blockmaxweight options once available in the glossary. --> |
jonathancross
Dec 13, 2016
Contributor
Hi @luke-jr, hopefully this version addresses your concerns as mentioned in email? If not, please provide feedback. Thanks.
| -As of Bitcoin Core 0.9, transactions which do not count as high-priority transactions | ||
| -need to pay a [minimum fee][/en/glossary/minimum-relay-fee]{:#term-minimum-fee}{:.term} (currently 1,000 satoshis) to be | ||
| +Bitcoin Core 0.9, added a [minimum fee][/en/glossary/minimum-relay-fee]{:#term-minimum-fee}{:.term} (currently 1,000 satoshis) to be |
luke-jr
Dec 13, 2016
Contributor
Pretty sure the minimum fee was always there, but 0.9 just changed the logic around trickling below-min-fee somewhat. It's only being explicitly disabled (by default) in 0.14. Perhaps these details are irrelevant, though, since in practice a minimum fee is needed to broadcast.
| -As of Bitcoin Core 0.9, transactions which do not count as high-priority transactions | ||
| -need to pay a [minimum fee][/en/glossary/minimum-relay-fee]{:#term-minimum-fee}{:.term} (currently 1,000 satoshis) to be | ||
| -broadcast across the network. Any transaction paying only the minimum fee | ||
| +As of Bitcoin Core 0.9, a [minimum fee][/en/glossary/minimum-relay-fee]{:#term-minimum-fee}{:.term} (currently 1,000 satoshis) has been required to |
|
Unless others object, this will be merged on Sunday, December 18th. @jonathancross @MarcoFalke @luke-jr Thanks! |
jonathancross commentedDec 3, 2016
A few unrelated lines also had trailing whitespace which was also removed.