Securities Trading

Tokenized Structured Finance

On-chain structured credit — tokenized ABS, CLOs, and private credit tranches.

Vendors

Centrifuge · Goldfinch · Maple

Compliance Center

Tranche structure + credit risk at Negotiation

S5 — Tokenized structured finance · Rails: securities · Protocols: Centrifuge, Goldfinch, Maple · Origin: United States — Federal
CTR (USD 10,000+)TRAVEL-RULE (USD 3,000+)ENHANCED-DUE-DILIGENCE (USD 50,000+)
S5 — TOKENIZED STRUCTURED FINANCEYOU ARE HERE● Lender/Investor…POLICY⬣ Tranche Selecti…CODE▲ Capital Deploym…CODE⬣ Repayment Water…CODE● Exit / MaturityPOLICYIntentIdentityDiscoveryNegotiationTransportAuthorizationFacilitationFinalitySTEP 1STEP 2STEP 3STEP 4STEP 5ETHEREUMVisual system: StablecoinAtlas.com · Steps mapped to 8 STP Stages
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L5 APPLICATIONWallet UX, consent, policy engineBank customer channel / issuer app
L4 ACCOUNTBalances, addresses, signing keysCore banking ledger / DDA

Step 1 · Lender/Investor OnboardingPolicy-EnforcedBlockchain-Native

An institutional investor completing subscription documents for a CLO fund — accreditation, suitability, and risk disclosure reviewed.

Investor completes onboarding for the structured credit pool. For institutional pools (Centrifuge/Aave integration, Maple Blue), this means KYB + accredited investor verification. For permissionless pools (Goldfinch Senior Pool), onboarding may be lighter — UID verification only. L4+L5 lit: identity and authorization are policy-enforced. The compliance surface varies dramatically by pool: institutional pools mirror traditional structured finance onboarding; permissionless pools have minimal gates.

Active Compliance Checkpoints
C2 OFAC SDN/SSI list screening — OFAC 50 USC § 1702 (United States — Federal) · GENIUS §6
⚠ ENHANCED-DUE-DILIGENCE triggered at USD 50,000 — 31 CFR § 1010.312 — Enhanced Due Diligence (United States — Federal)
Counterparty
Pool operator (Centrifuge SPV / Maple pool delegate)
Latency
1-5 days (institutional) / instant (permissionless)
Finality
N/A — onboarding complete
Vendors
MetaMask / Fireblocks · EOA / ERC-4337
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L4 ACCOUNTBalances, addresses, signing keysCore banking ledger / DDA
L3 EXECUTIONSmart contracts, swap / bridge logicClearing & matching engine
◆ Enforcement Line — code-enforced below, policy-enforced above

Step 2 · Tranche Selection & TermsCode-EnforcedBlockchain-Native

Structuring a CLO — senior tranche gets first claim on cash flows, junior tranche absorbs losses first, equity tranche earns the spread. The waterfall is the compliance artifact.

The compliance center of gravity. The investor selects a tranche: senior (lower risk, lower yield, first claim on repayment), mezzanine, or junior/equity (higher risk, higher yield, first loss). The smart contract encodes the waterfall — repayment priority, default triggers, liquidation thresholds. L3+L4 lit — tranche structure straddles code (smart contract waterfall) and policy (credit risk disclosures). Sanctions screening fires on the investor address. D9 (prudential) applies because the pool operator has credit risk management obligations.

Active Compliance Checkpoints
C2 OFAC SDN/SSI list screening — OFAC 50 USC § 1702 (United States — Federal) · GENIUS §6
Counterparty
Pool smart contract (tranche selection)
Latency
<1s · on-chain tranche selection
Finality
Pre-condition — tranche terms accepted
Vendors
Chainalysis OFAC Oracle · Uniswap v4 · Circle CCTP v2 · EOA / ERC-4337
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L3 EXECUTIONSmart contracts, swap / bridge logicClearing & matching engine
L2 CONSENSUSValidator ordering, block productionRTGS settlement engine
◆ Enforcement Line — code-enforced below, policy-enforced above

