# Key Management One of the most significant barriers to web3 adoption is the risk and complexity associated with **key management**. Functor directly addresses this with resilient and user-friendly solutions designed for an onchain world. The core innovation is enabling a **single signer** to operate securely across **infinite chains**. \ \ This unified identity is then paired with modern, robust security features that protect against loss and attack. A critical distinction of Functor's architecture is its commitment to **self-custody**. This means you, and only you, hold the ultimate authority and control over your private keys and assets. Functor’s tools like signer rotation and recovery are designed to enhance the security *of* your self-custodial wallet, not replace it with a custodial model where a third party holds your keys. ### **Signer Rotation and Recovery** AI agents and users can programmatically rotate their keys to minimize the risk associated with a single key being compromised. Furthermore, Functor enables resilient, self-custodial account recovery mechanisms, helping to prevent the permanent loss of assets. ### **Self-Custodial Enterprise Wallets** Institutions can finally deploy enterprise-grade wallets that offer sophisticated controls and recovery pathways without sacrificing self-custody. This provides the security guarantees they require with the core principles of decentralization. ### **Simplified User Onboarding** By supporting familiar authentication methods like passkeys, Functor abstracts away the complexity of seed phrases for everyday users, paving the way for a web2-like user experience with the full security of onchain self-custody. --- # Agent Instructions: 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: ``` GET https://functor.gitbook.io/functor-network-docs/use-cases/key-management.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.