What Is a Bridge Committee, and How Does It Work?
A bridge committee in cross-chain bridges is a group of signers that verifies source-chain deposits; enough signatures let the destination execute a transfer.
Web3 News Editorial2 min read

A bridge committee is a set of signers that watches a source chain and approves transfers, because the destination chain cannot read source-chain activity directly. Suibridge is a concrete example: its lock-and-mint process moves supported assets from Ethereum to Sui. The destination acts only after enough committee signatures approve the same transfer message.
Committee members sign a shared transfer message
A bridge committee turns a source-chain deposit into a message the destination can check. Each member independently observes the deposit event, then signs the message describing that transfer. Signatures count toward a threshold; once they reach it, the approved message can execute on the destination.
Think of a team reconciling a shared payment record: several people check the same receipt, and the receiving system accepts it only after enough authorized people approve it. The committee supplies those approvals across chains. It is not the destination chain reading Ethereum for itself.
Suibridge uses Sui validator stake for approvals and pauses
In Suibridge, Sui validators make up the committee, and their voting weight follows stake. When someone deposits a supported asset on Ethereum, validators observe the deposit and sign its transfer message. The asset mints on Sui only after the signatures reach the stake-weighted threshold.
- Deposit event: The source-chain record starts the transfer.
- Validator signatures: Committee members attest to the same transfer message.
- Threshold: The required share of stake makes the message eligible for execution on Sui.
An approved transfer leaves an on-chain record that a team can match to its Ethereum deposit. That record helps reconcile deposits with destination mints; the committee’s signatures are the approvals that authorize execution.
A pause uses a much smaller share of committee voting power than a restart. That lets a few members halt transfers quickly, while resuming requires broad agreement. For a team bridging regularly, a pause means transfers have stopped pending that wider approval; it does not by itself identify which deposit is affected. Treat the pause and restart as separate approval thresholds.
The committee is easy to confuse with the destination’s transaction validators. Here, the committee’s job is to attest that a source-chain transfer occurred; the destination executes the message after the threshold is met. When reconciling a transfer, match the Ethereum deposit to its on-chain record on Sui, so a pending or paused approval is not mistaken for a completed mint.