前言

背景：XRP Ledger 正在部署 fixCleanup3_1_3 修訂案，以解決長期存在的效能低落與多個正確性錯誤。 目的：本文說明此升級變更內容、誰需要採取行動，以及這些修正對網路健康、儲存效率與借貸/會計完整性的影響。節點操作員與驗證節點應特別注意，因為若未更新，當修訂案啟用時將會遭到斷線。對於一般錢包使用者及託管交易所客戶，則不需要採取任何行動。

懶人包

此更新會自動移除已過期的 NFT 報價，防止意外變更受限權限設定，強制在金庫提領時遵守信任線限制，並修正貸款會計更新。 主要優點包括 減少分類帳膨脹、加強權限安全，以及 更準確的借貸紀錄。驗證節點與節點操作員必須在啟用前升級，否則將被斷線。

內容主體

The XRP Ledger, a Layer 1 blockchain that facilitates multi-currency settlements using the XRP token, is scheduled to enable an important maintenance amendment named fixCleanup3_1_3. This upgrade targets several operational and correctness issues that have accumulated over time. Its purpose is to improve ledger hygiene, tighten permission enforcement, and ensure accurate accounting in decentralized lending flows. While typical end users who only hold XRP in wallets or on exchanges are unaffected, node operators and validators must update their software before the activation deadline or risk being amendment-blocked and falling out of consensus with the network.

One of the most visible changes involves non-fungible token (NFT) offers. On the ledger, creating an offer to sell an NFT leaves a persistent record. Historically, if an offer expired or was simply ignored, it could remain on the ledger indefinitely. That residual state contributes to ledger bloat, consuming storage and increasing the workload for nodes that maintain full history. The fixCleanup3_1_3 amendment introduces automatic cleanup of expired NFT offers, effectively removing stale listings once they are no longer valid. Conceptually, this is similar to deleting expired classifieds rather than preserving them in perpetuity, and it reduces unnecessary storage and lookup overhead for nodes and indexers.

Another area corrected by the amendment is the handling of Permissioned Domains. Permissioned Domains restrict certain actions—access to assets, order books, or special settings—to a defined set of accounts. Previously, a bug allowed the possibility that failed transactions could still alter restricted settings, unintentionally changing domain configuration even when the intended operation did not succeed. The amendment tightens checks so that failed operations cannot produce side effects on permissioned settings, closing a subtle but important attack surface and helping preserve intended domain policies.

Vaults are a critical primitive on the ledger for secure custody and collateralization. When tokens move out of a vault, the receiving account can only hold up to a preconfigured maximum—its trust-line limit. Prior to this upgrade, vault withdrawal processing did not consistently verify that the recipient’s trust-line limit could accept the incoming amount, which could lead to situations where a transfer bypassed the account’s limit. fixCleanup3_1_3 ensures that vault withdrawals now respect trust-line limits during execution, preventing unintended overflows or failed post-processing states. This change reduces the likelihood of inconsistent balances and enforces account-level constraints at the time of the transfer.

Lending and loan accounting have also received targeted corrections. The XRP Ledger supports decentralized lending workflows where loans, collateral vaults, and lender records must remain synchronized. In some scenarios—such as defaults or impairments—related ledger entries (the loan record, lender balances, and collateral vaults) were not reliably updated, producing stale or mismatched accounting. The upgrade rectifies this by ensuring all dependent ledger entries are updated atomically when a loan’s status changes. Accurate, timely updates prevent confusing balances for participants and make protocol behavior more predictable for developers building lending services.

The amendment also clarifies error handling for loan overpayments and strengthens checks for specialized entities called LoanBrokers. If a loan disallows overpayments, attempts to overpay will now return a clear permission error (tecNO_PERMISSION) rather than a vague invalid flag. This explicit error improves developer and user experience by making rejections easier to interpret and handle programmatically. Additionally, LoanBrokers advertise a “CoverAvailable” amount—first-loss capital intended to protect lenders. The amendment adds a safety check to ensure the advertised CoverAvailable matches the actual assets in the broker’s protected pseudo-account, reducing the risk of mismatches between advertised protection and real backing.

Activation logistics are straightforward but strict: the amendment will be enabled on a set date, and validators and node operators must run the updated software before that moment. Nodes that do not upgrade will be amendment-blocked and fall out of sync with the ledger. Reports indicate a significant portion of the network has already applied the update, but operators should verify their nodes are running the required release to avoid interruption. For wallet users and custodial services, no manual action is required; services that operate nodes on behalf of users must, however, ensure timely upgrades.

Operationally, the changes should yield a cleaner ledger state, fewer surprising permission side effects, and more reliable accounting for lending activities—outcomes that benefit developers, node operators, and broader ecosystem participants. From a technical perspective, improvements to automatic cleanup and stricter checks reduce technical debt and lower the long-term cost of maintaining the ledger. For financial primitives like loans and vaults, ensuring correctness and explicit error signalling is essential to maintaining trust and composability across DeFi services built on the ledger.

In summary, fixCleanup3_1_3 is a maintenance-focused but impactful amendment: it reclaims storage by removing expired NFT offers, protects controlled domain settings from accidental modification, enforces trust-line constraints on vault withdrawals, and fixes loan-accounting updates and Broker checks. The collective effect is improved stability and predictability of the XRP Ledger. Node operators should upgrade promptly; everyday XRP holders and custodial users do not need to take any action.

重點摘要表

注意：本摘要側重於 fixCleanup3_1_3 修訂案所引入的技術變更及其操作影響。不包含宣傳性內容，旨在幫助節點操作員、開發者與感興趣的使用者理解此升級的效果。