> For the complete documentation index, see [llms.txt](https://docs.bloq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloq.com/bloq-services/bloqstake/avalanche/getting-started.md).

# Stake AVAX

**Requirements**

## 1. Requirements

* **Mainnet:** A minimum of 2,000 AVAX per validator.
  * The minimum amount of time one can stake funds for validation is 2 weeks.
  * The maximum amount of time one can stake funds for validation is 1 year.
  * The maximum weight of a validator (their own stake + stake delegated to them) is the minimum of 3 million AVAX and 5 times the amount the validator staked. For example, if you staked 2,000 AVAX to become a validator, only 8,000 AVAX can be delegated to your node total (not per delegator).
* **Fuji Testnet:** A minimum of 1 AVAX per validator
  * The minimum amount of time one can stake funds for validation is 24 hours

More on the [Avalanche Staking docs](https://docs.avax.network/nodes/validate/staking).

### 1. Authenticate to the Bloq API

To use the Bloq API, visit [authentication.md](https://github.com/bloqpriv/bloq-services-monorepo/blob/gitbook/docs/bloq-services/bloqstake/auth/authentication.md).

### 2. Create a new validator node

Create a validator node by calling the BloqStake API with the authentication token.

```shell
curl -X POST https://api.bloq.com/staking/avalanche/fuji/validators \
  -H 'Authorization: Bearer <auth-token>' \
  -H 'Content-Type: application/json'
```

This `post` call will return a `nodeId` value. Save it and wait a couple of minutes after creating the validator, then run the following command as follows:

```shell
curl -X GET https://api.bloq.com/staking/avalanche/fuji/validators/node-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx \
  -H 'Authorization: Bearer <auth-token>' \
  -H 'Content-Type: application/json'
```

The response will include the `avalancheNodeId` property of the validator and other status information.\
Take note of this `avalancheNodeId` value, as you'll need it for the next step.

### 3. Register and fund the validator on Avalanche Network

{% hint style="danger" %}
**WARNING:** Note that once you register the validator, there is no way to change the parameters. You can’t remove your stake early or change the stake amount, node ID, or reward address.
{% endhint %}

To register the validator, with the `avalancheNodeId` value taken from the previous step, follow one of these guides:

* [Add a validator with Avalanche Wallet](https://docs.avax.network/nodes/validate/add-a-validator#add-a-validator-with-avalanche-wallet)

As the validator created needs to catch up with the Avalanche chain, after the deposit transaction is confirmed, it may take some time for the Validator to detect the new staking period.


---

# 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.bloq.com/bloq-services/bloqstake/avalanche/getting-started.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.
