# Introduction **Heima: The Chain Abstraction Protocol for Cross-Chain DEX Trading** It is purpose-built to eliminate the friction, fragmentation, and complexity of interacting with multichain ecosystems. With one omni account, users can manage assets, interact with dApps, and execute transactions across all supported blockchains — without switching wallets, bridging manually, or worrying about native gas tokens. Heima abstracts the complexity of cross-chain interactions through a four-part architecture: the Heima Layer 1 Network, Account Abstraction, Chain Abstraction, and Agent Hub. These components work together to create a modular, intent-centric automation ecosystem. Whether it’s cross-chain trading, staking, or arbitrage, Heima coordinates the execution logic seamlessly behind the scenes — making interactions feel as seamless as a centralized app, while remaining fully decentralized and non-custodial. Think of Heima as an intelligent coordinator behind the scenes. When a user wants to perform an action (like swapping a token or making a payment), they simply express what they want to do, called an “intent.” Heima then figures out the best way to execute that request, no matter which chains are involved. It even handles gas payments automatically, allowing users to pay fees with any token (like USDT/USDC) — eliminating the need to maintain balances of native gas tokens. This section introduces **Heima** and the **HEI Token**, the native utility token that powers the Heima ecosystem. --- # 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://docs.heima.network/overview-what-is-heima/introduction.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.