[toc]

---

# PR Template

---
name: Governance Proposal
about: Share and receive feedback on a governance proposal!
Title: "Proposal: "
labels: governance
---

<!-- < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < ☺
v ✰ Thanks for creating a Governance Proposal PR! ✰
v Before smashing the submit button please review the checkboxes.
v If a checkbox is n/a - please still include it but + a little note why
☺ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -->

## Description

<!-- Include the short (~200 word) description of the governance proposal being considered.-->

______

For contributor use:

- [ ] Included all files in folder in `/proposals/` using {year-month-proposal name}
- Proposal written in markdown titled `README.md`
- On-chain proposal draft titled `proposal.json`
- [ ] Used the [governance proposal](#) and [on-chain proposal](#) templates.

______

For admin use:

- [ ] Added appropriate labels to PR (ex. `WIP`, `R4R`, `docs`, etc)
- [ ] Reviewers assigned
- [ ] Squashed all commits, uses message "Merge pull request #XYZ: [title]" ([coding standards](https://github.com/tendermint/coding/blob/main/README.md#merging-a-pr))

-----

# [Proposal][Draft] Proposal Title

## Changelog

- {date}: {changelog}

## Authors and Credit

{Name}: {link e.g., github, discord, twitter}

## Status

{DRAFT | PROPOSED}

> Use DRAFT if the Governance Proposal is in a draft stage or PROPOSED if it's in review.

## Proposal

> A short (~200 word) description of the governance proposal being considered.

## Context

> A complete, yet brief...

## Governance Votes

The following items summarize the voting options and what it means for this proposal.

- **YES**: You approve the {type} proposal to...{one sentence summary}.
- **NO**: You disapprove of the proposal in its current form. The NO vote can be a request for improvements or adjustments, please indicated them in the relevant topic in the [Cosmos forum](https://forum.cosmos.network/). You agree that this proposal's motivation is valuable and that the team should create a follow-up proposal once the amendments are included.
- **NO (VETO)**: You veto the entire motivation for the proposal, are strongly opposed to its implementation, and will exit the network if passed. You are signalling the proposers should not create a follow-up proposal.
- **ABSTAIN**: You are impartial to the outcome of the proposal.

> State what voting for each option means in terms of this proposal. You can read more about voting options at: https://hub.cosmos.network/main/governance/overview.html#what-do-the-voting-options-mean

## Conclusion

## References

- {reference link}