Zum Hauptinhalt springen
Echtzeit-Radar & Feeds
Alle RSS Feeds ➔
👥 Community & Social
Windows Tipps & SecurityGrafikkarte vor Überhitzung schützen: So geht’s(25.09.2026 um 08:00 Uhr)
••••••••••
Windows Tipps & SecurityGrafikkarte vor Überhitzung schützen: So geht’s(25.09.2026 um 08:00 Uhr)
••••••••••
Intelligence View
⚡ tsecurity.de Intelligence

Delivery vs Payment (DvP): How CRE Solves the Hardest Problem in Finance

Recently, I wrote about CRE: The Missing Coordination Layer Between Traditional Banking and Blockchain. It's time to go deeper because coordination alone isn’t enough. The real problem has always been settlement. The Problem: S…

0
↗ Quelle (dev.to)
Reagiere als Erste:r — dein Feedback zählt!

Recently, I wrote about




CRE: The Missing Coordination Layer Between Traditional Banking and Blockchain.




It's time to go deeper because coordination alone isn’t enough. The real problem has always been settlement.



The Problem: Settlement Risk



At the core of every financial transaction is a simple requirement:




When one party delivers an asset, the other must pay.




This is known as Delivery vs Payment (DvP).

Asset transfer ↔ Payment transfer



Both must happen together or not at all. If they don’t, one party takes on risk.



Why DvP Breaks in Modern Systems



DvP works well inside a single system. But today’s financial world is fragmented across:




  • Banks

  • Blockchains

  • Custodians

  • Payment networks



Now consider this:

Asset → Exists on a blockchain

Payment → Exists in a bank ledger



Two completely different systems.



The real question becomes:




How do you guarantee both sides settle atomically across systems that don’t trust each other?




Before CRE: The Workarounds

The industry had previously resorted to the following before the emergence of solutions such as Chainlink Runtime Environment (CRE):




  • Intermediaries: Dependent on intermediaries such as clearing houses and custodians to facilitate trust between two parties

  • Time Delays: Time periods such as T+2 reduce risks

  • Manual Reconciliation: Systems reconcile transactions after the fact.



All of these introduce:




  • Counterparty risk

  • Operational complexity

  • Capital inefficiency



Why Blockchains Didn’t Fully Solve This



Blockchains introduced atomic settlement, but only within their own environment and it works perfectly.

Token A ↔ Token B (same chain)



But:

Token (on-chain) ↔ Cash (in a bank)



This is broken because blockchains cannot:




  • Access bank systems

  • Trigger external payments

  • Guarantee off-chain execution



Enter CRE: A New Settlement Primitive

Chainlink Runtime Environment (CRE) introduces:




Programmable, verifiable workflows across on-chain and off-chain systems




Instead of forcing everything onto one chain, CRE connects:



Smart contracts → Chainlink Runtime Environment → External systems (banks, APIs, other chains)



This approach enables a cross-system atomic settlement



A Real Example: Cross-System DvP in Action



Recently,

Chainlink,

JPMorgan Chase (via Kinexys), and

Ondo Finance



executed a cross-chain Delivery vs Payment transaction.



This is one of the clearest real-world examples of CRE in action.



What Was Being Traded




  • Asset: Tokenized U.S. Treasuries (OUSG)

  • Payment: Bank deposit on Kinexys



Where each part lived:




Ondo Chain → Asset layer


Kinexys → Bank payment layer


CRE → Coordination + execution layer




Step-by-Step: How the Transaction Happened



Step 1: The Intent

A participant wants to buy tokenized U.S. Treasuries (OUSG).



But:




  • The asset is on a blockchain

  • The money is in a bank



Step 2: The Risk

Without coordination:




Send money first → risk losing funds


Receive asset first → risk not getting paid




In the absence of atomic settlement, there are many hidden but critical risks that may affect the transaction. When one side of a transaction is executed before the other, a party may have fulfilled their side of the transaction but may not receive anything in return. This is referred to as principal risk. Even if both parties are willing to settle, there may be timing risks due to changes in market conditions or system and participant behavior.



Step 3: CRE Coordinates the Transaction

Instead of trusting either side, both systems are connected through Chainlink Runtime Environment (CRE)



Step 4: Conditional Logic Is Enforced

CRE defines the rules:




IF payment succeeds → release asset


IF asset transfer succeeds → finalize payment


ELSE → abort everything




The transaction reverts if any of the conditions fail. This is the beauty of atomic transactions.



Step 5: Parallel Execution

Both systems are triggered simultaneously:



On Ondo Chain:




Prepare transfer of OUSG tokens




On Kinexys:




Prepare transfer of bank deposit




Step 6: Verification and Consensus

CRE nodes:




  • Monitor both sides

  • Verify execution results

  • Reach consensus



Step 7: Atomic Settlement



Only when both sides are confirmed:




OUSG tokens → transferred


USD deposit → transferred




If anything fails:




Everything is rolled back




