> For the complete documentation index, see [llms.txt](https://docs.t-rex.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.t-rex.network/token-and-register.md).

# 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](/token-and-register/the-permissioned-token.md)                                               | The token's surface, what it is wired to, its operations, and its configuration rules.                                                   |
| [The eligibility registry](/token-and-register/the-eligibility-registry.md)                                           | How an address resolves to an identity, local registrations and the global link, required claim topics, trusted issuers, shared storage. |
| [The balance model](/token-and-register/the-balance-model.md)                                                         | Free, frozen and bridged. The two views of a position. Supply. What each movement does to the balances.                                  |
| [The compliance ledger](/token-and-register/the-compliance-ledger.md)                                                 | 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](/token-and-register/modular-compliance.md)                                                       | Rules as modules: the three types, how a rule answers, the modules that ship, binding and removing.                                      |
| [Identity-based control and spender compliance](/token-and-register/identity-based-control-and-spender-compliance.md) | How an identity moves the tokens of its linked wallets, and how a third-party spender is checked.                                        |
| [Lifecycle controls](/token-and-register/lifecycle-controls.md)                                                       | Issuance, redemption, freezes, forced transfers, recovery of a lost wallet, and the pause.                                               |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.t-rex.network/token-and-register.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.