Bridge signer-set change proposed/executed
Compound V3 (Comet)'s assessment for RD-F-103 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Compound V3 is not a canonical configurable-signer bridge. Native L2 governance relay bridges (Arbitrum Inbox, OP Messenger) do not expose user-configurable signer sets. Community MultiSig threshold stable at 5-of-9 per data cache (2026-04-27). No threshold change event detected.
Detail #
RD-F-103 targets configurable bridge signer sets (e.g., Wormhole guardians, LayerZero oracles, Axelar validators). Compound V3 uses native L2 bridges for governance message-passing only — user assets are not bridged, and the relay mechanism does not expose an independent signer-set. The Community MultiSig (0xbbf3f1421D886E9b2c5D716B5192aC998af2012c) serves as Pause Guardian and Proposal Guardian — threshold changes here would be covered under RD-F-182. No SignerAdded/SignerRemoved/ThresholdChanged events detected on Community MultiSig in last 30 days (data cache Safe API: threshold=5, owner_count=9, unchanged as of 2026-04-27T03:38:24Z).
Sources #
- URLhttps://etherscan.io/address/0xbbf3f1421d886e9b2c5d716b5192ac998af2012cretrieved 2026-04-27
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 →