SODAX Symbol
BETA

Relayer

The Relayer is the distributed signing and transaction submission layer that delivers verified cross-network messages within SODAX.

relayerbridge layermessagingcross-networksystem

What it is

The Relayer is the infrastructure component that transports and submits authenticated cross-network messages.

It works alongside the Generalized Messaging Protocol (GMP) to ensure that instructions created on one network are verified and executed on another.

The Relayer does not define message rules. Those are defined by GMP. It is the signer and submission layer that turns verified messages into on-chain transactions.

What it does inside SODAX

Within SODAX, the Relayer performs two core functions:

  • It collects and verifies signatures from an authorized signer set.
  • Once the required threshold is reached, it submits the corresponding transaction on the destination network.

When a contract emits a cross-network message, the Relayer infrastructure observes it, gathers signatures, and triggers the appropriate destination contract call. That destination contract then verifies the message through GMP before executing its logic.

The Relayer does not calculate routes, determine pricing, or decide how liquidity inventory is used. It does not move assets directly. It delivers verified instructions that allow destination contracts to act.

Why it exists

Blockchains do not natively observe each other. A contract on one network cannot automatically trigger logic on another network without an external actor. The Relayer exists to bridge this gap.

By separating:

  • Instruction definition (GMP),
  • Decision logic (Solver),
  • Asset movement (Asset Manager),
  • And message delivery (Relayer),

SODAX maintains clear architectural boundaries. The Relayer converts off-chain signature consensus into on-chain execution.

What this means for users and partners

For users, the Relayer is invisible. It ensures that once a cross-network action is initiated, the required contract calls are delivered and executed on the destination network.

For builders, it clarifies that cross-network execution relies on a distributed signer set rather than direct chain-to-chain communication.

Component boundaries remain explicit:

  • GMP defines how messages are verified.
  • The Relayer collects signatures and submits transactions.
  • The Solver determines how an Intent should be fulfilled.
  • The Asset Manager moves assets.
  • The Hub records final settlement state.

The Relayer delivers instructions. It does not define them, reason about them, or hold value.

Last updated: 2/19/2026