Three Amendments Activated on XRP Ledger, Older Nodes May Be Amendment-Blocked as AMM, NFT Trustline and PayChan Fixes Take Effect

• Three amendments enabled on XRPL mainnet after 14‑day countdown with ≥80% support

• Nodes running v2.4.0 and below risk being amendment blocked; upgrade recommended.

• Fixes target AMM rounding/invariants, block NFT-fee bypasses, and prevent creation of past-dated payment channels.

XRPL amendments: fixAMMv1_3, fixEnforceNFTokenTrustlineV2, fixPayChanCancelAfter activated on mainnet—upgrade nodes now to avoid amendment blocks. Read the full update.

Three new amendments have been activated on the XRPL mainnet after a successful 14‑day countdown period that held majority support above 80%.

Blockchain explorer XRPscan reported the three enabled amendments as fixAMMv1_3, fixEnforceNFTokenTrustlineV2 and fixPayChanCancelAfter. With activation complete, rippled nodes running v2.4.0 and below risk being amendment blocked and should be upgraded promptly.

What are the new XRPL amendments?

fixAMMv1_3, fixEnforceNFTokenTrustlineV2 and fixPayChanCancelAfter are protocol updates that patch AMM invariants, close NFT transfer‑fee loopholes, and stop creation of payment channels with past CancelAfter times. These amendments are active on mainnet following the 14‑day countdown.

How does fixAMMv1_3 change AMM behavior?

fixAMMv1_3 adds invariant checks and rounding for Automated Market Maker (AMM) deposits and withdrawals. The amendment ensures AMM balances meet invariants and reduces risk of rounding-related state drift.

How does fixEnforceNFTokenTrustlineV2 affect NFT fees?

fixEnforceNFTokenTrustlineV2 prevents NFT transfer fees from bypassing trustline restrictions. It blocks payment of fungible tokens as NFT transfer fees to an NFT issuer when the issuer’s trust line is unauthorized or deep‑frozen, closing a previously possible bypass.

Why does fixPayChanCancelAfter matter?

fixPayChanCancelAfter prevents creation of new payment channels with a CancelAfter timestamp earlier than the current ledger. Without this, transactions could create channels that immediately expire and are removed by the next ledger, causing ambiguous state and unnecessary churn.

How should node operators respond?

Operators must upgrade rippled nodes to the latest release. Nodes on v2.4.0 and below risk being amendment blocked and will stop validating new ledgers until upgraded.

1. Check current node version and ledger sync status.
2. Plan a maintenance window for the upgrade to the latest rippled version.
3. Verify post-upgrade ledger sync and monitor for amendment block warnings.

Sources reporting the activation include XRPscan and public updates from RippleX engineering. RippleX engineer Mayukha Vadari also hinted at a new spec for the XRP Ledger Standards (XLS) process, inspired by Ethereum’s EIP‑1 and adapted for XRPL governance and editorial roles.

Frequently Asked Questions

Will these amendments force ledger replays or state changes?

The amendments apply validation and behavioral changes; they do not retroactively alter past ledger history. They modify how new transactions and state transitions are validated going forward.

How quickly should organizations upgrade their nodes?

Upgrade promptly. Nodes on v2.4.0 and older risk being amendment blocked immediately after activation; schedule maintenance and validation testing without delay.

Key Takeaways

• Activation confirmed: Three amendments enabled on XRPL mainnet after 14‑day countdown.
• Node impact: Nodes on v2.4.0 and below risk amendment block; upgrade required.
• Protocol fixes: AMM invariants, NFT fee enforcement, and payment channel timestamp validation were addressed.

Conclusion

The latest XRPL amendments — fixAMMv1_3, fixEnforceNFTokenTrustlineV2 and fixPayChanCancelAfter — strengthen protocol invariants and close fee routing loopholes. Node operators should upgrade rippled to maintain consensus participation. Watch for the upcoming XLS spec proposal for formalized standards processes.