Home›Crypto›Market Structure›XRPL keeps Batch and Permission Delegation locked afte…

XRPL keeps Batch and Permission Delegation locked after exploit risks

XRPL development registry now marks the replacement amendments as “supported” with default No votes, while activation still requires validator approval and support above an 80% threshold for two weeks.

Reported · Written up by our desk · Market Structure

RippleX expects the next XRP Ledger core server release, xrpld 3.3.0, as soon as next week, aiming to put rewritten Batch and Permission Delegation amendments back into the validator process after authorization flaws were previously blocked from mainnet activation, according to CryptoSlate.

CryptoSlate reports that the original Batch amendment carried an authorization flaw that could have let an attacker execute inner transactions for arbitrary victim accounts without private keys, including unauthorized payments and ledger changes. For Permission Delegation, an invalid offline-signed transaction could still charge a victim account a transaction fee before failing authorization, enabling repeated submissions to drain XRP through fees, the outlet said. In both cases, disclosures indicated no funds were put at risk because validators blocked activation, and support was disabled for the affected amendment.

As part of the xrpld 3.3.0 rollout process, RippleX product head Jazzi Cooper outlined five proposed features for the release, including Confidential MPT, Batch, Permission Delegation, Sponsored Fees and Reserves, and Dynamic MPT, and said all five still require validator approval before activation. The 3.3 development registry marks BatchV1_1 and PermissionDelegationV1_1 as supported with default No votes, with “supported” meaning the server code recognizes the amendments while activation remains a separate validator step.

CryptoSlate adds that XRPL amendments can activate only after compatible code ships and that support must remain above 80% of trusted validators for two weeks, with the two-week countdown restarting if support falls to 80% or less before activation. On Aug. 1, the validated mainnet amendments object at ledger 105,997,300 contained no Majorities field, and neither replacement among enabled amendments was listed, meaning no mainnet majority countdown had yet begun for either change.

Latest closeXRP $1.082 ▲2.1%

More like this

Sources