> For the complete documentation index, see [llms.txt](https://hyperpot.gitbook.io/hyperpot-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hyperpot.gitbook.io/hyperpot-docs/terms.md). # Terms ## Terms These terms are a plain-language notice for the HyperPot mainnet beta. They are not a substitute for legal advice. By using HyperPot, you agree that you understand the risks below. ### Mainnet Beta HyperPot is live on HyperEVM mainnet as an experimental beta. The app, smart contract, keeper, indexer, documentation, and frontend may contain bugs or behave unexpectedly. Use small amounts only if you understand and accept the risk. ### No Custody HyperPot is a non-custodial on-chain application. You connect your own wallet and sign your own transactions. HyperPot never needs your seed phrase or private key. Only use the official website and verify the contract address before depositing. ### Official Contract Current HyperPot mainnet contract: ``` 0x5379aE36aBf49be3ca98C9933436A351c84676eE ``` Current network: ``` HyperEVM mainnet Chain ID: 999 ``` ### Deposits, Odds, and Payouts Players deposit native HYPE into the current round. Your chance of winning is proportional to your deposit size relative to the total pot. For example, if you deposited 1 HYPE into a 10 HYPE pot, your approximate chance of winning is 10%. Winners do not receive funds automatically in their wallet. Winnings are credited on-chain and must be claimed. ### Fees Each settled round may include protocol fees and entropy funding. The current public beta parameters are visible on-chain and in the app. Fees may change in future deployments or through owner-controlled configuration. ### Randomness HyperPot uses Pyth Entropy for randomness. Randomness is requested after a round closes. The app displays verification details so users can inspect how a winner was selected. No randomness system is risk-free. Oracle outages, delayed callbacks, RPC issues, or chain issues may affect settlement timing. ### Refunds and Cancelled Rounds If a round expires with fewer than two unique players, the keeper can cancel the round. When a solo round is cancelled, the solo depositor's amount is credited as claimable and can be withdrawn through the app. If a randomness request is stuck for too long, the contract includes a refund path for affected depositors. Refunds still require on-chain transactions and wallet interaction. ### Keeper and Indexer The keeper helps trigger expired round actions. The indexer powers leaderboard data. If the keeper or indexer is delayed or offline, the contract can still be inspected on-chain, but the app may show delayed data or require manual intervention. Leaderboard data is informational and may lag behind the chain. ### No Financial Advice HyperPot is not financial, investment, legal, or tax advice. Participation involves risk and may result in loss of funds. You are responsible for your own wallet security, transaction review, tax obligations, and compliance with applicable laws. ### Eligibility Do not use HyperPot if doing so is illegal or restricted in your jurisdiction. Do not use HyperPot if you are not legally allowed to participate in blockchain-based games, raffles, or similar applications where you live. ### No Guarantees HyperPot does not guarantee: * Profits * Rewards * Airdrops * Token allocations * Future benefits * Continuous uptime * Immediate settlement * Error-free frontend data ### Wallet Safety HyperPot will never ask for your seed phrase. HyperPot does not require ERC-20 token approvals for native HYPE deposits. Before confirming any transaction, verify: * The domain is official. * The network is HyperEVM mainnet. * The transaction sends the amount you expect. * The contract address matches the official contract. ### Changes The HyperPot team may update the frontend, docs, keeper, indexer, parameters, or future contract deployments. Material changes should be communicated through official channels when possible. ### Contact For support, bug reports, or questions, use the official support links in the HyperPot docs. --- # 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://hyperpot.gitbook.io/hyperpot-docs/terms.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.