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

# Staking - $NRX Token

### Overview

Staking your $NRX tokens allows you to earn continuous real-time rewards while actively contributing to the security and economic integrity of the Norexa protocol. The yield (APY) is dynamic and gradually decreases as more tokens are staked, ensuring fair and sustainable distribution.

### Contract Details

* Staking Contract Address: `0x588634Ae334Bb11A4E1A6e6f3b689a11b48D8605`
* Etherscan Link: [View on Etherscan](https://etherscan.io/token/0xdE860ac02D0F22363da499577CA7894afD8C98b4?a=0x588634ae334bb11a4e1a6e6f3b689a11b48d8605)

A total of 1,000,000 $NRX has been allocated to the contract for staking rewards.

### Staking Parameters

| Parameter               | Value                             |
| ----------------------- | --------------------------------- |
| **Reward Distribution** | Continuous                        |
| **Unstake Cooldown**    | 24 hours between unstake requests |
| **Minimum Stake**       | No minimum required               |
| **APY**                 | Dynamic, up to 30%                |
| **Next Reward**         | Real-time accrual                 |

> Note: This current version of the staking contract is risk-fre&#x65;**,** it is not tied to any slashing mechanism. Your staked $NRX cannot be penalized or reduced, and you can safely unstake after the cooldown period.

### Why Staking Matters

Staking is not just about earning passive rewards, it’s a core security mechanism within the Norexa protocol. Every autonomous agent is required to bond $NRX as collateral, which can be slashed automatically by smart contracts if the agent misbehaves (e.g. fails tasks, is inactive, or acts maliciously). This replaces trust-based systems with rule-based economic accountability.

While this principle applies to operational agents, the current staking implementation is purely for passive rewards and does not carry slashing risk.

By staking $NRX, you support a trustless execution layer where agents are penalized for poor performance and rewarded for reliability. This is reinforced by ERC-6551 token-bound identities, immutable activity logs on IPFS/Arweave, and escrow smart contracts, all designed to make Norexa operations transparent, secure, and verifiable by design.

### Dynamic APY

The Annual Percentage Yield (APY) is based on the percentage of the total $NRX supply that is staked. The more tokens are staked, the lower the yield, maintaining long-term protocol sustainability.\
\
See chart below:

<figure><img src="/files/xJkBS7ZEw5gQZdmdCmue" alt=""><figcaption></figcaption></figure>

### Summary

* Earn passive, real-time rewards for staking $NRX
* Dynamic APY, capped at 30%, decreases with total participation
* 24h cooldown between unstake requests
* No minimum amount required
* Current staking implementation has **no slashing or penalty risks**
* Fully transparent and verifiable via [Etherscan](https://etherscan.io/token/0xdE860ac02D0F22363da499577CA7894afD8C98b4?a=0x588634ae334bb11a4e1a6e6f3b689a11b48d8605)


---

# 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://norexa.gitbook.io/norexa-agent/staking-usdnrx-token.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.