> For the complete documentation index, see [llms.txt](https://docs.duels.trade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duels.trade/getting-started/access-and-sign-in.md).

# Access and sign-in

Open duels.trade and select **Launch App** or **Start Trading**. You can browse public areas while signed out, but you must sign in before using personal, wallet, trading, or duel-entry features.

## Log in or sign up

Select **Log In** or **Sign Up** in the header. Both open the same sign-in panel.

![Current duels.trade sign-in panel](/files/k3AdkOdS6Cuf20nRwAQG)

Choose one of the options shown:

* Enter your email address and select **Continue**.
* Select **Continue with Google**.
* Connect with **MetaMask**, **Rabby**, **Phantom**, or **Other Wallets**.

Email sign-in continues with a verification code. A self-custody wallet may ask you to connect the wallet and sign an authentication request.

{% hint style="info" %}
Signing in proves account or wallet ownership. It does not transfer funds.
{% endhint %}

## New accounts

New accounts may be asked to choose a username. Usernames must be 3–20 characters.

After sign-in, complete [Set up your account](/account-and-safety/account-setup.md), including your profile and security settings.

## Sign-in safety

* Check that you are on the official duels.trade site.
* Never enter a private key or recovery phrase.
* Read wallet requests before signing.
* Treat a payment or approval request as a separate action from authentication.

## Privy

Email, Google, wallet authentication, embedded-wallet functions, MFA, and X linking use Privy where applicable. See [How duels.trade uses Privy](/account-and-safety/privy-and-account-security.md).


---

# 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://docs.duels.trade/getting-started/access-and-sign-in.md?ask=<question>&goal=<endgoal>
```

`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.