Exchange Ranking
Top Exchanges
24h Volume Ranking
Popularity Ranking
Exchange BTC Balance
Proof of Reserves
Decentralized Exchanges
Funding Rate
Funding Heatmap
Liquidation Data
Max Pain
Long/Short Ratio
Whale L/S Ratio
Binance/Okex/Huobi L/S
Bitfinex Margin L/S
ETF Tracker
Solana ETF
XRP ETF
Hong Kong ETF
Bitcoin Treasuries
Crypto Reversal
Ethereum Reserves
HyperLiquid Wallet Analysis
Hyperliquid Whale Watch
Large Transactions
On-chain Movement
Bitcoin ROI
Stablecoin Market Cap
Options Analysis
News
Articles
Economic Calendar
Features
Wallet
Contract Calculator
Security
Collections
Watchlist
Following
XRP XRPL developers launch a public dashboard to turn amendment testing into score cards
This week, XRPL developer Dennis Angel launched a real-time dashboard to evaluate the extent to which the functionality of each amendment on the XRP ledger is actually implemented on devnet (development network) before entering the main network. The tool transforms an amendment readiness process that previously relied on trust into a public scorecard that clearly demonstrates which transaction types, fields and result codes have never been used in real transactions.
What the dashboard actually tracks
The tool built by Angel is hosted at amendments-staging.xrpl.foundation, which reads the complete specification surface of each amendment directly from the node rather than manually maintaining it. This includes each transaction type, optional fields, flags, result codes and ledger entries introduced by the amendment. The dashboard then monitors activity on devnet and checks whether any verified transaction has actually performed everything-green cells link to the transaction that performed the operation for the first time, and red cells mark the parts that have not yet been touched.
The developers directly explained the logic behind the project: "Every new XRPL feature is released as an amendment. After the validator votes, it becomes part of the agreement and takes effect permanently. This requires real evidence that the feature is being implemented end-to-end on devnet, not just isolated testing." As of this week, the dashboard is monitoring 16 amendments on devnet, 13 of which still have untested areas. The biggest gaps occur in newer amendments: Sponsor has 65 of 107 inspections that have never been performed, XChainBridge is missing 30 of 40, and MPTokensV1 is missing 27 of 102.
This week's scan also found 59 issues: 2 specification flaws, 23 documentation gaps, and 34 test gaps. One of the amendments-XLS-75 privilege delegation, which allows accounts to grant specific privileges (such as freezing a line of trust and nothing more) to another key-filled the remaining testing gap this week. According to Angel, the team added logic to map each commission transaction back to the specific permissions behind it, and then executed all remaining cells on devnet, bringing all 122 checks for its 12 fine-grained permissions to full coverage. He views the work as crowdsourcing, encouraging XRPL builders to "go find red cells" and run missing transactions themselves because dashboards can capture new activity in seconds.
Amendment testing comes at a time of sluggish adoption
The push for stricter pre-activation testing comes after a bumpy upgrade cycle. According to reports, Ripple's v3.2.0 update renamed core server software from rippled to xrpld and reduced node memory usage by 30% to 40%, but several weeks after its release, more than half of XRPL nodes have not adopted the update, although 89% of the set of trusted validators in the network have been upgraded.
