One World Chain Token Docs
  • Summary
  • DOCUMENTATION
    • Learn about the OWCT Platform
      • OWCT Overview: vision, strategy and platform components
      • The OWCT Blockchain
        • Discovering the Network
        • OWCT Consensus
        • Delegation through Staking with Validators
        • Ethereum (EVM) Compatibility and Smart Contracts
        • Boosting OWCT's Scalability
      • OWCT
        • OWCT Tokenomics
        • Wallets Supporting OWCT
        • OWCT on Other Chains
      • Interoperability
      • OWCT Governance and Development
        • OWCT Assembly
    • OWCT for Business
  • Developers
    • Network Details
      • OWCT Mainnet
      • OWCT Testnet
      • Token Faucets
      • Network Upgrades
        • Upgrade Guide
        • Upgrade Guide (explorer nodes)
        • Block 13,800,000 Fork
        • FIP's
    • OWCT Consensus
      • Contracts Overview
      • Stake, Delegate and Withdraw
      • Vote
      • End-of-Cycle Flow
      • Contract Addresses
    • How to run network nodes
    • Resources & Tools
      • TheGraph
      • WalletConnect on OWCT
    • Important smart contracts
      • OWCT Token
      • OWCT Dollar
      • Major Deployed Contracts
      • Bridges
        • OWCT (Mainnet) <=> OWCT (ETH)
        • OWCT (Mainnet) <=> OWCT (BSC)
        • OWCT (Mainnet) <=> OWCT (BASE)
        • ETH (Ethereum network) <=> ETH (OWCT network)
        • USDT (Ethereum network) <=> USDT (OWCT network)
        • USDC (Ethereum network) <=> USDC (OWCT network)
        • BNB (Binance network) <=> BNB (OWCT network)
    • How to become a validator
      • Getting started as a validator
      • Getting started on the OWCT testnet
  • Links
    • Discord
    • Facebook
    • GitHub
    • LinkedIn
    • Medium
    • Telegram
    • Twitter
    • YouTube
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/OneWorldChain/OWCT/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