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

securitiesstructured-financeabscloprivate-credittranching
Filter by shape:
|
S5 · SECURITIESTokenized structured finance·5 stations(2 compliance, 3 infra)·securitize · circle · chainalysis
S1INTENTS2S3DISCOVERYS4S5TRANSPORTS6S7FACILITATIONS8FINALITY01Custody02Sanctions03Subscription04Tx Monitoring05Settlement
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 Tokenized structured finance 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. 2 are compliance checkpoints, 3 are infrastructure.
3 code-enforced2 policy-enforced
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L5 APPLICATIONPool subscription portal / SEC-registered transfer agent (Securitize · Tokeny · Backed · Apex · SS&C pattern)
L4 ACCOUNTInvestor wallet ↔ on-chain identity claim issued by transfer agent

Step 1 · Lender/Investor OnboardingPolicy-Enforced

"An institutional investor completing subscription documents for a tokenized private-credit pool — accreditation, suitability, and risk disclosure reviewed before any capital is committed."

The policy-enforced gate that establishes legal capacity to subscribe. The verification produces an on-chain identity claim that the transfer-restriction module will check at every subsequent tranche transfer — onboard once, transfer many.

Institutional pools follow the traditional structured-finance pattern: KYB on the entity, accredited-investor verification under Reg D Rule 506(c)(2)(ii), and an SEC-registered transfer agent issuing the on-chain identity claim. Multiple industry actors fit the transfer-agent role — Securitize is the dominant actor for tokenized private funds [VERIFY current market share]; Tokeny SA, Backed Finance, Apex Group, SS&C, and U.S. Bank operate the same architectural slot.

Permissionless or community-trust-based pools — Centrifuge, Maple Finance, Goldfinch, and the direct-lending pool variants from institutional sponsors including KKR, Apollo, Ares, Blue Owl, and Golub Capital where authored — implement lighter onboarding: UID-style verification with the platform itself issuing the identity claim. Same data shape, different verification rigor.

L4 ACCOUNT and L5 APPLICATION lit: identity, the custodian's internal controls, and the transfer agent's record of beneficial ownership are policy-enforced bank-grade controls. The Investment Advisers Act of 1940 §204 (17 C.F.R. § 275.204-2) recordkeeping obligation attaches at the parallel adviser-side.

Honesty marker: The compliance surface varies dramatically by pool architecture. Institutional pools mirror traditional structured-finance onboarding — multi-day verification, third-party-attested credentials. Permissionless pools have minimal gates, and the regulatory enforceability of those minimal gates against a US-based investor remains an open question.
Counterparty
Pool operator · SEC-registered transfer agent
Latency
1–5 business days (institutional) · instant (permissionless)
Finality
Onboarding complete · on-chain identity claim issued
Cadence
Per investor onboarding · annual re-certification (institutional) · continuous attestation refresh (permissionless)
Vendors
Securitize · Tokeny · Backed Finance · Apex Group · SS&C · Verify Investor · Persona
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 ACCOUNTInvestor account ↔ tranche-specific identity claim consumed by transfer-restriction
L3 EXECUTIONERC-3643 transfer-restriction module + on-chain sanctions oracle (Securitize DS · Tokeny T-REX · Chainalysis · Elliptic · TRM Labs pattern)
◆ Enforcement Line — mixed code- and policy-enforced

Step 2 · Tranche Selection & TermsMixed EnforcementINGESTDETECTALERT

"Structuring a CLO — senior tranche gets first claim on cash flows, junior absorbs losses first, equity earns the residual spread. The waterfall is the compliance artifact, encoded in code rather than written in an indenture PDF."

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). Each tranche carries a different eligibility gate.

Tranche-tiered gating is enforced at the protocol level by the transfer-restriction module — Securitize DS Protocol is the dominant ERC-3643-aligned implementation [VERIFY current market share]; Tokeny T-REX is a parallel implementation; some pools use ad-hoc allowlist contracts or ERC-1404 variants. Reg D Rule 506(c) accredited-investor gating may differ across tranches: junior/equity tranches are commonly gated to qualified purchasers under §2(a)(51) of the ICA 1940; senior tranches accessible to the broader accredited-investor population.

