# The Reward & Compete Principle

Since the goal of the Trac Network is to become the fastest finalizing Crypto network, it is of upmost importance that validators and app deployers provide sufficient performance:

* Their nodes must have as little downtimes as possible.
* Their network connectivity must be sufficient.

To achieve this, the rewards are generous but are only granted under the rules of competition:

* Apps & users may choose validators individually if necessary to get transactions validated.
  * This is akin to broadcast transactions into the Mempool of specific mining pools of Bitcoin for example.
  * Leads to validators trying to achieve the best performance and compete with each other over availability and quality.
  * Individual license identities can be grouped into pools, opening market opportunities for validator pools.
  * ⇒ Creates an open and fair validator-to-user (b2c) market.
* Validators may decide to help validating an app network and compete with each other over the most successful apps for earning additional rewards.
* App deployers may ask the best validators to help validating their apps in return for further rewards.
* ⇒ Creates an open validator-to-deployer (b2b) market and unlocks more incentives.
* Users may choose an app over their overall availability and quality, as well and contribute heavily to the success of an app.
* ⇒ Creates a true consumer market on app level (b2c).


---

# 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/trac-network/the-reward-and-compete-principle.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.