# Denomination

**CC** is our native token, used for all major transactions and interactions in Cascadia. It also plays a crucial role in the blockchain's overall structure and governance.

**bCC** is our governance token, obtained by those who align their CC tokens. Holders of bCC gain the right to vote on key decisions in Cascadia's network.

{% hint style="info" %}
Our bCC contract is written in Vyper v0.2.7, hence, free from the malfunctioning reentrancy locks issue known in Vyper v0.2.15, v0.2.16, and v0.3.0. \
For more details, see [Vyper's tweet](https://twitter.com/vyperlang/status/1685692973051498497).
{% endhint %}

**tCC** is our testnet token, utilized to ensure Cascadia's robustness and reliability through various testing processes prior to mainnet operations.

**aCC** is the smallest denomination of Cascadia's native token used for micro-level transactions.

{% hint style="info" %}
Unlike the *u* (micro) denotation, Cascadia utilizes *a* to signify micro-level transactions, promoting increased precision and system adaptability.
{% endhint %}

**Atto** is a unit prefix in the metric system. It denotes a factor of 10^-18, or one quintillionth. This means that 1 CC can be divided into 1 quintillion (1,000,000,000,000,000,000) aCC.

**Why it matters:** The use of 'atto-' allows for a high degree of precision in transactions involving CC. This precision is essential for certain applications that might require operations with minuscule amounts of tokens.


---

# 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://cascadia.gitbook.io/gitbook/network/denomination.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.