All NewsEducationTV
Equities & FundsCrypto & Digital AssetsAI & TechnologyBusiness & CorporateUS Politics & PolicyGeopolitics & Global RiskMacro, Rates & FXCommodities & EnergyEuropean Politics & MarketsAsia-PacificReal Estate & Property
Story archiveAll categories
← All Stories

XRP Ledger upgrade reintroduces features previously pulled for critical bugs

Created at 1 Aug · 6:16 AM1 source↑ Market-relevant
IN SHORT

The XRP Ledger's upcoming xrpld 3.3.0 release will present validators with five proposed amendments, including revised versions of the Batch and Permission Delegation features that were previously withdrawn due to critical bugs. Three new features are also included.

✉Newsletter

PiQ Daily

Pick your topics. Get only what matters, on your cadence.

Key Numbers

3.3.0xrpld software release version
8maximum cross-account transactions in Batch feature
80%validator approval threshold for amendments
2consecutive weeks for validator approval

Who's Involved

Jazzi Cooper
Head of product at RippleX
Pranamya Keshkamat
Security researcher who identified a flaw in the Batch amendment
Cantina
Firm that identified a flaw in the Batch amendment
XRP Ledger upgrade reintroduces features previously pulled for critical bugs

↳ Why This Matters

This upgrade signifies a crucial step in enhancing the XRP Ledger's capabilities for tokenized assets and institutional use cases, despite the challenges posed by previously identified security vulnerabilities.

Key facts

  • The XRP Ledger's upcoming xrpld 3.3.0 release includes five proposed amendments.
  • Revised versions of the Batch and Permission Delegation features, previously withdrawn due to critical bugs, are among the proposals.
  • Batch allows atomic execution of up to eight cross-account transactions.
  • Permission Delegation permits institutions to grant scoped signing authority.
  • New features include Confidential MPT for private tokenized assets, Sponsored Fees and Reserves, and Dynamic MPT.
  • A minimum of 80% validator approval over two weeks is required for amendments to be activated.
  • The XRP Ledger is set to introduce its xrpld 3.3.0 software release, which will put five proposed amendments before validators. Notably, two of these amendments—Batch and Permission Delegation—are revised versions of features that were previously pulled from the network due to critical security flaws. The Batch amendment aims to allow up to eight cross-account transactions to execute atomically, meaning they all succeed or fail together. Permission Delegation is designed to let institutions grant specific, limited signing authority to other accounts without relinquishing full control.

    In addition to these reintroduced features, the release includes three entirely new amendments. Confidential MPT will leverage zero-knowledge proofs and encryption to keep balances and transfer amounts private on Multi-Purpose Tokens while allowing verification when needed. Sponsored Fees and Reserves will enable entities like banks to cover users' XRP transaction fees and reserve costs, potentially lowering barriers to entry. Dynamic MPT will allow issuers to specify which token properties can be modified after creation, avoiding the need for full token migrations when updates are required.

    Amendments on the XRP Ledger require a significant consensus, with at least 80% of trusted validators needing to approve them for two consecutive weeks before activation. Both the Batch and Permission Delegation amendments have previously undergone this process and failed to gain sufficient support. Security researchers had identified vulnerabilities in earlier versions, leading to advisories against their activation and emergency measures to prevent their deployment. The ledger's documentation has since listed these original amendments as obsolete, paving the way for these revised versions.

    Frequently asked questions

    The Batch amendment allows up to eight cross-account transactions to execute atomically, meaning all transactions must succeed or fail together.

    Permission Delegation enables institutions to grant specific, limited signing authority to other accounts without giving up full control.

    Amendments require at least 80% of trusted validators to approve them for two consecutive weeks to be activated.

    Security researchers found critical bugs in earlier versions of these features, which could have allowed unauthorized transactions or draining of balances.

    What Happens Next

    01Validators will vote on the five proposed amendments.
    02If approved, the amendments will be activated on the XRP Ledger.

    Get the newsletter.

    Pick the topics you actually care about. We'll email when there's news worth your time, on the cadence you choose. Cancel any time from your account.

    Cadence

    How It Developed

    The XRP Ledger's next software release, xrpld 3.3.0, will propose five amendments for validator approval.
    Two of the proposed amendments, Batch and Permission Delegation, were previously pulled from the network due to critical bugs.
    The Batch amendment allows up to eight cross-account transactions to execute atomically.
    The Permission Delegation amendment enables institutions to grant limited signing authority without full control.
    Three new amendments are also included: Confidential MPT for private tokenized assets, Sponsored Fees and Reserves for covering user transaction costs, and Dynamic MPT for adjustable token properties.
    All five amendments require 80% validator approval for two consecutive weeks to take effect.

    Sources

    T1
    XRP Ledger upgrade brings back features once pulled over critical bugsCoinDesk

    Related Stories

    XRP Ledger Set for v3.3.0 Upgrade with Five New Amendments
    31 Jul · 11:26 PM
    SBI Holdings Reaffirms $41.2B Stake in Ripple Amidst XRP Price Slump
    31 Jul · 1:56 PM
    FTX distributes $900M to former users in fifth reimbursement round
    31 Jul · 5:06 PM
    FTX users receive funds, Citadel buys stock, Coldcard warns users
    31 Jul · 8:06 PM
    Bitcoin cold wallets drained of $70M in firmware flaw attack
    1 Aug · 6:06 AM