T3RRA
For Academia

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.

Why T3RRA

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.

Optionality To Move

The asset is bet on the standard, not on T3RRA the company.

L3RS-1 is an open standard. An L3RS-1 asset carries its ComplianceModule, its route certificate, and its cryptographic envelope as protocol-level objects — not as T3RRA-proprietary database entries. Any L3RS-1-compliant infrastructure can, in principle, service the same asset. No remint. No migration. No restructuring.

The asset is bet on the standard, not on T3RRA the company. Over a long-dated mandate, where conventional tokenization platforms have estimated lock-in migration costs of 1–2% of NAV every seven to ten years, this is genuine optionality.

This is also the answer to the question every sophisticated prospect eventually asks — what happens if T3RRA the company fails? The asset keeps working on the standard. T3RRA becomes safer to bet on than its closed-garden competitors precisely because it does not need to exist for the asset to survive.

Deloitte platform migration cost surveys; internal estimates based on historical tokenization re-platforming events.

Citation

Cite T3RRA in your work.

BibTeX
@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}
}
What You Get

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.

How To Engage

Three steps.

1

Download the canon

Start with the Whitepaper, then the Crypto Spec. The other three are optional reading.

2

Email research@t3rra.co

Tell us what you work on and what caught your interest. We reply to every substantive email.

3

Join the next workshop

We run a quarterly research workshop. Invitations go to active correspondents and collaborators.

FAQ

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