Sanctions screening fires on the investor address via the on-chain sanctions-oracle primitive — Chainalysis OFAC Oracle is the dominant implementation on EVM chains; Elliptic and TRM Labs operate parallel attestation services. The screen runs at every transfer attempt, not only at subscription, so a subsequent OFAC designation freezes the position automatically.

L3 EXECUTION and L4 ACCOUNT lit: tranche structure straddles code (the smart-contract waterfall encoded at L3) and policy (the credit-risk disclosures and offering documents at the parallel adviser-side). C9 (prudential) applies because the pool operator carries credit-risk-management obligations; Risk Retention Rules / Reg RR (17 C.F.R. § 246) implementing Dodd-Frank §941 require pool operators to retain ≥5% of credit risk [VERIFY: framework not yet authored in compliance/registries/frameworks/].

Honesty marker: Risk Retention Rules / Reg RR is not yet a first-class authored framework in the registry, even though it is load-bearing for every structured-finance issuance under US law. Until authored, Reg RR provisions surface only as inline VERIFY citations in step prose rather than as resolved framework provisions in the path output.
Honesty marker: Tranche-tiered ERC-3643 enforcement assumes a transfer-restriction module that knows about tranche differentiation. Pools using single-tier allowlist contracts or ERC-1404 variants lose the per-tranche gating; off-chain placement-agent diligence has to fill the gap, which is a weaker compliance posture than the code-enforced equivalent.
Counterparty
Pool smart contract (tranche selection) · transfer-restriction module · on-chain sanctions oracle
Latency
<1s · on-chain check fires at subscription and at every subsequent transfer attempt
Finality
Pre-condition — tranche-tiered eligibility confirmed; capital deployment authorized
Cadence
Per subscription + per transfer attempt + on every OFAC list update propagated by the oracle
Vendors
Centrifuge · Maple Finance · Goldfinch · Securitize DS Protocol · Tokeny T-REX · Chainalysis OFAC Oracle · Elliptic
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 EXECUTIONERC-4626 vault contract — atomic deposit credit + tranche-token mint
L2 CONSENSUSConsensus block-inclusion settles the cash-leg transfer
◆ Enforcement Line — code-enforced at this layer

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

"Wiring subscription funds to a CLO SPV's custody account — capital committed, the investor receives their tranche certificate. In the tokenized variant, both legs settle in the same block."

Investor deposits the cash-leg stablecoin into the pool. The pool smart contract follows the ERC-4626 vault standard and mints a tranche token representing the investor's pro-rata claim on the tranche's cash flows. The capital is now deployed to borrowers through the pool's credit facility.

Cash-leg stablecoin choice is pool-policy-dependent. Circle USDC is the dominant cash-leg stablecoin for institutional tokenized-credit pool subscriptions; Circle EURC, Paxos USDP, and PayPal PYUSD fit the same role for euro-denominated and Paxos-issued alternatives. Most institutional pools accept a narrow set of named regulated stablecoins; permissionless pools may accept a broader set including non-regulated stablecoins where the pool's risk policy permits.

L2 CONSENSUS and L3 EXECUTION lit: consensus settles the deposit transaction; the ERC-4626 vault executes the mint atomically with the deposit credit. C10 (operational resilience) applies — smart-contract risk is real: a bug in the waterfall logic could mis-allocate repayments. C14 (consumer protection) applies for retail-accessible pools (rare for institutional private-credit; more common for community-trust-based pools).

Builder note: emit a `Subscribe(investor, tranche, amount, tokensMinted, blockNum)` event per subscription so downstream tax-reporting, NAV-tracking, and AUM-attribution systems can index by epoch without re-deriving from raw token transfers.

