> 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/account-and-safety/verify-x-with-privy.md).

# Verify X with Privy

duels.trade uses Privy to link an X account to your authenticated duels.trade account.

## Verification versus a manual link

* Typing an X username creates an unverified public link.
* Selecting **Connect X to verify** starts the Privy linking flow.
* A successful Privy link produces the **Verified** state and locks the X field to the linked username.

## Connect X

1. Open **Account → Profile Hub**.
2. Find **X / Twitter** under Social Links.
3. Select **Connect X to verify**.
4. If asked, complete your Privy login first.
5. Authorize the X connection in the Privy flow.
6. Return to Profile Hub and confirm the **Verified** badge.

For a wallet-only session, Privy may first ask you to complete wallet login. After that, duels.trade continues to X verification.

## What is verified

Privy returns the linked X identity to duels.trade. duels.trade records the verified X username and uses it on your public profile.

Verification does not verify trading performance, wallet ownership beyond your authenticated session, or any statement made by the X account.

## Disconnect X

Select **Disconnect** next to the Verified badge.

duels.trade removes the in-app verification and attempts to unlink the X identity from Privy. If the Privy unlink fails, the app reports that separately.

## Troubleshooting

If verification fails:

* Wait for Privy to finish loading.
* Allow cookies and pop-ups needed by the login flow.
* Temporarily disable an ad blocker or VPN if a captcha fails.
* Complete wallet login when prompted.
* Retry **Connect X to verify**.


---

# 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/account-and-safety/verify-x-with-privy.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.