mirror of
https://github.com/seigler/dash-docs
synced 2025-07-27 09:46:12 +00:00
Content - Sync guide and glossary with priority changes
This commit is contained in:
parent
95ffc9d8df
commit
7dd32a1b7d
3 changed files with 13 additions and 19 deletions
|
@ -9,8 +9,10 @@ required:
|
|||
summary_max_255_characters_no_formatting: >
|
||||
Transactions that don't have to pay a transaction fee because
|
||||
their inputs have been idle long enough to accumulated large
|
||||
amounts of priority. Note: miners choose whether to accept free
|
||||
transactions.
|
||||
amounts of priority.
|
||||
Note: As of Dash Core 0.12.3, all
|
||||
transactions require a fee. Also, coin age priority logic was
|
||||
removed in Dash Core 0.14.0.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- High-priority transaction
|
||||
|
@ -24,7 +26,6 @@ optional:
|
|||
not_to_be_confused_with_capitalize_first_letter:
|
||||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[High-priority transactions](/en/developer-guide#term-high-priority-transactions) --- Developer Guide"
|
||||
- "[Free transaction relay policy](https://en.bitcoin.it/wiki/Free_transaction_relay_policy) --- Bitcoin Wiki"
|
||||
#- "[High-priority transactions](/en/developer-guide#term-high-priority-transactions) --- Developer Guide"
|
||||
|
||||
---
|
||||
|
|
|
@ -7,10 +7,9 @@ required:
|
|||
title_max_40_characters_no_formatting: Minimum Relay Fee
|
||||
|
||||
summary_max_255_characters_no_formatting: >
|
||||
The minimum transaction fee a transaction must pay (if it isn't
|
||||
a high-priority transaction) for a full node to relay that
|
||||
transaction to other nodes. There is no one minimum relay
|
||||
fee---each node chooses its own policy.
|
||||
The minimum transaction fee a transaction must pay for a full
|
||||
node to relay that transaction to other nodes. There is no
|
||||
one minimum relay fee---each node chooses its own policy.
|
||||
|
||||
synonyms_shown_in_glossary_capitalize_first_letter:
|
||||
- Minimum relay fee
|
||||
|
@ -27,6 +26,6 @@ optional:
|
|||
|
||||
links_html_or_markdown_style_capitalize_first_letter:
|
||||
- "[Minimum relay fee](/en/developer-guide#term-minimum-fee) --- Developer Guide"
|
||||
- "[Transaction fees](https://en.bitcoin.it/wiki/Transaction_fees) --- Bitcoin Wiki"
|
||||
#- "[Transaction fees](https://en.bitcoin.it/wiki/Transaction_fees) --- Bitcoin Wiki"
|
||||
|
||||
---
|
||||
|
|
|
@ -671,18 +671,12 @@ Dash miner, as explained in the [block chain section][section block chain], and
|
|||
so it is ultimately up to each miner to choose the minimum transaction fee they
|
||||
will accept.
|
||||
|
||||
There is also a concept of so-called "[high-priority transactions][/en/glossary/high-priority-transaction]{:#term-high-priority-transactions}{:.term}"
|
||||
which spend duffs that have not moved for a long time.
|
||||
|
||||
These "priority" transaction can be often exempt from the normal fee
|
||||
requirements. As of Dash Core 0.12.2, 10 KB of each block are reserved for these
|
||||
high-priority transactions. 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.
|
||||
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. -->
|
||||
|
||||
As of Dash Core 0.12.2.x, a [minimum fee][/en/glossary/minimum-relay-fee]{:#term-minimum-fee}{:.term} (1,000 duffs following [DIP1][] activation) is required to
|
||||
broadcast a non-priority transaction across the network. Any transaction paying
|
||||
broadcast a transaction across the network. Any transaction paying
|
||||
only the minimum fee should be prepared to wait a long time before there's
|
||||
enough spare space in a block to include it.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue