GCRI · Technology
Distributed ledgers and digital assets
Distributed ledgers and digital assets use shared, replicated records maintained by consensus among participants. They support new forms of payment, asset registration and contracting, with distinct operational and financial risks. Fintech Nexus stewards this page for the Nexus Consortium.
Distributed ledgers and digital assets on the record.
- 01InstitutionThe Global Centre for Risk and Innovation (GCRI)
- 02The methodWhat distributed ledgers and digital assets covers
- 03Reference practiceDistributed ledgers are assessed against market infrastructure principles
- 04In systemic risk workShared ledgers, shared failure modes
- 05Applied inPlatforms that apply this method
- 06StewardshipWho maintains this page
- 07SourcesWhere this page’s references lead
What distributed ledgers and digital assets covers.
- 01
Core methods
consensus protocol analysis; self-executing contract code verification; on-chain analytics; cryptographic key management; token economic modelling; interoperability design.
- 02
Data and instruments
public ledger records; node and network telemetry; exchange order books; self-executing contract code repositories; audit reports.
- 03
Validation
Protocols and contracts are checked through formal verification, audits and adversarial testing. On-chain data allow independent reconciliation of balances and flows.
- 04
Limits
Code defects and governance disputes can cause irreversible losses. Links to the traditional financial system are often opaque.
- 05
Use in risk decisions
Ledger analysis informs how digital asset failures could spill into payments and markets. It supports evaluation of ledgers for transparent registries and aid distribution.
Distributed ledgers are assessed against market infrastructure principles.
| Reference | What it sets |
|---|---|
| CPMI-IOSCO PFMI | Risk management for systemically important infrastructures |
| FATF Recommendations | Anti-money laundering for virtual assets |
| FSB recommendations on crypto-asset activities | Regulation and supervision |
How the process runs.
Process
Distributed ledgers and digital assets: Payment from instruction to finality
An RTGS system checks a payment, queues it if funds are short, settles it gross in real time and gives final settlement.
01 Intake
- 01Payment instructionSource · ParticipantThe system should use, or at least accommodate, relevant internationally accepted communication procedures and standards.
- 04Validity and conditionality checksStep · System operatorA payment is accepted once it passes validity and conditionality checks, such as funds or credit. An invalid payment is generally rejected.
02 Settlement
- 02LiquidityDataset · ParticipantParticipants need liquidity for outgoing payments: central or commercial bank balances, incoming payments and intraday credit.
- 05QueueModel · System operatorA valid payment that fails conditionality checks is queued or rejected. Queuing and other liquidity-saving tools can cut liquidity needs.
- 06Settle in real time, grossStep · System operatorRTGS settles payments continuously, without deferral, usually one by one. Money settlements should use central bank money where practical.
03 Finality
- 07Final settlementRecord · System operatorThe system gives clear, certain final settlement by the end of the value date at least, intraday or real time where needed.
- 08ReconciliationStep · System operatorReconciliation checks that records issued by two different entities match. The pages read state no timing for payment systems.
04 Resilience
- 03Business continuity and secondary siteExercise · System operatorThe plan uses a secondary site and aims to resume critical IT within two hours and settle by end of day. Arrangements are regularly tested.
Outline of an external standard or method, from its public sources. It describes what the framework says, not a record of any run. It does not show that Nexus or any partner performs, certifies or approves a step. A gate is a step of the method, never a Nexus approval. The source is the CPMI-IOSCO Principles for financial market infrastructures. A business continuity plan covers disruption.
Shared ledgers, shared failure modes.
Ledgers replace a central operator with a protocol, which changes rather than removes operational, governance and legal risk. For public uses, the questions are finality, governance of protocol changes, key management and what happens when the ledger and the legal record disagree.
- Identify who can change the protocol.
- Assess key management and recovery.
- Check legal finality of recorded transfers.
Who maintains this page.
Fintech Nexus stewards distributed ledgers and digital assets: it keeps this description current and reviews how the method is applied across the platforms.
Where this page’s references lead.
The bodies and documents this page is read against. Status and editions change; each link goes to the issuing body.
Questions and answers.
Why does one institution host every method page?
How do I suggest a correction to a method page?
Contribute evidence from this page.
Reports is the Consortium’s quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.
- EmailGateway GW-GCRISend it from this pageEvidence, a correction, a case, a method, a review, a translation or profile input. It arrives tagged with this page, so the editor who owns it receives it.
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Reports community there. Curators review it; the DOI stays yours.
- ReportsGCRISee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.
Never send personal data, sensitive infrastructure detail or anything you have no right to share. A contribution is reviewed before use; sending it confers no authorship or editorial rights, and sponsorship never buys a finding.
Bring a method, a dataset or a question.
Information and enquiries are open today. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.
Legal documents.
Maps, data and figures on this site are shown for context and general information. They are not advice, forecasts or warnings; the limits of the information are set out in the Disclaimers and Data Notices.