Capital markets for regulated assets, without the old bottlenecks.
Compliant Asset · Geographic Freedom · Roaming Liquidity
Most tokenized assets still fail in three places: compliance depends on vendors, jurisdiction traps the asset where it was issued, and liquidity dies on the first venue that lists it. T3RRA is the settlement layer that fixes all three.
Built by the team that created TICEX, deployed inside the Bank of England's CBDC sandbox in 2020, and wrote the L3RS-1 standard.
L3RS-1 standard · 5 papers · 7 theorems · protocol-level Travel Rule · 8 chains at launch
Tokenized assets exist. Tokenized markets do not.
There are platforms that mint tokens, vendors that handle compliance, custodians that hold keys, and venues that offer partial liquidity. But these layers do not travel together. The result is an asset that exists on-chain yet remains institutionally unusable — trapped on one chain, in one jurisdiction, on one venue, with no path to the liquidity it was built to reach. This is not a technology problem. It is an architecture problem. No one has built the single layer that binds compliance, settlement, and liquidity together — until now.
Read the full diagnosisCoverage & Academic Correspondence
FT · Bloomberg · Reuters · MIT · Stanford · ETH · Imperial · Deloitte · Trail of Bits
Coverage and academic correspondence as of April 2026. Names for context, not endorsement.
One engagement. One rulebook. One settlement layer.
Structured like a deal desk. Settled like a protocol.
Today, bringing a tokenized asset to market means hiring a law firm, a transfer agent, a compliance vendor, a custody provider, and a listing venue — then hoping they all keep working together after launch. T3RRA replaces that entire stack with a single engagement.
We replace the bulge-bracket desk for issuances under USD 500 million.
We structure the deal.
SPVs, legal mapping, investor eligibility, transfer rules, servicing design.
We encode the rules.
Those decisions become part of the asset itself through L3RS-1 and the policy envelope.
We settle the trade.
Matching, routing, and settlement happen without breaking policy continuity.
The only platform on the market that wrote the standard, the structuring layer, and the settlement engine — and runs all three end-to-end.
From structuring call to settled trade.
Scoping
Asset reviewed. Jurisdiction mapped. Structure proposed.
Structuring
SPV formed. Legal opinions drafted. ComplianceModule authored.
Tokenization
L3RS-1 asset minted. Policy and identity bound at the protocol level.
Primary placement
Compliance-gated matching. Investor eligibility verified. Settlement executed.
Secondary trading
Asset listed across eight chains. Flow routes liquidity. Travel Rule holds at every hop.
Lifecycle
Distributions, reporting, corporate actions — all on-chain, all auditable.
Scoping
Asset reviewed. Jurisdiction mapped. Structure proposed.
Structuring
SPV formed. Legal opinions drafted. ComplianceModule authored.
Tokenization
L3RS-1 asset minted. Policy and identity bound at the protocol level.
Primary placement
Compliance-gated matching. Investor eligibility verified. Settlement executed.
Secondary trading
Asset listed across eight chains. Flow routes liquidity. Travel Rule holds at every hop.
Lifecycle
Distributions, reporting, corporate actions — all on-chain, all auditable.
A UK commercial real estate owner wants to issue a $40M revenue-participation note to eligible investors in Singapore and the UAE. T3RRA structures the issuance, binds transfer rules and Travel Rule continuity into the asset, and routes secondary liquidity across multiple chains — without ever losing policy integrity.
Built for issuers who need real capital markets execution.
Any organization with a real-world asset, a real cash flow, or a regulated instrument to bring to market. We have built mandates across every category below.
A Mediterranean shipping operator with twelve tanker SPVs. A Tier-2 bank tokenizing its deposit book. A renewables sponsor wrapping twenty years of hydro cash flows into a milestone-based vault. These are the mandates we have built. The categories below describe who we work with. The deals describe how.
4+
asset classes
3
continents
$100M+
structured
Mandates in execution as of April 2026.
Banks & Regulated Financial Institutions
Tier-2 banks, NBFIs, and trusted issuers running deposit-tokenization, treasury issuance, or custody-integrated regulated digital securities under their own banking licence.
Corporate Issuers
Operating companies raising senior debt, perpetual notes, revenue participation instruments, convertible structures, or hybrid capital — from first structuring call to final settlement.
Private Credit & Direct Lending Funds
Originators looking to fractionalize loan books, free up balance-sheet capacity, or distribute senior tranches to permissioned investor pools.
Infrastructure & Energy Sponsors
Hydropower, renewables, transmission, ports, terminals, toll concessions. Long-duration cash flows wrapped in milestone-based disbursement and revenue assignment.
Also: commodity merchants, royalty holders, agricultural producers, sovereign infrastructure operators, and corporate treasuries. If the asset is real and the rulebook is enforceable, the rails carry it.
Compliance that cannot break. Jurisdiction that does not limit. Liquidity that actually moves.
The three problems every section below is built to solve.
The asset carries its own passport.
The Travel Rule (FATF Recommendation 16) requires that originator and beneficiary identity data accompany every digital-asset transfer above threshold — enforced across every FATF-member jurisdiction. Every existing tokenization platform meets this requirement through a vendor service layer. When the vendor changes jurisdiction or loses a licence, compliance breaks mid-transfer. For an institution holding a large position, a broken compliance chain is not a technical inconvenience. It is a regulatory breach.
Travel Rule data bound at the protocol level
Identity carried across every chain Flow touches
No compliance officer, transfer agent, or service layer in the path
Geographic reach and liquidity depth are not two separate advantages. They are the same advantage, expressed twice. An asset Travel-Rule compliant in every FATF jurisdiction at the protocol level is institutionally eligible everywhere it lands — and where there are more eligible holders, there is deeper liquidity.
The Three Walls
Every regulated asset hits three walls. T3RRA is the only stack built to clear all three.
Compliant Asset
L3RS-1 Standard
Without this: unsellable to regulated capital.
Geographic Freedom
T3RRA Structuring
Without this: stranded in the country it was born in.
Roaming Liquidity
T3RRA Flow
Without this: stranded on whichever venue first lists it.
Everything above is the commercial thesis. Everything below is the proof.
One stack. Five layers. One cryptographic envelope.
Every claim below has a theorem. Every theorem has a paper. Click any card to read the proof.
Asset
Issuer-defined policy travels in the asset itself, not the contract that holds it.
Crypto Spec §3Routing
Routes are first-class objects with admissibility proofs and a learned re-ranker.
Flow §7 + §15Settlement
Five-of-nine threshold with a stated unforgeability theorem and atomicity under partial failure.
Crypto Spec §10–§11One signature. Four guarantees. Zero trust assumptions.
PolicyHash
A canonical hash of the ComplianceModule, recomputed at signing time and bound into the Fiat–Shamir transcript. Tampering with the policy invalidates the signature.
Route Certificate
A signed predicate proof that J ∧ T ∧ ID ∧ X held along every hop. Verifiable in 3 lines of SDK code.
Cross-Chain Certificate
A (5,9) committee signature with a stated unforgeability theorem under arbitrary network adversary. The settlement primitive that lets an L3RS-1 asset roam.
Six AI agents. Every one caged inside the compliance envelope.
Six agent classes — Onboarding, Tokenization, Marketplace, Trade, Liquidity, Treasury — each with a published action set, all caged inside the PG[Σ] envelope.
The fourteen AI capabilities, their architectures, and their published ablation results are detailed in the Flow paper §15 and on the platform page.
L3RS-1 assets roam.
One settlement layer. One compliance envelope. One liquidity pool. Distributed across every chain T3RRA touches.
8 Launch Chains
Roadmap
Five papers. Seven theorems. Zero hand-waving.
Read the math before you decide what to think. Every paper is dated, versioned, and citable.
Whitepaper v3.3
April 2026
The full T3RRA thesis: the five-layer stack, the Agent Mesh, the chain-agnostic vision. The single document to read first.
Read PDFCryptographic Specification rev B
April 2026
PG[Σ], compliance-gated matching, route admissibility, cross-chain certificate. Twenty-two sections, seven theorems, all definitions formal.
Read PDFFlow Liquidity Engine v1.1
April 2026
AI-enhanced, chain-agnostic routing for L3RS-1 assets. Section 15 covers the fourteen AI capabilities; Section 16 covers cross-chain sourcing.
Read PDFTokenomics v2.1
April 2026
Total supply, allocation, vesting, the MBSR vault, and the deflation curve. Sixteen sections, no yield promises.
Read PDFArchitecture v1.1
April 2026
The master frame. One stack, five layers, one envelope. The picture-and-paragraph version of the whole protocol.
Read PDFThe last number is the most important one on this page.
What we will not say.
The most credible thing an RWA website can publish in 2026 is the list of claims it refuses to make.
- 1We will not promise a yield.
- 2We will not name a token price.
- 3We will not show an anonymous endorsement and call it a customer.
- 4We will not call our compliance "robust" without naming the theorem that makes it so.
- 5We will not claim a chain we do not yet support.
- 6We will not invoke a regulator we have not actually spoken to.
- 7We will not redefine "decentralized" to mean whatever is convenient.
- 8We will not publish a benchmark we cannot reproduce on the public harness.
If a claim on this page is not citable to one of our five papers, it is not on this page.
Straight answers.
The questions serious counterparties actually ask.
