Equinox Stage 0

Getting Started#

This stage of the competition is simple. After being onboarded by our team as a new validator (we'll invite you to the #validators Discord channel), you just need to setup your node as per the steps below and get comfortable. Staking does not begin yet. Just be observant here. Validating and the fun will begin soon hereafter!

Step 0: Hardware Requirements#

Validators should expect to provision one or more data center locations with redundant power, networking, firewalls, HSMs and servers. We expect that a modest level of hardware specifications will be needed initially and that they might rise as network use increases. Participating in the testnet is the best way to learn more.

For the staking competition, we recommend following specs:

Validator Nodes#

  • 6 GB RAM
  • 100GB SSD
  • x64 2.0 GHz 4 vCPU

Sentry Nodes#

  • 6 GB RAM
  • 100GB SSD
  • x64 2.0 GHz 4 vCPU

Step 1: Install injectived#

First, download the Injective Chain Staking-40013 binaries from the official injective-chain-releases.

wget https://github.com/InjectiveLabs/injective-chain-releases/releases/download/v4.0.13-1631158675/linux-amd64.zip

This zip file will contain two binaries: injectived which is the Injective Chain daemon as well as peggo which is the Injective Chain ERC-20 bridge relayer daemon.

Then unzip and add injectived and peggo to your /usr/bin.

mv injectived /usr/bin
mv peggo /usr/bin

Run injectived --help and peggo --help to verify that your installation was successful.

Step 2: Initialize a new Injective Chain node#

Before actually running the Injective Chain node, we need to initialize the chain, and most importantly its genesis file.

# The argument <moniker> is the custom username of your node, it should be human-readable.
export MONIKER=<moniker>
# the Injective Chain has a chain-id of "injective-888"
injectived init $MONIKER

Running this command will create injectived default configuration files at ~/.injectived.

Step 3: Prepare configuration to join the Equinox Testnet#

You should now update the default configuration with the testnet's genesis file and application config file, as well as configure your persistent peers with a seed node.

git clone https://github.com/InjectiveLabs/testnet-config
# copy genesis file to config directory
cp testnet-config/staking/40013/genesis.json ~/.injectived/config/genesis.json
# copy config file to config directory
cp testnet-config/staking/40013/app.toml ~/.injectived/config/app.toml

You can also run verify the checksum of the genesis checksum - 1af15799b563f244df36efb88873a0a3562c4afa4bdefed46eb00ac9f3dc5f7c

sha256sum ~/.injectived/config/genesis.json

Then open update the persistent_peers field present in ~/.injectived/config/config.toml with the contents of testnet-config/staking/40013/seeds.txt and update the timeout_commit to 1500ms.

cat testnet-config/staking/40013/seeds.txt
nano ~/.injectived/config/config.toml
# timeout_commit = 1500ms

Step 4: Start your node and sync the Injective Chain#

injectived start

At this point, your node should start syncing blocks from the chain.

Step 5: Prepare your Kovan Ethereum Full Node (Optional)#

In the next stage of the competition, you'll need to have a trustworthy Kovan EVM full node RPC connection for your validator to connect to. If you don't have a Kovan Ethereum node setup already, you can follow our instructions here to create your own Kovan full node.

Last updated on