From d81db84aa0c1bb3685420787fcb1dc71045ea565 Mon Sep 17 00:00:00 2001 From: "Elliot." Date: Fri, 11 Apr 2025 16:29:44 -0700 Subject: [PATCH 1/2] Update tec-codes.md In certain cases, future `tec` codes may have other side effects on the ledger. For example, `tecWASM_REJECTED` is expected to be able to modify the value of the (new) "Data" field in the Escrow ledger entry. --- .../transactions/transaction-results/tec-codes.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/references/protocol/transactions/transaction-results/tec-codes.md b/docs/references/protocol/transactions/transaction-results/tec-codes.md index f04e28bcfcb..602d8f086dc 100644 --- a/docs/references/protocol/transactions/transaction-results/tec-codes.md +++ b/docs/references/protocol/transactions/transaction-results/tec-codes.md @@ -2,18 +2,18 @@ html: tec-codes.html parent: transaction-results.html seo: - description: tec codes indicate that the transaction failed, but it was applied to a ledger to deduct the transaction cost. + description: tec codes indicate that the transaction did not succeed, but it deducted the transaction cost and it was applied to a ledger. labels: - Transaction Sending --- # tec Codes [[Source]](https://github.com/XRPLF/rippled/blob/master/src/ripple/protocol/impl/TER.cpp "Source") -These codes indicate that the transaction failed, but it was applied to a ledger to apply the [transaction cost](../../../../concepts/transactions/transaction-cost.md). They have numerical values in the range 100 to 199. It is recommended to use the text code, not the numeric value. +These codes indicate that the transaction did not succeed, but it was applied to a ledger to apply the [transaction cost](../../../../concepts/transactions/transaction-cost.md) and may have had other side effects to the ledger. The `tec` codes have numerical values in the range 100 to 199. It is recommended to use the text code, not the numeric value. -Transactions with `tec` codes destroy the XRP paid as a [transaction cost](../../../../concepts/transactions/transaction-cost.md), and consume a [sequence number](../../data-types/basic-data-types.md#account-sequence). For the most part, the transactions take no other action, but there are some exceptions. For example, a transaction that results in `tecOVERSIZE` still cleans up some [unfunded offers](../../../../concepts/tokens/decentralized-exchange/offers.md#lifecycle-of-an-offer). Always look at the [transaction metadata](../metadata.md) to see precisely what a transaction did. +Transactions with `tec` codes destroy the XRP paid as a [transaction cost](../../../../concepts/transactions/transaction-cost.md), and consume a [sequence number](../../data-types/basic-data-types.md#account-sequence). Although the transactions did not succeed, they sometimes have some other effect. For example, a transaction that results in `tecOVERSIZE` still cleans up some [unfunded offers](../../../../concepts/tokens/decentralized-exchange/offers.md#lifecycle-of-an-offer). Always look at the [transaction metadata](../metadata.md) to see precisely what a transaction did. -{% admonition type="warning" name="Caution" %}A transaction that provisionally failed with a `tec` code may still succeed or fail with a different code after being reapplied. The result is final when it appears in a validated ledger version. For more information, see [Finality of Results](../../../../concepts/transactions/finality-of-results/index.md) and [Reliable Transaction Submission](../../../../concepts/transactions/reliable-transaction-submission.md).{% /admonition %} +{% admonition type="warning" name="Caution" %}A transaction that provisionally failed with a `tec` code may still succeed or fail with a different code after being reapplied. The result is final when it appears in a fully validated ledger version. For more information, see [Finality of Results](../../../../concepts/transactions/finality-of-results/index.md) and [Reliable Transaction Submission](../../../../concepts/transactions/reliable-transaction-submission.md).{% /admonition %} | Code | Value | Explanation | |:---------------------------|:------|:----------------------------------------| From 96f18b048b69279a2844f9aab18430c0ca062aa7 Mon Sep 17 00:00:00 2001 From: "Elliot." Date: Thu, 3 Jul 2025 08:43:29 -0700 Subject: [PATCH 2/2] Apply suggestions from code review Co-authored-by: Rome Reginelli --- .../protocol/transactions/transaction-results/tec-codes.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/references/protocol/transactions/transaction-results/tec-codes.md b/docs/references/protocol/transactions/transaction-results/tec-codes.md index 602d8f086dc..8cea3a03d40 100644 --- a/docs/references/protocol/transactions/transaction-results/tec-codes.md +++ b/docs/references/protocol/transactions/transaction-results/tec-codes.md @@ -2,7 +2,7 @@ html: tec-codes.html parent: transaction-results.html seo: - description: tec codes indicate that the transaction did not succeed, but it deducted the transaction cost and it was applied to a ledger. + description: A tec result code indicates that the transaction did not succeed, but it deducted the transaction cost and it was applied to a ledger. labels: - Transaction Sending --- @@ -11,9 +11,9 @@ labels: These codes indicate that the transaction did not succeed, but it was applied to a ledger to apply the [transaction cost](../../../../concepts/transactions/transaction-cost.md) and may have had other side effects to the ledger. The `tec` codes have numerical values in the range 100 to 199. It is recommended to use the text code, not the numeric value. -Transactions with `tec` codes destroy the XRP paid as a [transaction cost](../../../../concepts/transactions/transaction-cost.md), and consume a [sequence number](../../data-types/basic-data-types.md#account-sequence). Although the transactions did not succeed, they sometimes have some other effect. For example, a transaction that results in `tecOVERSIZE` still cleans up some [unfunded offers](../../../../concepts/tokens/decentralized-exchange/offers.md#lifecycle-of-an-offer). Always look at the [transaction metadata](../metadata.md) to see precisely what a transaction did. +A transaction that fails with a `tec` code destroys the XRP paid as a [transaction cost](../../../../concepts/transactions/transaction-cost.md) and consumes a [sequence number](../../data-types/basic-data-types.md#account-sequence). Although the transaction did not succeed, it may also cause some bookkeeping or cleanup work to be done. For example, a transaction that results in `tecOVERSIZE` still removes some [unfunded offers](../../../../concepts/tokens/decentralized-exchange/offers.md#lifecycle-of-an-offer). Always look at the [transaction metadata](../metadata.md) to see precisely what a transaction did. -{% admonition type="warning" name="Caution" %}A transaction that provisionally failed with a `tec` code may still succeed or fail with a different code after being reapplied. The result is final when it appears in a fully validated ledger version. For more information, see [Finality of Results](../../../../concepts/transactions/finality-of-results/index.md) and [Reliable Transaction Submission](../../../../concepts/transactions/reliable-transaction-submission.md).{% /admonition %} +{% admonition type="warning" name="Caution" %}A transaction that provisionally failed with a `tec` code may still succeed or fail with a different code after being reapplied. The result is final when it appears in a validated ledger version. For more information, see [Finality of Results](../../../../concepts/transactions/finality-of-results/index.md) and [Reliable Transaction Submission](../../../../concepts/transactions/reliable-transaction-submission.md).{% /admonition %} | Code | Value | Explanation | |:---------------------------|:------|:----------------------------------------|