Clearing & Settlement

LCH DigitalAssetClear

LCH SA's CCP clearing service for digital asset derivatives — traditional risk framework applied to tokenized instruments.

Vendors

LCH SA · GFO-X

Compliance center

CCP risk framework at Authorization + default waterfall at Facilitation

post-tradelchccpderivativesclearingdefault-waterfall
Filter by shape:
|
PT5 · POST-TRADELCH DigitalAssetClear·5 stations(4 compliance, 1 infra)·lch
S1INTENTS2S3S4S5TRANSPORTS6AUTHORIZATIONS7FACILITATIONS8FINALITY01Deposit02CCP Risk Gate03Funding Rate04Liquidation Engine05Filing
3+5 shape system
GatePre-condition — blocks if it failsMonitorConcurrent — observes without haltingObligationPost-settlement — reports after the factsolid = codedashed = policy
How to read this diagram
Each station on the rail represents a compliance or infrastructure event in the LCH DigitalAssetClear path. Hover any station to inspect it. The shape tells you what kind of event it is. The ring tells you how it's enforced.
Gate Monitor Obligation| Ingress Crossing Transform Settlement Venue
This path at a glance
5 stations across 5 of 8 segments. 4 are compliance checkpoints, 1 are infrastructure.
3 code-enforced2 policy-enforced
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L5 APPLICATIONHANDOFF

Step 1 · Trade Capture (Post-Trade Handoff)Policy-Enforced

"A digital asset derivative trade executed on GFO-X arriving at LCH SA for clearing."

**Cross-rail reference: Stages 1–4 fired on the Securities Trading rail.** A digital asset derivative (e.g., Bitcoin future settled in stablecoin) has been executed on GFO-X and submitted to LCH SA for CCP clearing. L5 lit only — the trade enters the post-trade pipeline. This step marks the handoff from execution venue (GFO-X) to central counterparty (LCH SA).

Counterparty
GFO-X (execution venue) → LCH SA
Latency
Instant · trade submission
Finality
N/A — clearing begins
Vendors
EOA (secp256k1 externally-owned accounts) + ERC-4337 account abstraction (EntryPoint singleton + UserOperation mempool — paymaster and aggregator extensions) · MetaMask · MetaMask Institutional (ConsenSys-operated; institutional custody/MPC integrations) · Fireblocks · Safe (Gnosis Safe — multisig + module framework) · Securitize Markets ATS (SEC-registered ATS) · INX Securities ATS · BlackRock BUIDL · Franklin BENJI · Hashnote USYC · Ondo OUSG · Apollo ACRED (Ethereum mainnet deployments; issuer profiles carry SEC-registered / NYDFS limited-purpose trust / Reg D 506(c) postures detailed in the respective compliance frameworks)
Chain
Ethereum (Ethereum Foundation (protocol research + core-dev grants; protocol itself is permissionless and operated by the validator set))
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L3 EXECUTIONCCP NOVATION
L2 CONSENSUSCCP NOVATION
◆ Enforcement Line — code-enforced at this layer

Step 2 · CCP Novation & Initial MarginCode-EnforcedINGESTDETECTALERT

"LCH stepping between buyer and seller for an interest rate swap — the same risk framework that clears $2.5 trillion in daily notional, now applied to digital assets."

LCH SA novates the trade and becomes the central counterparty. Initial margin is calculated using LCH's risk model (SPAN-based or VaR). Clearing members post margin — cash, sovereign bonds, or eligible collateral. Sanctions screening fires on all clearing members (D2). L2+L3 lit: novation logic and margin calculations are code-enforced at the CCP level. D9 (prudential) is primary — LCH's risk framework is regulated by ESMA and the Banque de France. D10 (operational resilience) ensures clearing continuity. **This is the compliance center of gravity** — the CCP's risk framework protects all downstream participants by absorbing counterparty exposure at the point of novation.

Counterparty
LCH SA (central counterparty)
Latency
~5 min · clearing cycle
Finality
Novated · initial margin posted
Vendors
Circle CCTP v2 (canonical USDC burn-and-mint cross-chain transport) · Wormhole · LayerZero · Across (intent-based settlement) · Chainalysis OFAC Oracle (on-chain SDN-list enforcement primitive · code-enforced at the contract layer for opt-in callers) · Ethereum Proof-of-Stake (Beacon Chain — Casper FFG finality + LMD-GHOST fork choice) — permissionless 32-ETH stake threshold; effective validator economics concentrated via Lido / Coinbase / Binance / Kraken / Figment staking pools · MEV-Boost relays (Proposer-Builder Separation — out-of-protocol; OFAC-compliant relays Flashbots / BloXroute Regulated have periodically dominated relay share) · Uniswap v4 (extensible AMM — concentrated liquidity + custom-logic extension framework) · Curve · Balancer · Securitize DS Protocol (on-chain transfer-restriction smart-contract framework enforcing eligible-investor whitelisting) · ERC-3643 / T-REX (industry-standard permissioned-token framework — Tokeny-developed, used by issuers outside the Securitize stack)
Chain
Ethereum (Ethereum Foundation (protocol research + core-dev grants; protocol itself is permissionless and operated by the validator set))
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L3 EXECUTIONCCP RISK
◆ Enforcement Line — code-enforced at this layer

Step 3 · Variation Margin & Risk MonitoringCode-EnforcedINGESTDETECTALERT

"Daily margin calls on an OTC swap portfolio — the CCP marks to market, calculates exposure changes, and calls for additional collateral."

