Protocol
sBridge

Relayers

Permissionless proof messengers: stateless, keyless, censorship-resistant

The relayer is the message-passing layer of sBridge, a stateless proof messenger with no keys and no authority. It detects lock events on source chains, constructs Merkle proofs, and submits them to SBChain for independent verification. The relayer cannot fabricate valid proofs; validity is verified by SBChain's consensus nodes, not taken on the relayer's word.

What Relayers Do

  • Monitor source chains (Ethereum, Solana, Bitcoin, Tron, SBT) for lock and burn events
  • Construct the appropriate Merkle or SPV proof for each detected event
  • Submit the proof to SBChain via a standard broadcast transaction
  • Collect a relayer fee for successful proof delivery (paid by the bridge user)

What Relayers Cannot Do

  • Fabricate a valid Merkle proof for an event that did not happen on-chain
  • Censor a transfer permanently — any other relayer can submit the same proof
  • Access, hold, or move user funds — relayers carry no key material
  • Affect the validity check — SBChain nodes verify proofs independently against block headers

Permissionless Operation

Relayers are permissionless. Anyone can operate one. If every SwapBlok-operated relayer went offline simultaneously, any third-party relayer could continue submitting proofs and the bridge would function normally. There is no whitelist, no registration, and no special permission required to relay proofs.

Proof Types by Chain

ChainProof Type
EthereumMerkle-Patricia trie proof
SolanaMerkle tree inclusion proof
BitcoinSPV Merkle proof
TronMerkle block proof
SBChainNative SBChain block proof