# Developers

The concept of Trac Network allows to create independent subnets. The use of subnets are encouraged if the different use-cases don't require the full validation power of mainnet. This means that using **Release 1** won't return validator rewards in $trac but in turn operate gas-less. Incentives to validate can then be provided from within the different apps that are being developed.

If a developer requires help from existing validators, developers can ask approved validators to secure their subnet. Validators  are pre-approved through licenses and committed to support the entire Trac Network, including subnets.

Due to high TPS and fast transaction finality. **Release 1** is especially equipped to support slower crypto networks. 

**Note:** Developing and releasing apps with **Release 1** will  continue to work post-mainnet release as these are independent subnets.

This gives developers the opportunity to develop several kinds of solutions without waiting for mainnet release. The there are a lot of use-cases that can already be covered but are not limited to:

* **Interoperability Layers**
  * Cross-chain communication
  * Cross-chain marketplaces, staking, lending (DeFi)
  * Real World Asset (RWA) trading
  * Bridges
  * Co-Processing
  * L2-apps
  * Oracles
* **L1s & L2s & Rollups**
  * Create entire crypto infrastructures just on a single Trac Network subnet
* **Chats / Social Networks**
  * Extend the built-in chat features using smart contracts
  * AI agents trigger contract interactions (trading e.g.)
  * Decentralized social networks
* **Content**
  * Buy/sell content (text, sound, video, games)
  * Content rendering (games, websites, books, comics)
  * Content creation (decentralized workgroups)
* **Gaming**
  * Multiplayer games
  * Metaverse experiences
  * In-game/metaverse rewards & marketplaces
* and many more!

What you shouldn't use **Release 1** for is to create token/collectible standards as there is no inter-contract communication implemented yet. This feature will be available in subsequent releases and mainnet.


---

# 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://docs.trac.network/documentation/developers.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.