> For the complete documentation index, see [llms.txt](https://docs.addax.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.addax.finance/testnet/staking.md).

# ADDX Staking

ADDX stakers receive **40% of protocol fees**. On mainnet that fee is the Addax charge of up to 0.1% of filled size. Funding is not included.

On testnet, staking also deposits ADDX into the staking contract and pays rewards in proportion to your stake.

## What staking does

Staking ADDX allocates your tokens to the staking contract, which distributes rewards accrued from protocol activity (such as a portion of trading fees) to stakers proportional to their stake.

|                  |                                                     |
| ---------------- | --------------------------------------------------- |
| Staking contract | `0xA0961eE578d708837225012fb13b7b6f0dF5Ec15`        |
| Stake token      | ADDX (`0xf6078Be81aBCC95BAC306356963E7adB986783f9`) |

## How to stake

1. Go to the staking section of the app.
2. **Approve** ADDX to the staking contract (one-time).
3. Enter an amount and confirm to stake.
4. Rewards accrue over time and can be **claimed**; unstake to withdraw your principal.

## ADDX vs gADDX

Don't confuse the two:

* **Staking ADDX** -> deposits ADDX into the staking contract for protocol rewards.
* **gADDX vault** -> deposits ADDX as *trading liquidity*, taking the other side of ADDX-collateralized trades (see [gToken Vaults](/testnet/overview.md)).

Both use ADDX but serve different roles and carry different risk/return profiles.

## Addresses

See [Contracts & Addresses](/testnet/contracts.md) for the full list.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.addax.finance/testnet/staking.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.