How to Submit a Governance Proposal

Anyone can propose a change to Pocket Network’s protocol, treasury, or parameters. You don’t need a formal role or special credentials. But proposals succeed when they’re well-researched, clearly written, and built with genuine community input.

Proposal Types

TypeFull NameScope
PIPPocket Improvement ProposalProtocol changes, governance structure
PEPPocket Ecosystem ProposalFunding, ecosystem investment, grants
PUPParameter Update ProposalOn-chain parameter changes

The Full Proposal Journey

Stage 1 — Research and Drafting

The most common reason proposals fail is insufficient research and community buy-in. Before writing:

  • Search the forum archive. Are there past proposals on this topic? If a similar one failed, understand why.
  • Understand technical implications. For PIPs and PUPs, understand how your change affects other parts of the protocol. Talk to technical contributors in Discord.
  • Gauge informal support. Discuss your idea in #governance on Discord. A proposal with zero informal support rarely passes.
  • Read the POKT Constitution. Any PIP touching governance structure or the Foundation must comply with the Constitution.

Stage 2 — Forum Discussion

The forum is where governance lives. All proposals must go through forum discussion before a vote.

Where to post:

  • Pre-Proposals — for initial temp checks and drafts
  • Proposals → Improvements (PIP) — formal protocol improvements
  • Proposals → Ecosystem (PEP) — funding and ecosystem proposals
  • Proposals → Parameters (PUP) — parameter changes

How to engage effectively:

  • Respond to every substantive comment — silence after posting kills proposals
  • Revise your draft publicly — note what changed and why
  • Don’t rush to a vote — give the community time to read and respond
  • Tag relevant stakeholders — node operators, PNF, whoever is affected

Stage 3 — The Proposal Template

Every formal proposal should include: title, type (PIP/PEP/PUP), author, abstract (one paragraph), motivation (why this matters), specification (exactly what changes), rationale (why this approach), and dissenting opinions (acknowledged counterarguments).

Stage 4 — The Snapshot Vote

Once forum discussion is adequate, a vote is opened on Snapshot. The vote is typically opened by PNF or a governance steward after confirming requirements are met.

  • Voting period: 7 days
  • Quorum: Defined in the governance framework — check current requirements on the forum
  • Weight: Stake-weighted voting

Stage 5 — Implementation

When a proposal passes, PNF or the designated implementer carries it out. Parameter changes (PUPs) can be executed quickly via governance transactions. Protocol changes (PIPs) require development and testing. After implementation, changes can be verified at poktscan.com/params.

Common Reasons Proposals Fail

  • Insufficient research — the proposal doesn’t account for known constraints
  • No community engagement before posting — the first the community hears of it is the formal proposal
  • Author goes silent during discussion — signals lack of commitment
  • Conflicts with the Constitution or existing governance decisions
  • Unclear specification — the community can’t evaluate what exactly would change