ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2026-09-27 15:37:57 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #3965 from XRPLF/mDuo13-patch-1

Browse Source 
Fix typo & other copy edits in "Finality of Results"
This commit is contained in:
Rome Reginelli
2026-09-24 12:52:04 -07:00
committed by GitHub
parent 48258ed342 b123f1362c
commit 79176391ee
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/concepts/transactions/finality-of-results/index.md
View File

@@ -41,15 +41,15 @@ When you initially submit a transaction, the `xrpld` server tentatively applies
- Combinations of two or more of these factors can also occur.
- The [order transactions apply in a closed ledger](../../ledgers/open-closed-validated-ledgers.md) is usually different than the order those transactions were tentatively applied to a current open ledger; depending on the transactions involved, this can cause a tentatively-successful transaction to fail or a tentatively-failed transaction to succeed. Some examples include:
- The [order transactions apply in a closed ledger](../../ledgers/open-closed-validated-ledgers.md) is usually different than the order those transactions were tentatively applied to a current open ledger. Depending on the transactions involved, this can cause a tentatively-successful transaction to fail or a tentatively-failed transaction to succeed. Some examples include:
- If two transactions would each fully consume the same Offer in the [decentralized exchange](../../tokens/decentralized-exchange/index.md), whichever one comes first succeeds, and the other fails. Since the order in which those transactions apply may change, the one that succeeded can fail and the one that failed can succeed. Since oOffers can be partially executed, they could also still succeed, but to a greater or lesser extent.
- If two transactions would each fully consume the same offer in the [decentralized exchange](../../tokens/decentralized-exchange/index.md), whichever one comes first succeeds, and the other may fail. Since the order in which those transactions apply may change, the one that succeeded can fail and the one that failed can succeed. Since offers can be partially executed or consume multiple other offers, they could also still succeed, but to a greater or lesser extent.
- If a [cross-currency payment](../../payment-types/cross-currency-payments.md) succeeds by consuming an Offer in the decentralized exchange, but a different transaction consumes or creates offers in the same order book, the cross-currency payment may succeed with a different exchange rate than it had when it executed tentatively. If it was a [partial payment](../../payment-types/partial-payments.md), it could also deliver a different amount.
- If a [cross-currency payment](../../payment-types/cross-currency-payments.md) succeeds by consuming an offer in the decentralized exchange, but a different transaction affects the same order book, the cross-currency payment may succeed with a different exchange rate than it had when it executed tentatively. If it was a [partial payment](../../payment-types/partial-payments.md), it could also deliver a different amount.
- A [Payment transaction][] that tentatively failed because the sender did not have enough funds may later succeed because another transaction delivering the necessary funds came first in the canonical order. The reverse is also possible: a transaction that tentatively succeeded may fail because a transaction delivering the necessary funds did not come first after being put into canonical order.
{% admonition type="success" name="Tip" %}For this reason, when running tests against the XRP Ledger, be sure to wait for a ledger close in between transactions if you have several accounts affecting the same data. If you are testing against a server in [stand-alone mode][], you must [manually close the ledger](../../../infrastructure/testing-and-auditing/advance-the-ledger-in-stand-alone-mode.md) in such cases.{% /admonition %}
{% admonition type="success" name="Tip" %}For this reason, when running tests that involve multiple accounts affecting the same data in the XRP Ledger, be sure to wait for a ledger close in between transactions. If you are testing against a server in [stand-alone mode][], you must [manually close the ledger](../../../infrastructure/testing-and-auditing/advance-the-ledger-in-stand-alone-mode.md) in such cases. This precaution is not necessary if all the transactions come from the same account, because those transactions always execute in sequence number order.{% /admonition %}
## See Also