LCH calculates variation margin daily: the change in mark-to-market value of each cleared position. Winners receive margin; losers pay. The risk engine monitors portfolio-level exposure, concentration risk, and stress scenarios. L3 Execution lit: margin calculations and risk monitoring run continuously, code-enforced. If a member's margin falls below requirements, intraday margin calls fire automatically. D9 (prudential) ensures that risk limits are enforced in real time, protecting the CCP and surviving members from cascading losses.

Counterparty
LCH SA risk engine
Latency
Daily (regular) / intraday (stress)
Finality
Conditional — margin calls may fire
Vendors
EOA (secp256k1 externally-owned accounts) + ERC-4337 account abstraction (EntryPoint singleton + UserOperation mempool — paymaster and aggregator extensions) · Uniswap v4 (extensible AMM — concentrated liquidity + custom-logic extension framework) · Curve · Balancer · Chainalysis OFAC Oracle (on-chain SDN-list enforcement primitive · code-enforced at the contract layer for opt-in callers) · Circle CCTP v2 (canonical USDC burn-and-mint cross-chain transport) · Wormhole · LayerZero · Across (intent-based settlement) · Securitize DS Protocol (on-chain transfer-restriction smart-contract framework enforcing eligible-investor whitelisting) · ERC-3643 / T-REX (industry-standard permissioned-token framework — Tokeny-developed, used by issuers outside the Securitize stack)
Chain
Ethereum (Ethereum Foundation (protocol research + core-dev grants; protocol itself is permissionless and operated by the validator set))
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L3 EXECUTIONDEFAULT WATERFALL
◆ Enforcement Line — code-enforced at this layer

Step 4 · Default WaterfallCode-EnforcedINGESTDETECTALERT

"The CCP's last line of defense — when a clearing member defaults, losses are absorbed in a prescribed sequence: defaulter's margin → default fund contribution → CCP equity → surviving members' default fund."

The default waterfall activates only if a clearing member fails to meet margin. Loss absorption sequence: (1) defaulter's initial margin, (2) defaulter's default fund contribution, (3) LCH SA's own "skin in the game" equity, (4) surviving members' default fund contributions. L3 Execution lit: the waterfall is code-enforced policy. D14 (consumer/member protection) applies — surviving members' exposure is capped and sequenced. D9 (prudential) ensures the waterfall is triggered correctly and losses absorbed in the prescribed order. **Structural note:** this is the same waterfall that protected markets during the 2008 crisis. Applying it to digital assets is what makes institutional adoption possible.

Counterparty
LCH SA default management (if triggered)
Latency
Event-driven · only on member default
Finality
Conditional — waterfall absorbs losses if default occurs
Vendors
EOA (secp256k1 externally-owned accounts) + ERC-4337 account abstraction (EntryPoint singleton + UserOperation mempool — paymaster and aggregator extensions) · Uniswap v4 (extensible AMM — concentrated liquidity + custom-logic extension framework) · Curve · Balancer · Chainalysis OFAC Oracle (on-chain SDN-list enforcement primitive · code-enforced at the contract layer for opt-in callers) · Circle CCTP v2 (canonical USDC burn-and-mint cross-chain transport) · Wormhole · LayerZero · Across (intent-based settlement) · Securitize DS Protocol (on-chain transfer-restriction smart-contract framework enforcing eligible-investor whitelisting) · ERC-3643 / T-REX (industry-standard permissioned-token framework — Tokeny-developed, used by issuers outside the Securitize stack)
Chain
Ethereum (Ethereum Foundation (protocol research + core-dev grants; protocol itself is permissionless and operated by the validator set))
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L5 APPLICATIONREPORTING

Step 5 · Settlement Finality & ReportingPolicy-EnforcedINGESTDETECTALERT

"The CCP's end-of-day settlement report — positions netted, margin settled, regulatory reports filed with ESMA and the Banque de France."

Settlement is final under the EU Settlement Finality Directive — LCH SA's settlement has legal finality protection across the EU. Regulatory reporting to ESMA and national competent authorities captures full position and margin data. L5 Application lit only. D11 (recordkeeping) and D12 (tax) apply — all trades, margin flows, and default events are logged for regulatory audit and tax reporting. **Key distinction:** LCH SA's DigitalAssetClear brings regulated CCP infrastructure to crypto — not "DeFi clearing" but traditional clearing applied to digital assets. The regulatory framework is EMIR, not experimental.

Counterparty
ESMA / Banque de France / national regulators
Latency
End of day · T+1 reporting
Finality
Final · EU Settlement Finality Directive protection
Vendors
EOA (secp256k1 externally-owned accounts) + ERC-4337 account abstraction (EntryPoint singleton + UserOperation mempool — paymaster and aggregator extensions) · MetaMask · MetaMask Institutional (ConsenSys-operated; institutional custody/MPC integrations) · Fireblocks · Safe (Gnosis Safe — multisig + module framework) · Securitize Markets ATS (SEC-registered ATS) · INX Securities ATS · BlackRock BUIDL · Franklin BENJI · Hashnote USYC · Ondo OUSG · Apollo ACRED (Ethereum mainnet deployments; issuer profiles carry SEC-registered / NYDFS limited-purpose trust / Reg D 506(c) postures detailed in the respective compliance frameworks)
Chain
Ethereum (Ethereum Foundation (protocol research + core-dev grants; protocol itself is permissionless and operated by the validator set))

Resolved 5 steps across 1 chain(s). 0 threshold(s) triggered. Frameworks: Common Reporting Standard / FATCA.

Coverage notes: 5 disclosed gap(s).

Other Clearing & Settlement Paths

SETTLEMENT CHAINS