From 9e343558cc0426d09c3b002b59ab2b08df6deb90 Mon Sep 17 00:00:00 2001 From: Oliver Eggert Date: Wed, 19 Nov 2025 15:16:42 -0800 Subject: [PATCH] update tec codes and release notes --- blog/2025/rippled-2.6.2.md | 8 +++----- .../transactions/transaction-results/tec-codes.md | 2 +- 2 files changed, 4 insertions(+), 6 deletions(-) diff --git a/blog/2025/rippled-2.6.2.md b/blog/2025/rippled-2.6.2.md index 502bd7f2e4..07cdd99a24 100644 --- a/blog/2025/rippled-2.6.2.md +++ b/blog/2025/rippled-2.6.2.md @@ -1,6 +1,6 @@ --- category: 2025 -date: "2025-11-12" +date: "2025-11-19" template: '../../@theme/templates/blogpost' seo: title: Introducing XRP Ledger version 2.6.2 @@ -23,8 +23,6 @@ If you run an XRP Ledger server, upgrade to version 2.6.2 as soon as possible to ## Install / Upgrade -**TODO**: Update packages hashes and commit message. - On supported platforms, see the [instructions on installing or updating `rippled`](../../docs/infrastructure/installation/index.md). | Package | SHA-256 | @@ -49,11 +47,11 @@ Date: Tue Sep 30 16:09:11 2025 -0400 The following amendment is open for voting with this release: -- **fixDirectoryLimit** - Removes directory page limits. ([#5935](https://github.com/XRPLF/rippled/pull/5935)) +- **fixDirectoryLimit** - Removes directory page limits. Object reserve requirements provide enough incentive to avoid creating unnecessary objects on the XRP Ledger. ([#5935](https://github.com/XRPLF/rippled/pull/5935)) ### Bug Fixes -- Fixed an assertion failure when all the inner transactions of a `Batch` transaction are invalid. ([#5670](https://github.com/XRPLF/rippled/pull/5670)) +- Fixed an assertion failure when all the inner transactions of a `Batch` transaction were invalid. ([#5670](https://github.com/XRPLF/rippled/pull/5670)) ## Credits diff --git a/docs/references/protocol/transactions/transaction-results/tec-codes.md b/docs/references/protocol/transactions/transaction-results/tec-codes.md index 100ca541d6..8f2d231e5b 100644 --- a/docs/references/protocol/transactions/transaction-results/tec-codes.md +++ b/docs/references/protocol/transactions/transaction-results/tec-codes.md @@ -27,7 +27,7 @@ A transaction that fails with a `tec` code destroys the XRP paid as a [transacti | `tecCANT_ACCEPT_OWN_NFTOKEN_OFFER` | 157 | The transaction tried to accept an offer that was placed by the same account to buy or sell a [non-fungible token](../../../../concepts/tokens/nfts/index.md). {% amendment-disclaimer name="NonFungibleTokensV1_1" /%} | | `tecCLAIM` | 100 | Unspecified failure, with transaction cost destroyed. | | `tecCRYPTOCONDITION_ERROR` | 146 | This [EscrowCreate][] or [EscrowFinish][] transaction contained a malformed or mismatched crypto-condition. | -| `tecDIR_FULL` | 121 | The transaction tried to add an object (such as a trust line, Check, Escrow, or Payment Channel) to an account's owner directory, but that account cannot own any more objects in the ledger. | +| `tecDIR_FULL` | 121 | The transaction tried to add an object (such as a trust line, Check, Escrow, or Payment Channel) to an account's owner directory, but that account cannot own any more objects in the ledger. This error is effectively impossible to receive if the [`fixDirectoryLimit`](../../../../../resources/known-amendments.md#fixdirectorylimit) amendment is enabled. | | `tecDUPLICATE` | 149 | The transaction tried to create an object (such as a [DepositPreauth][] authorization) that already exists. | | `tecDST_TAG_NEEDED` | 143 | The [Payment transaction][] omitted a [destination tag](../../../../concepts/transactions/source-and-destination-tags.md), but the destination account has the `lsfRequireDestTag` flag enabled. | | `tecEMPTY_DID` | 187 | The transaction tried to create a [DID entry][] with no contents. A DID must not be empty. {% amendment-disclaimer name="DID" /%} |