mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2025-12-06 17:27:57 +00:00
tx cost - edits for FeeEscalation peer review; moved fee levels discussion out of api reference into tx cost concept article
This commit is contained in:
@@ -10713,7 +10713,7 @@ Connecting to 127.0.0.1:5005
|
||||
<tr>
|
||||
<td>drops.base_fee</td>
|
||||
<td>String (Integer)</td>
|
||||
<td>The transaction cost required for a <a href="#reference-transaction-cost">reference transaction</a> to be included in a ledger under minimum load, represented in drops of XRP.</td>
|
||||
<td>The transaction cost required for a <a href="concept-transaction-cost.html#reference-transaction-cost">reference transaction</a> to be included in a ledger under minimum load, represented in drops of XRP.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>drops.median_fee</td>
|
||||
@@ -10723,12 +10723,12 @@ Connecting to 127.0.0.1:5005
|
||||
<tr>
|
||||
<td>drops.minimum_fee</td>
|
||||
<td>String (Integer)</td>
|
||||
<td>The minimum transaction cost for a <a href="#reference-transaction-cost">reference transaction</a> to be queued for a later ledger, represented in drops of XRP. If greater than <code>base_fee</code>, the transaction queue is full.</td>
|
||||
<td>The minimum transaction cost for a <a href="concept-transaction-cost.html#reference-transaction-cost">reference transaction</a> to be queued for a later ledger, represented in drops of XRP. If greater than <code>base_fee</code>, the transaction queue is full.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>drops.open_ledger_fee</td>
|
||||
<td>String (Integer)</td>
|
||||
<td>The minimum transaction cost that a <a href="#reference-transaction-cost">reference transaction</a> must pay to be included in the current open ledger, represented in drops of XRP.</td>
|
||||
<td>The minimum transaction cost that a <a href="concept-transaction-cost.html#reference-transaction-cost">reference transaction</a> must pay to be included in the current open ledger, represented in drops of XRP.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>expected_ledger_size</td>
|
||||
@@ -10767,44 +10767,6 @@ Connecting to 127.0.0.1:5005
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="reference-transaction-cost">Reference Transaction Cost</h3>
|
||||
<p>The "Reference Transaction" is the cheapest possible transaction, in terms of the necessary <a href="concept-transaction-cost.html">transaction cost</a>. Most transactions have the same cost as the reference transaction. Some transactions, such as <a href="reference-transaction-format.html#multi-signing">multi-signed transactions</a> require a multiple of this cost instead. When the open ledger cost escalates, the requirement is proportional to the basic cost of the transaction.</p>
|
||||
<h3 id="fee-levels">Fee Levels</h3>
|
||||
<p><em>Fee levels</em> represent the proportional difference between the minimum cost and the actual cost of a transaction. See the following table for a comparison:</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Transaction</th>
|
||||
<th>Minimum cost in drops</th>
|
||||
<th>Minimum cost in Fee levels</th>
|
||||
<th>Double cost in drops</th>
|
||||
<th>Double cost in fee levels</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>Reference transaction (most transactions)</td>
|
||||
<td>10</td>
|
||||
<td>256</td>
|
||||
<td>20</td>
|
||||
<td>512</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="reference-transaction-format.html#multi-signing">Multi-signed transaction</a> with 4 signatures</td>
|
||||
<td>50</td>
|
||||
<td>256</td>
|
||||
<td>100</td>
|
||||
<td>512</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><a href="concept-transaction-cost.html#key-reset-transaction">Key reset transaction</a></td>
|
||||
<td>0</td>
|
||||
<td>(Effectively infinite)</td>
|
||||
<td>N/A</td>
|
||||
<td>(Effectively infinite)</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h4 id="possible-errors-36">Possible Errors</h4>
|
||||
<ul>
|
||||
<li>Any of the <a href="#universal-errors">universal error types</a>.</li>
|
||||
|
||||
Reference in New Issue
Block a user