> For the complete documentation index, see [llms.txt](https://dexsport-3.gitbook.io/dexsport-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dexsport-3.gitbook.io/dexsport-docs/getting-started/is-it-safe.md). # Is Dexsport safe? License and audits Yes. Dexsport operates under a license from Anjouan, No. ALSI-202508043-FI2, and the platform's smart contracts have been audited by two independent firms, CertiK and Pessimistic. Payouts come from the shared liquidity pool through the blockchain, and every transaction can be verified. ## The license Dexsport is operated by Dexapp LTD, which holds a gambling license issued in Anjouan under number ALSI-202508043-FI2. That is the legal basis the platform operates on. You can check the license yourself: click the license seal at the bottom of any page on [dexsport.io](https://dexsport.io). It opens the Anjouan license validation page, which shows the company name, the website, the license number and the operating status. ## The audits Security on Dexsport rests on two things: the smart contracts and the liquidity pool itself. All of the code has been reviewed by independent security firms: * [CertiK](https://www.certik.com/projects/dexsport): the Dexsport page on CertiK, with the audit and the security score * [Pessimistic](https://github.com/pessimistic-io/audits/blob/main/DexSport%20Security%20Analysis%20by%20Pessimistic.pdf): the full audit report, PDF An audit is an outside review of the platform's code, done by a company with no stake in the outcome. Two separate firms looked at the contracts that hold the pool and process bets and payouts. ## Where your money is held Funds are held and paid out through smart contracts, not on a company balance sheet. Winnings come straight from the liquidity pool, which is a shared vault whose balance is visible to everyone. Your funds stay under your control. When you deposit from a connected Web3 wallet, the money goes directly from your wallet to the liquidity pool contract. Withdrawals are instant and go straight back to your wallet. ## How to check it yourself Every transaction is recorded on the blockchain, so it can be checked at any time by anyone. In your profile, the Transactions section lists each deposit and withdrawal with the amount, the token and network, the date, the status, and the transaction hash. Copy that hash into any blockchain explorer and you can see the transaction on the chain and confirm the funds were sent. The same applies to the pool balance itself. It is on-chain and public. ## If something does not look right Contact support in the chat on the platform. Include your nickname, the bet ID if it concerns a bet, and the transaction hash if it concerns a deposit or withdrawal. One point on security: if someone contacts you on X or Telegram claiming to be from Dexsport, ask support to confirm that the handle is official before you share anything. --- # 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://dexsport-3.gitbook.io/dexsport-docs/getting-started/is-it-safe.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.