External keeper/relayer not redundant
Balancer (v2 + v3)'s assessment for RD-F-062 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Balancer does not require keepers or relayers for core AMM operations. Swaps are permissionless — any address can interact with the Vault directly. v2 GaugeController (0xC128468b7Ce63eA702C1f104D55A2566b13D3ABD) distributes gauge emissions but BAL emissions are being ended per March 2026 DAO decision. v3 ProtocolFeeController (0xa731C23D7c95436Baaae9D52782f966E1ed07cc8) manages fee collection but is not a keeper dependency. No single keeper/relayer that causes protocol halting on failure.
Detail #
Template: green = permissionless operation or multiple independent keeper providers. Balancer's AMM is fully permissionless for swaps. Gauge system is peripheral.
Sources #
- EtherscanBalancer GaugeController — Etherscanv2 GaugeController 0xC128468b7Ce63eA702C1f104D55A2566b13D3ABD — gauge emissions onlyretrieved 2026-05-05
- v3 ProtocolFeeController — Etherscanv3 ProtocolFeeController 0xa731C23D7c95436Baaae9D52782f966E1ed07cc8retrieved 2026-05-05
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 →