iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Delivery-versus-payment (DvP) links an asset transfer to its corresponding payment so neither leg is intended to settle alone. Hyperledger technologies can help coordinate that exchange, but the guarantee depends on where the assets live, how the payment is verified, and what happens when a participant, ledger, or off-chain process fails. A 2024 Hyperledger and Kaleido webinar illustrated several approaches; its demonstration is an educational example, not proof of production readiness.
What DvP settlement means
In DvP, delivery of an asset is conditioned on payment. In a securities transaction, for example, the securities transfer and cash payment are linked so one party is not left having delivered irrevocably without receiving the other leg. The Linux Foundation Decentralized Trust event description characterizes DvP as a way to mitigate settlement risk through the simultaneous exchange of securities and cash; Hyperledger Cacti uses the same basic idea in its financial-markets explanation.
That coupling targets principal or settlement risk. It does not, by itself, remove counterparty, operational, cyber, legal, liquidity, or regulatory risks. Nor does tokenizing an asset automatically make it a compliant security or create a legally recognized cash instrument. Those questions depend on the asset, jurisdiction, participants, and governing arrangements.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesDvP is distinct from payment-versus-payment (PvP): DvP links an asset leg, such as securities, to payment, while PvP links two payment legs, commonly in a currency exchange. The shared idea is conditional settlement; the exchanged items differ.
#1 Best Overall
What the 2024 Hyperledger and Kaleido webinar covered
The Linux Foundation event listing dates the webinar to April 24, 2024, and names Kaleido founder Steve Cerveny and senior full stack engineer Andrew Richardson as panelists. The listing describes a discussion of DvP challenges and benefits and an enterprise-flow demonstration. The LF Decentralized Trust event description says the toolkit was powered by Hyperledger FireFly and compatible with Hyperledger Besu, Hyperledger Fabric, and many public chains. These are descriptions of the event and its proposed toolkit, not independent assessments of platform performance or deployment readiness.
The presentation accompanying the webinar organizes DvP choices around the network, asset type, intermediary, and settlement mechanism. That framing is useful because “DvP on blockchain” is not one architecture: the exchange may involve one ledger, several ledgers, or an on-chain action paired with an off-chain event.
How the illustrated cross-chain DvP flow works
Kaleido’s April 2024 presentation demonstrates a hash-time-locked arrangement using an ERC-721 asset chain and a separate ERC-20 payment chain. A hash lock lets both legs refer to the same secret without revealing it at the outset; time locks provide deadlines for claims. The demonstrated sequence is:
Free tools Windows power users keep installed
One-click scans. No signup required.
- The seller escrows the NFT. The seller places the NFT in a settlement contract on the asset chain, chooses a secret, and sets an expiry. The contract records a hash of the secret.
- The buyer escrows payment. The buyer deposits ERC-20 payment into a contract on the payment chain using the same secret hash and a shorter expiry than the NFT leg.
- The seller claims payment. The seller reveals the secret to satisfy the payment contract and claim the payment. Revealing it makes the secret available on-chain.
- The buyer claims the NFT. The buyer uses the disclosed secret to satisfy the asset contract and claim the NFT before its deadline.
The shorter payment expiry is intended to give the seller an opportunity to claim payment while leaving the buyer time to claim the asset after the secret is revealed. The contracts and participants still need well-defined expiry ordering, monitoring, and recovery behavior. If a claim does not happen in time, the applicable timeout and refund paths matter; the exchange does not become one instantaneous transaction spanning both ledgers.
This is a vendor demonstration of one coordination pattern, not a universal protocol prescription. The design’s exact behavior depends on the contracts, chain finality assumptions, token controls, participant actions, and legal terms. In particular, a cross-chain process should not be described as equivalent to one globally atomic transaction merely because both legs use a shared hash.
Which DvP architecture fits the settlement domain?
The main design choice is where the asset and payment commitments reside and who or what can attest that each condition has been met. The following comparison summarizes the patterns described in Kaleido’s presentation and technical explainer.
| Approach | Settlement domain | Coordination mechanism | Key dependency |
|---|---|---|---|
| Single-ledger smart contract | Both commitments execute on one ledger | A contract records the commitments and executes them together or not at all; asset locking is optional in Kaleido’s description and depends on the exchange and desired guarantees. | The relevant commitments must genuinely share the contract’s execution domain, and the contract’s assumptions must be suitable for the assets and parties. |
| Multiple ledgers | Two or more ledgers, potentially using different protocols | Shared-hash claims coordinate the legs; time locks let unfulfilled settlements expire. | Each ledger’s timing and finality, expiry ordering, claim behavior, and timeout recovery must be accounted for. |
| On-chain plus trusted off-chain action | A ledger and an external system or event, such as physical delivery | Recorded evidence or sign-off gates an on-chain release; legal arrangements govern the off-chain domain. | A contract can check recorded confirmation, but cannot itself establish that a physical event occurred truthfully. |
| Supervised off-chain settlement | Settlement involving a trusted intermediary or notary | An intermediary may hold escrowed assets, or a notary may guarantee validity and execution; the trusted party may have authority to cancel or reverse a failed settlement. | The parties rely on intermediary governance, authority, and operations as well as the technical system. |
One ledger: the narrowest atomicity claim
When both commitments are actually handled by the same ledger and contract execution domain, a smart contract can make the operation conditional as a unit. That is the simplest atomicity story in the patterns presented. It does not automatically cover a separate ledger, a bank payment system, a physical handover, or any other external commitment.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Several ledgers: coordination with timeouts
Across chains, hash and time locks provide a way for counterparties to claim linked legs, while deadlines bound how long funds or assets remain committed. The parties need to understand the expiry sequence and the outcome at each failure point: who can claim, when a refund becomes available, and what happens if one chain is delayed or unavailable. These are operational parts of settlement design, not implementation details to leave implicit.
On-chain and off-chain: evidence is not the event itself
For physical goods or legacy-system actions, a smart contract can wait for a confirmation, but it cannot observe the real-world event directly. The design must specify what counts as evidence, who submits or verifies it, how a participant can challenge it, and which legal framework governs the external action. Cancellation, expiry, and dispute resolution need defined owners and procedures.
Rank #4
Supervision: an explicit trust trade-off
An intermediary or notary can provide oversight, escrow, validity checks, or a cancellation and reversal path. That may be appropriate for sensitive or regulated activity, but it adds a trusted actor and governance dependency. Comparing designs therefore means comparing trust assumptions, not simply counting smart contracts or ledgers.
How Hyperledger Cacti frames cross-network settlement
Hyperledger Cacti’s financial-markets example describes a CBDC payment on one ledger coordinated with the transfer of securities entitlements on a separate ledger. The intended DvP outcome requires those distinct legs to be coordinated atomically from the transaction’s perspective. It is a technical illustration of the cross-network problem, not evidence that a specific live deployment uses that design.
The distinction is important: a system may coordinate conditional steps without giving participants the same all-at-once guarantee as a single contract execution. The architecture must state what “success” means across both networks, how it detects partial completion, and which recovery or dispute mechanism applies.
Best Value
A separate example: a tokenized-bond lifecycle
An LF-hosted case-study presentation describes a digital-bond platform for a Spanish regulated central securities depository (CSD). It says a native tokenized bond was denominated and settled in tokenized cash, with issuance, coupons, principal repayments, and DvP included in the lifecycle. The presentation attributes the technology stack to ioBuilders and says the project was built for the Spanish CSD/CCP associated with SIX Digital Exchange Group.
This case study is separate from the ERC-721/ERC-20 Kaleido webinar demonstration. It illustrates a broader lifecycle around a tokenized bond, but the presentation’s description alone does not establish that its arrangements generalize to other markets or jurisdictions.
How to interpret the settlement-time statement
Kaleido’s April 2024 presentation states that traditional clearing and settlement can take up to T+2 days and that systems typically operate only during business hours. This is a vendor-authored statement from that presentation, not an independently verified or universally current statistic. Settlement cycles and operating schedules vary by market and instrument, so it should not be treated as a present-day rule for every transaction.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The reviewed materials establish no other independently sourced figure for market size, speed, cost, or risk reduction. Avoid inferring that a DvP architecture will settle faster or cheaper, or reduce risk by a quantified amount, without evidence for the particular market and implementation.
Questions to resolve before choosing an implementation
A useful design review starts by defining the settlement outcome and tracing every commitment, including those outside a ledger. Before adopting a vendor platform or pattern, settle the following points with the relevant technical, operational, legal, and compliance owners:
- Assets and authority: Identify the legal asset represented by each token, who controls transfers, and whether the cash or payment instrument is recognized for the intended transaction.
- Execution domain: Map which asset and payment legs share a ledger or execution environment and which depend on another chain, institution, or physical process.
- Failure and recovery: Define finality assumptions, expiry ordering, refunds, cancellation rights, points of no return, and responses to delays or outages.
- Evidence and disputes: For every off-chain condition, name the evidence source, who is authorized to confirm it, how it can be contested, and who resolves a dispute.
- Trust and governance: Document the role and authority of any intermediary or notary, including how it is appointed, monitored, and held accountable.
- Security and compliance: Evaluate contract security, key management, privacy, cybersecurity, regulatory obligations, and operational controls in the relevant jurisdiction.
- Platform claims: Treat compatibility, interoperability, performance, and customer claims as vendor descriptions unless independently validated. The 2024 event’s platform description named Hyperledger FireFly, Hyperledger Besu, Hyperledger Fabric, and public-chain compatibility; product details can change, so verify current versions, topology, governance, support, and security model before deciding.
What the webinar does—and does not—establish
The April 2024 webinar and its presentation are useful for understanding the design space: same-ledger execution, cross-ledger hash/time-lock coordination, and settlement that depends on trusted external action. They show why DvP is a coordination problem spanning assets, ledgers, and legal or operational domains. They do not, on their own, establish production readiness, independent performance, jurisdiction-specific legal sufficiency, or the suitability of any one architecture for a particular institution.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
