Admin/upgrade transaction in mempool

Babylon Protocol's assessment for RD-F-102 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

Babylon Genesis chain upgrades execute via Cosmos SDK x/gov software upgrade proposals — not EVM admin transactions in mempool. No EVM mempool to monitor. Cosmos SDK upgrade path: proposal → voting period (3 days) → validator coordination → upgrade at specified block height. No admin-EOA-in-mempool pattern applicable. Signal structurally inapplicable in EVM form.

Sources #

Docs
Babylon Governance Documentation — Software Upgrade ProcessBabylon governance docs — upgrade process via on-chain governance, no EVM mempool patternretrieved 2026-05-04

Methodology #

Detect an admin-role or upgrade transaction appearing in the mempool before confirmation.

See the full factor methodology and distribution across all protocols →

rubric_version v1.7.0 protocol babylon-protocol factor RD-F-102 score gray collected_at 2026-05-04 19:43:27