The XRP Ledger’s core software, xrpld, shipped version 3.3.0 earlier this month, and with it a package of six proposed protocol amendments now sitting in front of the network’s trusted validators. Nearly all of them are aimed at one customer: the institution that wants to move regulated assets on a public chain without broadcasting its balance sheet to everyone watching.
The headline change is Confidential Transfers, which would let holders of Multi-Purpose Tokens encrypt balances and payment amounts while leaving the account and the token type visible to the network. It uses EC-ElGamal encryption paired with zero-knowledge proofs. In its first version it stays deliberately narrow — holders have to opt in, and it works only for direct payments between accounts.
The rest of the package is plumbing for the same buyer. Batch would let up to eight transactions across different accounts execute atomically, so either all of them settle or none do. Permission Delegation would let an institution hand out narrowly scoped signing authority without handing over control of the account. Sponsor would let a third party pay fees and reserves on a user’s behalf. Dynamic MPT would let issuers change selected token properties after issuance, which is what you need when a compliance rule changes and the token has to change with it. A sixth amendment bundles routine fixes.
The gate is the story
None of this is live. Under the XRP Ledger’s amendment process, a proposal has to hold support from more than 80% of trusted validators for two consecutive weeks before it activates. With the unique node list sitting at 35 validators, that means 28 of them have to agree — and keep agreeing for a fortnight. As of this week, none of the six had cleared the bar. There is no scheduled activation date, because there cannot be one.
Here is the part that gets skipped in most write-ups. Batch and Permission Delegation are not new proposals. Both reached the voting phase back in February and did not make it through. The ledger’s own documentation has listed the original versions as obsolete since, replaced by the revised amendments now on the ballot. This is a second attempt, not a first.
Our take: Governance is the product here, and it cuts both ways. A chain that lets a company ship whatever it wants to institutional users is not a neutral settlement layer, and banks say they care about that. But it also means the roadmap Ripple presents in a sales meeting is not a roadmap Ripple controls. CoinDesk framed this package as aimed at roughly $530 million of tokenized assets currently on the ledger — a real number, and a small one against the size of the pitch. The gap between those two figures is exactly what this vote decides.
What to watch
- The two-week clock, not the daily tally. An amendment crossing 80% means nothing until it stays there. Watch for the start of a sustained run, not a single day’s reading.
- Whether the revisions were the problem. If BatchV1_1 and PermissionDelegationV1_1 stall the way their predecessors did, the objection was never about the code.
- Confidential Transfers separately. It is the one genuinely new capability in the set, and the one most likely to draw scrutiny from regulators who spent the last decade asking chains to be more transparent, not less.
- September 15. The Senate’s cloture vote on the CLARITY Act lands in the middle of this, and it will move the conversation about tokenized assets far more than any single amendment will.
Price action has dominated XRP coverage this month, driven almost entirely by Washington. The amendment vote has barely registered by comparison. That is backwards. Legislation decides whether institutions are allowed to use a ledger like this one. The validators decide whether it can actually do what those institutions need.