Skip to content

Commit

Permalink
docs: misc updates (#429)
Browse files Browse the repository at this point in the history
* docs: small fee correction

* docs: reward allocation update

Clarify MN reward breakdown
  • Loading branch information
thephez committed Dec 12, 2024
1 parent bce5572 commit df26dc9
Show file tree
Hide file tree
Showing 2 changed files with 24 additions and 23 deletions.
4 changes: 2 additions & 2 deletions docs/core/guide/transactions-transaction-fees-and-change.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,11 +6,11 @@

# Transaction Fees and Change

Transactions pay fees based on the total byte size of the signed transaction. Fees per byte are calculated based on current demand for space in mined blocks with fees rising as demand increases. The [transaction fee](../resources/glossary.md#transaction-fee) is split between the miner (25%) and masternode (75%), as explained in the [block reward allocation section](https://docs.dash.org/en/stable/docs/user/introduction/features.html#block-reward-allocation). It is ultimately up to each [miner](../resources/glossary.md#miner) to choose the minimum transaction fee they will accept.
Transactions pay fees based on the total byte size of the signed transaction. Fees per byte are calculated based on current demand for space in mined blocks with fees rising as demand increases. The [transaction fee](../resources/glossary.md#transaction-fee) is split between the miner (25%) and masternode (75%), as explained in the [block reward allocation section](../../user/introduction/features.rst#block-reward-allocation). It is ultimately up to each [miner](../resources/glossary.md#miner) to choose the minimum transaction fee they will accept.

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.

As of Dash Core 0.12.2.x, a [minimum relay fee](../resources/glossary.md#minimum-relay-fee) (1,000 [duffs](../resources/glossary.md#duffs) following [DIP1](https://github.com/dashpay/dips/blob/master/dip-0001.md) activation) is required to broadcast a transaction across the [network](../resources/glossary.md#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.
As of Dash Core 0.12.2.x, a [minimum relay fee](../resources/glossary.md#minimum-relay-fee) (1,000 [duffs](../resources/glossary.md#duffs)/KB following [DIP1](https://github.com/dashpay/dips/blob/master/dip-0001.md) activation) is required to broadcast a transaction across the [network](../resources/glossary.md#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.

Since each transaction spends Unspent Transaction Outputs (UTXOs) and because a UTXO can only be spent once, the full value of the included UTXOs must be spent or given to a miner as a [transaction fee](../resources/glossary.md#transaction-fee). Few people will have UTXOs that exactly match the amount they want to pay, so most transactions include a change output.

Expand Down
43 changes: 22 additions & 21 deletions docs/user/introduction/features.rst
Original file line number Diff line number Diff line change
Expand Up @@ -429,16 +429,24 @@ the winning proposals in the budget system. Depending on budget
utilization, this results in an approximate coin allocation over
a budget cycle as follows:

+-----+----------------------------------------+
| 80% | Mining and Masternode Reward |
+-----+----------------------------------------+
| 20% | Decentralized Governance Budget |
+-----+----------------------------------------+

When the Dash Core v20 hard fork activates, Dash's governance budget will grow
to 20% of the block subsidy per the governance proposal approved in September
2023. Additional details can be found in the :ref:`Treasury expansion section
<block-subsidy-reallocation-treasury-expansion>`.
.. _block-reward-table:

+------------+--------------------------------------------------------------------+
| Percentage | Usage |
+============+====================================================================+
| 20% | Mining Reward |
+------------+--------------------------------------------------------------------+
| 20% | Decentralized Governance Budget |
+------------+--------------------------------------------------------------------+
| 60% | Masternode Reward |
| | |
| | - 62.5%: Paid to all masternode types on the Core chain |
| | - 37.5%: Allocated to the Platform credit pool to pay evonodes |
+------------+--------------------------------------------------------------------+

The masternode reward division supports both regular masternodes and Evolution masternodes
(evonodes). This allocation ensures that evonodes, which require higher collateral and provide
additional services, receive appropriate compensation.

.. _block-subsidy-reallocation-treasury-expansion:

Expand All @@ -448,17 +456,10 @@ Treasury expansion
In September of 2023, the Dash network approved a `proposal
<https://www.dashcentral.org/p/TREASURY-REALLOCATION-60-20-20>`__ to double the
governance budget by modifying the block subsidy allocation. The new allocation
designates 20% for miners, 20% for the governance system budget, and 60% for
masternodes. The expansion will go into effect upon activation of the Dash Core
v20 hard fork.

+-----+----------------------------------------+
| 20% | Mining Reward |
+-----+----------------------------------------+
| 20% | Decentralized Governance Budget |
+-----+----------------------------------------+
| 60% | Masternode Reward |
+-----+----------------------------------------+
designated 20% for miners, 20% for the governance system budget, and 60% for
masternodes. The expansion went into effect upon activation of the Dash Core
v20 hard fork. See the :ref:`block reward table <block-reward-table>` for the
current details.

Miner and masternode reallocation
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Expand Down

0 comments on commit df26dc9

Please sign in to comment.