Updated for the 2026 CFA® Level I curriculum.
A distributed ledger replaces one central record keeper with a shared record that many participants hold at once. For CFA Level I, you need to describe how this structure supports specific financial functions, not how the underlying code works. Exam questions typically present a financial scenario and ask which ledger feature, network type, or consensus method fits it. This note walks through the mechanics, the network design choices, and the main financial applications in that order.
Quick Answer
Distributed ledger technology (DLT) is a system where multiple participants hold synchronized copies of a transaction record. Cryptographic linking and a consensus process coordinate updates across the network. This structure supports payments, clearing and settlement, asset tokenization, identity verification, custody, and compliance recordkeeping. Its financial value comes from a shared, tamper-resistant record.
Key Takeaways
DLT maintains synchronized copies of a transaction record across multiple participants instead of one central database.
Cryptographic linking between blocks and a consensus process among participants protect the ledger from unauthorized changes.
Permissioned networks restrict participation to approved members; permissionless networks allow open participation.
Proof of work and proof of stake are two ways to reach consensus on which transactions are valid.
Smart contracts automate actions once agreed conditions are met, supporting faster settlement and tokenization.
Financial applications include payments, clearing and settlement, tokenization, identity, custody, and recordkeeping.
DLT can reduce reconciliation and settlement time, but legal, governance, and adoption limits still apply.
What You Need to Know for CFA Level I
Define a distributed ledger as synchronized records maintained across network participants.
Explain how blocks, cryptographic linking, consensus, and smart contracts work together at a conceptual level.
Compare permissioned and permissionless networks by access, governance, and privacy.
Distinguish proof of work from proof of stake as two consensus mechanisms.
Describe how DLT applies to payments, clearing, settlement, tokenization, identity, custody, and recordkeeping.
Recognize that DLT offers potential efficiency gains, not guaranteed advantages, and still depends on legal and operational conditions.
How Distributed Ledger Technology Works
A distributed ledger is a database of transactions that is copied and synchronized across many participants in a network.
Transaction Recording and Block Linking
When someone submits a transaction, the network groups it with other transactions into a block. That block links to the previous block using cryptography, creating a chain of records that is difficult to alter without detection.
Consensus and Immutability
Before a block joins the ledger, network participants must agree it is valid. This agreement process is called consensus. Consensus replaces the role a single clearinghouse or bank would normally play. Once enough participants agree, every copy of the ledger updates at the same time.
This design gives the ledger a property often called immutability. In practice, this means altering a past record is very difficult and easy to detect, not that alteration is mathematically impossible. Level I candidates should treat immutability as strong resistance to tampering, not an absolute guarantee.
Smart Contracts and Automated Execution
Many DLT systems also support smart contracts. A smart contract is a self-executing set of rules coded into the ledger. When specified conditions are met, the contract automatically carries out an action, such as releasing payment once a delivery condition is confirmed. This automation reduces the need for a separate intermediary to verify each step manually.
Permissioned vs Permissionless Networks
Financial institutions choose a network type based on how much control and privacy a transaction requires. The two main categories are permissioned and permissionless networks.
Feature | Permissioned Network | Permissionless Network |
|---|---|---|
Participation | Approved participants only | Open to anyone |
Governance | Controlled by a defined group | Distributed among all participants |
Privacy | Higher, transaction details limited to approved members | Lower, transactions typically visible to all |
Speed | Often faster due to fewer validators | Often slower due to broader validation |
Typical use | Interbank settlement, institutional platforms | Public cryptocurrency networks |
Neither design is universally better. A regulated settlement platform usually needs permissioned access because participants must be verified and transaction details must stay private. A public payment network built for broad access favors a permissionless design because it prioritizes open participation over centralized control. The right choice depends on the financial application's trust, privacy, and governance requirements.
Proof of Work vs Proof of Stake
Proof of work and proof of stake are two conceptual approaches to reaching consensus on a distributed ledger.
Feature | Proof of Work | Proof of Stake |
|---|---|---|
Validation method | Participants solve a computational puzzle | Participants commit (stake) assets as collateral |
Resource use | High computing power and energy | Lower computing power and energy |
Incentive to act honestly | Cost of computation discourages fraud | Risk of losing staked assets discourages fraud |
Attack cost | Requires controlling significant computing power | Requires controlling a significant stake |
Both mechanisms aim to solve the same problem: agreeing on which transactions are valid without a central authority. Proof of work relies on computational effort as the cost of participation. Proof of stake relies on committed capital as the cost of participation. Level I coverage stops at this conceptual comparison. You do not need to calculate mining costs or validator returns.
Financial Applications of DLT
DLT supports several financial functions by changing how records are created, verified, and shared.
Application | DLT Feature Used | Potential Benefit | Limitation |
|---|---|---|---|
Payments and remittances | Shared ledger, consensus | Faster cross-border transfer, fewer intermediaries | Regulatory approval and network adoption still required |
Clearing and settlement | Synchronized records, smart contracts | Near-simultaneous settlement, less reconciliation | Legal recognition of ledger-based ownership varies by jurisdiction |
Tokenization | Cryptographic record of ownership | Fractional ownership, easier transfer of rights | Token must still be linked to an enforceable legal claim |
Identity verification | Permissioned access, cryptographic records | Reusable, verifiable identity credentials | Requires standardized rules across institutions |
Custody | Shared, tamper-resistant records | Clearer audit trail of asset ownership | Custodian still needs operational and legal safeguards |
Compliance recordkeeping | Immutable transaction history | Easier audit and regulatory reporting | Data privacy rules may limit what can be shared |
Tokenization deserves a brief note. Tokenization converts ownership rights in an asset into a digital record on a ledger. This can apply to real estate, securities, or other assets. Level I treats tokenization as a recordkeeping and transfer mechanism here. The investment features of tokenized and other digital assets are covered in the Digital Assets: Investment Features and Comparison With Other Asset Classes study note.
Worked Example
Northbridge Clearing Group, a syndicate of five regional banks, wants to transfer ownership of a syndicated loan position among approved members only. The group builds a permissioned ledger. Each bank must be verified before joining, and only syndicate members can view transaction details. A smart contract is coded to transfer ownership automatically once the buying bank's payment is confirmed on the ledger.
Step 1: Identify the network type. The syndicate restricts participation to approved banks, so this is a permissioned network, not permissionless.
Step 2: Identify the automation feature. The smart contract updates ownership records automatically once payment is confirmed, removing the need for a manual reconciliation step between banks.
Step 3: Identify the efficiency gain. Settlement happens closer to real time because the ownership update and payment confirmation occur on the same shared ledger.
Step 4: Identify the remaining limitation. The smart contract enforces the coded conditions, but it does not replace the legal agreement between the banks. If a dispute arises over loan terms, the banks still need an enforceable contract and a legal process to resolve it.
The permissioned network and smart contract improve coordination and speed among approved participants. Governance rules and legal enforceability still sit outside the ledger itself.
Common Exam Traps
Treating DLT as one cryptocurrency
DLT is the underlying technology. Cryptocurrencies are one application built on top of it. A question about ledger design is not automatically a question about a specific coin.
Assuming distributed means no governance
Permissioned networks still have rules about who can join and how decisions get made. Distribution of copies does not remove the need for governance.
Calling ledger records absolutely immutable
Cryptographic linking makes tampering difficult to hide, not impossible. Choose answers describing strong resistance to alteration, not guaranteed permanence.
Confusing permissioned access with proof of stake
Permissioned versus permissionless describes who can participate. Proof of work versus proof of stake describes how validation happens. These are separate design choices and can combine in different ways.
Claiming smart contracts remove all legal or operational risk
Smart contracts automate execution once conditions are coded and met. They do not replace legal enforceability or eliminate operational error in how conditions are defined.
Practice Question
A group of regulated banks wants to settle interbank transactions on a shared ledger. Regulation requires that only approved institutions can validate transactions and that transaction details remain private among participants. Which network design best fits this requirement?
A permissionless network using proof of work consensus
A permissioned network with restricted participation
A permissionless network with public transaction visibility
Correct Answer: B
Explanation: The scenario requires approved participants only and private transaction details. A permissioned network restricts validation rights to approved institutions and can limit visibility to network members, matching both requirements directly.
Option A. Proof of work describes a consensus mechanism, not participant approval. This choice also allows open participation, which conflicts with the regulatory requirement.
Option C. Permissionless networks allow open participation and typically expose transaction details broadly, which fails the privacy requirement in the scenario.
Continue Your CFA Level I Prep With KeyPoint
Use structured lessons, practice questions, mock exams, and progress tracking to focus on the time you have left
FAQs About Distributed Ledger Technology
What is distributed ledger technology?
Distributed ledger technology is a system where multiple participants hold synchronized copies of a transaction record. Updates go through cryptographic linking and a consensus process instead of relying on one central authority to maintain the record.
What is the difference between permissioned and permissionless DLT?
Permissioned networks restrict participation to approved members and often limit transaction visibility. Permissionless networks allow open participation and typically make transaction details visible to anyone on the network.
How is DLT used in financial services?
DLT supports payments, clearing and settlement, tokenization of assets, identity verification, custody, and compliance recordkeeping. Each application uses shared, synchronized records to reduce reconciliation steps and support faster verification.
What is a benefit of using a shared ledger?
A shared ledger lets multiple participants view the same synchronized record instead of reconciling separate databases. This can reduce settlement time and lower the risk of mismatched records between parties.