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

# Community

Where to follow the project, contribute to the code and get in touch.

### Channels

| Channel  | Link                                                                                 |
| -------- | ------------------------------------------------------------------------------------ |
| LinkedIn | [linkedin.com/company/t-rex-network](https://www.linkedin.com/company/t-rex-network) |
| X        | [x.com/trex\_network](https://x.com/trex_network)                                    |
| Telegram | [t.me/TREXNetwork](https://t.me/TREXNetwork)                                         |
| Discord  | [discord.gg/k5B3NdhwQH](https://discord.gg/k5B3NdhwQH)                               |

### Code

| Repository                                                            | Content                                                      |
| --------------------------------------------------------------------- | ------------------------------------------------------------ |
| [T-REX-Network/T-REX](https://github.com/T-REX-Network/T-REX)         | The token suite, the compliance and the cross-chain endpoint |
| [T-REX-Network/ONCHAINID](https://github.com/T-REX-Network/ONCHAINID) | The identity layer                                           |

* **Questions and bugs.** Open an issue on the repository concerned. For a security finding, use the address in [Security](/resources/security.md) and no public issue.
* **Contributions.** Pull requests are welcome. The T-REX repository describes the process in its `CONTRIBUTING.md`. Both codebases are GPL-3.0.
* **A first step.** The [Quickstart](/build/quickstart.md) builds the code and runs the tests.

### The standard

ERC-3643 is maintained by the ERC-3643 Association, which gathers the institutions and the builders that use the standard. The specification is [EIP-3643](https://eips.ethereum.org/EIPS/eip-3643). How T-REX relates to it is in [T-REX and ERC-3643](/the-primary-register/t-rex-and-erc-3643.md).

### Build on the protocol

| You build                                              | Start with                                                                           |
| ------------------------------------------------------ | ------------------------------------------------------------------------------------ |
| A wallet, a custody service, a venue or an application | The [Build](/build.md) section                                                       |
| An application to list in the AppStore                 | [T-REX AppStore](/appstore.md), then write to <contact@t-rex.network>                |
| A gateway adapter for a messaging provider             | [Build an ERC-7786 gateway adapter](/build/build-an-erc-7786-gateway-adapter.md)     |
| T-REX Lite on a new chain                              | [Implement T-REX Lite on a new chain](/build/implement-t-rex-lite-on-a-new-chain.md) |

### Contact

| For                                | Reach                                   |
| ---------------------------------- | --------------------------------------- |
| The T-REX Network                  | [t-rex.network](https://t-rex.network/) |
| General questions and partnerships | <contact@t-rex.network>                 |
| Security findings                  | <security@t-rex.network>                |


---

# 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/community.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.