Honesty marker: ERC-4626 vault audits (Trail of Bits, OpenZeppelin, ConsenSys Diligence, ChainSecurity, Spearbit, Code4rena patterns) cover the code at a moment in time — they do not guarantee that subsequent governance upgrades, oracle changes, or composed-protocol interactions remain bug-free. Audited does not mean unauditable.
Honesty marker: Cash-leg stablecoin solvency, peg maintenance, and address-freeze authority all sit upstream of the pool's compliance posture. A pool depositing USDC trusts Circle to honor redemption, maintain the peg, and not freeze the pool's address; analogous trust assumptions apply to every other regulated stablecoin choice. The pool's compliance is at least as strong as its weakest cash-leg dependency.
Counterparty
Pool smart contract (ERC-4626 vault pattern)
Latency
~12s · single Ethereum block · atomic deposit + mint
Finality
Capital deployed · tranche token minted · `Subscribe` event emitted
Cadence
Per subscription event · idempotent (no batching at the pool-vault layer)
Vendors
Circle USDC · Circle EURC · Paxos USDP · PayPal PYUSD · OpenZeppelin (ERC-4626 reference) · Solmate (gas-optimized ERC-4626) · Trail of Bits (vault audit pattern)
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 EXECUTIONWaterfall contract — priority-ordered distribution executes per repayment event
◆ Enforcement Line — code-enforced at this layer

Step 4 · Repayment Waterfall & MonitoringCode-EnforcedINGESTDETECTALERT

"A CLO trustee distributing monthly cash flows according to the waterfall — senior tranches paid first, then mezzanine, then equity gets the residual (if any). In the tokenized variant, the trustee's discretion is replaced by smart-contract logic that runs every block."

Borrower repayments flow through the smart-contract waterfall. Senior tranche holders receive their yield first, then mezzanine, then junior/equity absorbs the residual. If a borrower defaults, the junior tranche absorbs losses first. The waterfall executes automatically with no trustee discretion at the distribution layer.

L3 EXECUTION lit: the waterfall is pure smart-contract logic. C9 (prudential) applies to the pool operator's credit monitoring; recordkeeping (C11) attaches to the pool's distribution events with retention floors under SEC Rule 17a-4 (17 C.F.R. § 240.17a-4) and the parallel adviser-side IAA §204 (17 C.F.R. § 275.204-2).

Risk Retention Rules / Reg RR (17 C.F.R. § 246) cash-flow horizontal-strip retention is re-verified at each distribution event — the pool operator's required ≥5% retention under Dodd-Frank §941 must remain unbroken across the life of the pool [VERIFY: framework not yet authored in compliance/registries/frameworks/].

