Bridge signer-set change proposed/executed

Evidence summary #

T-09 v1 launch signal. Sushi does not operate a canonical bridge. SushiXSwap v1/v2 routes via Stargate/LayerZero (third-party). Signal applies to Stargate or LayerZero signer-set changes that would affect SushiXSwap routing. No unscheduled Stargate or LayerZero signer-set change detected as of 2026-05-17. Data-cache layerzero.present: false (pipeline scope; SushiXSwap v2 uses LayerZero externally as a dependency, not as an OApp). Sushi has no direct control over bridge signer sets.

Sources #

Methodology #

Detect whether a bridge validator or signer-set change has been proposed or executed.

See the full factor methodology and distribution across all protocols →