A formal model for compliant tokenized settlement.
The T3RRA canon is five peer-reviewable papers covering the asset standard, cryptographic construction, liquidity model, tokenomics, and system architecture. Seven stated theorems. 164 pages total.
Formal, provable, open.
Formally specified.
PG[Σ] is defined as a policy-gated threshold signing scheme with explicit security reductions. Flow's route admissibility is a predicate you can prove things about. CGM is proven strategy-proof.
Provenance.
L3COS research stream dates to 2013. Participation in the Bank of England CBDC sandbox, 2020. The system has been through multiple production environments before L3RS-1 was published.
Open spec.
L3RS-1 Profile F is published and versioned under CC-BY-4.0. Reviewers welcome. We track errata and respond to all substantive comments.
Five papers. Seven theorems.
Whitepaper v3.3
The complete T3RRA thesis: the five-layer stack, the Agent Mesh, the chain-agnostic vision, and the cryptographic foundations. The single document to read first.
T3RRA Research, "Whitepaper v3.3," April 2026.
Cryptographic Specification rev B
PG[Σ] policy-gated threshold signing, compliance-gated matching, route admissibility, cross-chain certificate unforgeability. Seven stated theorems with proofs in the appendices.
T3RRA Research, "Crypto Spec v1.0 rev B," April 2026.
Flow Liquidity Engine v1.1
AI-enhanced, chain-agnostic routing for L3RS-1 assets. Section 15 covers the fourteen AI capabilities with architecture, training data, ablation, and failure modes.
T3RRA Research, "Flow v1.1," April 2026.
Tokenomics v2.1
Total supply, allocation, vesting, the MBSR vault, and the deflation curve. Sixteen sections, no yield promises, no token-price discussion.
T3RRA Research, "Tokenomics v2.1," April 2026.
Architecture v1.1
The master frame. One stack, five layers, one envelope. The picture-and-paragraph version of how the five primitives fit together.
T3RRA Research, "Architecture v1.1," April 2026.
Cite T3RRA in your work.
@techreport{t3rra2026whitepaper,
author = {{T3RRA Research}},
title = {T3RRA Whitepaper v3.3},
year = {2026},
month = {April},
url = {https://t3rra.co/docs/T3RRA_Whitepaper_v3.3.pdf}
}
@techreport{t3rra2026cryptospec,
author = {{T3RRA Research}},
title = {T3RRA Cryptographic Specification v1.0 rev B},
year = {2026},
month = {April},
url = {https://t3rra.co/docs/T3RRA_CryptoSpec_v1.0_revB.pdf}
}Access and collaboration.
Drafts and errata
Access to pre-publication drafts of future papers and a live errata feed for the existing canon.
Formal verification
Collaboration on EasyCrypt mechanization (Q4 2026) and Tamarin protocol model (Q1 2027).
Workshop track
Invitations to the research workshop track where we present new work and discuss open problems.
Three steps.
Download the canon
Start with the Whitepaper, then the Crypto Spec. The other three are optional reading.
Email research@t3rra.co
Tell us what you work on and what caught your interest. We reply to every substantive email.
Join the next workshop
We run a quarterly research workshop. Invitations go to active correspondents and collaborators.
Common questions.
What is the licensing of the spec?
L3RS-1 Profile F is published under CC-BY-4.0. You may implement, extend, and cite it freely with attribution.
Is the work reproducible?
A public reproducibility harness is planned for Q3 2026. It will include the AI capability benchmarks, the strategy-proofness simulator for CGM, and the PG[Σ] verification harness.
How do I submit comments or corrections?
Email research@t3rra.co with the document name, section number, and your comment. We track all feedback and publish errata.
How does T3RRA relate to existing standards like ERC-3643?
L3RS-1 Profile F is designed to interoperate with ERC-3643 and similar permissioned token standards. The key difference is that compliance in L3RS-1 is a cryptographic primitive, not a contract-level check.
The spec is published. The theorems are stated. Send us your counterexample.
research@t3rra.co
