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

# Distribution mechanics:

* Epochs: Revenue accrues in weekly epochs.<br>

* Snapshot set: balances snapshotted at fixed block intervals to minimize wash-trading games around distribution.<br>

* Direct ETH airdrop: At epoch end, a distributor sends ETH to eligible wallets.<br>

* Exclusions: Protocol contracts, burned addresses, and CEX wallets (unless the exchange opts in to per-user passthrough) are excluded or handled via formal whitelisting agreements.

* Distributions are pro-rata, meaning your $ETH rewards scale with your $OPAL balance.

* Stake $OPAL to access protocol rewards. no lockups, un-stake anytime. Staking is designed to align with regulatory best practices.\ <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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.opaldex.com/tokenomics/distribution-mechanics.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.
