> For the complete documentation index, see [llms.txt](https://riskguard-1.gitbook.io/riskguard-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://riskguard-1.gitbook.io/riskguard-docs/whitepaper/07-risk-token.md).

# 7. The RISK Token

> RISK is designed as a utility token that aligns the incentives of users, contributors, and the protocols RiskGuard analyzes — not as a speculative instrument.

{% hint style="warning" %}
**Important — forward-looking.** The RISK token has not been issued. It is planned for a later phase, only after the product has an active user base and demonstrated revenue. Token design and timing are subject to change and to legal and regulatory review. Nothing in this section is an offer to sell or a solicitation to buy any token.
{% endhint %}

RiskGuard's product stands entirely on its own without a token. The RISK token is a mechanism layered on top of a working product to align incentives across the ecosystem and to fund continued development in a community-aligned way. Its design deliberately ties every unit of utility to real product usage.

## Token utilities

1. **Subscription discounts** — paying for Pro or Whale plans in RISK confers a meaningful discount versus fiat pricing.
2. **Feature unlocking via staking** — staking RISK unlocks advanced analytics features without a recurring subscription.
3. **B2B API access** — protocols and applications consuming RiskGuard's risk API stake RISK in proportion to their call volume, tying network demand to token demand.
4. **Governance** — token holders vote on which new protocols and chains RiskGuard prioritizes for support.
5. **Contribution rewards** — users earn RISK for valuable contributions such as reporting false positives in detection or scoring, and through referrals.
6. **Priority analysis** — stakers receive more frequent risk re-analysis of their portfolios.

## Distribution

RISK is planned as an SPL token on Solana with a fixed supply of one billion units. The distribution is weighted toward community and product, with founder and treasury allocations subject to extended cliffs and vesting to align long-term incentives.

| Allocation                 | Share | Terms                                    |
| -------------------------- | ----- | ---------------------------------------- |
| Community airdrop          | 27%   | Gradual unlock over 18 months            |
| Product reserve            | 22%   | Reserved for product development         |
| Founders                   | 20%   | 12-month cliff + 36-month linear vesting |
| Grants & partnerships      | 13%   | Ecosystem development                    |
| Treasury / working capital | 10%   | 6-month cliff + 36-month vesting         |
| DEX liquidity              | 8%    | At launch                                |

## Non-custodial staking

All staking is non-custodial and executed through audited smart contracts. RiskGuard reads stake status on-chain to verify entitlements but never takes custody of staked tokens. A third-party security audit is a prerequisite to launch. This architecture is consistent with the product's broader principle: **RiskGuard reads the blockchain, it never holds user funds.**

{% hint style="info" %}
**Sequencing.** The token follows the product, not the other way around. The intended sequence is: mature product → active users → demonstrated revenue → ecosystem grants → token. This ordering protects both the product's credibility and the token's long-term integrity.
{% endhint %}


---

# 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://riskguard-1.gitbook.io/riskguard-docs/whitepaper/07-risk-token.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.