Bitica Coin Docs
  • Summary
  • DOCUMENTATION
    • Learn about the Bitica Platform
      • Bitica Overview: vision, strategy and platform components
      • The Bitica Blockchain
        • Discovering the Network
        • Bitica Consensus
        • Delegation through Staking with Validators
        • Ethereum (EVM) Compatibility and Smart Contracts
        • Boosting Bitica's Scalability
      • Bitica Token (BDCC)
        • BDCC Tokenomics
        • Exchanges, Wallets, On-Ramps and DeFi Tools Supporting BDCC
        • BDCC on Other Chains
      • Interoperability
      • Bitica Governance and Development
        • Bitica Assembly
        • Bitica Improvement Proposals (FIPs)
      • Wallets supporting Bitica
    • Bitica for Business
    • Things you can do on Bitica
      • Interacting with the Bitica Blockchain
      • Bitica Ecosystem
      • Community
      • Grants and Bounties
    • Bitica Mobile Infrastructure Use Cases
  • Developers
    • Network Details
      • Bitica Mainnet
      • Bitica Testnet Bitica
      • Token Faucets
      • Network Upgrades
        • Upgrade Guide
        • Upgrade Guide (explorer nodes)
        • Block 13,800,000 Fork
        • FIP's
    • Bitica Consensus
      • Contracts Overview
      • Stake, Delegate and Withdraw
      • Vote
      • End-of-Cycle Flow
      • Contract Addresses
    • How to run network nodes
    • Resources & Tools
      • TheGraph
      • WalletConnect on Bitica
    • Important smart contracts
      • Bitica Token
      • Bitica Dollar
      • Major Deployed Contracts
      • Bridges
        • Ethereum ↔ Bitica GoodDollar Token
        • Ethereum ↔ Bitica BDCC20 Tokens
        • BSC ↔ Bitica BNB
        • BSC ↔ Bitica Native
        • BSC ↔ Bitica BDCC20
        • Ethereum ↔ Bitica Native
    • How to become a validator
      • Getting started as a validator
      • Getting started as on the Bitica testnet
  • Links
    • Instagram
    • Facebook
    • GitHub
    • LinkedIn
    • Telegram
    • Staking Telegram
    • Twitter
    • Twitter
Powered by GitBook
On this page
  • Step 1 - Stop all running containers
  • Step 2 - Pull the latest quickstart script
  • Step 3 - Upgrade your DB using OEs upgrade tool
  • Step 4 - Update Client version in env file and rerun quickstart
  • Step 5 - Verify Upgrade
  1. Developers
  2. Network Details
  3. Network Upgrades

Upgrade Guide (explorer nodes)

This guide is intended specifically for explorer nodes.

PreviousUpgrade GuideNextBlock 13,800,000 Fork

Last updated 1 year ago

Since we don't host snapshots for explorer DBs, some extra steps are required in order to update from V1.0.0 to V2.0.0.

Step 1 - Stop all running containers

sudo docker stop $(sudo docker ps -q)

Step 2 - Pull the latest quickstart script

cd <to quickstart.sh location>
wget -O quickstart.sh https://raw.githubusercontent.com/Bitica/master/scripts/quickstart.sh

Step 3 - Upgrade your DB using OEs upgrade tool

It is highly recommended to take a back up of your database folder before attempting!.

Follow the instruction here to upgrade from V13->V16 DBs . The data base is stored in <path to quickstart.sh>/fusenet/database/FuseNetwork/db/dee77c98f8210dbb/archive

Step 4 - Update Client version in env file and rerun quickstart

vim .env
Add the following (without quotes) "CLIENT=OE"
Save and exit :w :q
sudo ./quickstart.sh

Step 5 - Verify Upgrade

Check your node on our It should be online and the client should be "OpenEthereum//v3.2.6-stable", ensure your node is connected to peers and syncing/ in sync.

https://github.com/openethereum/3.1-db-upgrade-tool
health site