Token and register

The token layer is where ownership is recorded and where the rules of an asset are enforced. It is an implementation of ERC-3643, extended with the balance model, the position ledger and the cross-chain accounting that turn a compliant token into the register of a security.

This section describes the token as it exists on the reference chain. How the register reaches other chains is covered under Cross-chain: the distributed register.

A token suite is the set of contracts deployed for one asset.

Contract	Role
Token	The ERC-3643 token. Records positions and runs the two gates before every movement.
TREXRegistry	The eligibility registry. Resolves addresses to identities and decides whether an identity may hold the asset.
IdentityRegistryStorage	Local registrations of addresses, shareable between the tokens of one issuer.
ModularCompliance	The compliance. Applies the rules of the asset, keeps each identity's total position, issues cross-chain validations.
TREXAccessManager	The roles that gate every privileged function of the suite.

Page	What it covers
The permissioned token	The token's surface, what it is wired to, its operations, and its configuration rules.
The eligibility registry	How an address resolves to an identity, local registrations and the global link, required claim topics, trusted issuers, shared storage.
The balance model	Free, frozen and bridged. The two views of a position. Supply. What each movement does to the balances.
The compliance ledger	The position of each identity across all its addresses and chains, the pending amounts, and how the ledger stays equal to the supply.
Modular compliance	Rules as modules: the three types, how a rule answers, the modules that ship, binding and removing.
Identity-based control and spender compliance	How an identity moves the tokens of its linked wallets, and how a third-party spender is checked.
Lifecycle controls	Issuance, redemption, freezes, forced transfers, recovery of a lost wallet, and the pause.