XRP Ledger Issues Critical Update Warning: Validators Have 13 Days to Act

• XRPL validators have 13-day deadline to upgrade to rippled version 2.6.2 release
• Update includes fix DirectoryLimit amendment and critical bug fix for transactions
• Smart Escrows introduce custom on-chain conditions for fund release mechanisms

XRP Ledger validators received a crucial upgrade alert requiring action within a 13-day timeframe. Jon Nilsen, an XRPL validator, issued a message warning validators to upgrade to rippled version 2.6.2 or face amendment-blocking. The deadline stands at 13 days and 20 hours from the alert date.

Nilsen stated that validators running XRPL nodes must update to the latest version or risk being blocked by upcoming amendments. The upgrade notification comes as the XRP Ledger community prepares for protocol changes that require validator consensus.

Version 2.6.2 Includes Key Amendment and Bug Fix

An XRPL blog post from November 19 announced the availability of rippled version 2.6.2. This release serves as the reference server implementation of the XRP Ledger protocol. The version includes the fixDirectoryLimit amendment and addresses a critical bug.

The fixDirectoryLimit amendment removes directory page limits on the ledger. This amendment was activated for voting with the release. The bug fix addresses an issue that caused assertion failures when all inner transactions within a Batch transaction were invalid.

Ripple CTO David Schwartz confirmed his hub has operated on rippled version 2.6.2 for more than one week without issues. This indicates the CTO has already implemented the upgrade and validated its stability across operations.

XRPL validator Vet expressed optimism about Smart Escrows arriving on the XRP Ledger. This feature introduces custom conditions for escrowing funds directly on-chain using the native escrow functionality. Users can configure escrow fund release based on XRP price data from oracles alongside other applications.

RippleX software engineer Mayukha Vadari outlined a new vision for permissionless programmability on XRPL. The first major component introduces Smart Features, allowing developers limited customizability built on individual XRPL primitives. Escrow became the first primitive to receive this enhancement through Smart Escrows.

XRPL Escrows function as on-chain contracts governing all-or-nothing fund transfers between accounts based on pre-agreed terms. Currently, escrows can only hold XRP tokens. However, the TokenEscrow amendment, currently under voting, will enable holding both IOUs (issued assets) and MPTs (multi-purpose tokens).