Permission Delegation is no longer a forecast on the XRP Ledger. The PermissionDelegationV1_1 amendment enabled on mainnet Thursday at 5:29 p.m. ET, in ledger 107,524,865. The ledger’s own EnableAmendment record shows it, and XRPL Dashboard and CoinDesk reported the same activation.
Friday’s clock is Batch. It is not live yet.
What is scheduled this morning
Two Batch amendments reach the end of their two-week windows Friday, if validator majorities hold. The ledger’s Amendments record shows fixBatchV1_2 gained its majority on Sept. 25 at 10:12 a.m. ET, and BatchV1_1 at 10:46 a.m. ET the same day.
That puts fixBatchV1_2’s projected activation at about 10:12 a.m. ET Friday. The switch itself happens in an EnableAmendment pseudo-transaction on a following flag ledger, expected around 10:29 a.m. BatchV1_1 follows: projected at about 10:46 a.m., with its enable transaction expected near 11:03 a.m.
These are projections, not guaranteed times. An amendment needs more than 80% of trusted validators for two straight weeks. With 35 validators on the current list, that means at least 29 yes votes. If support drops to 28 or below, the majority is lost and the two-week clock restarts. That happened to Permission Delegation in September.
The vote margins
XRPL Dashboard’s roll call early Friday showed fixBatchV1_2 at 35 of 35 trusted validators. BatchV1_1 sat at 30 of 35, one vote above the 29 needed. Counts differ by tracker, so treat these as one source’s read.
What Batch does
BatchV1_1 adds the Batch transaction. One account can submit up to eight inner transactions together. They can be set as all-or-nothing groups, so a two-sided settlement either completes in full or not at all. The standard is XLS-56.
BatchV1_1 replaces the original Batch amendment. That version was disabled in xrpld 3.1.1 after developers found a critical bug, per XRPL.org. fixBatchV1_2 is the companion fix. It shipped in xrpld 3.4.1, an emergency release for security-sensitive issues. Servers on older software risk becoming “amendment blocked,” unable to keep up with the ledger, once it turns on.
The PaymentBurn caveat stays
Permission Delegation’s warning is unchanged. Until fixCleanup3_4_0 is enabled, XRPL.org recommends not delegating the PaymentBurn permission. Before that fix, a delegate holding it can also mint new trust-line tokens or MPTs in certain cases. Other permissions are unaffected.
The fix is not close to done. The ledger logged a majority for fixCleanup3_4_0 early Friday, about 5:34 a.m. ET. If that held for two weeks, the earliest activation would be around Oct. 23. But Friday morning roll calls had it at or below the line: 28 of 35 on XRPL Dashboard, and 27 of 35 in CoinDesk’s report. Treat PaymentBurn as off-limits for now.
Evernorth: expected is not closed
Separately, Evernorth’s Oct. 6 Form 8-K still points to a closing “on or about” Oct. 9 and Nasdaq trading as XRPN “on or about” Oct. 12. As of Friday morning, EDGAR showed no closing 8-K. Expected is not closed.
What to check
Batch day is a protocol event. It is about capability and operator risk, not price. Before treating either Batch amendment as live, look for its EnableAmendment transaction on the ledger after the morning windows, not just the countdown.
Sources: XRPL.org Known Amendments; XRP Ledger Amendments object and ledger 107,524,865; XRPL Dashboard; CoinDesk; SEC EDGAR