> 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/lava-pools.md).

# LAVA Pools

Pools will be used for LAVA distribution. The pools will collect LAVA constantly and distribute the rewards on a weekly basis.

The $LAVA transaction fees will be distributed as follows:

* 50% of the fees will be available as a reward for Cronus Nodes and Elysium Forges
* 10% of the $LAVA will be divided between the Demeter Nodes.
* 10% of the $LAVA will be used to fill up the Vulcan Forged gaming pools (for non-Frenzy pass holders).
* 10% of the $LAVA is donated to the Elysium ecological & environmental pool.
* 20% is burned.

The marketplace royalty fees will be distributed as follows:

* 40% will be distributed as rewards for nodes (the Magma Protocol will be used to convert tokens paid into PYR)
* 50% will be distributed to the foundation treasury (the Magma Protocol will be used to convert tokens paid into PYR).
* 10% will be donated to the Elysium ecological & environmental pool

The LAVA sowing fees will be distributed as follows:

* 20% of the LAVA will be burned.
* 80% of the fees will be available as a reward for Cronus Nodes and Elysium Forges

Cronus Node Rewards

Cronus node holders will be rewarded for keeping the Elysium blockchain secure through transaction fees, royalty fees, and sowing fees. The Cronus node will receive a bonus on top of the base generation amount because there are costs to keep the node online and secure.

All Cronus node holders will receive part of the sowing costs, LAVA gas fees on Elysium, and the royalty fees. Cronus node holders can participate in the God Pool and NFT Pool. Please check the ‘rewards for nodes’ section at the top of this article for specifications regarding the rewards.<br>


---

# 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/lava-pools.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.