# Background and Problem Statement This section outlines the core motivations behind the creation of Heima. It explores the challenges faced by both users and developers operating within today’s fragmented multichain environment, where **cross-chain interactions, pricing inconsistencies, and the lack of automation** create significant friction. You’ll also learn how Heima addresses these issues through a **modular, intent-driven architecture** and how it compares to existing chain abstraction approaches, highlighting where they fall short and why a more comprehensive solution is needed. Summarily, this section will: * Outline the **key problems** users and developers face in the current multichain ecosystem. * Introduce Heima’s approach to solving them through a four-part architecture: Heima Network, Account Abstraction, Chain Abstraction, and a programmable Agent Hub. * Compare existing chain abstraction models and highlight their **limitations** in scalability, security, and UX. By understanding the depth of these issues and the limitations of current solutions, the need for a system like Heima becomes clear: a modular, programmable coordination protocol that enables truly seamless, cross-chain interactions for the next generation of decentralized applications. --- # 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/background-and-problem-statement.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.