Role separation: upgrade ≠ fee ≠ oracle

Evidence summary #

All role types (upgrade, fee parameters, oracle config) are governed by the same BABY governance module — no separate role holders. Oracle is not applicable (no price oracle in core protocol). Upgrade role = governance. Fee parameters changed via governance (Proposal #8 reduced unbonding fees). Role separation is structurally absent in a pure on-chain governance model without granular role contracts. Not a data gap — structural architecture of Cosmos SDK x/gov.

Sources #

Methodology #

Determine whether the upgrade role, fee-collection role, and oracle-config role are assigned to distinct addresses.

See the full factor methodology and distribution across all protocols →