The primary register
T-REX is organized around one idea: the on-chain contract holds the register of the asset and enforces it. It is designed to be the primary register, not a copy of a register kept elsewhere. Everything else in the protocol follows from it. The identity layer exists because a register must know its holders. The compliance layer exists because a register must refuse what it may not record. The cross-chain architecture exists because a register must see the whole distribution of the asset.
Whether the on-chain register is also the legal register of a given asset depends on the jurisdiction and on the asset. Where the legal register has to be kept off-chain, it replicates what happens on T-REX. The first page of this section covers both cases.
This section explains the idea and its consequences.
The reconciliation problem, why a token that mirrors an off-chain book does not solve it, what changes when the on-chain record leads, and how that record relates to the legal register.
The functions of a securities depository and the contracts that perform them. Why a register must be global to enforce the rules of a security.
What the standard defines, what T-REX adds around it, and where T-REX narrows it.
What each gate checks, how it decides, and which operations pass through it.
What is final on a satellite, what is recorded on the register, when a transfer is legally final, and how the protocol manages the time in between.
Last updated