Large governance proposal queued

Veda (BoringVault)'s assessment for RD-F-101 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

Veda has no on-chain Governor contract (data cache governor_address = null, snapshot_space = null). Per-vault governance is via RolesAuthority admin ACL, not a Governor proposal queue. Signal requires an on-chain Governor with ProposalCreated/ProposalQueued events — structurally inapplicable to Veda's architecture. Admin ACL changes on RolesAuthority are an F102-class (mempool) signal, not an F101-class (governance proposal) signal.

Sources #

Internal
Veda data cache 00-data-cache.json governanceData cache sources.governance: type='unknown', governor_address=null, timelock_address=null, snapshot_space=null — no Governor architectureretrieved 2026-05-17

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 →

rubric_version v1.7.0 protocol veda factor RD-F-101 score gray collected_at 2026-05-17 12:41:22