Taraxa Project
WebsiteExplorerCommunity Site
  • 👋Welcome!
  • ðŸ’ĩWallet
    • Metamask
    • Ledger
    • Taraxa's Network Connection Details
  • ðŸŒąBecome a Validator
    • ⚙ïļSet up validator node
    • ðŸ–ĨïļConsensus node hardware requirements
    • ðŸšĐRegister node via community site
    • ⛓ïļRegister node directly on-chain
    • ðŸ“ĢSolicit delegation
    • 🛠ïļNode upgrade & reset
  • 💰Staking
    • 💧Liquid Staking
    • ðŸšĐStaking via community site
    • ⛓ïļStaking directly on-chain
  • 🌉Ficus Root Bridge
    • ↔ïļBridge usage guide
    • 📜On-chain contracts
    • 🔎Audit Report
  • ðŸ’ĨTaraxa Grant Program
  • Develop on Taraxa
    • 🚀Start building on Taraxa!
    • 🔗Connecting to Taraxa
    • 📓Smart Contracts
      • Remix
    • ⚒ïļCommon frameworks & Examples
    • 💧Testnet faucet
    • ðŸ”ĐTaraxa RPC Specs
  • Node Operations
    • ⚙ïļDeploy A Node
      • Digital Ocean
      • AWS
      • Alibaba Cloud
      • Scaleway
      • Vultr
      • Linode
      • Azure
      • Hetzner
      • GitHub is blocked
    • ðŸŠķLite Consensus Node (beta)
    • ⏚ïļUpgrade a Node
      • ⮆ïļUpgrade Node
      • 🔁Reset Node
    • 🔀Syncing From Snapshot
    • 📎Node's Public Address
    • 🗝ïļNode's VRF Key
    • 📒Node Proof of Ownership
    • ❓Node Operations FAQ
    • ðŸ”ĒNode Release Notes
    • ⚙ïļInstall A Local Node
      • Windows
      • Mac
      • Linux
      • Digital Ocean
      • AWS
      • Alibaba Cloud
      • Scaleway
      • Vultr
      • Linode
      • Azure
      • Hetzner
      • GitHub is blocked
  • FAQ
    • 1ïļLayer-1 Tech
    • 🊙TARA Token
    • ðŸŒąMainnet
    • 🔁Exchange Integration
  • Whitepaper
    • Abstract
    • Intro: Scaling the World
    • Taraxa Architecture
    • Economic Model
    • Governance
    • Further Reading
  • NATIVE TOKEN CONVERSION
    • ðŸ’ĄIntroduction
    • 🗓ïļConversion Status
    • ❓Conversion FAQ
    • ⚗ïļMock Conversion
    • 📋Exchange Submission
  • Governance
    • â„đïļIntroduction
    • ⚡Voting Guide
Powered by GitBook
On this page
  • 1. Lite Consensus Node on the Taraxa Mainnet
  • 1.1 Set up a Lite Consensus Node on the Mainnet from scratch
  • 1.2 Turn an existing full node into a Lite Consensus Node on the Mainnet
  • 1.3 Syncing from snapshot
  • 2. Lite Consensus Node on the Taraxa Testnet
  • 2.1 Set up a Lite Consensus Node on the Testnet from scratch
  • 2.2 Turn an existing full node into a Lite Consensus Node on the Testnet
  • 3. Node upgrade & reset
  • 3.1 Node Upgrade
  • 3.2 Node Reset

Was this helpful?

  1. Node Operations

Lite Consensus Node (beta)

Light-weight non-archival consensus node

PreviousGitHub is blockedNextUpgrade a Node

Last updated 21 days ago

Was this helpful?

If you don't wish to run a full archival node, you can choose to run a light-weight consensus node that has ~90% savings in disk space requirements. The Lite Consensus Node achieves the disk space savings by pruning the state DB and only keeping a set of the most recent Periods.

Lite node requires pruning, and you need to restart your lite node for pruning to start. It's recommended to set up a script to periodically restart the lite node to keep disk space usage to a mininum.

Here are the .

Here's how you can set up a Lite Consensus Node.

1. Lite Consensus Node on the Taraxa Mainnet

1.1 Set up a Lite Consensus Node on the Mainnet from scratch

mkdir -p mainnet/config
cd mainnet
wget https://raw.githubusercontent.com/Taraxa-project/taraxa-ops/master/taraxa_compose_mainnet/docker-compose.light.yml -O docker-compose.yml
docker-compose up -d
docker-compose logs

1.2 Turn an existing full node into a Lite Consensus Node on the Mainnet

cd mainnet
docker-compose down
wget https://raw.githubusercontent.com/Taraxa-project/taraxa-ops/master/taraxa_compose_mainnet/docker-compose.light.yml -O docker-compose.yml
docker-compose up -d
docker-compose logs

1.3 Syncing from snapshot

Because the Taraxa network state has gotten very large, it takes quite a long time to sync. An alternative is to sync from a snapshot, which will drastically cut down on the amount of syncing time and can get your node up & running much more quickly.

2. Lite Consensus Node on the Taraxa Testnet

2.1 Set up a Lite Consensus Node on the Testnet from scratch

mkdir -p testnet/config
cd testnet
wget https://raw.githubusercontent.com/Taraxa-project/taraxa-ops/master/taraxa_compose/docker-compose.light.yml -O docker-compose.yml
docker-compose up -d
docker-compose logs

2.2 Turn an existing full node into a Lite Consensus Node on the Testnet

cd testnet
docker-compose down
wget https://raw.githubusercontent.com/Taraxa-project/taraxa-ops/master/taraxa_compose/docker-compose.light.yml -O docker-compose.yml
docker-compose up -d
docker-compose logs

3. Node upgrade & reset

3.1 Node Upgrade

cd mainnet
wget -O docker-compose-new.yml https://raw.githubusercontent.com/Taraxa-project/taraxa-ops/master/taraxa_compose_mainnet/docker-compose.light.yml && mv docker-compose-new.yml docker-compose.yml
sudo docker-compose down
sudo docker-compose pull
sudo docker-compose up -d
sudo docker-compose logs -f

3.2 Node Reset

cd mainnet
wget -O docker-compose-new.yml https://raw.githubusercontent.com/Taraxa-project/taraxa-ops/master/taraxa_compose_mainnet/docker-compose.light.yml && mv docker-compose-new.yml docker-compose.yml
sudo docker-compose down -v
sudo docker-compose pull
rm -f config/mainnet.json
sudo docker-compose up -d
sudo docker-compose logs -f

>> <<

ðŸŠķ
hardware requirements for a lite consensus node
Latest snapshots