Skip to content

LibraryStorage and networks2021Design paperCorpus record

T-REX - Token for Regulated EXchanges

ERC 3643. Joachim Lebrun , Tony Malghem , Kevin Thizy , Luc Falempin , Adam Boudjemaa.

ERC 3643, T-REX - Token for Regulated EXchanges. The T-REX token is an institutional grade security token standard.

Status in the source: Final. A reading of the public specification, not a copy of it and not a certification.

T-REX - Token for Regulated EXchanges is worth reading for the rule it actually adds: The T-REX token is an institutional grade security token standard.

The five-minute read

The rule

The T-REX token is an institutional grade security token standard.

What was already failing

A node that cannot fetch, filter, or relay the data it is supposed to validate is not a peer of the network the paper describes.

What the number does not mean

The source marks this final. That is a statement about the text, not a promise that every wallet or node has shipped it.

What a builder should be able to point at

An implementation either constrains REX or it is a different design.

One action, walked through

  1. Open ERC 3643 and read the status line before the examples.
  2. Write down the rule in one sentence. A fair version of that sentence is: The T-REX token is an institutional grade security token standard.
  3. Name the object that changes: REX.
  4. Ask what an old client, an old contract, or an offline counterparty does. If the document is silent, the silence is part of the design.

The argument, unpacked

What the text is allowed to settle

Ethereum Request for Comment 3643 can settle the shape of T-REX - Token for Regulated EXchanges. It cannot settle whether a later client, a later fork, or a later wallet still does this.

What this page will not pretend

There is no benchmark, no adoption number, and no claim that the mechanism is safe outside the assumptions written in the source.

What has to be true

  • You are implementing ERC 3643 at the status the text itself states: Final.
  • The object that has to change is REX. A neighbouring document with a similar name is not this one.
  • Measurements of delay in one year do not travel with the specification.

What happened after the paper

The source marks this final. That is a statement about the text, not a promise that every wallet or node has shipped it. Later documents can narrow, replace, or ignore this one. Cite the number you mean.

What to check before you use the idea

  • Which message does T-REX - Token for Regulated EXchanges add, and which old peer must still be answered?
  • What does a node do when the short form fails and the full object is required?
  • Which names are normative: REX?

Terms

ERC 3643
The public text titled T-REX - Token for Regulated EXchanges.
Final
The document's own label for how finished the text is. It is not a market fact.

The problem the paper names

A node that cannot fetch, filter, or relay the data it is supposed to validate is not a peer of the network the paper describes.

What the design proposes

  • The T-REX token is an institutional grade security token standard.
  • This standard provides a library of interfaces for the management and compliant transfer of security tokens, using an automated onchain validator system leveraging onchain identities for eligibility checks.
  • The standard defines several interfaces that are described hereunder: - Token - Identity Registry - Identity Registry Storage - Compliance - Trusted Issuers Registry - Claim Topics Registry The advent of blockchain technology has brought about a new era of efficiency, accessibility, and liquidity in the world of asset transfer.

How the mechanism is specified

  • Taken from the specification, the next constraint is: This standard provides a library of interfaces for the management and compliant transfer of security tokens, using an automated onchain validator system leveraging onchain identities for eligibility checks.
  • Locate REX in ERC 3643 and apply it to one transaction or call.
  • Then check the failure the class of rule always has: a node that did not upgrade, a reverted call, a replayed signature, or a peer that does not speak the message.

What this page does not treat as proven

  • A peer protocol is not a consensus rule. A peer can disconnect. A block is still valid or not on its own.
  • Measurements of delay in one year do not travel with the specification.
  • The source marks this final. That is a statement about the text, not a promise that every wallet or node has shipped it.

Why a venture studio still reads it

Use ERC 3643 when a pitch says 'T-REX - Token for Regulated EXchanges' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.

This is Blockchain Lab's reading of a public design paper. It is not the paper, not a copy of it, and not an offer of tokens, equity, custody or a partnership. Later network behaviour can diverge from the text. Nothing here is investment, legal or technical advice.

Research status: Design paper. Last reviewed: 1 October 2026. This is a reading of a public paper, not investment, legal or security advice.