XRP Ledger delegation goes live with its PaymentBurn fix two validator votes short

More than 80% of trusted validators for two straight weeks becomes a headcount once the list is 35 long, and the headcount is 29 ^[2]. Twenty-eight would be exactly 80%, and the rule says more than; 29 is about 82.9% ^[14]. The PaymentBurn fix stood at 27 on Friday, about 77.1% ^[8][15]. Two more votes start a 14-day clock, so the warning lifts no sooner than two weeks out, or rather two weeks after whichever day the 29th validator signs on ^[16].

The scoring bug in the Oct. 8 report bears on that count ^[10]. A server that loses track of two validators measures support against 33 instead of 35, and CoinDesk reported that this can make a proposal look closer to passing than it is ^[11]. If neither dropped validator was among the fix's 27 supporters, that server would show 27 of 33, about 81.8% and over the bar, while the true figure is 77.1% ^[17]. A patch that would identify validators by a permanent ID is still under review ^[11].

The case for delegation is about hot keys. A business signing all day needs keys online, and a broad key on an internet-connected machine raises the damage a hacker can do ^[12]. Delegation splits that authority by job: the helper signs with its own keys, can do only what it was granted, and the owner can change or withdraw the grant ^[5]. Banks already divide payment and compliance work among staff, and the ledger can now enforce the split ^[13]. About $4.26 billion of tokenized assets and RLUSD sat on the ledger on average in the second quarter, by Evernorth's count ^[9].

Operators face two limits on what they can hand off, and the PaymentBurn flaw should be the shorter-lived one. Its fix is two votes from a countdown ^[16], and other permissions are unaffected ^[7]. The missing spending cap is part of how grants work, since permissions restrict action types and impose no automatic cap ^[4]. CoinDesk's account does not mention any amendment that would add amount limits. I'd expect the first institutional delegations to go to compliance, a stablecoin issuer approving new customers from a helper account while its main keys stay offline ^[6], because a customer approval moves no money.

That view can miss in a few ways. The fix could reach 29 within days and lift the burn warning about two weeks later ^[16]. Support could fall back below 29 and restart the clock ^[2]. Or an issuer could fund a smaller operating account, delegate payments from it, and treat that balance as its cap. The last case would prove the view wrong, and it would show up as issuers granting payment permissions before any amount limit exists on the ledger.