> For the complete documentation index, see [llms.txt](https://docs.nerve-protocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nerve-protocol.com/tokenomics/npx-token-distribution.md).

# $NPX Token Distribution

1. **Liquidity Pool (100%):**

* All tokens will be allocated to the liquidity pool. This ensures ample liquidity for seamless trading, enabling token holders to buy and sell $NPX across Ethereum decentralized exchanges at launch.

2. **Policy Notes:**

* **Incentives and Rewards :**\
  Node operator incentives will **be paid in ETH** alongside $NPX distributions. ETH rewards cover transaction fees and keep enclave operators motivated to secure the network while Nerve matures on Ethereum.
* **Operator Alignment:**\
  Liquidity-first distribution keeps the token accessible to operators, agent builders, and node runners without hidden allocations.
* **Future Expansions:**\
  Governance updates may introduce mission staking pools or cross-chain liquidity bridges; proposals will be submitted through privacy-preserving on-chain votes.


---

# 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.nerve-protocol.com/tokenomics/npx-token-distribution.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.