Doing tokenization #1, Tokenization is an Ecosystem
Tokenization is often described as “putting assets on-chain,” but that framing misses what makes tokenization work in real markets: it is an ecosystem of infrastructure, participants, controls, and incentives-not a single technical act.
Two foundations largely determine whether an RWA/tokenized product can move from a demo to a scaled market:
The two foundations
Settlement layer
Plain definition: A settlement layer is whatever system (or combination of systems) gets you to final settlement - the point at which a transfer is irrevocable and unconditional and is a legally defined moment.
Why this matters: If you cannot say exactly when settlement is final-and which record is authoritative-then token transfers may be technically valid but legally ambiguous (especially under insolvency, disputes, or operational errors). Different tokenized products use different approaches for “the authoritative record of ownership,” and that this can confuse investors and create disputes if not disclosed and governed properly.
Key point: “Settlement layer” is not just “pick an L1.” It includes decisions about:
- Authoritative ledger / register: On-chain is the legal register vs off-chain register with on-chain representation (or a hybrid).
- Finality and insolvency treatment: Your definition of finality has to line up with legal finality (and what happens during participant default).
- Atomicity vs prefunding/netting: Whether you want atomic DvP/PvP (and therefore often require prefunding) or rely on netting and conventional settlement flows.
- Permissioning/privacy constraints: Public-chain transparency can create confidentiality and compliance issues (and pseudonymity complicates KYC), pushing some designs toward permissioned or hybrid rails.
Institutional access
Plain definition: Institutional access is the capability set that lets regulated capital hold, trade, and settle tokenized instruments in a way that satisfies custody/safeguarding, AML/CFT, market integrity, reporting/audit, and operational resilience expectations.
What it includes (minimum viable):
- Custody and safeguarding: Tokens are transferred via private keys managed in wallets; custody risk and operational failure modes differ from conventional markets.
- Onboarding + AML/CFT + sanctions: Public chain pseudonymity can complicate KYC and amplify market integrity risks (e.g., wash trading using multiple addresses).
- Execution venues and regulated channels (where required): Trading for regulated products often needs compliant venue/intermediary paths and surveillance.
- APIs/standards + operational controls: Integration is how institutions participate; fragmentation makes this harder and influences which rails “win.”
Why it’s a gating factor: US regulatory posture can shift quickly in ways that change what institutional architectures are viable. In March 2026, the SEC issued an interpretation clarifying how federal securities laws apply to certain crypto assets and transactions, including a “coherent token taxonomy,” and it explicitly describes when a non-security crypto asset can become (and cease to be) subject to an investment contract.
What regulators keep emphasizing
Credible settlement assets
Lack of credible settlement assets limits scalability of tokenization arrangements.
Without reliable on-chain settlement assets, scaling tokenized markets is difficult because seamless DvP cannot be performed post-trade; Investors may be pushed into less reliable payment media compared with conventional transactions.
This is where “tokenized money” becomes part of the ecosystem: the Financial Stability Board explicitly focuses on tokenized money that may be used as a settlement asset (e.g., commercial bank deposits, wholesale central bank money forms) as part of tokenization’s scaling and risk profile.
Interoperability and integration with existing infrastructure
RWA ecosystem is still nascent, and that interoperability challenges between blockchains result in liquidity fragmentation.
Competing, non-interoperable DLT networks fragment assets and users, lock liquidity across networks, and increase operational and cyber risks-especially when bridges rely on APIs and smart contracts that “lock up” assets.
Why the settlement layer differs by RWA class
Tokenized securities / fund shares: You must specify what the authoritative record is (on-chain vs off-chain register). Example: for BlackRock’s BUIDL, the official record of ownership is maintained in a transfer agent’s off-chain books; whereas Franklin’s on-chain MMF example uses the blockchain as the official record (with recordkeeping details).
Tokenized repo and collateral mobility: Settlement is the product. Tokenization can enable shorter settlement cycles and improved collateral mobility, but also observes that industry experimentation has often focused on infrastructure, issuance, settlement processes, and repo transactions rather than active secondary trading.
Tokenized money / settlement assets: The cash leg defines the safety/finality profile of the whole market. Tokenized money as a potential settlement asset and analyzes vulnerabilities such as liquidity/maturity mismatch, leverage, and operational fragilities that can grow with interconnectedness.
Other ecosystem layers you can add under the two foundations
DeFi protocols for yield and composability
Why it’s important: DeFi provides programmable market primitives-trading, lending/borrowing, and other services-built from composable smart contracts (“money lego”). That matters for tokenization because, once a token exists, DeFi can supply native mechanisms for liquidity, collateralization, and (in some cases) yield generation and financing that complement traditional infrastructure.
Why it already looks remarkably complete: The core DeFi building blocks already exist and are widely used in crypto markets: DEX-style trading, lending platforms, and even insurance-like arrangements, with stablecoins playing a central role in providing liquidity and serving as trading pairs and collateral on DeFi lending/borrowing platforms.
Important caveat: DeFi activities have been mostly self-referential (primarily swapping crypto for crypto, not financing the real economy), so “complete” here means “mature primitives exist,” not “RWA-ready at scale.”
Interoperability
Why it’s important: Without interoperability, tokenized assets end up split across many ledgers and venues. Non-interoperable DLT networks fragment users and assets, lock liquidity, and can undermine the efficiency gains tokenization claims to deliver. Fragmentation also increases operational risk because bridging requires additional linkages (often via APIs and smart contracts) that become attack surfaces.
Why it already looks remarkably complete: Even though interoperability remains a scaling constraint, concrete “bridges” already being built in two directions:
- connectivity between DLT issuance/settlement components and traditional CSD/settlement systems (e.g., the Euroclear D-FMI example), and
- “network of networks” approaches such as Canton and multi-platform initiatives such as GL1 designed to enable transaction/data synchronization with privacy controls and programmable compliance tooling.
Oracles
Why it’s important: Tokenized markets still depend on off-chain facts-prices, NAVs, reference rates, corporate actions, identity/eligibility proofs, and sometimes proof-of-reserves. When smart contracts rely on external price feeds through oracles, that dependency can become a single point of failure or corruption if oracles are manipulated or not auditable.
Why it already looks remarkably complete: Oracles are a well-established part of the crypto ecosystem: they are critical dependencies of many DeFi protocols and errors/manipulation can trigger cascading actions such as liquidations, creating spillovers across protocols. The existence of both mature oracle services and a well-understood risk taxonomy (manipulation, downtime, governance, auditability) is a sign the layer is “built,” even if its governance and assurance models remain a work in progress for regulated RWAs.
Liquidity providers
Why it’s important: Tokenization does not automatically create secondary markets. “Native securities” have shown low secondary market liquidity so far, partly because industry effort has focused on issuance and settlement, not active trading; lacking liquidity then disincentivizes investors from holding tokens for active trading. For funds, secondary markets could support liquidity, collateralization, better price transparency, and reduced information asymmetry-assuming timely, high-quality disclosures.
Why it already looks remarkably complete: On-chain markets have already developed well-defined liquidity mechanisms. Automated market maker (AMM) models as a form of disintermediated liquidity provision via pools where liquidity providers contribute assets and traders trade against the pool. These models bring new trade-offs and potential investor harm/market integrity concerns, so the “completeness” is functional (mechanisms exist) rather than regulatory (acceptance varies).
Risk and compliance management
Why it’s important: Tokenization often increases automation speed and ecosystem interconnectedness-so operational failures propagate faster. Additional risks around data privacy vs transparency (including potential confidentiality breaches and GDPR-style tensions), KYC complications from pseudonymity, and market integrity risks like wash trading enabled by multiple addresses.
Why it already looks remarkably complete: A global compliance baseline for crypto/digital asset market activities is being built out by standard-setters. IOSCO’s 2023 policy recommendations cover governance/conflicts, market manipulation and surveillance, cross-border cooperation, custody/client asset protection, operational/technological risk, and retail distribution-many of the same control families institutions expect in traditional markets.
On the AML side, the Financial Action Task Force continues to track implementation of virtual-asset standards and Travel Rule obligations, emphasizing supervision and cross-border consistency challenges.
For jurisdiction-specific anchoring, note that Singapore’s PSN02 notice (latest version dated 2 April 2024 per MAS publication metadata) explicitly defines AML/CFT requirements for digital payment token services, underscoring that “compliance is infrastructure,” not a bolt-on.
Key recommendations for practitioners
Designing tokenization as an ecosystem becomes simpler if you treat it as a sequence of decisions with explicit “definition of done” criteria.
Start with these three:
Design from legal finality + operating model backward.
First decide what the authoritative register is and what “final settlement” means in your model (legal moment, reversals, recovery under insolvency), then decide whether you need public-chain, permissioned, traditional rails, or a hybrid link.Treat settlement asset strategy as a first-class architecture decision.
Tokenization scaling is constrained by credible settlement assets and that without reliable on-chain settlement assets, seamless DvP is difficult; Tokenized money is a core focus of tokenization’s scaling and risk profile.Implement institutional access as a composable capability set.
Build custody and wallet controls, identity and onboarding, transfer restrictions, surveillance/reporting, and venue connectivity as modular components-because regulatory classification and requirements can change and may force reconfiguration. The March 2026 SEC interpretation is a concrete reminder that “taxonomy” and “what laws apply” can shift quickly and materially alter viable architectures.
