> For the complete documentation index, see [llms.txt](https://vulcan-forged.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vulcan-forged.gitbook.io/whitepaper/white-paper/elysium-forges-tiers-and-rewards/elysium-nodes/revenue-streams-and-rewards/elysium-nft-pool.md).

# Elysium NFT Pool

Previously a 1% boost for the base generation amount for each Vulcanite NFT held was proposed. Vulcan Forged will now offer a bonus for higher-level Vulcanites.

Vulcanite and OG badge holders will be able to boost their staking income. The NFT Pool will reward  LAVA based on the following increased reward boosts:

* Hold at least 1 x Level 1 Vulcanite: base generation amount + 1.00%
* Hold at least 1 x Level 2 Vulcanite: base generation amount + 1.25%
* Hold at least 1 x Level 3 Vulcanite: base generation amount + 1.50%
* Hold at least 1 x Level 4 Vulcanite: base generation amount + 1.75%
* Hold at least 1 x Level 5 Vulcanite: base generation amount + 2.00%
* Hold at least 1 x Level 6 Vulcanite: base generation amount + 2.5%

For a maximum bonus of 10% on top of the base rewards an owner will receive.

OG Badge bonus (not stackable): 2.5% staking reward for the total reward.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://vulcan-forged.gitbook.io/whitepaper/white-paper/elysium-forges-tiers-and-rewards/elysium-nodes/revenue-streams-and-rewards/elysium-nft-pool.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 `build a script that syncs our docs to a CMS` 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.