# Why Hashi? As decentralized applications (dApps) increasingly interact with multiple blockchains, ensuring the security of cross-chain communication is more important than ever. Traditional solutions often face security challenges due to reliance on a single oracle or validator, introducing vulnerabilities and risks. **Hashi** addresses these challenges with its unique approach, which focuses on leveraging multiple oracles and secure block relaying to guarantee reliable cross-chain interactions. #### **Secure Block Relaying** One of Hashi's core functions is its **block relaying mechanism**, which allows it to securely transmit **block headers** from one chain to another. This process ensures that dApps working across chains can verify the validity of blockchain states with confidence. Instead of relying on individual messages, Hashi enables the transfer of block headers, ensuring data integrity through cryptographic verification. #### **Multi-Oracle Validation** Hashi further enhances security by requiring **multiple independent oracles** to validate and agree on the authenticity of block headers. This multi-oracle model significantly reduces the risks of depending on a single entity and increases the robustness of cross-chain transactions. #### **Avoiding Vendor Lock-In** Hashi serves as an **abstraction layer** between your dApp and the underlying oracles or relayers, meaning you’re not tied to any one provider. This flexibility allows developers to integrate multiple oracles from various vendors without the fear of vendor lock-in. Hashi abstracts the complexity, enabling seamless switching between oracles while maintaining the security of your cross-chain interactions. This way, you're always in control, and as new oracles emerge, you can easily adopt them without restructuring your dApp. #### **Reducing Single Points of Failure** In contrast to traditional cross-chain solutions that often rely on a single validator, Hashi distributes trust across multiple oracles. This significantly mitigates the risk of a single point of failure, ensuring that the security of your cross-chain transactions doesn’t hinge on one entity. #### **Scalable Security** Hashi’s **additive security model** allows you to scale the level of security according to your needs. By involving more oracles in the validation process, you can dynamically increase the security for high-value transactions or sensitive data, making Hashi adaptable for both simple and complex cross-chain applications. *** #### **Who Should Use Hashi?** * **Cross-Chain Application Developers**: Hashi provides a reliable, secure solution for developers building dApps that interact across multiple blockchains. * **Interoperability-Focused Projects**: For teams needing cross-chain verification, Hashi’s abstraction layer and multi-oracle setup ensure flexibility and security. * **Bridge Operators**: Hashi allows for robust security through its multi-oracle architecture, offering a solution that reduces the risks associated with traditional cross-chain bridges. Hashi is built to provide **flexibility, scalability, and security**. Its multi-oracle, block-relaying architecture ensures that your cross-chain interactions are safe, reliable, and free from vendor lock-ins, giving you the freedom to innovate and adapt as the blockchain ecosystem evolves. --- # 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://crosschain-alliance.gitbook.io/hashi/introduction/why-hashi.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.