Nibiru governance and upgrades

Workflow: How to Use this Skill

Start with the canonical query bundle in Quick start (mainnet). That is the default first step when the user asks about a proposal and you need the core governance state.

After that, choose the recipe that matches the user’s question:

1. For a live proposal’s voting properties, use Recipe: Show voting and quorum info for a live proposal. This is the fast path when the user wants a voting and quorum summary instead of only raw proposal or tally JSON.
2. For governance thresholds in the same output, use reference.md#explorer-style-quorum-report.
3. If the proposal is a software upgrade, use Software-upgrade proposal: extract plan (name/height/info/binaries) to inspect plan.name, plan.height, and parsed binaries from plan.info.
4. If the user wants validator-only participation rather than all voters, use Validator votes (filter votes to validator set).

Additional resources

• Quorum, threshold, and veto: reference.md#quorum-threshold-and-veto
• Explorer-style quorum report: reference.md#explorer-style-quorum-report

Quick start (mainnet)

1. Configure CLI for mainnet (uses your ud wrapper):

ud nibi cfg prod
nibiru config

This selects the default, non-archive mainnet RPC and JSON output. Keep the default RPC for current proposal state. Use ud nibi cfg prod --archive only for a read-only historical query whose data has been pruned, then restore the default RPC with ud nibi cfg prod.

2. Pick a proposal id:

ID=27

3. Run the canonical set of queries (JSON output):

nibiru q gov proposal "$ID"
nibiru q gov votes "$ID" --limit 1000
nibiru q gov tally "$ID"
nibiru q gov deposits "$ID"
nibiru q gov params

nibiru q staking pool
nibiru q staking validators --limit 1000

Mapping: “Proposal #27” explorer fields → on-chain queries

• Proposal metadata (status, times, title/summary, total_deposit, proposer):

  • nibiru q gov proposal "$ID"
  • Example fields: .status, .submit_time, .voting_end_time, .title, .summary, .total_deposit, .proposer

• Deposits table:

  • nibiru q gov deposits "$ID"

• Votes table (all votes, incl. weighted):

  • nibiru q gov votes "$ID" --limit 1000

• Current tally (yes/no/veto/abstain counts):

  • nibiru q gov tally "$ID"

• Quorum/threshold/veto thresholds:

  • nibiru q gov params (or nibiru q gov param voting|deposit|tallying)

• Bonded voting power denominator (for quorum math):

  • nibiru q staking pool (use .bonded_tokens)

Software-upgrade proposal: extract plan (name/height/info/binaries)

Nibiru mainnet currently surfaces software upgrades as a gov v1 proposal that executes legacy content (you’ll typically see MsgExecLegacyContent wrapping a SoftwareUpgradeProposal).

Extract the upgrade plan:

nibiru q gov proposal "$ID" | jq '
  .messages[]
  | select(."@type" == "/cosmos.gov.v1.MsgExecLegacyContent")
  | .content
  | select(."@type" == "/cosmos.upgrade.v1beta1.SoftwareUpgradeProposal")
  | .plan
'

Parse the binaries object out of plan.info (it’s a JSON string):

nibiru q gov proposal "$ID" | jq -r '
  .messages[]
  | select(."@type" == "/cosmos.gov.v1.MsgExecLegacyContent")
  | .content
  | select(."@type" == "/cosmos.upgrade.v1beta1.SoftwareUpgradeProposal")
  | .plan.info
  | fromjson
  | .binaries
'

Recipe: Show voting and quorum info for a live proposal

Quick command:

jq -s '
  .[0] as $t
  | .[1] as $p
  | ($p.bonded_tokens|tonumber) as $bonded
  | ($t.yes_count|tonumber) as $yes
  | ($t.no_count|tonumber) as $no
  | ($t.abstain_count|tonumber) as $abstain
  | ($t.no_with_veto_count|tonumber) as $veto
  | ($yes+$no+$abstain+$veto) as $total
  | {
      bonded_tokens: $bonded,
      total_voted_tokens: $total,
      quorum_pct: (if $bonded==0 then null else ($total / $bonded * 100) end),
      yes_pct_of_non_abstain: (
        if ($yes+$no+$veto)==0 then null
        else ($yes / ($yes+$no+$veto) * 100)
        end
      ),
      veto_pct_of_non_abstain: (
        if ($yes+$no+$veto)==0 then null
        else ($veto / ($yes+$no+$veto) * 100)
        end
      )
    }
' <(nibiru q gov tally "$ID") <(nibiru q staking pool)

Raw sources:

• nibiru q gov tally "$ID" for current vote weights
• nibiru q gov params for quorum / threshold / veto parameters
• nibiru q staking pool for bonded_tokens

For a fuller report with governance thresholds and field notes, see reference.md#explorer-style-quorum-report and reference.md#field-meanings.

Validator votes (filter votes to validator set)

nibiru q gov votes includes all voters (delegators + validators). To match “Validators Votes” UIs, filter to validator accounts by converting each validator’s nibivaloper... to its corresponding nibi... address.

Helpers:

# Shows both Bech32 Acc (nibi...) and Bech32 Val (nibivaloper...)
nibiru debug addr nibi1ah8gqrtjllhc5ld4rxgl4uglvwl93ag0sh6e6v

Example report (bonded validators who voted on $ID):

ID=27
VOTES_JSON="$(nibiru q gov votes "$ID" --limit 1000)"
VALS_JSON="$(nibiru q staking validators --limit 2000)"

echo "$VALS_JSON" \
  | jq -r '.validators[] | select(.status=="BOND_STATUS_BONDED") | .operator_address' \
  | while read -r valoper; do
      acc="$(nibiru debug addr "$valoper" | sed -n 's/^Bech32 Acc: //p')"
      vote="$(echo "$VOTES_JSON" | jq -c --arg acc "$acc" '.votes[] | select(.voter==$acc) | {voter, options}')"
      if [[ -n "$vote" ]]; then
        moniker="$(echo "$VALS_JSON" | jq -r --arg valoper "$valoper" '.validators[] | select(.operator_address==$valoper) | .description.moniker')"
        tokens="$(echo "$VALS_JSON" | jq -r --arg valoper "$valoper" '.validators[] | select(.operator_address==$valoper) | .tokens')"
        echo "$moniker $valoper $acc tokens=$tokens vote=$vote"
      fi
    done

Governance transactions (tx)

Run ud nibi cfg prod before any governance transaction. Do not broadcast through an archive RPC.

• Vote:

nibiru tx gov vote "$ID" yes --from <key-or-addr>

• Weighted vote:

nibiru tx gov weighted-vote "$ID" yes=0.6,no=0.3,abstain=0.1 --from <key-or-addr>

• Deposit:

nibiru tx gov deposit "$ID" 1000000unibi --from <key-or-addr>

• Submit a software-upgrade proposal (legacy content path):

nibiru tx gov submit-legacy-proposal software-upgrade v2.11.0 \
  --title "v2.11.0" \
  --description "Upgrade to v2.11.0" \
  --deposit 20000000000unibi \
  --upgrade-height 36757700 \
  --upgrade-info '{"binaries":{"linux/amd64":"https://...","linux/arm64":"https://...","docker":"ghcr.io/...:2.11.0"}}' \
  --from <key-or-addr>

Upgrade module queries (after a proposal passes)

• nibiru q upgrade plan only works once an upgrade is scheduled in x/upgrade. Before then, it can return “no upgrade scheduled”.