> For the complete documentation index, see [llms.txt](https://takes.gitbook.io/takes-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://takes.gitbook.io/takes-docs/holders/connect-and-sign-in.md). # Connect and sign in Connect wallet opens the wallet picker. Opening Portfolio or Referrals & rebates also requires sign-in: approve a message signature to verify your wallet. This signature moves no funds and costs no network fee. If you reject it, choose Sign in or Retry sign-in when ready, or Continue exploring to keep browsing public pages. Disconnect wallet is available in the sign-in dialog; the connected wallet control opens your wallet account. Use the network control beside your connected wallet to change networks. A pool action can also ask you to switch to that pool's network. Confirm the switch in your wallet; if automatic switching is unavailable, switch there manually. A rejected or failed switch can be retried. Network filters change which data you see; they do not move funds or change the wallet's network. After session expiry, Portfolio can keep showing saved values and ask you to sign in to refresh. Check the connected wallet and refresh before relying on those values. To fund another network, use [Move USDC](/takes-docs/trade.md#move-usdc-between-networks). --- # 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://takes.gitbook.io/takes-docs/holders/connect-and-sign-in.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.