Software Upgrade proposals are used to coordinate all full nodes to upgrade to the same new software at a specified block height.
Here’s a template for writing a software proposal! This template will be automatically generated when you create a topic in this category; you are free to edit it as you need.
Hi OP! Here are some things to keep in mind when writing a proposal:
- There is a 10000 character limit for a proposal (incl. format and links)
- Once a proposal is on-chain it cannot be changed or edited. Make sure to solicit feedback and edits from stakeholders (i.e. Validators and delegators) BEFORE you move on-chain.
- For transparency, take a pdf snapshot of this forum post and pin it to IPFS before going on-chain (e.g. Using a service such as Pinata - https://www.pinata.cloud/ ). Include the link in your on-chain proposal text.
- YYYY-MM-DD Created initial post
List of changes (including links to relevant content):
The following items summarize the voting options and what it means for this proposal:
NO WITH VETO - A ‘NoWithVeto’ vote indicates a proposal either (1) is deemed to be spam, i.e., irrelevant to Cosmos Hub, (2) disproportionately infringes on minority interests, or (3) violates or encourages violation of the rules of engagement as currently set out by Cosmos Hub governance. If the number of ‘NoWithVeto’ votes is greater than a third of total votes, the proposal is rejected and the deposits are burned.
ABSTAIN - You wish to contribute to quorum but you formally decline to vote either for or against the proposal.