The relayer exists to make destination claims easier for users. It validates the request and submits the on-chain transaction asynchronously.

​
Direct claim

Direct routes need only:
  • order_id
  • 32-byte secret
The relayer checks that the secret hashes to the destination intent’s commitment hash and that the destination vault is ready.

​
Hop claim

Avalanche hop routes also need:
  • recipient signature
  • destination blockchain ID
  • destination bridge factory
  • final recipient
  • fee token and amount
The signature must match the authorization hash verified by AvalancheEscrowVault. 
keccak256(
  abi.encode(
    HOP_AUTHORIZATION_TYPEHASH,
    chainId,
    vault,
    commitmentHash,
    bridgeFactory,
    destBlockchainId,
    recipient,
    primaryFeeToken,
    primaryRelayerFee
  )
)
The recipient signs this hash with EIP-191 personal_sign.
Do not let clients freely edit hop destination fields after the user signs. The relayer checks them against stored order and registry data, and the vault verifies the signature.

​
Accepted does not mean mined

POST /claims returns 202 Accepted when the relayer has queued the transaction. It does not mean the transaction is mined. Continue polling the orderbook until the claim transaction is indexed.