Join the Public Mainnet

·

Welcome to the OKTC public mainnet—a decentralized, high-performance blockchain network designed for scalability, security, and developer flexibility. Whether you're launching a full node for the first time or upgrading an existing setup, this guide walks you through every essential step with clarity and precision.

This comprehensive walkthrough covers node initialization, configuration, synchronization, and even the path toward becoming a validator. We'll also explore key system requirements, genesis setup, seed node integration, and seamless software upgrades.

By the end, you'll have a fully functional OKTC node contributing to the network’s robustness and decentralization.


Supported Platforms

OKTC supports full node deployment across major operating systems:

All instructions provided are compatible with these platforms. Ensure your development environment is updated and capable of handling Go-based blockchain applications.

👉 Get started with setting up your node environment today.


Minimum System Requirements

To ensure stable and efficient operation of your exchaind node, meet the following minimum hardware specifications:

For detailed performance benchmarks and recommended configurations based on node type (full node, sentry, or validator), refer to the official node requirement documentation.

Running a node below these specs may lead to synchronization delays, increased downtime, or failure to maintain consensus with the network.


Setting Up a New Node

Follow these steps to initialize a brand-new OKTC full node from scratch.

Initialize the Node

Begin by initializing your node and generating the necessary configuration files:

exchaind init <your-moniker>
Note: Monikers must use only ASCII characters. Unicode or special characters may prevent your node from being discoverable on the network.

You can modify your moniker later by editing the ~/.exchaind/config/config.toml file.

Configure Anti-Spam Settings

To protect your node from low-value transaction spam, adjust the minimum gas price in the ~/.exchaind/config/exchaind.toml file:

minimum-gas-prices = "0.000000001okt"

Setting a minimum gas price helps filter out frivolous transactions and ensures your node prioritizes meaningful network activity.

Your node is now initialized and ready for further configuration.


Genesis & Seeds

Fetch the Genesis File

The genesis file defines the initial state of the blockchain. Download the latest genesis.json from the mainnet repository:

curl -s https://raw.githubusercontent.com/okx/mainnet/main/oktc-genesis.json > ~/.exchaind/config/genesis.json

Verify the integrity of the file:

exchaind validate-genesis

This command confirms that the genesis configuration is valid and matches network standards.

Add Seed Nodes

For peer discovery, add reliable seed nodes to your configuration file located at ~/.exchaind/config/config.toml. Seed nodes help your node locate and connect to healthy peers on the network.

Locate current seed node addresses in the mainnet repo README, then update the seeds field:

seeds = "seed1-node-address,seed2-node-address"

For deeper insights into peer-to-peer networking and seed mechanics, consult Tendermint’s P2P specification documentation.

👉 Secure your connection to the OKTC network now.


Starting Your Node

Launch your full node using the following command:

exchaind start

Monitor logs to verify synchronization:

tail -f ~/.exchaind/logs/exchaind.log

You should see block heights increasing as your node catches up with the latest chain state. Initial sync may take several minutes to hours depending on hardware and network speed.

Once fully synced, your node actively participates in transaction validation and block propagation.


JSON-RPC Endpoint

Interact with the blockchain programmatically via the JSON-RPC API. The endpoint allows dApps, wallets, and tools to query blockchain data and broadcast transactions.

Access full API documentation to learn about available methods, request formats, and response structures.

Developers can connect to the public RPC URL or run their own local endpoint for enhanced privacy and reliability.


Upgrading Your Node

If you're running an older version of exchaind, follow these steps to upgrade smoothly to the latest mainnet release.

Reset Node Data

First, clean outdated data while preserving critical identity files:

exchaind unsafe-reset-all

This removes old blockchain data but retains your priv_validator.json and config.toml. Your node will attempt to reconnect to previously configured peers upon restart.

Critical Note: Never reuse the same priv_validator.json across multiple nodes. Doing so risks double-signing violations, which can result in slashing penalties or permanent validator removal.

Upgrade Software

Update the OKTC software to the latest stable version:

cd $HOME/exchain
git fetch --all
git checkout master
make install

Ensure you have the latest stable version of Go installed (preferably Go 1.19+). Verify with:

go version

Check the OKTC GitHub releases page for changelogs and version-specific details.

After installation, confirm the correct binary version:

exchaind version

Restart your node:

exchaind start

Your node is now upgraded and synchronized with the latest network protocol.


Upgrade to Validator Node

With a fully synced full node in place, you're ready for the next step: becoming a validator.

The top 100 validators by staked OKT are eligible to propose and sign new blocks. To qualify:

  1. Own or stake a competitive amount of OKT tokens.
  2. Set up secure key management (preferably using hardware wallets or KMS).
  3. Follow the Validator Setup Guide to create a validator transaction.

Running a validator brings rewards—but also responsibility. Downtime, double-signing, or poor performance can lead to penalties.

👉 Explore how to become a trusted validator on OKTC.


Frequently Asked Questions (FAQ)

Q: What is the difference between a full node and a validator?
A: A full node validates transactions and maintains a complete copy of the blockchain. A validator is a full node that actively participates in consensus by proposing and voting on blocks. Only validators in the top 100 by stake can enter the active set.

Q: Can I run a node on a virtual private server (VPS)?
A: Yes. Many users deploy OKTC nodes on VPS providers like AWS, DigitalOcean, or Google Cloud. Ensure your VPS meets minimum hardware requirements and uses an SSD for optimal performance.

Q: How do I check if my node is syncing correctly?
A: Use exchaind status and observe the latest_block_height. Compare it with public block explorers. When both values match, your node is fully synced.

Q: What happens if my validator goes offline?
A: Occasional downtime may result in missed rewards. Prolonged inactivity can lead to being temporarily jailed, preventing participation until manually unjail via transaction.

Q: Is it safe to reuse my priv_validator.json file after reinstalling?
A: You can reuse it only for the same node. Never copy it to another machine—this causes double-signing, which violates consensus rules and risks penalties.

Q: How often are software upgrades released?
A: Upgrades depend on network needs and community governance. Major updates are announced in advance through official channels with detailed migration guides.


Core Keywords

oktc mainnet, full node setup, exchaind configuration, genesis file download, seed nodes addition, json-rpc api, upgrade validator node, okt blockchain