> For the complete documentation index, see [llms.txt](https://scorum.gitbook.io/scorum-network-2.0-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://scorum.gitbook.io/scorum-network-2.0-whitepaper/scorum-products-overview/native-tokens.md).

# Native Tokens

The Scorum ecosystem operates with two primary tokens: Scorum Coin (SCR) and Scorum Power (SP). Both are crucial for the network's functionality, yet they serve distinct purposes.

**Scorum Coin (SCR)** is the native token with a fixed supply of 30 million coins. SCR is integral to the ecosystem, facilitating various interactions such as transfers among users, gameplay in Aviatrix, placing bets on ScorumBet, staking and as the main token for all subsequent projects.

**Scorum Power (SP)** is an internal token necessary for enabling technical interactions between the system's users. It holds a direct and fixed correlation with SCR at a 1:1 ratio, meaning every SP is backed by one SCR, anchoring its value firmly within the ecosystem. SP is also used in the blogging platform for upvotes, incentivizing user engagement and content quality.

Currently, all 30 million tokens are active in circulation over the past six years, having been fully distributed after the token sale in 2018. 

**Token Distribution:**

**User Management:** 50% of the token supply is managed by users, fostering decentralization and community governance.

**Development Fund:** 25% of tokens are allocated to a development fund, ensuring sustained growth and innovation within the ecosystem.

**Inactive Tokens:** 25% of the token supply is currently held in accounts that have not been accessed for an extended period. 

A key feature of SCR transactions within the Scorum ecosystem is their fee-free nature, promoting an efficient and cost-effective environment for all forms of digital engagement.

Currently, [SCR coin is traded on the decentralized crypto exchange Osmosis](https://app.osmosis.zone/assets/SCR).

<br>


---

# 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://scorum.gitbook.io/scorum-network-2.0-whitepaper/scorum-products-overview/native-tokens.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.