Researchers affiliated with the Bank for International Settlements (BIS) have tested the XRP Ledger as a way to verify official statistics, according to a working paper published on 2 September.
The experimental system linked the XRP Ledger with Statistical Data and Metadata eXchange (SDMX), an international standard used by organisations including the BIS to exchange statistical information.
Rather than storing complete datasets on the blockchain, the prototype generated cryptographic fingerprints for the data and recorded them on the XRP Ledger’s Devnet. A recipient could then check whether a downloaded file matched the version originally released by its publisher.
The work was not a production deployment, a partnership with Ripple or an endorsement of XRP as an investment. The paper also made clear that its findings belonged to the authors and might not represent the institutional position of the BIS.
Official statistics are usually made available through websites, databases and automated data feeds. Users must generally trust that the file they download is authentic and that its contents have not been altered since publication.
To create an independent verification record, the researchers converted an SDMX file into a standardised format before publication. The system then calculated a SHA3-512 cryptographic hash.
A hash acts like a unique digital fingerprint for a file. Even a minor alteration to the original data creates a different hash, allowing a recipient to repeat the calculation and compare the result with the fingerprint stored on the XRP Ledger.
The prototype could verify either an entire file or selected statistical series within it. Where several series were involved, their individual hashes were combined into a Merkle root. This enabled multiple data components to be represented by one on-chain record while still allowing each component to be checked independently.
That root was recorded through an XRP Ledger transaction. The SDMX file then contained a reference to the transaction, giving a verifier the information needed to find the blockchain record and carry out the comparison.
The system did not determine whether the statistics themselves were accurate. Its role was narrower: to show that the file being checked matched the version associated with the original record.
Results came from XRPL Devnet testing
Under controlled test conditions, the paper reported a median publication time of about three to five seconds. Verification took approximately one to two seconds.
Publication latency covered the creation and confirmation of the blockchain record. Verification involved recalculating the file’s fingerprint and comparing it with the information held in the relevant XRP Ledger transaction.
The researchers cautioned that those figures should not be regarded as guaranteed production performance. The measurements came from an experimental system running on XRPL Devnet, rather than the public XRP Ledger mainnet used for real transactions.
XRPL Devnet provides test XRP through a faucet, enabling developers to experiment without using assets with market value. Its activity levels, reliability requirements and operating conditions differ from those of the mainnet.
The researchers selected XRPL partly because of its relatively rapid transaction confirmation and low transaction costs. However, the experiment did not directly compare its performance with Ethereum, Solana, permissioned databases or traditional digital timestamping services.
The code has been published in a public BIS repository. Its documentation describes the software as an experimental proof of concept that is not intended for production use and is not actively maintained.
Identity was included in the verification process
Showing that a file has not changed addresses only part of the wider verification challenge. A malicious actor could produce a valid hash for a fraudulent file and publish it from an unrelated blockchain address.
The prototype attempted to address that problem through a publisher identity system. It used a W3C Verifiable Credential, signed by an identity key linked to the publisher’s XRP Ledger address.
A recipient could use the credential to check whether the organisation publishing the file controlled the recognised address. The process therefore examined both the integrity of the data and the identity of the publisher.
The SDMX message contained the transaction reference, the ordered Merkle leaves and the credential required for verification. A user could reproduce the Merkle root from the received file and compare it with the ledger record through a single lookup.
The researchers said the architecture might eventually support zero-knowledge proofs. That could allow an organisation to demonstrate selected facts about restricted data without revealing the complete dataset.
They also pointed to possible applications for artificial intelligence agents. Automated systems increasingly collect statistics without a person manually checking every source. A machine-readable verification record could allow software to reject files that had been altered or attributed to the wrong publisher.
Those uses remain proposed extensions. The published repository contains experimental code, not a production service for central banks, national statistics agencies or AI companies.
No XRP payments or settlement were involved
The prototype used XRP Ledger infrastructure because each on-chain record requires a transaction. It did not use XRP for payments, liquidity, settlement or cross-border transfers.
On mainnet, anchoring a record would require only a small transaction fee, although the amount would depend on network conditions and the publication method chosen by an institution.
Using the XRP Ledger in this way would not necessarily create significant demand for its native asset. A publisher could record many statistical series through a single Merkle root, reducing the number of transactions required.
The experiment nevertheless broadens the range of applications tested on XRPL beyond payments and tokenised financial assets. The network is also developing institutional features involving permissioned trading, lending and asset issuance.
In related coverage, XRP Ledger’s institutional infrastructure has expanded through permissioned markets and native lending proposals. Those financial applications are separate from the statistical verification system examined by the BIS-affiliated researchers.
Research published by Evernorth found that XRP Ledger order-book volume rose by 79% while the number of daily traders declined during the second quarter.
Neither that development nor the institutional work indicates that the statistical prototype will enter production. They provide wider context for the financial and non-financial applications being explored across the XRP Ledger ecosystem.
Further work would be needed
Before an official statistics provider could rely on the system, additional security, governance and operational work would be required. Institutions would need policies covering publisher keys, compromised credentials, transaction failures and corrections to datasets that had already been issued.
The permanent nature of blockchain records also presents a difficulty. Official statistics are often revised when agencies receive new information or correct mistakes. A production system would need to distinguish legitimate revisions from unauthorised changes, while making clear which version was current.
Publishers would also have to decide whether to rely on a public blockchain, operate additional infrastructure or combine blockchain records with established digital-signature systems. Privacy requirements could restrict the metadata placed in public transactions.
The authors said the approach was not confined to SDMX. It could also be adapted for other structured formats, including XBRL, which is used by companies and regulators for financial reporting.
No implementation timetable was provided. The repository says the software is unmaintained, and the BIS has not announced plans to deploy the system across its official statistical publications.
The findings therefore do not show that the BIS has adopted the XRP Ledger. They show that an experimental system, running on XRPL Devnet, could verify statistical files within seconds under controlled conditions.
