# Open Tooling & Roadmap

An open ecosystem cannot rely on black boxes. Every layer of T-Rex is built with transparency and accessibility in mind, so that developers can plug in, extend, and innovate without friction.

All core smart contracts mentioned in this Litepaper (Passport, Badges, Validators) are public, and verified. Anyone can inspect them, audit them, or query them directly. Mainnet and testnet addresses are published openly, ensuring accountability.

<figure><img src="/files/lBklKxmzy8Dw7oGOcVtd" alt="" width="563"><figcaption></figcaption></figure>

To lower the barrier for integration, T-Rex provides SDKs and APIs. The Passport SDK enables DID login and Persona management inside applications. The Badge SDK gives projects the tools to mint and query Badges, design their own credentials, and segment users with precision. These toolkits make it easy for builders to add identity and reputation features without reinventing the wheel.

**The T-Rex ecosystem is designed to grow in phases:**

* In its first phase, the focus is on core on-chain features: Passport resolution, basic Validators, and reputation tags.
* The next phase expands into Web2 integrations and learning credentials, with attestations feeding into Personas.
* The final phase introduces zk-enabled selective disclosure, allowing people to prove sensitive traits without revealing private data, and enabling portability across ecosystems.

This roadmap ensures that the system matures step by step. Developers can build with confidence today, while knowing that new capabilities will continue to enrich the ecosystem tomorrow. By keeping contracts open, SDKs accessible, and evolution predictable, T-Rex makes sure the Value Graph remains a shared foundation for everyone.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://trex-1.gitbook.io/trex/open-ecosystem-and-culture/open-tooling-and-roadmap.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.