Gonka Governance
pre-vote layer

Documentation

How Gonka Governance works

This portal is a thin UI on top of two CosmWasm contracts deployed on the Gonka chain. Everything you can do here — pledging, rating, advancing the lifecycle — is also one CLI call away. Look for the ⌨ Show CLI commands pill near each block to see the exact inferenced invocations that have the same effect.

Pre-propose module

dao-pre-propose-gonka

Holds drafts, pledges, ratings, and pre-vote outcomes. Every action you take on this site ultimately calls this contract.

gonka1sa4xv8fuyq5pe44jj56r5suegtcz2m9k5plkwpxnc9k44lmx02gsgszwgpView on explorer →

Voting module

dao-voting-gonka

The source of voting power. Locking GNK here mints power proportional to the lock duration; that power is what the pre-propose contract reads when you rate or pre-vote.

gonka1v837zexseh4m8g5ajvu8ag74c2v9xfyv3mx0pu202ltjesqe2s9qctp8h2View on explorer →

Voting power = locked GNK × duration

You don't burn or pay anything to participate — you lock GNK in dao-voting-gonka for a fixed term. Longer locks earn more weight, and the original principal returns on unlock.

TierDurationMultiplier100 GNK locked = …
Three months90 days1×100 voting power
Six months180 days2×200 voting power
Twelve months360 days4×400 voting power
Lock GNK →

A draft's lifecycle

Every proposal moves through these on-chain states. Anyone (not just an admin) can push a draft forward once the gates are met.

  1. 1

    Author submits a draft

    Discussion

    Anyone with non-zero voting power can publish a draft. The full title, summary and optional external link are stored on-chain (no IPFS).

    Gate: Author must hold non-zero voting power.

  2. 2

    Community pledges and rates

    Discussion

    While the draft is open, anyone can pledge GNK to the deposit pool, withdraw their pledge, or rate the draft up/down weighted by their voting power. Comments live off-chain in the portal.

    Gate: Open until either the discussion deadline expires or the gates below are met.

  3. 3

    Anyone can start the pre-vote

    Pre-voting

    Once the deposit pool reaches the configured minimum and the cumulative rating power crosses the floor, anyone can call start_pre_vote. The draft is now locked into a binding pre-vote.

    Gate: total_pledged ≥ min_pledge_for_pre_vote AND yes_power + no_power ≥ min_rating_voting_power.

  4. 4

    Outcome recorded

    Passed / Failed

    When the pre-vote closes the operator (admin) records the outcome. Pledges from passing drafts are refundable; failed drafts are also refundable in this MVP. A future milestone wires this to dao-proposal-single so finalization is fully on-chain.

  5. 5

    Author may cancel any time before pre-vote

    Canceled

    If the author no longer wants to pursue the draft they can cancel it from Discussion. Pledges are refundable.

Useful read-only queries

Everything this UI shows is read directly from the contracts — no special API needed. Reproduce any of it from the CLI:

  • List drafts

    Same data the feed renders.

  • Inspect a single draft

    Title, summary, totals, status.

  • Pledgers for a draft

    Address + amount pairs.

  • Rating tally

    yes / no power and # of distinct raters.

  • My voting power

    From dao-voting-gonka. Replace the address.

  • My active locks

    Open positions in dao-voting-gonka.

What lives off-chain

To keep the contract state lean we keep two strictly cosmetic things in the portal's own database (Postgres). They never affect on-chain rules:

  • Comments — Reddit-style threaded discussion under each draft.
  • Comment likes / dislikes — feed signal only.

Everything that affects the outcome of a vote (drafts, pledges, ratings, locked GNK, admin records) is written and read directly from the contracts above. That makes the result independently verifiable: you don't have to trust this portal to trust the outcome.