> For the complete documentation index, see [llms.txt](https://docs.behodler.io/user-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.behodler.io/user-docs/tokens/eye.md). # EYE ![](https://1067066616-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MdNOsIa99O7FXqrv_0j%2F-MfDXA0z3gjLaf0q8suA%2F-MfDXdgaLbWPzv-wwT-W%2Feye.png?alt=media\&token=86bbf1a4-2948-4653-b806-41ebf09af7d3) EYE is the utility & governance token for MorgothDAO, and the Behodler ecosystem. In MorgothDAO, it will be leveraged via game theory to address governance such as a dispute resolution system similar to Kleros. In Limbo, EYE can also be used to subtlety adjust staking reward APYs. In keeping with the ethos of everything in the Behodler ecosystem, Eye is burnable and deflationary. **EYE** Contract: 0x155ff1A85F440EE0A382eA949f24CE4E0b751c65 Etherscan: ## Launch EYE was launched in September 2020 with an initial fixed supply of 10 million tokens. * 30% of the supply was airdropped to DGVC/ETH LPs * 30% was held by Justin Goro and Degen Labs - split as following * one-third held in a multi-sig wallet * two-thirds time locked in Unicrypt * 40% reserved to incentivize Liquidity Queuing ## Airdrops During December 2020 100,000 EYE was airdropped to existing Uniswap EYE/ETH LPs --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.behodler.io/user-docs/tokens/eye.md?ask=&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 `automate deployments from our CI pipeline` 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.