> For the complete documentation index, see [llms.txt](https://docs.oortech.com/edge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oortech.com/edge/eco-partners/eco-partner-tokenomics.md). # Eco Partner Tokenomics Eco partners around the globe manufacture and distribute edge nodes for OORT Edge. [Learn more about eco partners](/edge/eco-partners.md). ### Collateral Eco partners are required to deposit **50 OORT per each device** which will be returned after the serving period (360 days). This is to encourage eco partners to be more accountable and provide high-quality customer services for OORT miners. ### Penalties Edge device owners are encouraged to appeal to the Foundation whenever an eco partner fails to deliver quality devices or services. If the appeal is successful, the eco partner’s collateral with respect to the edge devices will be deducted as penalties. ### Rewards Eco partners receive a 5% mining reward share of each device. {% hint style="info" %} 25% of the rewards are released immediately daily, and 75% are released linearly in 270 days. {% endhint %} --- # 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.oortech.com/edge/eco-partners/eco-partner-tokenomics.md?ask=&goal= ``` `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.