Transactions and Governance (Cosmos SDK 0.53)

Gonka uses the standard Cosmos SDK CLI with your governance key stored on the dedicated machine you setup when joining the network. This needs to be the cold key you setup here.

Unordered transactions are supported and recommended here to avoid sequence contention. (docs.cosmos.network)

Recommended CLI flags (use these on every `tx` command)

# Set once per shell      # the name in your file keyring (or the bech32 addr)
FLAGS="--from=$FROM --yes \
  --unordered --timeout-duration=60s \
  --gas=2000000 --gas-adjustment=5.0 --keyring-backend=file --node $SEED_API_URL/chain-rpc/"

--unordered + --timeout-duration makes the tx valid for a bounded time and bypasses account sequence ordering (the tx sequence is left unset). This is available from SDK v0.53+. (docs.cosmos.network)
--gas-adjustment lets the CLI overshoot simulation a bit to avoid "out of gas." Tune as needed. (Go Packages, docs.humans.ai)

Vote on a Proposal (quick path)

Most participants only need to verify a proposal and cast a vote. Do these four things:

1) Identify the right proposal_id (and verify it's the one you were told)

List proposals, then inspect the one you were given and cross-check its fields (title/summary/metadata/messages):

# List all proposals (IDs + basic info)
inferenced query gov proposals -o json

# Inspect a specific proposal in detail
inferenced query gov proposal $PROPOSAL_ID -o json

Confirm the id, title, summary, and (if present) metadata match what was shared with you. If the proposal includes embedded messages, you'll also see their @type and fields here. (Cosmos gov v1 stores proposal content on-chain and exposes it via query gov proposal.) (Cosmos SDK Documentation)

2) Review the contents carefully (especially param updates)

If the proposal includes a params update (e.g., MsgUpdateParams), compare the proposed params against the current on-chain params before voting:

# 2a) Get current module params (example: inference module)
inferenced query inference params -o json > current_params.json

# 2b) Extract proposed params from the proposal (adjust jq path if your chain nests differently)
inferenced query gov proposal $PROPOSAL_ID -o json \
  | jq '.proposal.messages[] | select(."type"=="inference/x/inference/MsgUpdateParams") | .value' \
  > proposed_params.json

# 2c) Diff
diff -u current_params.json proposed_params.json || true

For MsgUpdateParams, modules typically expect the full params object and the authority to be the gov module account (that's normal—just confirm it). (Cosmos SDK Documentation, Cosmos Hub)

3) Know the voting options & the (very) short gov flow

Options: yes, no, nowithveto, abstain. NoWithVeto is a "no" plus a veto signal; Abstain contributes to quorum without supporting or opposing. (Cosmos SDK Documentation, Cosmos Tutorials)
Flow: proposals open (after deposit) → voting period runs → outcome decided by quorum/threshold/veto parameters → if passed, messages execute via the gov module. You may change your vote any time before the voting period ends; the last vote counts. (Cosmos Hub)

4) Cast (or change) your vote

Run this from the same machine that holds your cold governance key (you'll be prompted for the keyring password because --keyring-backend=file):

# options: yes | no | nowithveto | abstain
inferenced tx gov vote $PROPOSAL_ID yes $FLAGS

You can submit another tx gov vote later with a different option to change your vote before the voting window closes. To confirm what's recorded:

# See tally
inferenced query gov tally $PROPOSAL_ID -o json

# (Optional) list votes
inferenced query gov votes $PROPOSAL_ID -o json

(Cosmos CLI exposes vote, votes, and tally queries; voters can re-vote until the period ends.) (Cosmos SDK Documentation)

Submit a Parameter Change Proposal

TL;DR: draft a proposal with a MsgUpdateParams, include all params for that module, ensure the deposit meets min_deposit, submit, then track/deposit/vote. MsgUpdateParams requires providing the full parameter set for the target module. (hub.cosmos.network)

1) Get the governance module address (authority)

Many modules' MsgUpdateParams require authority to be the gov module account. You can get this by running this on a machine that has joined the node (your full node/server:)

inferenced query auth module-accounts | grep -B2 'name: gov'

The gov module executes proposal messages if they pass. Copy that address for the authority field. (docs.cosmos.network)

2) Export current params for the target module

You will edit these, but include the entire object in the proposal. Again, run this on your main server connected to the node

# Example for a custom "inference" module
inferenced query inference params -o json > current_params.json

MsgUpdateParams expects the full struct, not partial fields. (hub.cosmos.network)

3) Check the minimum deposit

inferenced query gov params -o json | jq '.params.min_deposit'

Your proposal's deposit must meet/exceed min_deposit. (hub.cosmos.network)

4) Draft the proposal file

Use the built-in wizard to scaffold draft_proposal.json, then choose other → pick your message type (e.g., /inference.inference.MsgUpdateParams).

inferenced tx gov draft-proposal
# fills draft_proposal.json and draft_metadata.json

The draft-proposal helper is part of modern gov v1 CLIs. (docs.cosmos.network, hub.cosmos.network)

You will want to select the message you are proposing. To change the parameters for the main chain, use /inference.inference.MsgUpdateParams

This will produce a draft_proposal.json and a draft_metadata.json

The metadata file should be hosted off-chain, preferably on IPFS.

Edit draft_proposal.json so it looks like:

{
  "messages": [
    {
      "@type": "/inference.inference.MsgUpdateParams",
      "authority": "cosmos1...gov...",       // from step 1
      "params": { /* paste & modify from current_params.json */ }
    }
  ],
  "metadata": "ipfs://CID",  // Path to the metadata file hosted on IPFS
  "deposit": "10000000nicoin",               // meet min_deposit
  "title": "Adjust epoch length",
  "summary": "Increase epoch length to 1000"
}

Reminder

Include the entire params object, not just the fields you changed. (hub.cosmos.network)

5) Submit the proposal

This MUST be done on your private machine with your cold account information.

inferenced tx gov submit-proposal ./draft_proposal.json $FLAGS

You will need to enter your passphrase to send the proposal.

Governance proposals in v1 are JSON files with embedded messages executed by the gov module if the vote passes. (docs.cosmos.network)

6) Ensure your proposal is on-chain

inferenced query gov proposals

This will give a list of current proposals on the chain, you should see yours and get the proposal_id.

Add a Deposit (if needed)

If the initial deposit was short, top it up:

# amount example: "5000000nicoin"
inferenced tx gov deposit <proposal_id> <amount> $FLAGS

(docs.cosmos.network)

Vote

Again, this will need to be from you private machine with your Governance account:

# options: yes | no | nowithveto | abstain
inferenced tx gov vote <proposal_id> yes $FLAGS

(There's no auto-YES for proposers; cast your vote explicitly.) (docs.cosmos.network)

Track Proposal Status

# One proposal
inferenced query gov proposal <proposal_id> -o json
# Tally only
inferenced query gov tally <proposal_id> -o json
# List all
inferenced query gov proposals -o json