> For the complete documentation index, see [llms.txt](https://docs.defi.app/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.defi.app/knowledge-base/introduction/core-features.md). # Core Features Defi App is a standout choice for anyone looking to move away from centralized exchanges (CEX) and traditional wallets. Why? ### Wallet Abstraction & Unified Management Manage multiple wallets—both EVM and Solana—under one streamlined interface, making it easy to switch between them as needed. Defi App creates both an EVM and Solana wallet for new users, allowing you to get started immediately without the hassle of wallet setup. *** ### Gasless Transactions Defi App sponsors gas fees, removing the need for users to hold specific gas tokens, simplifying transactions across different chains. *** ### Seamless Swaps Across Chains Swap tokens seamlessly across different chains without needing to deal with gas tokens, bridges, or slippage. *** ### Cross-Chain Compatibility Manage assets seamlessly across both EVM and Solana ecosystems without switching between platforms. Cross-chain swaps are executed behind the scenes, eliminating the need for users to manage bridging or token compatibility manually. --- # 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.defi.app/knowledge-base/introduction/core-features.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.