> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hyperlane.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Dispatch Fees

> Understanding origin and interchain fees for Hyperlane cross-chain transfers

## Fee Estimation

When sending a cross-chain message with Hyperlane GMP, two fees are paid:

1. **Origin Fee** – transaction fee on the origin chain (charged by the blockchain)
2. [**Interchain Fee**](/docs/protocol/core/interchain-gas-payment) – charged by relayer to cover destination chain transaction fees

This fee structure ensures that:

1. The user has enough funds to pay for the origin transaction
2. The cross-chain message will have enough gas to execute on the destination chain and pay for the message delivery
3. The total cost of the transfer is transparent to the user before execution

#### Fee Token Considerations

When sending cross-chain messages, the fee tokens vary by origin chain type and IGP:

1. **EVM Chains**

   * Uses native gas token (e.g., ETH) for both origin and interchain fees

2. **Sealevel (Solana) Chains**

   * Uses native gas token (e.g., SOL) for both origin and interchain fees

3. **Cosmos Chains**

   * Supports custom tokens; fees are specified using the `denom` parameter on an IGP
   * Fees are specified using the `denom` parameter

<Note>
  Read more about transfer fees and calculations:

  * [Interchain Gas Payment](/docs/protocol/core/interchain-gas-payment) - Handling gas payments between chains and relayer fees
  * [Post Dispatch Hooks](/docs/protocol/core/post-dispatch-hooks-overview) - Framework for executing actions after message dispatch
</Note>

## Warp Route Fees

When using Warp Routes to bridge tokens, there may be additional application fees denominated in the token being bridged.

See [Warp Route Fees](/docs/applications/warp-routes/interface) for more details