# Bridging Process with Hyperlane Warp Routes

When a user initiates a token transfer across chains, the process follows these steps:

1. **Message Sending**: The user calls `transferRemote` on the Warp Route contract, specifying the destination chain and recipient
2. **Token Handling**: Depending on the Warp Route type:
   * Native tokens are locked in the contract
   * ERC20 tokens are transferred to the contract
   * Synthetic tokens are burned
3. **Message Dispatch**: The Warp Route sends a message through the Hyperlane Mailbox with token details
4. **Validator Attestation**: Validators in the Gelato Hyperlane Cluster sign the message
5. **Message Relay**: The Gelato Hyperlane Relayer delivers the message to the destination chain
6. **Security Verification**: The ISM on the destination chain verifies validator signatures
7. **Token Release**: The destination Warp Route contract mints or releases tokens to the recipient