> For the complete documentation index, see [llms.txt](https://docs.hilomarket.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hilomarket.com/hilo-oracle.md). # Hilo Oracle The HILO Oracle allows users to actively contribute data to markets and help make their outcomes **more accurate, faster, and transparent**. #### 1. Normal voting vs. Oracle voting In a normal HILO market, one user can generally contribute **one vote**, meaning their contribution has a weight of 1. With Oracle Mode, users can increase the weight of their contribution by locking HILO tokens. For example: * Lock **100 HILO** on YES → **100 votes** toward YES * Lock **100,000 HILO** on YES → **100,000 votes** toward YES The more HILO a user commits, the greater the weight of their contribution to the market. The system calculates how much HILO is required to move the market toward a user's target and allows the user to decide whether to make that contribution. #### 2. Helping resolve markets faster Imagine a football match where Team A is currently showing an 80% probability of winning. The match finishes and **Team A wins**. Instead of waiting for a manual resolution process, an Oracle user can immediately contribute toward the correct outcome and target the market at **100% Team A**. HILO calculates the required token commitment, and the user can lock the required HILO. This creates a transparent, visible resolution process where the community can see how users are contributing to the outcome. #### 3. Different ways to contribute Oracle users can contribute using different order types: * **Market Orders** — immediately add weight to an outcome at the current market conditions. * **Limit Orders** — contribute only when a specified condition or price is reached. * **Target Orders** — specify the outcome level they want the market to reach, with HILO calculating the required contribution. This allows users to continuously adjust markets as new information becomes available. For example, if a market remains at 50/50 even though real-world information strongly indicates that one outcome is now more likely, Oracle users can contribute HILO to move the market toward a more accurate representation. #### 4. Why use HILO Oracle? The Oracle is designed to make market data: **More accurate**\ Users can continuously contribute information and adjust markets as real-world events develop. **Faster**\ Users can react immediately instead of waiting for a centralized resolution process. **Transparent**\ Oracle contributions are visible, allowing everyone to see how the market is being adjusted. **Community-driven**\ The data and resolution process is contributed to by users rather than relying entirely on a single centralized source. #### 5. How Oracle users earn Users are rewarded for contributing to the Oracle through **Oracle Points**. Your locked HILO actively contributes to the Oracle and generates points. For example: **100,000 HILO locked → 100,000 active Oracle Points** These points can qualify the user for HILO rewards according to the Oracle reward system. Users can also accumulate additional points when their contributions correctly help a market move toward its eventual resolution. #### 6. Unrealized Oracle Points Oracle Points can also reflect the ongoing performance of a user's contribution before a market is resolved. For example: A user moves a market from **50% → 60%**. Later, new information causes the market to move to **80%** in the same direction. The user's contribution has moved with the market and can generate **unrealized Oracle Points** based on that movement. This makes Oracle Points dynamic rather than simply being a one-time reward. #### 7. What happens if you're wrong? The key difference is that Oracle participation is designed to have **no direct financial loss from an incorrect contribution**. If a user contributes toward an outcome that turns out to be incorrect, they do not lose their locked HILO. Instead, the consequence is that their HILO can remain locked for longer according to the Oracle's unlock rules. This creates an economic incentive to provide accurate information without turning Oracle participation into a traditional financial bet. #### 8. Protecting the Oracle The locking mechanism also helps protect the system from malicious or low-quality contributions. A user cannot simply manipulate a market for free. To significantly influence a market, they must commit HILO and accept the possibility that their tokens will remain locked longer if their contribution is incorrect. This creates an incentive structure where users are rewarded for providing useful information while making manipulation more costly. #### The result HILO Oracle turns market participants into contributors to a **real-time, transparent data and resolution layer**. Users can use their HILO to: **Contribute → Adjust → Resolve → Earn Points → Receive Rewards** The goal is to create a system where users are rewarded not for risking their portfolio, but for **contributing useful information to the network.** --- # 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.hilomarket.com/hilo-oracle.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.