Validator Upgrade Guide: Self Chain MainNet v2 CosmWasm Activation

Validator Upgrade Guide: Self Chain MainNet v2 CosmWasm Activation

Hello Validators and Node Operators,

The Self Chain community has officially approved the governance proposal for the Mainnet v2 upgrade, enabling CosmWasm smart contracts at block height #4,805,959 (estimated April 18, 2025, ~11:08:09 UTC).

This blog provides clear, detailed instructions to ensure a smooth validator node upgrade.


πŸ“Œ Upgrade Overview

  • Target Upgrade Block Height: #4,805,959
  • Estimated Upgrade Time: April 18, 2025, ~11:08:09 UTC
  • Required Binary: mainnet-v2.0.0 (CosmWasm enabled)

At block height #4,805,959, Self Chain will halt to execute the upgrade. Validators must promptly upgrade to participate in consensus.


⏰ Upgrade Timeline

Milestone Scheduled Date & Time (UTC)
🟒 Governance Proposal Passed Completed
πŸ“₯ Binary Availability Available Now
⛓️ Chain Halt at Block #4,805,959 April 18, 2025 (~11:08:09 UTC)
πŸš€ Node Restart (CosmWasm Active) Immediately After Halt (April 18, 2025)

Step-by-Step Validator Upgrade Instructions

Carefully follow each step below to upgrade your node seamlessly.


πŸ“₯ Step 1: Download the Official Binary

Official Binary Downloads:


πŸ” Step 2: Verify Binary Integrity (Checksum Verification)

Ensure the downloaded binary's integrity by verifying its checksum:

SHA256 Checksums:

Binary FileSHA256 Checksum
selfchaind-linux-amd64711c4b6af77bd6da4bf5aac7c1cc83179d9d213da9f99a48fc2754ddb073b6cc
selfchaind-linux-arm640ae04d58fe62b9496cc24a31dfba7a6eaf567a1f549f6018338891f8d39f9534
selfchaind-darwin-amd64a599c6377ad15563b09240f1282e6382cd8c08e5375047b900dbaaa99fdd7146
selfchaind-darwin-arm646b2adf70246ee9d868c0cbfb336d5167f52d41ad26f5b91e006a2a9708482b30

Use this command to verify:

sha256sum selfchaind-linux-amd64

Match the output exactly to the checksum provided above.


πŸ”‘ Step 3: Optional - PGP Signature Verification

If desired, validators can further verify authenticity using the official PGP signature:

gpg --verify selfchaind-mainnet-v2.0.0-linux-amd64.tar.gz.asc selfchaind-mainnet-v2.0.0-linux-amd64.tar.gz
Official public PGP key: Link to official PGP key

⚠️ Step 4: Back Up Validator Data

Prior to the upgrade, securely back up your validator private keys, configuration, and critical data.


πŸ›‘ Step 5: Stop Your Validator Node

At block #4,805,959 (~11:08:09 UTC, April 18):

  • Gracefully stop your existing node:
sudo systemctl stop selfchaind

Ensure your validator has fully stopped.


πŸ”„ Step 6: Replace Binary and Restart Node

Replace your current binary with the new verified binary:

  • Backup old binary and place new binary into your system’s binary path.
  • Ensure correct permissions.

Restart your validator node immediately after binary replacement:

sudo systemctl start selfchaind

πŸ› οΈ Step 7: Verify Your Node’s Status

Monitor logs to ensure the validator restarts correctly and rejoins consensus:

journalctl -u selfchaind -f

Confirm your node:

  • Syncs new blocks normally
  • Actively participates in consensus
  • Runs with no critical errors

Check validator status on Mintscan Self Chain Explorer.


For validators using Cosmovisor, set up the upgrade directory:

mkdir -p ~/.selfchain/cosmovisor/upgrades/v2/bin
cp /path/to/selfchaind-mainnet-v2.0.0 ~/.selfchain/cosmovisor/upgrades/v2/bin/selfchaind

Cosmovisor will handle the restart automatically at the upgrade height.


πŸ“‹ Final Validator Pre-Upgrade Checklist

Complete this checklist before upgrade day:

  • [ ] Official binary downloaded and checksum verified.
  • [ ] Optional: PGP signature verified.
  • [ ] Node data backed up securely.
  • [ ] Cosmovisor (if used) properly set up.
  • [ ] Node monitoring in place.
  • [ ] Prepared to restart node promptly after block #4,805,959.

Ensure your validator meets the minimum recommended specifications:

  • CPU: 4 cores minimum
  • RAM: 16 GB minimum
  • Storage: SSD with at least 500 GB available
  • Operating System: Linux (Ubuntu recommended)
  • Ports: Ensure necessary ports (26656, 26657, etc.) remain open.

πŸ›‘οΈ Rollback & Contingency

In the unlikely event of issues:

  • Pause your node operations.
  • Immediately reach out via the Self Chain Discord #validator-support channel.
  • Follow official team guidance for rollback procedures if necessary.

πŸ™‹β€β™‚οΈ Support & Resources

Need assistance? Connect with the Self Chain team:

Our team will be actively supporting validators throughout the entire upgrade.

Subscribe to Self Chain Blog

Don’t miss out on the latest issues. Sign up now to get access to the library of members-only issues.
jamie@example.com
Subscribe