Large governance proposal queued
Beefy Finance's assessment for RD-F-101 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
T-09 v1 production signal (tier-B). Signal requires on-chain ProposalCreated/ProposalQueued events on a tracked Governor contract. Beefy has no on-chain Governor (governor_address: null; governance type: snapshot_only per data-cache). Governance is purely Snapshot-based; all execution goes through the dev multisig (3-of-6) manually. There is no on-chain proposal queue to monitor. The malicious-pattern sub-checks (flash-loanable quorum, delegatecall in calldata, role-change selectors via Governor calldata) are all architecturally moot.
Sources #
- DocsBeefy Contracts and TimelocksBeefy docs — contracts-and-timelocks: no standalone timelock, no Governorretrieved 2026-05-16
- Beefy data cache — governance struct00-data-cache.json — sources.governance: {type: snapshot_only, governor_address: null, timelock_address: null}retrieved 2026-05-16
Methodology #
Detect whether a governance proposal with potentially protocol-impactful payload has been queued for execution (including Security-Council threshold-reduction variant).
See the full factor methodology and distribution across all protocols →