Cronos POS Chain Docs
  • Getting Started
    • 📑Cronos POS Chain Introduction
    • 🔰Architecture
  • For USERS
    • 🌟New brand and domains
    • 💰Wallets
      • chain-maind
      • Ledger Hardware Wallets with chain-maind
      • Crypto.com DeFi Desktop Wallet
      • Conducting IBC Transfer with Keplr Wallet
      • Using Ledger Device with Keplr Wallet
      • Mainnet Address Generation
      • Mainnet Address Verification
      • Multisig Account
      • Delegation Guide
      • Key Principles for Wallet Security
    • 🛠️Token Migration Web Tool
    • 🚰Croeseid Testnet Faucet
  • For Node Hosts
    • ⛓️Running Nodes
      • Public Node Sync
      • Quicksync
      • Cronos POS Chain Mainnet: Running a Full Node
        • Upgrade Guide
          • The "V5" upgrade guide (v4.* to v5.0.1) :
          • The "V4" upgrade guide (v3.* to v4.2.2) :
          • The "DRACO II" upgrade guide (v2.* to v3.3.2) :
          • The "Canis Major" upgrade guide (v1.* to v2.0.1) at block height 922,363:
          • Running "Canis Major" network upgrade with cosmovisor
      • Cronos POS Chain Mainnet: Running a Validator
      • Cronos POS Chain Mainnet Validator Security Checklist
      • Croeseid Testnet: Running Nodes
      • Mainnet/Testnet: Running Nodes using AWS 1-click Deployment
      • Mainnet/Testnet: Running Nodes using Azure 1-click Deployment
      • Croeseid Testnet: Running Nodes With Nix
      • Devnet: Running Latest Development Node
    • 🔄Advanced TMKMS Integration
    • 💫Notes on Performance
    • 🔃Notes on Production Deployment
  • Block Explorers
    • 📊Cronos POS Chain Mainnet Explorer
    • 📊Croeseid Testnet Explorer
  • Cronos PoS Chain Protocol
    • ⛓️Chain Details
      • Genesis
      • Protocol Documentation
      • Chain ID, Address Format and Signatures
      • Create the IBC-enabled tokens on the Cronos POS Chain with Solo Machine
      • List of parameters
      • Proposal Process
      • Technical glossary
    • 🎛️Modules
      • module_supply
      • module_slashing
      • module_authz
      • module_bank
      • module_mint
      • module_gov
      • module_staking
      • module_distribution
      • module_nft
  • Cronos PoS Integration
    • 🔄Integration documentation
    • 🛂Node Setup and RPC node
    • 🔲Blocks and Transactions
Powered by GitBook
On this page
  • Pre-requisites
  • Install nix
  • Install chain utils for testnet
  • Initialization
  • Run
  • Isolated installation
  1. For Node Hosts
  2. Running Nodes

Croeseid Testnet: Running Nodes With Nix

PreviousMainnet/Testnet: Running Nodes using Azure 1-click DeploymentNextDevnet: Running Latest Development Node

Last updated 5 months ago

Pre-requisites

Nix supports both Linux and Mac, for Windows users, you can follow the .

Install nix

Follow official instructions to install nix: https://nixos.org/download.html

for Mac user, you might need to consult the , simply put, if you have a recent Mac, you can install nix with sh <(curl -L https://nixos.org/nix/install) --darwin-use-unencrypted-nix-store-volume

Install cachix and enable crypto-com binary cache:

$ nix-env -iA cachix -f https://cachix.org/api/v1/install
$ cachix use crypto-com

Install chain utils for testnet

$ nix-env -iA chain-utils-testnet -f https://github.com/crypto-org-chain/chain-main/archive/v3.1.0-croeseid.tar.gz

After installation, you'll have these commands in your PATH:

  • chain-maind, the chain binary for testnet

  • init-node, the script to initialize the chain data directory with state sync enabled

  • print-systemd-config, print a systemd config file to stdout

Initialization

$ export CHAINHOME=/path/to/data # optional, default to $HOME/.chain-maind
$ MONIKER=testnode init-node

Change the value of MONIKER to your node's name.

state sync is initialized and enabled by init-node automatically, if you don't want that to happen, you can disable it by edit $CHAINHOME/config/config.toml manually, set enable field to false under section [statesync] like this:

[statesync]
enable = false

Run

You can now run the chain node manually:

$ chain-maind start --home $CHAINHOME

Or setup systemd service on linux:

$ print-systemd-config | sudo tee /etc/systemd/system/chain-maind.service
$ sudo systemctl start chain-maind

Isolated installation

One of the strengths of nix package manager is you can have multiple isolated installations, it would be important when you want to manage both testnet and mainnet chains or different versions of them on a single machine.

$ nix build -f https://github.com/crypto-org-chain/chain-main/archive/v3.1.0-croeseid.tar.gz chain-utils-testnet -o testnet
$ export CHAINHOME=$PWD/testnet_data
$ MONIKER=testnode ./testnet/bin/init-node
$ ./testnet/bin/chain-maind start --home $CHAINHOME

Please refer to for instructions to issue transactions and create validator.

⛓️
manual instructions
nix manual for macos installation
Croeseid Testnet