Step 3 · Capital Deployment (USDC → Pool)Code-EnforcedBlockchain-Native

Wiring subscription funds to a CLO SPV's custody account — capital committed, the investor receives their tranche certificate.

Investor deposits USDC into the pool. The pool smart contract mints a tranche token (e.g., Centrifuge DROP/TIN, Maple pool token) representing the investor's position. L2+L3 lit: consensus and execution process the deposit. The capital is now deployed to borrowers through the pool's credit facility. D10 (operational resilience) applies — smart contract risk is real: a bug in the waterfall logic could mis-allocate repayments. D14 (consumer protection) applies for retail-accessible pools.

⚠ TRAVEL-RULE triggered at USD 3,000 — 31 CFR § 1010.410(f) — Funds Transfer Recordkeeping (United States — Federal)
Counterparty
Pool smart contract (Centrifuge / Maple)
Latency
~12s · Ethereum block
Finality
Capital deployed · tranche token minted
Vendors
Circle CCTP v2 · EOA / ERC-4337 · Ethereum PoS Validators · Uniswap v4 · Chainalysis OFAC Oracle
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L3 EXECUTIONSmart contracts, swap / bridge logicClearing & matching engine
◆ Enforcement Line — code-enforced below, policy-enforced above

Step 4 · Repayment Waterfall & MonitoringCode-EnforcedBlockchain-Native

A CLO trustee distributing monthly cash flows according to the waterfall — senior tranches paid first, then mezzanine, then equity gets the residual (if any).

Borrower repayments flow through the smart contract waterfall. Senior tranche holders receive their yield first, then mezzanine, then junior/equity. If a borrower defaults, the junior tranche absorbs losses first. All of this is code-enforced — the waterfall executes automatically with no trustee discretion. L3 Execution lit: the waterfall is pure smart contract logic. D9 (prudential) applies to the pool operator's credit monitoring. Honesty marker: unlike traditional CLOs, there is no trustee with fiduciary duties, no rating agency, and no independent credit assessment for most DeFi structured products.

⚠ CTR triggered at USD 10,000 — 31 CFR § 1010.311 — Currency Transaction Report (United States — Federal)
Counterparty
Pool waterfall contract
Latency
Continuous · triggered by repayment events
Finality
Conditional — distributions follow waterfall priority
Vendors
EOA / ERC-4337 · Uniswap v4 · Chainalysis OFAC Oracle · Circle CCTP v2
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L5 APPLICATIONWallet UX, consent, policy engineBank customer channel / issuer app
L4 ACCOUNTBalances, addresses, signing keysCore banking ledger / DDA

Step 5 · Exit / MaturityPolicy-EnforcedBlockchain-Native

A CLO reaching its maturity date — principal returned, final distributions calculated, the fund winds down.

The investment reaches maturity or the investor exits via secondary market sale (if the tranche token is transferable). Principal is returned according to the waterfall. L4+L5 lit: exit is policy-enforced. Tax reporting (D12) applies on realized yield. Honesty marker: many DeFi structured credit pools have experienced defaults (Maple's Orthogonal Trading default, Goldfinch's Stratos/Cauris defaults). The compliance framework — credit committee governance, default recovery, investor communication — is still immature compared to traditional structured finance.

Active Compliance Checkpoints
C11 SAR/CTR filing via BSA E-Filing — 31 CFR § 1010.320 (United States — Federal) · GENIUS §9
Counterparty
Pool operator / secondary market
Latency
Variable · maturity-dependent
Finality
Final · principal and yield distributed
Vendors
EOA / ERC-4337 · MetaMask / Fireblocks

Resolved 5 steps across 1 chain(s). 3 threshold(s) triggered. Frameworks: Bank Secrecy Act, GENIUS Act, OFAC Sanctions Program, FATF Recommendation 16 (Travel Rule), Common Reporting Standard / FATCA.