# Why Sei? The Kawa Protocol is built on the Sei blockchain due to its unique and advantageous features that make it an ideal environment for Kawa's design. Here, we will discuss the reasons behind choosing the Sei blockchain over other EVM-based blockchains. * **Instant Finality**: Sei blockchain offers instant finality, which means that transactions on Sei are confirmed immediately. This feature is particularly useful for the Kawa Protocol, as it allows users to quickly deposit, borrow, and withdraw assets across multiple chains, improving the overall user experience. * **Scalability**: The Sei blockchain has been designed to scale efficiently, allowing it to handle a large number of transactions without sacrificing performance. This scalability is crucial for Kawa, as it aims to support a growing number of assets and blockchains. * **Security**: Sei offers a secure environment for Kawa, providing robust protection against potential attacks and vulnerabilities. This is essential for maintaining user trust and ensuring the safety of users' funds. * **Interoperability**: One of the key features of the Kawa Protocol is its ability to support multiple chains, enabling seamless access and communication across different blockchains. Sei's focus on interoperability makes it a perfect fit for Kawa's vision. * **Growing Ecosystem**: Although Sei is relatively new compared to other blockchains, its ecosystem is rapidly expanding, with numerous projects and applications being developed on the platform. By building on Sei, Kawa can tap into this growing ecosystem and leverage its growth potential. In summary, the Sei blockchain offers instant finality, scalability, security, interoperability, and a growing ecosystem, making it an ideal environment for the Kawa Protocol. \ \ Building on Sei allows Kawa to deliver a seamless experience for users, supporting the cross-chain borrowing and lending of assets, and fostering a thriving, interconnected DeFi 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://kawa-fi.gitbook.io/kawa/overview/why-sei.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.