External keeper/relayer not redundant
M^0's assessment for RD-F-062 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Core protocol does not use Gelato or Chainlink Automation keepers. WormholeTransceiver relies on Wormhole Standard Relayer (0x27428dd2d3dd32a4d7f7c497eaaa23130d894911) for cross-chain message delivery — a distributed relay network but with a default relayer dependency. If Wormhole relayers fail, cross-chain transfers stall (manual relay possible). Wormhole guardian set (19 nodes) is the validator dependency for VAA attestation.
Sources #
- EtherscanWormholeTransceiver EtherscanWormholeTransceiver proxy 0x0763196A091575adF99e2306E5e90E0Be5154841 — internal txs show Wormhole Standard Relayer calls to 0x27428dd2d3dd32a4d7f7c497eaaa23130d894911retrieved 2026-05-16
Methodology #
Determine whether the protocol depends on a single keeper or relayer (Gelato, Chainlink Automation, custom) with no redundancy or failover.
See the full factor methodology and distribution across all protocols →