RWA Cross-Chain Settlement
Tokenized real-world asset trading with cross-chain bridge settlement via Chainlink CCIP.
CTR (USD 10,000+)TRAVEL-RULE (USD 3,000+)ENHANCED-DUE-DILIGENCE (USD 50,000+)
Step 1 · Investor Account (Ethereum)Policy-EnforcedBlockchain-Native
An investor logged into their brokerage account — KYC verified, accreditation confirmed, ready to trade.
Investor wallet on Ethereum holding a tokenized RWA (e.g., Ondo OUSG, Securitize security token). The investor has completed KYC and, for Reg D securities, accredited investor verification. The token itself may carry ERC-3643 transfer restrictions — the wallet address must be whitelisted before receiving or sending. L4+L5 lit: identity and authorization are policy-enforced through the whitelist.
Step 2 · Transfer Restriction CheckCode-EnforcedBlockchain-Native
A transfer agent verifying both parties before executing a stock transfer — the securities equivalent of sanctions screening plus accreditation verification.
The ERC-3643 identity registry checks both sender and receiver addresses. This is more than sanctions screening — it's securities-grade transfer restriction. Both parties must be on the token's whitelist, maintained by the transfer agent (Securitize, Tokeny). L3 Execution lit: the check is code-enforced at the smart contract level. If either party is not whitelisted, the transfer reverts.
Step 3 · Trade Execution (Ethereum)Code-EnforcedBlockchain-Native
Executing a stock trade on a regulated ATS — price discovery, order matching, trade confirmation.
The RWA token trades on a compliant venue (Securitize Markets, INX, tZERO). The trade matches against the order book or executes as a bilateral OTC transaction. L3+L4 lit: execution logic and account state update simultaneously. Market integrity (D13) applies — the venue monitors for manipulation. Unlike DeFi swaps, RWA trades execute on venues with market surveillance obligations.
Step 4 · Cross-Chain Bridge (CCIP)Code-EnforcedBlockchain-Native
Transferring securities between depositories (e.g., DTC to Euroclear) — the security must maintain its regulatory wrapper across the transfer.
The RWA token (or its payment leg in USDC) bridges from Ethereum to Base via Chainlink CCIP. This is the compliance center of gravity: the securities transfer restriction must survive the cross-chain hop. CCIP's programmable token transfers can carry metadata (whitelist status, investor accreditation) across chains, but this is nascent infrastructure. L1+L2+L3 lit — transport runs below the enforcement line. Open question: who enforces the whitelist on the destination chain?
Step 5 · Settlement on Destination ChainCode-EnforcedBlockchain-Native
The DTC's book-entry transfer completing — the security has arrived at the new depository with its regulatory status intact.
The RWA token arrives on Base with transfer restrictions intact (if the ERC-3643 registry is mirrored cross-chain) or needs re-verification (if not). USDC payment settles atomically with the token delivery if DvP is enforced. L3+L4 lit: execution and account layers process the settlement. The transfer agent updates both chain registries.
Step 6 · Post-Trade ReportingPolicy-EnforcedBlockchain-Native
The transfer agent's cap table update and regulatory filing — the trade is recorded, ownership updated, and reporting obligations met.
Settlement is final. The transfer agent (Securitize) updates the cap table across both chains. Regulatory reporting obligations attach — Form D amendments if new investors, tax reporting on realized gains. L5 Application lit only. The cross-chain RWA trade is complete, but the compliance surface is permanently expanded: the token now exists on two chains with two whitelist registries to maintain.
Resolved 6 steps across 2 chain(s). 3 threshold(s) triggered. Frameworks: Bank Secrecy Act, GENIUS Act, OFAC Sanctions Program, FATF Recommendation 16 (Travel Rule), Common Reporting Standard / FATCA.