> For the complete documentation index, see [llms.txt](https://docs.logosnodos.online/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.logosnodos.online/mainnet-node/avail-network/staking-bonding.md).

# Staking / Bonding

* <mark style="color:red;background-color:green;">**ON YOUR VPS**</mark>

1. Generate session keys

```
curl -H "Content-Type: application/json" -d '{"id":1, "jsonrpc":"2.0", "method": "author_rotateKeys", "params":[]}' http://localhost:9944
```

2. Restart node

```
sudo systemctl restart availd.service
```

*Note : Save your session keys it will needed to connect your dashboard with your node*

* <mark style="color:red;background-color:green;">**ON YOUR DASHBOARD**</mark>

1. Navigate to the Avail network explorer at [https://explorer.avail.so/(opens in a new tab)](https://explorer.avail.so/) and choose the correct network.
2. Create a `stash` account.
3. Navigate to the **Staking** tab in the Explorer.
4. Click on `Stash` to initiate the bonding process.

<figure><img src="/files/ntj1TvLzesWj5GwFYyZa" alt=""><figcaption><p><em>Tips : Don't BOND all your tokens because you need some gas fee (you can increase your bonding anytime soon)</em></p></figcaption></figure>

5. Fill in the bonding preferences. Then click `Bond` and `Sign and Submit`.&#x20;

<figure><img src="https://docs.availproject.org/img/bonding-preference.png" alt=""><figcaption><p><em>Minimum bonding for joining mainnet is 50K AVL</em></p></figcaption></figure>

6. Click on `Session Key` and enter the hex-encoded result. (*Input your session keys that I mention to saved before*)
7. Click `Set Session Key` -> `Sign and Submit`and enter your password when prompted.

<figure><img src="https://docs.availproject.org/img/avail/set-session-keys.png" alt=""><figcaption><p><em>After submitting the extrinsic, you'll observe that <strong>Set Session Key</strong> changes to <strong>Validate</strong>. Make sure your node is fully synchronized before proceeding further.</em></p></figcaption></figure>

8. Click `Validate` on the **Staking** tab.

<figure><img src="https://docs.availproject.org/img/avail/start-validating.png" alt=""><figcaption></figcaption></figure>

9. Set your validator commission percentage.
10. Enter your password and click `Validate`.

<figure><img src="https://docs.availproject.org/img/avail/set-validate-commission.png" alt=""><figcaption></figcaption></figure>

<mark style="color:red;background-color:green;">CONGRATULATIONS !!!</mark>

Your validator is now prepared to begin the validation process. If you wish to discontinue, you can click the stop icon. Please note that the Avail interface doesn't automatically verify if your node is synchronized; you'll need to confirm this manually. If your node has sufficient stake, the Avail blockchain will likely select it in the next epoch or two.

<figure><img src="https://docs.availproject.org/img/avail/validator-ready.png" alt=""><figcaption></figcaption></figure>


---

# 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.logosnodos.online/mainnet-node/avail-network/staking-bonding.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.