Notice · 6 November 2026
Whitepaper v3.3 and Flow v1.1 have been withdrawn and are being revised. Earlier editions described a platform token mechanism; T3RRA Ltd has withdrawn that mechanism and has no token. Revised editions will be published here.
Two papers. Eight theorems. Twenty-two specification sections.
The technical canon — two papers covering the foundation-governed L3RS-1 standard, its cryptographic implementation, and the architecture. Published, dated, versioned, and citable. Architecture first if you only read one.
Canon last updated: November 2026.
55 pages. Read the math.
Cryptographic Specification rev B
PG[Σ], CGM, route admissibility, certificate unforgeability — with theorems.
Twenty-two sections. Eight 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.
Cite as: L3RS Foundation, Crypto Spec v1.0 rev B, 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 first if you want to understand how the five primitives fit together before diving into the formal specification.
Cite as: T3RRA Research, Architecture v1.1, April 2026
Reading order, by who you are.
Asset Owner
Architecture → L3RS-1 chapters of the Crypto Spec (§3–§5)
~30 pages, ~1 hour
Investor (Allocator)
Architecture
Stop there unless you want the cryptographic detail.
17 pages, ~30 minutes
Bank / Institution
Architecture → Crypto Spec (§3–§6, §10–§11)
~40 pages, ~2 hours
Regulator / Supervisor
Crypto Spec (§3–§6, §10–§11) → Architecture
~40 pages, ~2 hours
Builder
Crypto Spec → Architecture
Bring coffee.
55 pages, ~4 hours
Academic
Crypto Spec → Open Problems (§15 of Crypto Spec) → bibliography
~40 pages and three weeks of follow-up reading
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}
}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 settlement layer built on L3RS-1. L3RS-1 is the foundation-governed open standard authored by Zurab Ashvil and stewarded by the L3RS Foundation.
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.
What we got wrong, and when we fixed it.
| Date | Where | Correction |
|---|---|---|
| 2026-04-02 | Crypto Spec §6.4 | Tightened the binding lemma statement to match the proof in Appendix B. No change to the theorem. |
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 →