# Multi-Chain Features

## Why Multichain?

The decision to adopt a multichain approach is driven by our commitment to inclusivity, flexibility, and resilience. By operating across multiple chains, our protocol ensures:

1. **Wider Accessibility**: Users from different blockchain ecosystems can interact without the need for complex peer-to-peer solutions.
2. **Enhanced Security**: Distributing operations across various chains reduces the risk of systemic failures and enhances the security of the protocol.
3. **Optimized Performance**: Each blockchain has unique attributes; by leveraging their individual strengths, our protocol optimizes performance and efficiency.

<figure><img src="/files/ZfDaSyTRL7sQAlosUNse" alt=""><figcaption></figcaption></figure>

## Supported Chains

**Solana**

* **High Throughput**: Solana's high-performance blockchain offers fast and cost-effective transactions, ideal for high-frequency operations.
* **Unique Features**: Our protocol harnesses Solana's innovative features like Proof of History (PoH) to enhance transaction efficiency.

**Sei**

* **Optimized for DeFi**: Sei's architecture, specifically designed for DeFi applications, aligns perfectly with our protocol.
* **Customizability**: The flexibility of Sei's network allows for tailored optimizations, enhancing our protocol's performance in DeFi-centric use cases.

**Ethereum**

* **Widespread Adoption**: As the most established blockchain for smart contracts, Ethereum's extensive user base provides significant exposure and adoption potential.
* **Ecosystem**: Ethereum's mature ecosystem offers well-developed tools and services that complement our protocol's functionalities.

**EVM-Compatible Chains**

* **Interoperability**: EVM compatibility ensures that our protocol can be easily deployed on any EVM-based chain, facilitating seamless cross-chain interactions.
* **Diverse Ecosystems**: This compatibility allows us to tap into various niches and communities across different EVM chains.

**Blast**

* soon


---

# 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://pier-protocol.gitbook.io/pier-protocol/introduction/multi-chain-features.md?ask=<question>
```

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.