This is more than just a successful transaction, it introduces a new financial primitive:




  1. Cross-System Atomicity

    DvP is no longer limited to a single ledger.



  2. Trust-Minimized settlement as trust would only be on protocol.

    No need to trust:




    • The counterparty

    • The bank

    • The blockchain




  3. Real-World Asset enablement as Tokenized assets can now settle against:




    • Bank deposits

    • Stablecoins

    • Future CBDCs





For years, blockchain technology has claimed the promise of "Faster, cheaper, trustless settlement." However, until the problem of cross-system DvP is resolved, the promise is incomplete. Now, with the introduction of CRE, the settlement is not only happening on a particular blockchain but across the entire financial system.

1. Sofort-Triage & Abwehrmaßnahmen

SOC Incident Playbook: Remote Code Execution (RCE) Defense
Syntax validiert (0 Fehler)
title: Detect Exploitation - Delivery vs Payment (DvP): How CRE Solves the Hardest Problem in Finance
id: a1a3c11d-1d70-4ec0-b372-60baa7998df7
status: experimental
description: Automatisch generierte SIEM-Erkennungsregel basierend auf CTI Intelligence
references:
  - https://tsecurity.de/
author: iShareStuff CTI Automated Detection Engine
date: 2026-09-26
logsource:
  category: network_connection
  product: any
detection:
  selection:
      CommandLine|contains:
        - 'exploit'
  condition: selection
falsepositives:
  - Legitime administrative Zugriffe oder Penetrationstests
level: high
tags:
  - attack.initial_access
Syntax validiert (0 Fehler)
rule CTI_Threat_Indicator {
    meta:
        author = "iShareStuff CTI Automated Detection Engine"
        date = "2026-09-26"
        description = "YARA Signature for "
    strings:
        $str = "Delivery vs Payment (DvP): How" ascii wide
    condition:
        any of them
}
Syntax validiert (0 Fehler)
index=security sourcetype IN ("cisco:asa", "pan:traffic", "zeek_conn", "suricata", "WinEventLog:Security")
("Delivery vs Payment DvP How CRE Solves t")
| stats count earliest(_time) as first_seen latest(_time) as last_seen by src_ip, dest_ip, dest_host, signature
| eval first_seen=strftime(first_seen, "%Y-%m-%d %H:%M:%S"), last_seen=strftime(last_seen, "%Y-%m-%d %H:%M:%S")
| sort - count
Syntax validiert (0 Fehler)
message: "*Delivery vs Payment DvP How CRE Solves t*"
Syntax validiert (0 Fehler)
CommonSecurityLog
| where Message has "Delivery vs Payment DvP How CRE Solves t"
| summarize EventCount = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by SourceIP, DestinationIP, DestinationPort, Activity
| extend DetectionRule = "iShareStuff-CTI-Compiled"
| sort by EventCount desc

2. Cyber Threat Intelligence & Forensik

🎯
MITRE ATT&CK Matrix Navigator 14 Taktiken
Reconnaissance
-
Resource Development
-
Initial Access
Execution
Persistence
-
Privilege Escalation
Defense Evasion
Credential Access
-
Discovery
-
Lateral Movement
-
Collection
-
Command and Control
Exfiltration
-
Impact
tsecurity.de Cognitive Threat RAG
Fokus-Vektor:

Kognitive Analyse für identifizierte Bedrohung: Erhöhte Bedrohungslage im Bereich Delivery vs Payment (DvP): How CRE Solve.... Basierend auf 368k Vektor-Korrelationen werden sofortige Isolationsmaßnahmen für betroffene Endpunkte empfohlen.

🛡️ Angriffsfläche & Exposure

Netzwerk/Remote-Zugriff ohne Vorauthentifizierung möglich.

⚡ Empfohlene Sofortmaßnahmen
  • 1. Perimeter-Inspektion: Relevante Portfreigaben und exponierte Endpunkte unverzüglich scannen.
  • 2. Patch-Applikation: Hersteller-Hotfix einspielen oder betroffene Daemons in isolierte DMZ-Segmente überführen.
  • 3. Telemetrie & EDR-Alerts: Prozessaufrufe und Child-Processes auf anomale Shell-Spawns überwachen.
🔗 Semantisch verwandte Zero-Days MariaDB 11.7 VEC
Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten Delivery vs Payment (DvP): How CRE Solves the Hardest Problem in Finance

Thematisch verwandte Begriffe: Delivery, Payment, Solves, Hardest · 6 Treffer

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Zum Aktualisieren ziehen
ZERO-DAY CVE-2026-88003 | InvoicePlane is a self-hosted open source application for managing invoi…
Advisory →
tsecurity.de Icon
Offline-Lesen, Eilmeldungen & 0ms Ladezeit

Installiere tsecurity.de direkt auf deinen Home-Bildschirm für das ultimative Vollbild-Magazinerlebnis ohne Browser-Leisten.

Nächster Beitrag