Constructor args match governance proposal

Evidence summary #

Cosmos SDK upgrades use on-chain MsgSoftwareUpgrade proposals with declared upgrade height and plan JSON. V2 (Jun 12 proposal → Jun 16 activation) and V4 (Proposal #18, Nov 2025) both had on-chain proposals. However, independent verification of upgrade-plan-declared-binary vs. actually-deployed binary not performed at this tier. The Cosmos SDK upgrade mechanism is inherently transparent (on-chain proposal with version string), but binary hash attestation was not independently verified.

Sources #

Methodology #

Determine whether the deployed contract's constructor arguments match what the governance proposal or deploy announcement stated.

See the full factor methodology and distribution across all protocols →