> 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/account/security.md). # Security: login code and 2FA An account with an email logs in with a one-time code: a **6-digit code** is sent to that address every time you sign in. An account on a Web3 wallet logs in by signing a request in the wallet. Which security options you get follows from that difference. Open your profile from the avatar in the top right corner and go to **Settings**. **An account with an email.** Settings holds a **Security** block with two switches, and a **Connected accounts** block where Telegram and Google can be linked. Every linked method leads to the same account. **An account on a Web3 wallet.** Here the protection works differently: the wallet itself is the protection. You log in by signing a request in it, so no code is sent anywhere, and the keys to the account are the keys to your wallet. There is no Security block on such an account, and adding an email does not open one: the address is there for mail, not for logging in. ## Two-factor authentication 2FA adds a second step on top of the login code, so that access to your mailbox alone is not enough. Both options live in the **Security** block and are available to accounts with an email. * **Email passcode for withdrawal.** A one-time code arrives by email on every withdrawal. * **Authenticator app.** The one-time code comes from an app and is asked for both at login and at withdrawal. ![The Security block with its two switches](https://3235441457-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZGaNfrspeR8PjegVRwpU%2Fuploads%2Fgit-blob-31f5970e71e0f15dde9bb9a3c516f63aa418341d%2Flogin-08-settings-security.jpg?alt=media) ## If the login code does not arrive Check the spam folder first, because a code can land there. Give the mail a minute as well, since delivery is not always instant. If the code still does not come, write to support at **** from the email address attached to your account. Send the message from that address, because it is what confirms the account is yours, and state the new email address you want to use. Support can change the email address on an account through a separate procedure. ## Wallet logins and the signature When you connect a Web3 wallet, the platform asks you to sign an authorization request. That signature only confirms that the wallet is yours. It does not cost gas, and it does not move your funds anywhere. Signing it is a normal part of logging in, and you will be asked again on later logins. You stay in control of your wallet the whole time. Payouts come from the liquidity pool through smart contracts, and every transaction is recorded on the blockchain, so you can check it yourself at any point. ## No KYC Dexsport does not ask for identity documents. Your account is active straight after registration, whether you signed up with email, Google, Telegram, or a wallet. ## Watch out for impersonators If someone contacts you on X or Telegram claiming to work for Dexsport, do not share anything before checking. Ask support in the platform chat to confirm that the handle is official. Support will confirm or deny it. ## If you cannot log in Turn off browser extensions and any VPN, clear your cache and cookies, then close and restart the platform before trying again. If the login still fails, contact support with your nickname. --- # 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/account/security.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.