A new live dashboard launched this week by XRP Ledger developer Denis Angell provides a public scorecard to quantify the testing of amendments on the devnet before they reach mainnet, aiming to enhance transparency in the protocol update process.
The tool, accessible at amendments-staging.xrpl.foundation, reads amendment specifications directly from the node. It monitors devnet activity to identify whether each component—including transaction types, optional fields, flags, result codes, and ledger entries—has been exercised by a validated transaction. Functionality that has been exercised is marked with green cells, linked to the originating transaction, while untested components are highlighted in red.
“Every new XRPL feature ships as an amendment. Validators vote it in, and once it’s active it’s part of the protocol for good. That deserves real evidence that the feature has been exercised end to end on devnet, not just tested in isolation,” Angell explained. This approach shifts amendment readiness from a matter of trust to one of verifiable, public data.
Currently, the dashboard monitors 16 amendments on devnet, with 13 still exhibiting untested surface areas. Notable gaps include the Sponsor amendment (65 of 107 checks unexercised), XChainBridge (30 of 40 checks missing), and MPTokensV1 (27 of 102 checks short).
The tool’s scan has identified 59 findings across amendments, comprising two spec bugs, 23 documentation gaps, and 34 test gaps. The XLS-75 permission delegation amendment, which allows accounts to delegate specific powers, recently addressed its remaining test gaps. Angell noted that logic was added to map each delegated transaction to its specific permission, resulting in all 122 checks across its 12 granular permissions now being exercised on devnet.
Angell encourages XRPL builders to engage with the tool, framing the effort as crowdsourced. The dashboard updates in near real-time, reflecting new devnet activity within seconds.
This initiative for more rigorous pre-activation testing follows past upgrade challenges. As CryptoPotato reported in July, Ripple’s v3.2.0 update, which renamed the core server software to xrpld and reduced node memory usage by 30% to 40%, saw slow adoption. Weeks after its release, over half of XRPL nodes had not adopted the update, despite 89% of the network’s trusted validator set having implemented it.
Uncertainties remain regarding the specific nature of the identified spec bugs, documentation gaps, and test gaps. It is also uncertain whether all XRPL builders will participate in the crowdsourced effort to address the remaining untested areas.
Why This Matters
The materials describe a narrow update: XRPL developer Denis Angell launched a live dashboard that scores XRP Ledger amendments based on how much of their functionality has been exercised on devnet before mainnet deployment. The exact date of the dashboard’s launch.
Broader Context
Source materials place the factual news in this context: XRPL developer Denis Angell launched a live dashboard this week that scores every amendment on the XRP Ledger for how much of its functionality has actually been exercised on devnet before it reaches mainnet.
Leave a Reply