Product Docs
Product DocsTechnical DocsLearning & GovernanceUseful Links
  • Product Docs
  • Node Docs
  • Learning Docs
  • Node documentation for cheqd network
  • 👉Getting Started
    • Setup a new cheqd node
      • Pre-Requisites & Requirements
      • (Alternative) Install with Docker
      • Configure cheqd node
      • Configure cosmovisor
    • Command Line usage
      • Manage keys
      • Manage accounts
      • Manage a node
      • Make transactions
      • Use fee abstraction
  • 🏦Validator Guides
    • Guide for validators
      • FAQs for validators
      • Optimising disk storage with pruning
      • Troubleshooting consistently high CPU/memory loads
      • Unjailing a jailed validator
      • Move validator to a different machine
      • Backup and restore node keys with Hashicorp Vault
    • Network-wide Software Upgrades
      • Upgrade Guides
        • Upgrade to v0.6.x
        • Upgrade to v2.x (with Ubuntu 24.04 LTS upgrade)
        • Upgrade to v3.x
        • Upgrade to v3.1.x
      • Creating a software upgrade proposal
      • Upgrade Process
  • 🧑‍💻Developing on cheqd
    • Building from source
      • Build with Docker
      • Run a localnet with Docker
    • Indexers
      • SubQuery
  • Architecture
    • Architecture Decision Record (ADR) Process
    • Identity ADRs
    • List of ADRs
      • ADR 001: Payment mechanism for issuing credentials
      • ADR 002: Importing/exporting mnemonic keys from Cosmos
      • ADR 003: Command Line Interface (CLI) tools
      • ADR 004: Token fractions
      • ADR 005: Genesis parameters
      • ADR 006: Community tax
      • ADR 007: Revocation registry
      • ADR 011: AnonCreds
      • ADR Template
  • 🤝Contributing to cheqd
    • Contributor Guide
    • License
    • Code of Conduct
    • Security Policy
  • 🆘Support
    • System Status
    • Slack Channel
    • Discord
Powered by GitBook
LogoLogo

General

  • Website
  • Blog
  • Get $CHEQ

Product Docs

  • Product Docs
  • cheqd Studio
  • Creds.xyz
  • Bug/Feature Requests

Technical Docs

  • Node Docs
  • GitHub
  • Block Explorer

Learning Docs

  • Learning Docs
  • Governance Docs
  • Governance Forum
  • Governance Explorer
On this page
  • Automatic upgrades with Cosmovisor
  • Manual Upgrades for Standalone Nodes
  • Node Built from Source Code
  • Docker Users

Was this helpful?

Edit on GitHub
Export as PDF
  1. Validator Guides
  2. Network-wide Software Upgrades

Upgrade Process

After the proposal status is marked as passed, the upgrade plan will become active. You can query the upgrade plan details using the following command:

cheqd-noded query upgrade plan --chain-id cheqd-mainnet-1

This will return output similar to:

height: "1000"
info: ""
name: <name of proposal>

At block height 1000, the BeginBlocker will be triggered. At this point, the node will be out of consensus, awaiting the upgrade to the new version.

The log messages like these should be expected:

5:17PM ERR UPGRADE "<proposed upgrade name>" NEEDED at height: 1000:
5:17PM ERR UPGRADE "<proposed upgrade name>" NEEDED at height: 1000:
panic: UPGRADE "<proposed upgrade name>" NEEDED at height: 1000:

Once the new application version is installed and running and 1/3 of the voting power on the network is restored, the node will resume normal operations.

Automatic upgrades with Cosmovisor

If your node is configured to use Cosmovisor, the upgrade action will be performed automatically at the specified block height.

To check if your node is configured to run with Cosmovisor, run the following command:

systemctl status cheqd-cosmovisor.service

If there's a running systemd service, running this sub-process /usr/bin/cosmovisor run start, then your node is using Cosmovisor.

Additionally, you should make sure that in your cheqd-cosmovisor systemd service configuration file, you have these environment variables set to true:

Environment="DAEMON_ALLOW_DOWNLOAD_BINARIES=true"
Environment="DAEMON_RESTART_AFTER_UPGRADE=true"

By default, the configuration file can be found at this location - /usr/lib/systemd/system/cheqd-cosmovisor.service;.

Manual Upgrades for Standalone Nodes

Node Built from Source Code

If you are running a node built from source, you will need to:

  1. Refer to the upgrade proposal details.

  2. Check out the git tag corresponding to the latest release. This is important in cases code in our main branch doesn't match the latest release.

  3. Build the updated binary.

Docker Users

Last updated 4 months ago

Was this helpful?

For standalone nodes, follow the instructions in . Make sure to choose the release suggested in the software upgrade proposal.

Additionally, we're also publishing the docker images in our , so in case you're running cheqd node in Docker, you can always find the latest image there.

🏦
our installation guide
GitHub Container Registry