# Utility token

Cetra will use two tokens:

* `$CTR` - ERC20 governance token of the protocol
* `$veCTR` - vote-escrowed token with utility features

`$CTR` will be used for rewarding chambers investors. `$CTR` holders will be able to lock their tokens for chosen amount of time and recieve `$veCTR` in exchange. The longer the time, the higher the voting power.

## ve(3,3), bribes and liquidity markets

Chambers investors receive `$CTR` emissions, and `$veCTR` lockers receive protocol fees, bribes, and voting power.

<figure><img src="/files/m1pSsjrg6LJjicqVFzNf" alt=""><figcaption></figcaption></figure>

We believe this model can open new opportunities for protocols bootstrapping liquidity in their token's pools. Instead of making liquidity mining programs, associated with high selling pressure, they can:

* Apply for adding their token to Cetra's borrowing market
* Lend their token to liquidity providers
* Vote with `$veCTR` or simply bribe corresponding chamber

After that investors will be able to safely provide liquidity to new protocols' pools, making it tradable without having exposure to volatile tokens.

This solves multiple problems of investors and protocols:

* Investors don't need no more to have exposure to risky long-tail assets\
  \&#xNAN;*Not only tokens themselves are risky, but liquidity-mining programs are usually associated with high selling pressure.*
* Protocols don't want to make expensive liquidity-mining programs\
  \&#xNAN;*Protocols can pay less rewards, as the required action is much safer for investor.*<br>


---

# 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://cetra.gitbook.io/welcome/tokenomics/utility-token.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.