Jump to content
Today Crypto

Crypto stories, filed each day

What does a relayer do in a bridge? Gnosis Bridge explained

What is a bridge relayer? It submits a signed message on the destination chain and pays its gas; validators authorize the message, while the relayer delivers it.

The Today Crypto Editors

What does a relayer do in a bridge? Gnosis Bridge explained

A relayer submits a signed cross-chain message to its destination chain and pays the transaction gas; in the Arbitrary Message Bridge (AMB) used by Gnosis Bridge, validators authorize the message and relayers deliver it. For a stuck transfer, this distinction tells you whether the message still needs valid signatures or is waiting for someone to submit it.

The relayer watches for events on the source chain, obtains the required signatures, then sends a transaction to the destination bridge contract. That transaction carries the message and signatures for the destination contract to check. Comparing the cost of that destination transaction with gnosis bridge fees helps separate who pays to deliver a message from the bridge’s fees. On Gnosis Bridge, those costs arise in different parts of the transfer.

Relayers deliver messages; validators authorize them

Bridge validators sign a message to attest that it came from an accepted source-chain event. The destination contract checks those signatures against the validator set and the required threshold. The transaction sender is not the authority for the message: anyone who can submit the required signed message can trigger that verification.

  • Source event: records the message on the originating chain.
  • Validator signatures: attest to the message the bridge should accept.
  • Relayer transaction: carries the message and signatures to the destination contract and pays its gas.

These roles can sit in the same operational process, but they answer different questions. Signatures establish whether the destination should accept the message; submission determines when the destination gets a chance to execute it. The signatures cover the message hash, so a relayer cannot change the signed message and still have it pass verification.

Who relays messages in each Gnosis Bridge direction?

From Ethereum to Gnosis Chain, bridge validators’ oracle software listens for the source event, gathers signatures and executes the message on Gnosis Chain. The oracle process delivers the message, while validator signatures provide its authorization.

From Gnosis Chain to Ethereum, the user can act as the relayer: once the required signatures are collected, whoever submits the claim transaction on Ethereum causes the destination contract to check them and execute the message. That submitter pays Ethereum gas. The submitter does not need to be the person who initiated the original cross-chain message.

Relayer vs validator in a bridge

A validator signs; a relayer submits. The difference matters when a message is pending. If the signatures have not reached the required threshold, delivery cannot make the destination accept it. If the signatures are ready but nobody submits the destination transaction, the message is waiting on delivery instead.

Confusing the roles can send you to the wrong party: asking a relayer to provide validator authorization will not complete an unsigned message, while asking validators to fix a ready claim may not resolve a missing destination transaction.

Who pays gas for a relayed message?

The account that sends the destination transaction pays that chain’s gas. For an Ethereum-to-Gnosis message, the validators’ oracle software executes the destination transaction; for a Gnosis-to-Ethereum claim, the person who submits it pays Ethereum gas. The party paying gas can differ from the user who started the message.

A relayer is a liveness dependency, not a safety authority. If relaying stops, signed messages wait for submission; once the required signatures exist, the message remains claimable by a submitter. The relayer can delay delivery, but it cannot alter the signed content and have the destination contract accept the altered message.