> For the complete documentation index, see [llms.txt](https://phantasma.gitbook.io/main/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://phantasma.gitbook.io/main/about/dual-token-system.md).

# Economy

Phantasma uses two native assets with separate roles: SOUL and KCAL.

SOUL is the staking and governance asset. It is also the data escrow asset used when a transaction grows permanent chain state. KCAL is the resource asset used for transaction execution, VM gas, and block data.

Separating these roles lets users and applications reason about two different costs:

* KCAL is paid for computation, VM execution, and transaction data in blocks.
* SOUL is escrowed when a transaction creates or expands persistent chain state.

Staking SOUL generates claimable KCAL. Users who want network participation can stake SOUL and claim KCAL over time. Users or applications that only need to pay for transactions can hold KCAL directly.

## Native Assets

{% content-ref url="/pages/9FzlcbGrUvgNmWj1e5ML" %}
[SOUL](/main/about/dual-token-system/soul.md)
{% endcontent-ref %}

{% content-ref url="/pages/5SWgHn7cm1t6zCZ4rwyQ" %}
[KCAL](/main/about/dual-token-system/kcal.md)
{% endcontent-ref %}

## Developer Notes

Developers should plan for both fee dimensions:

* `maxGas` limits the KCAL a transaction can spend on execution and block data.
* `maxData` limits the SOUL a transaction can escrow for persistent state growth.

For storage-specific behavior, see the storage and data escrow page.

{% content-ref url="/pages/1S9chjEOb3hhPuNmbdic" %}
[Storage And Data Escrow](/main/developers/blockchain/smart-contracts/storage-and-data-escrow.md)
{% endcontent-ref %}


---

# 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://phantasma.gitbook.io/main/about/dual-token-system.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.