Clearing & Settlement

DTCC/NSCC T+1 Clearing

Traditional CCP clearing — NSCC as central counterparty, CNS netting, T+1 settlement.

Vendors

DTCC · NSCC · Broker-Dealers

Compliance center

NSCC as CCP at Authorization + fail management at Facilitation

post-tradedtccnsccccpnettingt-plus-1
Filter by shape:
|
PT1 · POST-TRADEDTCC/NSCC T+1 clearing·5 stations(3 compliance, 2 infra)·dtcc
S1INTENTS2S3S4S5TRANSPORTS6AUTHORIZATIONS7FACILITATIONS8FINALITY01Deposit02Netting03Margin Check04Bridge05Filing
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 DTCC/NSCC T+1 clearing 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. 3 are compliance checkpoints, 2 are infrastructure.
3 code-enforced2 policy-enforced
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L5 APPLICATIONHANDOFF

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

"The trade ticket arriving at the back office — the front office (Securities rail) has already executed, now post-trade processing begins."

**Cross-rail reference: Stages 1-4 fired on the Securities Trading rail.** The trade has already been executed — identity verified, price discovered, terms negotiated. This path begins at the post-trade handoff. The trade is captured in DTCC's Trade Information Warehouse. L5 Application lit only — the handoff is a recordkeeping event. All earlier compliance gates were satisfied on the originating rail.

Counterparty
DTCC Trade Information Warehouse
Latency
Instant · trade capture
Finality
N/A — post-trade processing 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 · NSCC Novation & Netting (CNS)Code-EnforcedINGESTDETECTALERT

"The clearing house stepping between buyer and seller — NSCC becomes the buyer to every seller and the seller to every buyer. Netting reduces gross obligations by ~98%."

NSCC novates the trade: it becomes the central counterparty to both sides. CNS (Continuous Net Settlement) nets all trades per security per participant, reducing gross settlement obligations by approximately 98%. L2+L3 lit: consensus (multilateral netting) and execution (novation logic) operate below the enforcement line. D9 (prudential) is primary — NSCC's risk management framework (margin requirements, clearing fund contributions) is the systemic risk control.

Counterparty
NSCC (central counterparty)
Latency
End of trade date · batch netting
Finality
Net obligations calculated · settlement pending
Vendors
Circle CCTP v2 (canonical USDC burn-and-mint cross-chain transport) · Wormhole · LayerZero · Across (intent-based settlement) · 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 · Chainalysis OFAC Oracle (on-chain SDN-list enforcement primitive · code-enforced at the contract layer for opt-in callers) · 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 MARGIN
◆ Enforcement Line — code-enforced at this layer

Step 3 · Margin & Risk ManagementCode-EnforcedINGESTDETECTALERT

"A futures exchange margin call — participants must post collateral proportional to their risk exposure, or face position liquidation."

NSCC calculates margin requirements via its NSCC Rules and VaR-based risk model. Clearing members post margin (cash, Treasuries, eligible securities) to NSCC's Clearing Fund. If a member defaults, the Clearing Fund and NSCC's loss allocation waterfall absorb losses. L3 Execution lit: margin calculations and risk monitoring are code-enforced at the CCP level. This is the compliance center of gravity — NSCC's risk framework is what makes T+1 settlement systemically safe.

Counterparty
NSCC risk management
Latency
Continuous · intraday margin calls possible
Finality
Pre-condition — settlement blocked if margin insufficient
Vendors
Chainalysis OFAC Oracle (on-chain SDN-list enforcement primitive · code-enforced at the contract layer for opt-in callers) · Uniswap v4 (extensible AMM — concentrated liquidity + custom-logic extension framework) · Curve · Balancer · 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 EXECUTIONDTC SETTLEMENT
L2 CONSENSUSDTC SETTLEMENT
L1 NETWORKDTC SETTLEMENT
◆ Enforcement Line — code-enforced at this layer

Step 4 · T+1 Settlement (DTC Book-Entry)Code-Enforced

"The Federal Reserve's Fedwire Securities Service — book-entry transfer of securities with simultaneous payment, but at DTCC it happens one business day after trade."

Settlement occurs T+1 via DTC's book-entry system. Securities move as book entries on DTC's ledger; cash moves through the Federal Reserve's National Settlement Service. DvP is enforced — securities and cash move simultaneously. L1+L2+L3 lit — the full stack below the enforcement line. If settlement fails (insufficient securities or cash), the fail enters NSCC's fail management process with penalty charges (SEC Rule 204).

Counterparty
DTC book-entry system / Fed NSS
Latency
T+1 · next business day
Finality
Final on DTC settlement confirmation
Vendors
Circle CCTP v2 (canonical USDC burn-and-mint cross-chain transport) · Wormhole · LayerZero · Across (intent-based settlement) · EOA (secp256k1 externally-owned accounts) + ERC-4337 account abstraction (EntryPoint singleton + UserOperation mempool — paymaster and aggregator extensions) · Ethereum devp2p / libp2p transport · EIP-4844 blob-data DA layer (canonical DA for OP Stack and other rollup-based L2s — Base, Arc, Tempo, Arbitrum, Optimism, etc.) · 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 · Chainalysis OFAC Oracle (on-chain SDN-list enforcement primitive · code-enforced at the contract layer for opt-in callers) · 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 · Fail Management & ReportingPolicy-EnforcedINGESTDETECTALERT

"The back office's end-of-day reconciliation — fails identified, buy-in notices issued, regulatory reports filed."

Settlement is final — or a fail is recorded. Failed settlements trigger SEC Rule 204 close-out requirements (buy-in within specified timeframes). NSCC tracks fails and can force close-outs. L5 Application lit only. Regulatory reporting (FINRA TRACE, CAT) captures the full trade lifecycle. **Structural note:** the T+1 compression (from T+2, effective May 2024) reduced but did not eliminate settlement fails. The Post-Trade rail exists because finality is never guaranteed — it must be managed.

Counterparty
NSCC fail management / SEC / FINRA
Latency
T+1 (settlement) / T+3 (fail close-out deadline)
Finality
Final if settled · managed if failed
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