# Hyperlane Components
The Gelato Hyperlane Cluster leverages several key components of the Hyperlane protocol.
### **Hyperlane Mailbox**
The Mailbox smart contracts form the foundation of Hyperlane's messaging infrastructure:
* They expose an on-chain API for sending and receiving interchain messages
* Messages are dispatched from the origin chain and delivered to the destination chain
* The Mailbox maintains a merkle tree of all dispatched messages
### **Hyperlane Validators**
Validators are responsible for attesting to the validity of cross-chain messages. They monitor the Mailbox on the origin chain, sign merkle roots that reflect the current state of the Mailbox, and provide cryptographic proofs that messages were actually sent
The Gelato Hyperlane Cluster includes validators operated by Gelato, working alongside validators from Hyperlane, Decent, and other trusted partners.
### **Hyperlane Relayers**
Relayers ensure messages are delivered from the origin chain to the destination. They monitor for dispatched messages on the origin chain, submit messages and validator signatures to the destination chain, and handle gas payments and transaction execution.
Gelato operates dedicated relayers to ensure reliable message delivery for ABC rollups.
### **Interchain Security Modules (ISMs)**
ISMs are smart contracts responsible for verifying that messages delivered to the destination chain were actually sent on the origin chain. They check validator signatures against a known set of trusted validators, can implement various security models (multisig, threshold, etc.), and allow for customizable security settings.
### **Hyperlane Warp Routes**
Warp Routes provide the token bridging functionality. These allow for permissionless transfer of assets across chains and support native tokens, ERC20 tokens, and synthetic assets. Warp Routes can implement different bridging models based on token type.
---
# 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.abundance.xyz/modular-bridging/hyperlane-components.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.