> For the complete documentation index, see [llms.txt](https://docs.pharos.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pharos.xyz/tooling-and-infrastructure/wallets.md). # Wallet ## Overview Wallets and custody solutions are used to manage accounts, sign transactions, and control assets on the Pharos Network. As a developer, you’ll use wallets for interacting with applications, while custody solutions are important for managing funds securely, especially in production environments. ## What You Can Do with Wallets * Create and manage accounts * Sign and send transactions * Interact with smart contracts * Connect to decentralized applications * Manage assets across networks ## Custody for Applications For applications and teams, custody solutions provide more advanced capabilities such as: * Multi-signature (multisig) transaction approvals * Secure key management * Role-based access control * Operational security for managing funds ## Why It Matters Choosing the right wallet or custody solution is important for both development and production. * Individual developers typically use wallets for testing and interaction * Teams and protocols rely on custody solutions for secure fund management and operational workflows ## Available Solutions Pharos supports wallet and custody solutions for different use cases. Refer to the pages below for setup and usage: * Safe MultiSig * Fordefi --- # 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.pharos.xyz/tooling-and-infrastructure/wallets.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.