> 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/resources/deployments.md).

# Deployments

This page lists the addresses of the protocol contracts on each network, and how to verify them from the chain itself.

> **Placeholder.** No address is published on this page at this time. The tables below show the contracts a network deployment contains.

### Network contracts

One deployment of each per network. Every asset and every identity of the network uses them.

#### Token suite

| Contract                              | Address   |
| ------------------------------------- | --------- |
| `TREXFactory`                         | `[[TBC]]` |
| `TREXImplementationAuthority`         | `[[TBC]]` |
| `TrustedGatewayRegistry`              | `[[TBC]]` |
| Access manager of the network         | `[[TBC]]` |
| `UtilityChecker` (proxy)              | `[[TBC]]` |
| `MaxBalancePerIdentityModule` (proxy) | `[[TBC]]` |
| `SpenderVerificationModule` (proxy)   | `[[TBC]]` |
| `SpenderWhitelistModule` (proxy)      | `[[TBC]]` |

#### Identity suite

| Contract                 | Address   |
| ------------------------ | --------- |
| `IdentityFactory`        | `[[TBC]]` |
| Beacon of the identities | `[[TBC]]` |
| `ERC734Validator`        | `[[TBC]]` |
| `KeyApprovalModule`      | `[[TBC]]` |
| `RecoveryModule`         | `[[TBC]]` |
| `ReputationRegistry`     | `[[TBC]]` |
| `EASClaimIssuer`         | `[[TBC]]` |

#### Gateways

| Messaging provider | Gateway adapter | Address   |
| ------------------ | --------------- | --------- |
| `[[TBC]]`          | `[[TBC]]`       | `[[TBC]]` |

### Contracts of an asset

The contracts of an asset are not listed here: each Issuer deploys its own suite. From the address of a token, every other address is read on-chain.

| Contract                         | Read                                                  |
| -------------------------------- | ----------------------------------------------------- |
| Registry                         | `Token.identityRegistry()`                            |
| Compliance                       | `Token.compliance()`                                  |
| Identity storage                 | `TREXRegistry.identityStorage()`                      |
| Access manager of the suite      | `Token.authority()`                                   |
| ONCHAINID of the asset           | `Token.onchainID()`                                   |
| Modules of the compliance        | `ModularCompliance.getModules()`                      |
| Gateway and peer for a satellite | `Token.routeFor(chainKey)`, `Token.peerFor(chainKey)` |

`TREXFactory.getToken(salt)` returns the token deployed with a salt, and the event `TREXSuiteDeployed` lists the contracts of each suite.

### Verify an address

An address published here can be checked against the contracts themselves.

| Check                                                   | Read                                                                                        |
| ------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
| The factory points at the published contracts           | `TREXFactory.getImplementationAuthority()`, `getIdFactory()`, `getTrustedGatewayRegistry()` |
| A token reads the published gateway registry            | `Token.trustedGatewayRegistry()`                                                            |
| A registry reads the published identity factory         | `TREXRegistry.identityFactory()`                                                            |
| An identity uses the published key registry and factory | `Identity.registryModule()`, `Identity.identityFactory()`                                   |
| The beacon of the identities                            | `IdentityFactory.beacon()`                                                                  |
| The version a shared suite runs                         | `TREXImplementationAuthority.currentVersion()`, `implementations()`                         |
| A gateway is trusted                                    | `TrustedGatewayRegistry.isTrusted(gateway)`                                                 |


---

# 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/resources/deployments.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.