ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-11-28 23:55:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update reserves info

Browse Source 
Reserves blog post: edits per review
This commit is contained in:
mDuo13
2024-12-06 15:42:14 -08:00
parent 1b517c8c01
commit 74fc83479e
37 changed files with 145 additions and 97 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/concepts/transactions/transaction-queue.md
View File

@@ -40,7 +40,7 @@ The `rippled` server uses a variety of heuristics to estimate which transactions
- Transactions with an `AccountTxnID` field cannot be queued.
- A single sending address can have at most 10 transactions queued at the same time.
- To queue a transaction, the sender must have enough XRP for all of the following:
- Destroying the XRP [transaction cost](transaction-cost.md) as specified in the `Fee` fields of all the sender's queued transactions. The total amount among queued transactions cannot be more than the base account reserve (currently 10 XRP). (Transactions paying significantly more than the minimum transaction cost of 0.00001 XRP typically skip the queue and go straight into the open ledger.)
- Destroying the XRP [transaction cost](transaction-cost.md) as specified in the `Fee` fields of all the sender's queued transactions. The total amount among queued transactions cannot be more than the base account reserve (currently {% $env.PUBLIC_BASE_RESERVE %}). (Transactions paying significantly more than the minimum transaction cost of 0.00001 XRP typically skip the queue and go straight into the open ledger.)
- Sending the maximum sum of XRP that all the sender's queued transactions could send.
- Keeping enough XRP to meet the account's [reserve requirements](../accounts/reserves.md).
- If a transaction affects how the sending address authorizes transactions, no other transactions from the same address can be queued behind it.