> For the complete documentation index, see [llms.txt](https://support.bancor.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.bancor.network/bancor-amm/transactions-and-metamask/connect-your-web3-wallet-to-bancor.md).

# Connect your Web3 Wallet to Bancor

After you've set up your wallet, you need to make sure you are connected to the right network.

Currently, Bancor is available on the Ethereum Mainnet. You can make sure you are connected to the correct network by clicking on the MetaMask extension in your browser and checking the top box for the information. The network can be changed both when you input your MetaMask password (not private key) or after you've logged in.

<img src="https://support.bancor.network/hc/article_attachments/6777858282258/Ether.PNG" alt="Ether.PNG" height="508" width="300">

This applies to all Web3 wallets - if you connect with an unsupported network, you will see an error message and the Bancor web app will prompt you to change it.

<img src="https://support.bancor.network/hc/article_attachments/6779910608786/NETWORK.jpg" alt="NETWORK.jpg" height="543" width="251">

If you are still facing issues with connecting your wallet, please reach out via email - <support@bancor.network>

<br>


---

# 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://support.bancor.network/bancor-amm/transactions-and-metamask/connect-your-web3-wallet-to-bancor.md?ask=<question>&goal=<user_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.