Credit-quality signals in the tokenized-pool world come from a different stack than the traditional CLO ratings tower. On-chain transparency provides real-time NAV, delinquency state, and portfolio composition; DeFi-native credit oracles — Credora and RWA.xyz are the most-cited names [VERIFY current production status] — produce credit-attribute attestations that token holders consume directly. NRSRO ratings (S&P, Moody's, Fitch) are largely absent from the tokenized-pool segment as of early 2026, even where the pool size would warrant them in traditional finance.

Capital Structure / Waterfall
01Pool operator feesServicing, management, and platform fees taken from gross repayments before tranche distributions begin.
02Senior tranche interestLowest yield, highest payment priority. Senior token holders receive their coupon before any junior-tranche distribution begins.
03Senior tranche principal (during amortization)During the principal-repayment period, scheduled senior amortization runs ahead of junior distributions.
04Mezzanine tranche interestMid-tier yield. Mezzanine holders paid only after senior interest and principal obligations are met for the period.
05Junior / equity residualWhatever remains after all senior obligations. First-loss position — absorbs losses before any senior tranche if a borrower defaults.
Honesty marker: Pure-DeFi structured-credit pools have no trustee with fiduciary duties, no rating agency, and no independent credit assessment in the NRSRO sense. Credit-quality signals come from on-chain transparency and DeFi-native credit oracles rather than from S&P / Moody's / Fitch — a structurally different governance pattern, not a strictly inferior one.
Honesty marker: On-chain default workout and recovery is immature. The waterfall contract executes distribution logic automatically each repayment cycle, but legal recovery against defaulted borrowers happens off-chain through traditional commercial-recovery channels — restructuring negotiations, judgment enforcement, asset seizure — on traditional timelines (months to years). The on-chain transparency does not eliminate the off-chain workout process.
Counterparty
Pool waterfall contract
Latency
Continuous · per repayment event · waterfall execution within single block
Finality
Distribution confirmed · token-holder balances updated · `Distribution` event emitted
Cadence
Per repayment event · monthly accounting cycle for off-chain reporting · annual audit cycle for institutional pools
Vendors
Centrifuge · Maple Finance · Goldfinch · Credora (DeFi credit oracle) · RWA.xyz (DeFi data aggregator) · Steakhouse Financial (institutional pool monitoring) · DeFi Llama (TVL aggregation)
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 APPLICATIONSEC-registered ATS venue (Securitize Markets · Prometheum · INX · tZERO · OnChain Markets pattern) + tax-reporting application
L4 ACCOUNTToken-holder account ↔ transfer-agent master register update on redemption or transfer

Step 5 · Exit / MaturityPolicy-Enforced

"A CLO reaching its maturity date — principal returned, final distributions calculated, the fund winds down. Or, mid-life, an investor selling a tranche position to a counterparty on the secondary market."

Two exit modes. Scheduled maturity returns principal according to the waterfall; the SEC-registered transfer agent updates the master register to reflect the redemption. Secondary-market sale, mid-life, requires that the tranche token be transferable on an SEC-registered ATS under Reg ATS Rule 301 (17 C.F.R. § 242.301) — Securitize Markets is the dominant venue as of early 2026 [VERIFY current market share]; Prometheum, INX Securities, tZERO, and OnChain Markets operate the same venue category.

L4 ACCOUNT and L5 APPLICATION lit: exit is policy-enforced. The transfer agent's master-register update is the legal record of redemption; the ATS venue's recordkeeping is the legal record of the secondary trade. The on-chain burn (for redemption) or transfer (for secondary sale) is the technical execution, but the binding legal artifacts sit at L4 and L5.

Tax reporting (C12) applies on realized yield. US persons are subject to IRS §6045 cost-basis reporting at the broker-dealer or ATS level; EU intermediaries are subject to DAC7 (digital-platform reporting) and DAC8 (crypto-asset reporting) propagating to the investor's tax residence. Recordkeeping retention floors apply across multiple regimes simultaneously: SEC Rule 17a-4 (17 C.F.R. § 240.17a-4) for the broker-dealer side, Reg ATS Rule 303 (17 C.F.R. § 242.303) for the ATS side, IAA §204 (17 C.F.R. § 275.204-2) for the adviser side.

For cross-border investors the reporting overlap can be material. A US-resident investor exiting a Cayman-domiciled tokenized-pool position via an EU-registered ATS may produce reportable events under §6045 (US), DAC8 (EU), and the Cayman fund-vehicle's own AML reporting simultaneously. Pool operators typically address this in the offering documents but the per-investor reconciliation is non-trivial.

Honesty marker: The broader DeFi structured-credit pool category has experienced material defaults [VERIFY current default history per pool — including community-trust-based pools and direct-lending pools]. The compliance framework — credit committee governance, default recovery, investor communication — remains less mature than traditional structured finance.
Honesty marker: Secondary-market exit via Reg ATS-registered venue is theoretically available but practically thin. Most tokenized-credit tranche tokens show minimal secondary volume as of early 2026; investors should plan to hold to maturity and treat secondary liquidity as opportunistic rather than reliable. The bid/offer spreads on the venues that do quote tokenized-credit tranches are wider than the equivalent traditional secondary-market spreads, reflecting both the thin order books and the per-tranche identity-verification overhead at the venue level.
Counterparty
Pool operator (maturity exit) · SEC-registered ATS secondary venue (secondary-market exit)
Latency
Variable · maturity-dependent for scheduled exit · T+0 to T+2 for ATS secondary trade
Finality
Final · principal and accumulated yield distributed · master register reflects exit
Cadence
Once per investor at maturity · ad-hoc per secondary-market event · annual tax-reporting cycle for the position
Vendors
Securitize Markets · Prometheum · INX Securities · tZERO · OnChain Markets · Lukka (institutional crypto tax reporting) · CoinTracker (retail tax-reporting pattern)
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 Securities Trading Paths

SETTLEMENT CHAINS