Validator & Exchange Node Restart Guide – Self Chain Mainnet v2.0.2


Dear Validators and Exchange Partners,

Following the resolution of the recent consensus halt on Self Chain Mainnet v2, we're now providing detailed instructions to help you quickly and safely restart your validator and exchange nodes. Please carefully follow the instructions outlined below.


Who Should Follow This Guide?

  • Validators (Mandatory)
  • Exchange Nodes (Mandatory)
  • RPC/API Node Operators

📌 Updated Official Resources

🛠️ Container Images:

Public Container Image (v2.0.2) (Recommended):

reg.nodeops.xyz/public/selfchain:2.0.2

Public Container Image (v1.0.1):

reg.nodeops.xyz/public/selfchain:1.0.1

📦 Official Snapshot (Post-upgrade height #4,806,246):

👉 Download Snapshot

(Snapshot height #4,806,246 ensures immediate post-upgrade consensus stability.)


🚩 Validator & Exchange Node Restart Steps

Carefully follow these steps:

🔹 Step 1: Stop Your Node

Stop your node immediately to prevent state inconsistencies:

sudo systemctl stop selfchaind

If you're using Docker/containers, stop your running container clearly:

docker stop selfchain
docker rm selfchain

🔹 Step 2: Completely Reset Node State

Clear previous corrupted or inconsistent state:

selfchaind tendermint unsafe-reset-all --home ~/.selfchain

For container deployments, remove old data clearly:

rm -rf $HOME/.selfchain/data/*

🔹 Step 3: Restore Official Snapshot (Height #4,806,246)

Download and restore the provided snapshot:

# Download snapshot
wget -O selfchain_2.0.2_4806246.tar.lz4 "https://fatal-coral-jaguar.myfilebase.com/ipfs/QmWZtCNTtvRqRFaGB6Nt4MCo7ZBSLmWjchrYUSttKbmEji?download=true&filename=selfchain_2.0.2_4806246.tar.lz4"

# Extract snapshot
lz4 -c -d selfchain_2.0.2_4806246.tar.lz4 | tar -x -C $HOME/.selfchain

Ensure extraction completes without errors.


Deploy your node clearly using the recommended container image (2.0.2):

docker run -d \
  --name selfchain \
  -v ~/.selfchain:/root/.selfchain \
  -p 26656:26656 -p 26657:26657 \
  reg.nodeops.xyz/public/selfchain:2.0.2 start

🔹 Step 5: Validators Only — Ensure priv_validator_state.json is Correct

Make sure this file (~/.selfchain/data/priv_validator_state.json) is correctly set:

{
  "height": "4806246",
  "round": 0,
  "step": 0
}

If the file is missing or incorrect, recreate it manually with the above values.


🔹 Step 6: Restart Your Node Clearly

  • If running via systemd (traditional deployment):
sudo systemctl start selfchaind
  • If using Docker (container deployment):

(Already started in Step 4, verify status clearly)

docker logs -f selfchain

🔹 Step 7: Validators Only — Unjail (if necessary)

If your validator was jailed due to downtime/slashing, unjail clearly:

selfchaind tx slashing unjail \
--from=<validator_wallet> \
--chain-id=self-1 \
--fees=5000uslf \
--gas=auto --gas-adjustment=1.5 -y

🔹 Step 8: Immediate Node Verification

Monitor your logs and ensure normal synchronization:

  • For traditional deployment:
journalctl -u selfchaind -f
  • For Docker deployment:
docker logs -f selfchain

Ensure clearly:

  • Your node syncs properly and participates in consensus.
  • No AppHash mismatch or consensus errors occur.
  • RPC/API endpoints operate normally.

Post-Restart Checklist

After completing the above clearly:

  • Node is fully synced & operational.
  • Validator actively participates in consensus.
  • RPC/API endpoints serving accurate blockchain data.
  • Exchanges: deposits, withdrawals, and blockchain services stable.

📢 Special Instructions for Exchanges

All exchanges must:

  • Pause deposits/withdrawals briefly during this restart.
  • Restart nodes following the above steps clearly.
  • Verify services immediately post-restart and promptly resume user transactions.

🙋‍♂️ Immediate Support & Assistance

For rapid support:


🙏 Special Acknowledgment

A sincere thank you to NodeOpsHQ and BuildOnNodeOps for their invaluable, round-the-clock support during this incident.

We deeply appreciate all validators, exchanges, and community members for your cooperation and patience throughout this recovery process.

Warm regards,
Self Chain Core Team

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