T3RRA
Documents

Five papers. Seven theorems. Twenty-two specification sections.

The full technical canon — five papers covering the foundation-governed L3RS-1 standard, the cryptographic implementation, the liquidity engine, the tokenomics, and the architecture. Published, dated, versioned, and citable. Read in any order. Whitepaper first if you only read one.

Canon last updated: June 2026.

The Canon

158 pages. Read the math.

5 · SETTLEMENTCross-chain certificate · (5,9) committeeArchitecture §4.54 · ROUTINGBest-execution pathfinding (Flow)Flow §23 · EXECUTIONCompliance-gated matching (CGM)Whitepaper §52 · ENFORCEMENTPG[Σ] policy-gated threshold signingWhitepaper §41 · ASSETL3RS-1 v1.0.0 Profile FWhitepaper §3
54 pp · April 2026

Whitepaper v3.3

The full thesis, the five-layer stack, the Agent Mesh, the chain-agnostic vision.

The single document to read first. Covers the category problem, the four moats, the L3RS-1 standard, the PG[Σ] primitive, the CGM mechanism, the Flow router, the cross-chain certificate, and the economic model. Cites the other four papers throughout.

Read PDF

Cite as: T3RRA Research, Whitepaper v3.3, April 2026

38 pp · April 2026

Cryptographic Specification rev B

PG[Σ], CGM, route admissibility, certificate unforgeability — with theorems.

Twenty-two sections. Seven stated theorems with proofs in the appendices. Formal definitions of PolicyHash, ComplianceModule, transcript binding, predicate composition, committee signatures, and atomic DvP. The most-cited document in academic correspondence.

Read PDF

Cite as: L3RS Foundation, Crypto Spec v1.0 rev B, April 2026

27 pp · April 2026

Flow Liquidity Engine v1.1

AI-enhanced, chain-agnostic routing for L3RS-1 assets.

Section 7 defines the route admissibility predicate and proves soundness. Section 15 covers the fourteen named AI capabilities with architecture, training data, ablation, and failure modes. Section 16 covers cross-chain sourcing across the eight launch chains. Section 17 lists the open problems.

Read PDF

Cite as: T3RRA Research, Flow v1.1, April 2026

22 pp · April 2026

Tokenomics v2.1

Total supply, allocation, vesting, the T3RRA Standard Rate Card (§9.1), the MBSR vault, the deflation curve.

Sixteen sections. Defines the protocol token, the fee model, the staking model, the MBSR vault deflation curve, and the governance bounds. Contains zero yield promises and zero token-price discussion.

Read PDF

Cite as: T3RRA Research, Tokenomics v2.1, April 2026

17 pp · April 2026

Architecture v1.1

The master frame — one stack, five layers, one envelope.

The picture-and-paragraph version of the whole protocol. Eleven sections. The right document to read second, after the Whitepaper, if you want to understand how the five primitives fit together before diving into the formal specifications.

Read PDF

Cite as: T3RRA Research, Architecture v1.1, April 2026

Where to Start

Reading order, by who you are.

Asset Owner

Whitepaper → Architecture → L3RS-1 chapters of the Crypto Spec (§3–§5)

~95 pages, ~3 hours

Investor (Allocator)

Whitepaper → Tokenomics → Architecture

Stop there unless you want the cryptographic detail.

~100 pages, ~3 hours

Bank / Institution

Whitepaper → Architecture → Tokenomics → Flow (§7, §15, §16)

~110 pages, ~3.5 hours

Regulator / Supervisor

Whitepaper → Crypto Spec (§3–§6, §10–§11) → Architecture

~80 pages, ~3 hours

Builder

Crypto Spec → Flow → Architecture

Bring coffee.

81 pages, ~5 hours

Academic

Crypto Spec → Flow §15 → Open Problems (§15 of Crypto Spec, §17 of Flow) → bibliography

~70 pages and three weeks of follow-up reading

Versioning

How to cite us.

Every paper carries a version (e.g. v3.2, rev B, v1.0) and a date. We bump the version when we change a theorem statement, add a section, or correct a non-trivial error. Minor typo fixes do not bump the version.

The current versions are listed above. Older versions will be archived when new versions release.

@techreport{l3rs_cryptospec_2026,
  author      = {{L3RS Foundation}},
  title       = {Cryptographic Specification},
  institution = {L3RS Foundation},
  year        = {2026},
  month       = {April},
  type        = {Technical Report},
  number      = {v1.0 rev B},
  url         = {https://www.t3rra.co/docs/T3RRA_CryptoSpec_v1.0_revB.pdf}
}
Issuer of Record

T3RRA LTD.

T3RRA LTD is a private limited company registered in England and Wales, company number 16266973, registered office 5 Stratford Place, London W1C 1AX, United Kingdom. Founded 2025. Operator of a certified Built-on-L3RS-1 implementation. L3RS-1 is the foundation-governed open standard authored by Zurab Ashvil and stewarded by the L3RS Foundation.

Founded 2025Operator · Certified Built-on-L3RS-1 implementation
Reproducibility

A public harness, in progress.

A public reproducibility harness covering the Flow ablation studies, the PG[Σ] verification harness, the CGM strategy-proofness simulator, and the cross-chain certificate test vectors lands in Q3 2026. Every benchmark we publish on this site or in the papers will be reproducible from the harness with one command.

Subscribe for the launch announcement at research@t3rra.co.

Errata

What we got wrong, and when we fixed it.

DateWhereCorrection
2026-04-02Crypto Spec §6.4Tightened the binding lemma statement to match the proof in Appendix B. No change to the theorem.
2026-03-28Flow §15.7Corrected the LSTM forecaster horizon from 5–30 minutes to 5–60 minutes to match the published ablation.
2026-03-15Whitepaper §4Clarified that L3RS-1 Profile F is the institutional profile; Profiles A–E are reserved for future retail and government use cases.

If you find an error in any paper, email research@t3rra.co. We acknowledge within 48 hours and credit the correction here.

Proof Desk

Ask the proofs

Answers come only from T3RRA's published corpus, with citations for substantive supported claims.

Find your path

Routes you to published materials and proof. No advice, eligibility, or personal data.

Answers are drawn only from T3RRA's published corpus. The Proof Desk does not ask for identity, investor status, jurisdiction, wealth, holdings, or mandate information. General site analytics and security logging may apply as described in the Privacy Policy.

For mandate-specific questions, start an originator intake →