From 94d4b801db899e1eb2d0210b1ff6ec48dfe0f683 Mon Sep 17 00:00:00 2001 From: mDuo13 Date: Wed, 30 Jan 2019 17:46:23 -0800 Subject: [PATCH] TxQ: rephrase queuing restrictions again --- .../consensus-network/transaction-queue.md | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/content/concepts/consensus-network/transaction-queue.md b/content/concepts/consensus-network/transaction-queue.md index ebb77101f6..459d299372 100644 --- a/content/concepts/consensus-network/transaction-queue.md +++ b/content/concepts/consensus-network/transaction-queue.md @@ -28,14 +28,15 @@ The transaction queue plays an important role in selecting the transactions that The `rippled` server uses a variety of heuristics to estimate which transactions are "likely to be included in a ledger." The current implementation uses the following rules to decide which transactions to queue: -* Transactions must be properly-formed and [authorized](transaction-basics.html#authorizing-transactions) with valid signatures. -* 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: - - The `Fee` fields of all queued transactions. - - 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] -* 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**. +- Transactions must be properly-formed and [authorized](transaction-basics.html#authorizing-transactions) with valid signatures. +- 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: [Updated in: rippled 1.2.0][New in: rippled 1.2.0] + - Destroying the XRP [transaction cost](transaction-cost.html) as specified in the `Fee` fields of all the sender's queued transactions. This amount cannot be more than the base account reserve (currently 20 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.) + - 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](reserves.html). +- 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**. ### Fee Averaging