External keeper/relayer not redundant
PancakeSwap'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 #
LayerZero V1 default relayer (LayerZero Labs) is a single-relayer dependency for CAKE bridging. If LayerZero Labs' relayer goes down, CAKE cross-chain transfers freeze. Predictions: Chainlink oracle network is multi-node (not a single keeper), but prediction round execution may depend on a keeper calling executeRound(). ApolloX manages its own keeper for perps. Rate-limiting caps exist for bridge (partial mitigant).
Sources #
- EtherscanCakeProxyOFT readContractCakeProxyOFT: chainIdToOutboundCap, chainIdToInboundCap — daily rate limits exist as mitigantretrieved 2026-04-28
- Secure integration with LayerZero — Composable SecuritySearch result: 'In practice, almost no one built alternative relayers...most applications defaulted to using LayerZero Labs' relayer'retrieved 2026-04-28
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 →