> For the complete documentation index, see [llms.txt](https://docs.adcpcapital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adcpcapital.com/operations/wallet-and-network.md). # Wallet and Network ## Supported network The current controlled pilot expects a wallet connected to **Base Sepolia**, chain ID `84532`. See [Base Sepolia](/network/base-sepolia.md). ## Connecting The application uses the WalletConnect/Reown protocol for wallet connection. No page requires a connected wallet merely to view it — connection is required only to sign a write transaction (originating credit, repaying, contributing capital, etc.). ## Wrong-network handling If your wallet is connected to a different chain than the one the application expects, the application shows this explicitly, rather than silently reading stale or incorrect data — and offers a one-click network-switch action where your wallet supports it. ## Disconnecting Standard wallet disconnect behaviour applies — disconnecting your wallet from the application does not affect your wallet itself or any position you hold; it only ends the application's read access to your connected address. ## Account safety ADCP never asks for a seed phrase, private key, or password. The only interaction the application ever requests is a standard wallet connection and, where you choose to proceed, a standard transaction signature — the same pattern any reputable Ethereum-compatible application uses. --- # 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://docs.adcpcapital.com/operations/wallet-and-network.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.