ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-11-20 03:35:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

TxQ: fix 'amount the xrp' typo

Browse Source
This commit is contained in:
mDuo13
2019-01-30 01:54:12 -08:00
parent fab0afa6ed
commit cd9730d17f
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/concepts/consensus-network/transaction-queue.md
View File

@@ -32,7 +32,7 @@ The `rippled` server uses a variety of heuristics to estimate which transactions
* Transactions with an `AccountTxnID` field cannot be queued. * Transactions with an `AccountTxnID` field cannot be queued.
* A single sending address can have at most 10 transactions queued at the same time. In order for a transaction to be queued, the sender must have enough XRP to pay all the XRP costs of all the sender's queued transactions, including all of the following: * A single sending address can have at most 10 transactions queued at the same time. In order for a transaction to be queued, the sender must have enough XRP to pay all the XRP costs of all the sender's queued transactions, including all of the following:
- The `Fee` fields of all queued transactions. - The `Fee` fields of all queued transactions.
- The sum amount the XRP that each transaction could send. - The sum amount of XRP that all queued transactions could send.
- The amount of XRP the account must keep in [reserve](reserves.html). [Updated in: rippled 1.2.0][New in: rippled 1.2.0] - The amount of XRP the account must keep in [reserve](reserves.html). [Updated in: rippled 1.2.0][New in: rippled 1.2.0]
* If a transaction affects how the sending address authorizes transactions, no other transactions from the same address can be queued behind it. [New in: rippled 0.32.0][] * If a transaction affects how the sending address authorizes transactions, no other transactions from the same address can be queued behind it. [New in: rippled 0.32.0][]
* If a transaction includes a `LastLedgerSequence` field, the value of that field must be at least **the current ledger index + 2**. * If a transaction includes a `LastLedgerSequence` field, the value of that field must be at least **the current ledger index + 2**.