# On-chain Operation Eggle’s gameplay and economy are entirely driven by smart contracts, ensuring fairness, transparency, and automation. At the heart of this design are two primary contracts that define how players interact with their animals and claim rewards.
Egg
## **Health Check Contract** The Health Check contract oversees the well-being of all Eggle animals. To keep their animal alive and growing, players send **10 ENG daily** to the animal’s **Token Bound Account (TBA)** rather than directly to the contract. This design deepens ownership and makes each animal a true on-chain entity.
full chicken
If neglected, an animal’s health status will degrade step by step—**Full → Hungry → Weak → In Danger → Dead**. Once Dead, it remains an NFT but loses all utility: it can no longer be fed, revived, or exchanged for harvest rewards. This mechanic brings realism and responsibility into Eggle, rewarding only those who show consistent care. {% content-ref url="/pages/ry4E7rhl2cnSyRyXEdSD" %} [Phase 2 - Raising](/how-to-play/phase-2-raising.md) {% endcontent-ref %} {% content-ref url="/pages/eKebZoXGtW065fU3JvU1" %} [Dead or Alive](/breakdown/dead-or-alive.md) {% endcontent-ref %} ## **Treasury Contract** The Treasury contract is the final stop in a player’s journey—where dedication is turned into tangible rewards. Once an animal reaches maturity in **Full** status, it can be sent to the Treasury contract. In return, the system distributes rewards directly to the player’s wallet, fully automated and trustless.
swag chicken
## **The Bigger Picture** Together, the **Health Check contract** and the **Treasury contract** form Eggle’s on-chain core, weaving responsibility, reward, and transparency into a single loop. Every action—feeding, growing, harvesting—is fully recorded on-chain, turning Eggle into more than a game: it is a decentralized ecosystem where attention and commitment directly shape outcomes. {% content-ref url="/pages/AClPWdvNFdRhHLbwv0J6" %} [Phase 3 - Harvesting](/how-to-play/phase-3-harvesting.md) {% endcontent-ref %} --- # Agent Instructions: 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: ``` GET https://docs.eggle.xyz/essentials/on-chain-operation.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.