> For the complete documentation index, see [llms.txt](https://kawa-fi.gitbook.io/kawa/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kawa-fi.gitbook.io/kawa/overview/kawa-core.md). # Kawa Core Kawa Core is the central component of Kawa's cross-chain infrastructure, serving as the primary state for user balances. Hosted on the Sei blockchain, Kawa Core manages actions that affect the value locked in the protocol, such as borrowing and withdrawing transactions. ### **Key Components** * **Master State**: Kawa Core is the master state for user balances, ensuring a reliable and accurate representation of user assets across the platform. * **Sei Blockchain**: The Sei blockchain hosts Kawa Core, providing a robust and secure foundation for the platform's main state. * **Transaction Management**: Actions reducing value locked in the protocol, such as borrowing and withdrawing transactions, must originate from Kawa Core. Meanwhile, actions crediting value to the protocol are received and validated by the XCM Aggregator after being sent by a Kawa Port. * **Sei Wallet Integration**: All users are required to have a Sei wallet to interact with Kawa's platform. The Kawa user interface (UI) is designed to abstract away any complexities, streamlining the process into as few transactions as possible. --- # 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://kawa-fi.gitbook.io/kawa/overview/kawa-core.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.