> For the complete documentation index, see [llms.txt](https://cascadia.gitbook.io/gitbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cascadia.gitbook.io/gitbook/governance/analytics.md).

# Analytics

| CC Purchase Record           | Amount of CC acquired by the wallet.  |
| ---------------------------- | ------------------------------------- |
| CC Sales Record              | Amount of CC offloaded by the wallet. |
| User's bCC Balance           | Current bCC holding of a user.        |
| Cooldown Commencement        | When a user started their cooldown.   |
| CC Stake Withdrawal Activity | When a user withdrew their staked CC. |
| Wallet's Bonding Volume      | Total bonded by the wallet.           |
| cCC Redemption Volume        | cCC the wallet has converted.         |
| Pending cCC Redemption       | cCC yet to be redeemed by the wallet. |
| Inbound CC Transfer Volume   | CC received by this wallet.           |
| Outbound CC Transfer Volume  | CC sent from this wallet.             |
| Wallet's Lifespan            | Duration since wallet's creation.     |
| Current Wallet Balance       | Existing balance of the wallet.       |
| Ethereum Bridge Volume       | Amount transferred from Ethereum.     |
| Airdrop Claim Volume         | Airdrops claimed by this wallet.      |

**Social Metrics**

| Discord Membership Date   | When the individual joined the Discord. |
| ------------------------- | --------------------------------------- |
| Duration as a Contributor | Time frame of active contribution.      |

Below, there are analytics a user can search to find more information, based on:

**Age:** This category includes all wallets that have created any transaction on-chain. The ranking system is calculated based on age, determined by the first wallet transaction.

**CC:** This category ranks all wallets based on the amount of CC they've transferred on-chain. If a user receives CC, the ranking increases.

**ccBalance:** This category shows the ranking of wallets based on their current CC balance. A higher balance results in a higher ranking score.

**cccClaim:** This category shows the ranking of wallets based on the amount of cCC claims. A higher cCC claim results in a higher score.

**cccClaimable:** This category shows the ranking of wallets based on the amount of cCC claimable balances (cCC that can be claimed but hasn't been yet). A higher claimable balance results in a higher score.

**Cooldown:** This category shows the ranking of wallets based on the time passed since their Cooldown Start action on the bCC contract. Recently started cooldowns result in a higher score.

**bCC Balance:** This category shows the ranking of wallets based on their current bCC balance. A higher balance results in a higher ranking score.

**ValidatorTokens:** This category shows the ranking of validators based on their token balances. A higher balance results in a higher ranking score.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://cascadia.gitbook.io/gitbook/governance/analytics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.