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

# Sign In and Connect

**The `Connect wallet` button opens one modal that handles every supported sign-in path — Phantom, MetaMask, Telegram, Google, and Email.**

The sign-in modal opens with `Welcome to GraphDex` and a single ask: pick the way you want to sign in. Wallet options sit at the top, social and email options below. By signing in you accept the Terms of Service and Privacy Policy linked in the same modal.

After sign-in, the terminal shows a `Connected` state on the bottom navigation. That's the signal you're ready to place orders — alongside a quick verification pass on wallet, balance, and Trading Settings before the first trade.

{% hint style="success" %}
**One modal, five entry points**

Open it from `Connect wallet` and pick the path that matches the wallet or account you already have.
{% endhint %}

## WALLET OPTIONS

**Phantom** and **MetaMask** are shown at the top of the modal. If your browser can't reach the extension, the button switches state to make it obvious.

* `No Phantom Detected` — the Phantom extension isn't installed or isn't reachable from the current tab.
* `No MetaMask Detected` — same for MetaMask.
* Install and unlock the relevant extension, refresh, and re-open the modal.
* The wallet itself may show a separate connection prompt — approve it there.

## SOCIAL AND EMAIL

For accounts without a browser wallet extension, the modal exposes three account-style entry points.

* **Telegram** — OAuth sign-in via Telegram. See [Connect with Telegram](/graphdex-docs/getting-started/connect-with-telegram.md).
* **Google** — OAuth sign-in via a Google account. See [Connect with Google](/graphdex-docs/getting-started/connect-with-google.md).
* **Continue with Email** — lightweight email-based sign-in for first looks.

## AFTER SIGN-IN

Five quick checks before your first order:

1. Terminal shows the `Connected` state on the bottom navigation.
2. The correct wallet is connected — confirm the address.
3. Wallet balance is enough for the order and network fees.
4. [Trading Settings](/graphdex-docs/trading/trading-settings-overview.md) reflect the execution profile you want.
5. The token's metrics and audit signals were reviewed before sending the order.

{% hint style="info" %}
If sign-in doesn't complete: allow pop-ups and redirects, unlock the wallet extension, make sure Telegram or Google opens the right account, and try again from a fresh tab. If it still fails, use the [Help Center](/graphdex-docs/help-and-feedback/help-center.md).
{% endhint %}

## FAQs

<details>

<summary>What sign-in methods are supported?</summary>

**Phantom, MetaMask, Telegram, Google, Email** — all in the same modal.

</details>

<details>

<summary>What does <code>No Phantom Detected</code> / <code>No MetaMask Detected</code> mean?</summary>

The extension isn't installed in the current browser, or it's installed but not reachable from this tab. Install and unlock it, refresh the terminal, and re-open the modal.

</details>

<details>

<summary>How do I know sign-in worked?</summary>

The terminal shows a `Connected` state in the lower navigation area. Confirm the wallet address matches the wallet you intended to connect.

</details>

<details>

<summary>Sign-in doesn't complete — what now?</summary>

* Allow pop-ups and redirects for the GraphDex domain.
* Unlock the wallet extension if you're using Phantom or MetaMask.
* Make sure Telegram or Google opens the correct account.
* Try again on a current browser version.
* If the issue persists, send a report through the [Help Center](/graphdex-docs/help-and-feedback/help-center.md).

</details>


---

# 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://graphdex-1.gitbook.io/graphdex-docs/getting-started/sign-in-and-connect.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.