Issuance & Redemption

Ondo USDY Treasury Note

Tokenized Treasury note — yield-bearing, general access, 40-50 day settlement window reveals securities nature.

Vendors

Ondo Finance

Compliance center

40-50 day settlement window at Negotiation — the securities tell

issuanceusdyondoyieldtokenized-treasurysettlement-window
Filter by shape:
|
I5 · ISSUANCEOndo USDY issuance·5 stations(2 compliance, 3 infra)·ondo
S1INTENTS2S3DISCOVERYS4NEGOTIATIONS5TRANSPORTS6S7FACILITATIONS801Subscription02KYC03Reg D Gate04Mint05Self-Custody
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 Ondo USDY issuance 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.
2 code-enforced3 policy-enforced
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L5 APPLICATIONCUSTODIAN
L4 ACCOUNTCUSTODIAN

Step 1 · Investor OnboardingPolicy-Enforced

"The investor's identity verification — KYC/AML completed and geographic restrictions enforced."

Investor initiates USDY subscription via Ondo platform. L5 Application (Ondo UI) and L4 Account (Ondo compliance engine) are lit. KYC (D1) and sanctions screening (D2) verified at onboarding. US persons are screened out per Reg S — this is a non-US offering. Enforcement is policy-driven: Ondo's compliance team gates the subscription.

Counterparty
Ondo Finance Inc (issuer)
Latency
Minutes to hours · KYC/AML verification
Finality
Investor verified — ready for subscription
Vendors
MetaMask · MetaMask Institutional (ConsenSys-operated; institutional custody/MPC integrations) · Fireblocks · Safe (Gnosis Safe — multisig + module framework) · 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) · 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 ACCOUNTSource of funds verification

Step 2 · Subscription & USD DepositPolicy-EnforcedINGESTDETECTALERT

"The deposit instruction — investor commits USD and Ondo verifies source of funds."

Investor deposits USD via bank wire to Ondo's custodian account. Ondo verifies the source of funds (D1 — identity continuity) and confirms that the investor is not a blocked party. Money transmission licensing (D8) is active here — the deposit is not yet deployed. This step is policy-enforced because source verification relies on bank documentation review.

Counterparty
Investor's bank + Ankura Trust (custodian)
Latency
1-3 days · bank wire settlement + verification
Finality
USD received and sourced — awaiting settlement
Vendors
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 EXECUTIONSecurities deployment

Step 3 · 40-50 Day Settlement WindowPolicy-EnforcedINGESTDETECTALERT

"The securities tell — the 40-50 day window is the compliance admission that USDY is a security, not a stablecoin."

Ondo deploys the collected USD into short-term US Treasuries and bank deposits. The 40-50 day settlement window is the load-bearing compliance fact: a stablecoin settles instantly. A 40-50 day window means the instrument is going through a securities offering process. This window satisfies Reg S seasoning: the securities vest after 40 days, US persons are permanently locked out. Prudential requirements (D9) and consumer protection (D14) fire during deployment. Enforcement is policy-driven: Ondo's treasury management team executes the deployment.

Counterparty
US Treasury market + deposit banks
Latency
40-50 days · securities settlement
Finality
NAV calculated — tokens pending issuance
Vendors
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 EXECUTIONMINT
L2 CONSENSUSMINT
◆ Enforcement Line — code-enforced at this layer

Step 4 · Token Mint + Transfer RestrictionsCode-Enforced

"The issuance event — USDY tokens are minted and transfer restrictions are code-enforced."

After the 40-50 day settlement window, USDY is minted to the verified investor's address on-chain (multi-chain: Ethereum, Solana, Mantle, Sui, Aptos). L3 Execution (mint contract) and L2 Consensus (chain block inclusion) are lit. The mint contract enforces transfer restrictions (D8 — money transmission gate, D14 — consumer protection): blocked addresses and geographic restrictions are hardcoded. Two versions available: rUSDY (rebasing, yield accrues automatically) and USDY (non-rebasing, manual claim). Enforcement is code-enforced: the restrictions are in the smart contract.

Counterparty
Ondo USDY mint contract (multi-chain)
Latency
~12-30s · varies by chain
Finality
Final on chain block confirmation
Vendors
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) · 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 APPLICATIONWALLET
L4 ACCOUNTWALLET
◆ Enforcement Line — code-enforced at this layer

Step 5 · Investor Wallet (Yield-Accruing)Code-Enforced

"The investor's updated balance — USDY received and accruing daily yield (~4.5% APY)."

Newly minted USDY arrives in the investor's verified wallet on-chain. L4 Account and L5 Application lit. Unlike USDC/USDT (non-yield stablecoins), USDY accrues daily yield in the background. rUSDY (rebasing version) balance increases daily; USDY (non-rebasing version) maintains fixed balance, with yield claimable on-demand. Recordkeeping (D11) and tax reporting (D12) obligations fire — each daily yield accrual is a taxable event per US tax law. Yield distribution is on-chain via rebase or claim, entirely code-enforced.

Counterparty
Investor's verified self-custody or custodial wallet
Latency
Instant on mint confirmation
Finality
Final · USDY available for transfer and yield accrual
Vendors
MetaMask · MetaMask Institutional (ConsenSys-operated; institutional custody/MPC integrations) · Fireblocks · Safe (Gnosis Safe — multisig + module framework) · 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) · 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).

TOOL 01 · 14-DIMENSION COMPARISON

Deposit vs Stablecoin Comparator

Side-by-side comparison of tokenized deposits (bank liability) vs stablecoins (reserve-backed) across 14 compliance dimensions.

TOKENIZED DEPOSITSTABLECOIN= relative strength (3 = strong)REGULATORY PERIMETERFDIC Insurance EligibilityIssuer ClassificationBasel Capital TreatmentPrimary Regulatory FrameworkOPERATIONALKYC / OnboardingAML / Transaction MonitoringProgrammabilityCross-Network InteropSETTLEMENTSettlement AvailabilitySettlement FinalityCounterparty RiskRISK & ACCESSRedemption ModelTransaction PrivacyAccess Model

Other Issuance & Redemption Paths

SETTLEMENT CHAINS