# Disclaimer #### Decentralized Technology Gud Guess is proud to be completely decentralized on the Arbitrum-One network. Every single mechanic in the Gud Guess ecosystem functions 100% on-chain. As long as the Arbitrum-One network is running, so is Gud Guess. #### Responsibility Because of the decentralized nature of the project, Gud Guess and any developers & contributors are not responsible for any loss you incur while using the dapp or protocol. Please always DYOR and ensure you understand the actions you take when using any blockchain project or technology. #### Audit All Gud Guess smart contracts have been [audited by Solidity Finance](https://solidity.finance/audits/GudGuess/). #### Gud Guess Tickets Tickets for the current week's jackpot must be bought before guessing closes each week after **Thursday 23:59:59 UTC**. The purchase transaction must be processed prior to this deadline. We do not have any control over transaction speed, therefore we are not responsible for any tickets purchased submitted before the guessing close times. It is not possible to inject tickets for the current week after the guess close time. All Gud Guess tickets are non-refundable. #### On-chain Uniswap V3 Price Feeds As mentioned on the [BTC/USD Close Price Calc page](/gg-game-mechanics-and-jackpot/btc-usd-close-price-calc.md), the BTC/USD price comes from a TWAP price built into the Uniswap V3 protocol that anyone can see on-chain. We recommend researching how [TWAPs](https://en.wikipedia.org/wiki/Time-weighted_average_price) work, their security implications, benefits, and risks. --- # 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.gudguess.com/disclaimer.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.