> 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/sign-up.md). # How to sign up and log in You can create a Dexsport account in four ways: with an email address, with Google, with Telegram, or by connecting a Web3 wallet such as MetaMask. Registration takes under a minute, and the account is active straight away, with no KYC and no documents. Each of the four methods is shown screen by screen in [Logging in step by step](/dexsport-docs/getting-started/login-step-by-step.md). ## Signing up Go to [dexsport.io](https://dexsport.io) and click **Sign Up** in the top right corner. Then pick the method you prefer. **Email, Google, or Telegram.** Standard registration. With an email you sign in with a one-time 6-digit code sent to that address. After registration you can switch on extra protection in Settings. **Web3 wallet.** Choose your wallet from the list or use WalletConnect, usually by scanning a QR code. The wallet first asks whether to connect, then the site shows a **Verify wallet** button, and pressing it sends the authorization request to your wallet to sign. That signature only confirms the login, it does not cost gas and it does not move your funds. If you already have a promo code, click "I have promo code" during sign-up and enter it there. If you registered first and found the code later, hover over your avatar, open **Promo code**, paste it, and click Activate. ## Logging back in Click **Sign Up** in the top right corner. It is the same button for both cases: it opens one window that handles registration and login, so use the method you registered with. With an email, a 6-digit code is sent to your address and you enter it to finish signing in. For a wallet login, select your wallet or WalletConnect and sign the authorization request again. If the site will not load or the login does not go through, turn off browser extensions and any VPN, clear your cache and cookies, then restart the platform and try again. ## What to do next **Pick your welcome bonus.** Right after registration you choose which Welcome Bonus you want on your first three deposits: Sports, which pays freebets, or Casino, which pays a deposit bonus and free spins. The choice is not locked in. On the **Promotions** page the Welcome Bonus block has a switch with Casino, Sports and Skip, and it applies to the next deposit you have not claimed yet, so the first deposit can be sports and the second casino. **Set up your profile.** Open Settings. A username is created for you at registration, and you can change it there to something of your own. In the same place you can add an email address and choose which mailings you get. If you registered with email, Google or Telegram, Settings also holds an email passcode for withdrawal and two-factor authentication. A wallet account has none of those: its protection is the wallet itself. The username matters in one practical way: support asks for it to find your account, so it is worth having one you will remember. After that you can deposit and start betting. --- # 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/sign-up.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.