Self Chain Docs
WebsiteTwitter
  • Learn
    • About Self Chain
    • Keyless wallet
      • MPC-TSS
      • Secure Signing
      • Account Abstraction
  • Getting Started
    • Glossary
    • Frequently Asked Questions
    • Set up a wallet
      • Adding Self Chain to Keplr Wallet
      • Setting up Keplr with Ledger Wallet
      • Adding Self Chain to Leap Cosmos Wallet
    • How To Stake SLF
    • Self Chain Mainnet
    • How to IBC Transfer
  • Developer Guide
    • Self Chain Networks
    • Frontend dApps
    • Faucet
  • SLF Tokenomics
    • Token Allocation and Utility
      • Bonded Tokens Vs Circulating Supply
      • Address Transparency
    • FRONT Migration
      • How to Bridge FRONT from BNB Chain (BEP20) to Ethereum (ERC20)
      • How to Migrate FRONT to SLF using Binance Convert
    • FRONT Migration FAQs
    • Central Exchanges FRONT to SLF Migration
  • Staking and Delegation
    • Delegating $SLF
    • Redelegating $SLF
    • Undelegating $SLF
    • How to delegate $SLF with Frontier Wallet
    • How to Delegate $SLF with Ledger
    • How to Participate in SLF Binance Simple Earn Product
  • Nodes & Validators
    • Node Setup Guide
    • Node Configuration FAQs
    • Run a Validator Node
    • Validator FAQs
    • Releases
    • Run a Validator Node with NodeOps
    • Setting up Cosmovisor
    • Log Console Troubleshooting
    • Run Selfchain testnet node
  • Governance
    • Draft a Proposal
      • Text Proposal
      • Community Spend Proposal
      • Paramter Change Proposal
      • Software Upgrade Proposal
      • Cancel Software Upgrade
    • Submitting a Proposal
    • Depositing funds
    • Voting on a Proposal
    • FAQs
  • Official Links
  • Branding and Logos
Powered by GitBook
On this page
  • What is a Software Upgrade Proposal?
  • Proposal Structure
  1. Governance
  2. Draft a Proposal

Software Upgrade Proposal

What is a Software Upgrade Proposal?

A Software Upgrade Proposal allows the network to transition to a new version of the blockchain software. The proposal specifies an upgrade plan and schedule that validators and node operators must follow to avoid disruptions.

Use Cases

  • Fix bugs in the current software.

  • Enhance security and performance.

  • Addressing bugs or issues in the current software.

Proposal Structure

Title: A concise title summarizing the upgrade (e.g., “Proposal to Upgrade Self Chain to v2.0”).

Summary: summarize the upgrade in 2-3 sentences, including the new software version and the rationale for the upgrade.

Upgrade Plan:

  • Testing: Describe any testing that has been conducted to validate the upgrade.

  • Validator Actions: Outline the steps validators and node operators must take to upgrade their nodes.

  • Upgrade Height: Indicate the block height when the upgrade will take effect.

  • New Software Version: Specify the version number (e.g., v2.0).

Preprate the JSON file:

{
  "messages": [
    {
      "@type": "/cosmos.upgrade.v1beta1.MsgSoftwareUpgrade",
      "authority": "self10d07y265gmmuvt4z0w9aw880jnsr700jlfwec6",
      "plan": {
        "name": "v2.0-upgrade",
        "time": null,
        "height": "1000000",
        "info": "https://selfchain.xyz/releases/v2.0",
        "upgraded_client_state": null
      }
    }
  ],
  "metadata": "ipfs://CID",
  "deposit": "10000000uslf",
  "title": "Add CosmWasm Support",
  "summary": "Adding CosmWasm module support",
}

height: Set height to a block number after the voting period ends(calculate based on blocks per year).

To query the gov account for the authority field, use the command:

selfchaind query auth module-account gov --node http://165.232.125.66:26657
PreviousParamter Change ProposalNextCancel Software Upgrade

Last updated 5 months ago