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

# Token Flow

This page explains, in simple terms, where your tokens are, when they move, and where you can see them. There are four main places/accounts involved:

{% hint style="success" %}
The [Crynux Portal](https://portal.crynux.io) now shows all token locations linked to your node wallet—Node Wallet, Beneficial Wallet, Stake Locked, and Relay Account—so you can review your entire token distribution in one place.
{% endhint %}

| Place             | Description                                                                       | Visible in on-chain wallet? | Where to view                                                            | Network check                                    |
| ----------------- | --------------------------------------------------------------------------------- | --------------------------- | ------------------------------------------------------------------------ | ------------------------------------------------ |
| Node Wallet       | Your on-chain node wallet (e.g., MetaMask).                                       | Yes (except staked portion) | [Crynux Portal](https://portal.crynux.io), MetaMask (node address)       | Check both L2 blockchains (switch networks)      |
| Beneficial Wallet | On-chain beneficial wallet (if configured) that receives refunds and withdrawals. | Yes (when used)             | [Crynux Portal](https://portal.crynux.io), MetaMask (beneficial address) | Check both L2 blockchains (switch networks)      |
| Stake Locked      | Tokens locked as stake after you start the node.                                  | No                          | [Crynux Portal](https://portal.crynux.io), Node WebUI                    | Check both L2 blockchains (switch node versions) |
| Relay Account     | Task fees credited while your node executes tasks. Stored in the Crynux Relay.    | No                          | [Crynux Portal](https://portal.crynux.io), Node WebUI                    | -                                                |

## Token Flowchart

```mermaid
flowchart TD
  NW["Node Wallet"]
  BW["Beneficial Wallet"]
  SL["Stake Locked"]
  RA["Relay Account"]

  NW -->|"Stake at start"| SL
  SL -->|"Refund on stop (no Beneficial)"| NW
  SL -->|"Refund on stop (with Beneficial)"| BW
  RA -->|"Withdraw (no Beneficial)"| NW
  RA -->|"Withdraw (with Beneficial)"| BW
```

## Token Movement

### Node Wallet

* When you start the node, the required stake is deducted from your On-chain Node Wallet.
* The deducted amount becomes Stake Locked. It will not show in MetaMask (or other wallets) because it is locked. You can see the locked amount in the [Crynux Portal](https://portal.crynux.io) and the Node WebUI (see Stake Locked below).
* When you stop the node and there is no Beneficial Address set, the stake refund goes back to the Node Wallet and will be visible there.
* When withdrawing task fees in the Portal and there is no Beneficial Address set, withdrawals go to the Node Wallet.

### Stake Locked

* What it is: the portion of tokens deducted from the Node Wallet at start and locked as stake by the node.
* Visibility: not visible in on-chain wallet balances; visible in the Node WebUI as “CNX Staked”, and in the [Crynux Portal](https://portal.crynux.io).
* Lifecycle: created when the node starts; released when the node stops.
  * If a Beneficial Address is configured, the released stake is refunded to the Beneficial Wallet.
  * Otherwise, the released stake is refunded to the Node Wallet.
* You cannot transfer Stake Locked directly; it becomes spendable only after it is refunded on stop.

### Beneficial Wallet

* If a Beneficial Address is configured for the Node Wallet, the stake refund after stopping the node is sent to the Beneficial Wallet. It will not appear in the Node Wallet; check the wallet that controls the Beneficial Address.
* If a Beneficial Address is configured, Portal withdrawals of task fees are sent to the Beneficial Wallet.
* Always verify balances using the wallet that holds the Beneficial Address.

### Relay Account

* Task fees earned by your node are credited to the Relay Account, which is recorded in the Crynux Relay.
* This balance is not reflected in the on-chain balance of your wallet. You can view it in the [Crynux Portal](https://portal.crynux.io) and in the Node WebUI.
* How to view: import or select your Node Wallet address in MetaMask, open the Crynux Portal, connect with the Node Wallet, and check the Dashboard. You can also check the Node WebUI.
* How to withdraw: in the Portal, use Withdraw to move funds from the Relay Account to an on-chain address.
  * If a Beneficial Address is configured, withdrawals go to the Beneficial Wallet.
  * Otherwise, withdrawals go to the Node Wallet.


---

# 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://docs.crynux.io/crynux-blockchains/token-flow.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.
