> For the complete documentation index, see [llms.txt](https://docs.cakewallet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cakewallet.com/cupcake/cupcake.md). # Cupcake Cupcake turns an old iOS or Android phone into an air-gapped hardware wallet that signs for Cake Wallet. Supports Monero, Bitcoin, and Litecoin with MWEB. Cupcake is the latest app in the Cake Wallet family, focused on making crypto security possible for everyone. No more waiting weeks for shipping and customs, no more $200+ costs, no more terrifying data breaches. If you have an old phone lying around, Cupcake lets you turn it into a powerful hardware wallet with just a few taps. It works similarly to an air-gapped hardware wallet, separating the private keys from the main wallet app and becoming a dedicated signer. Cupcake contains the private keys for transaction signing, while Cake Wallet has only the view keys (or public keys) necessary to see your balance, historical transactions, and generate new transactions for Cupcake to sign. ## Download Cupcake can be downloaded from the [App Store](https://apps.apple.com/eg/app/cupcake-by-cake-wallet/id6737430272), [Play Store](https://play.google.com/store/apps/details?id=com.cakewallet.cupcake), and the [GitHub repo](https://github.com/cake-tech/cupcake/releases). Cupcake is currently only supported on iOS and Android. ## Supported cryptocurrencies Cupcake supports: * **Monero** * **Bitcoin** * **Litecoin** (including MWEB) More cryptocurrencies will be supported in the future. --- # 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.cakewallet.com/cupcake/cupcake.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.