Clearing & Settlement

On-Chain Repo

Repurchase agreements on Canton Network — smart contract as compliance artifact, automated lifecycle events.

Vendors

Digital Asset · Canton · BNY · Goldman Sachs · HSBC

Compliance center

Smart contract = compliance artifact at Negotiation + automated lifecycle at Facilitation

post-traderepocantonbnygoldmansmart-contract
Filter by shape:
|
PT4 · POST-TRADEOn-chain repo (Canton Network)·6 stations(3 compliance, 3 infra)·digital-asset · bny · goldman
S1INTENTS2S3S4NEGOTIATIONS5TRANSPORTS6S7FACILITATIONS8FINALITY01Deposit02Sanctions03Canton Sync04State Update05Canton Sync06Filing
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 On-chain repo (Canton Network) 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
6 stations across 5 of 8 segments. 3 are compliance checkpoints, 3 are infrastructure.
4 code-enforced2 policy-enforced
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L5 APPLICATIONHANDOFF

Step 1 · Repo Initiation (Post-Trade Handoff)Policy-Enforced

"A repo desk agreeing to lend securities overnight — the collateral already exists, now the financing structure is created."

Cross-rail reference: the underlying securities were acquired on the Securities Trading rail. The repo transaction begins with both counterparties holding positions — one has securities to pledge, the other has cash to lend. Canton Network receives the repo instruction. L5 lit only — handoff.

Counterparty
Canton repo platform
Latency
Instant
Finality
N/A — repo structuring 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
L4 ACCOUNTREPO TERMS
L3 EXECUTIONREPO TERMS
◆ Enforcement Line — code-enforced at this layer

Step 2 · Daml Smart Contract NegotiationCode-EnforcedINGESTDETECTALERT

"GMRA (Global Master Repurchase Agreement) negotiation — but the contract is executable code, not a PDF. Every term is programmable."

The compliance center of gravity. A Daml smart contract encodes the repo terms: haircut, repo rate, maturity date, eligible collateral, margin call triggers, substitution rights. The smart contract IS the compliance artifact — it replaces the paper GMRA with executable, auditable code. L3+L4 lit: execution logic (contract deployment) and account state (collateral allocation) update simultaneously. Sanctions screening fires on both counterparties. D9 (prudential) applies — haircut and margin requirements are regulatory minimums.

Counterparty
Counterparty (via Daml contract negotiation)
Latency
<1s · Canton consensus on contract deployment
Finality
Repo terms agreed · smart contract deployed
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) · EOA (secp256k1 externally-owned accounts) + ERC-4337 account abstraction (EntryPoint singleton + UserOperation mempool — paymaster and aggregator extensions) · Securitize LLC (SEC-registered transfer agent; runs Reg D 506(c)(2)(ii) accredited-investor verification workflow) — off-chain compliance function paired with on-chain DS Protocol enforcement · EigenLayer (restaking primitive — slashing-conditional re-pledge of staked ETH and LSTs to Actively Validated Services; compliance-relevant for AVSs that supply oracle / fast-finality / DA security to downstream protocols)
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 EXECUTIONREPO OPENING
L2 CONSENSUSREPO OPENING
L1 NETWORKREPO OPENING
◆ Enforcement Line — code-enforced at this layer

Step 3 · Collateral Delivery (Opening Leg)Code-Enforced

"The opening leg of a repo — securities delivered to the cash lender (or tri-party agent), cash delivered to the securities borrower. Simultaneously."

Atomic DvP on Canton: securities transfer to the cash lender while cash (or stablecoin) transfers to the borrower in the same transaction. For tri-party repos, BNY Mellon acts as the tri-party agent — holding collateral and managing substitutions. L1+L2+L3 lit — the full stack below the enforcement line. Canton's privacy ensures each party sees only their leg of the transaction.

Counterparty
BNY Mellon (tri-party agent) / bilateral counterparty
Latency
<1s · atomic on Canton
Finality
Opening leg settled · repo active
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
L3 EXECUTIONLIFECYCLE
◆ Enforcement Line — code-enforced at this layer

Step 4 · Automated Lifecycle ManagementCode-EnforcedINGESTDETECTALERT

"The tri-party agent managing intraday margin calls, collateral substitutions, and mark-to-market revaluations — but automated by smart contract."

The Daml contract automatically manages the repo lifecycle: daily mark-to-market, margin calls if collateral value drops below the haircut threshold, collateral substitutions (if permitted by the contract terms), and interest accrual. All lifecycle events fire automatically — no human intervention, no missed margin calls, no disputed valuations. L3 Execution lit: lifecycle management is purely code-enforced. This is the second compliance center of gravity — automated lifecycle eliminates operational risk.

Counterparty
Daml smart contract (autonomous lifecycle)
Latency
Continuous · triggered by price feeds / time
Finality
Conditional — lifecycle events fire automatically
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 EXECUTIONREPO CLOSING
L2 CONSENSUSREPO CLOSING
L1 NETWORKREPO CLOSING
◆ Enforcement Line — code-enforced at this layer

Step 5 · Maturity / Closing LegCode-Enforced

"The repo maturing — securities return to the borrower, cash plus interest returns to the lender. The mirror image of the opening leg."

At maturity (or on early termination), the closing leg fires atomically: securities return to the original holder, cash plus accrued interest returns to the lender. Same atomic DvP as the opening leg but in reverse. L1+L2+L3 lit. The Daml contract self-terminates after the closing leg settles — no residual obligations, no open positions, no reconciliation needed.

Counterparty
Original counterparties (reversed)
Latency
<1s · atomic on Canton
Finality
Final · repo closed · contract terminated
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 6 · Reporting & Audit TrailPolicy-EnforcedINGESTDETECTALERT

"The repo report filed with regulators — but the smart contract has already produced a complete, immutable audit trail of every lifecycle event."

The Daml smart contract has produced a complete audit trail: every margin call, every substitution, every mark-to-market event, every interest payment — all immutably recorded on Canton. Regulatory reporting (SFTR for EU, Form N-MFP for US money funds) can be generated directly from the contract's event log. L5 Application lit only. Structural note: the smart contract as compliance artifact means the audit trail is a byproduct of operation, not a separate process. This is what "programmable compliance" means in practice.

Counterparty
Regulators (SFTR / SEC / central banks)
Latency
Batch · end of day
Finality
Final · full lifecycle audit trail on Canton
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 6 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