> For the complete documentation index, see [llms.txt](https://gaya-blockchain.gitbook.io/gaya-blockchain/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gaya-blockchain.gitbook.io/gaya-blockchain/gaya-wallet.md). # Gaya Wallet ### Overview Gaya Wallet represents the consumer-facing gateway to the Gaya ecosystem, designed to make cryptocurrency management accessible, rewarding, and seamless for users of all experience levels. As a self-custodial wallet with integrated financial services, Gaya Wallet bridges the gap between traditional finance and the decentralized future. #### Vision To become the primary interface through which millions of users interact with cryptocurrencies, eliminating the complexity barriers that have historically limited mainstream adoption while providing advanced features for power users. #### Key Differentiators * **Self-Custodial Security**: Users maintain complete control over their private keys * **Visa Integration**: Spend crypto anywhere Visa is accepted globally * **Reward Ecosystem**: Multiple earning mechanisms built into daily usage * **Cross-Ecosystem Integration**: Seamless connection with Gaya Blockchain's GameFi, DeFi, SocialFi, and RWA platforms --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://gaya-blockchain.gitbook.io/gaya-blockchain/gaya-wallet.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.