> For the complete documentation index, see [llms.txt](https://docs.accumulated.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.accumulated.finance/accumulated-evm/aevm.md). # AEVM {% hint style="info" %} AEVM is currently on the devnet phase {% endhint %} ### Overview Accumulated EVM (AEVM) is Accumulated Finance’s native application-specific blockchain, purpose-built to optimize liquid staking and DeFi operations. It serves as the backbone for the protocol, enabling seamless cross-chain interactions for Liquid Staking Tokens (LSTs) across EVM-compatible networks. AEVM delivers unparalleled scalability, low transaction costs, and robust infrastructure, ensuring efficient execution of staking, lending, and leverage staking within the Accumulated Finance ecosystem. ### Key Features * **App-Chain Design**: Tailored specifically for Accumulated Finance’s liquid staking and DeFi functionalities. * **Cross-Chain Interoperability**: Supports LST transfers and operations across EVM-compatible blockchains. * **Scalability**: Handles high transaction volumes with minimal latency. * **Low-Cost Transactions**: Reduces gas fees for users compared to general-purpose EVM chains. * **Governance Integration**: Facilitates $ACFI token-based governance for protocol decisions. --- # 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://docs.accumulated.finance/accumulated-evm/aevm.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.