nRide ICS Testnet Repository

This repo describes the process of launching an ICS chain on the provider CosmosHUB Testnet.

nRide Website

Phases of Launch

There are several phases of the nRide ICS Chain launch:

1. Build the binaries using the spawn-cli
2. Create a pre-spawn genesis.json file
3. TX a consumer-chain create message in the Security-Providing Network
4. After spawn time is reached, copy the Crosschain-Validation state into the Consumer Node
5. Start the Consumer Node

Note: If you start your node before spawn time has reached and no CCV state is imported, you will get an error that your network does not reach the "default-Power-reduction".

Although you can create Validators in the Genesis file, this set is not necessary for the consensus engine. The Validator Set in an ICS chain serves as a blockchain history database and RPC/gRPC nodes and as a Token distribution service to Stakers. Rewards will be distributed to the underlying ATOM Validators resp. their stakers and the network stakers on a 50:50 ratio. So with opting-in as a CosmosHUB mainnet Validator, you will generate rewards for your Stakers and your own Commission Share.

Opt in as Cosmos Validator

If you already run a Cosmos Validator in the active Set, for opting-in only, there is only one command necessary:

• You must submit your opt-in transaction before the spawn time is reached to start signing blocks as soon as the chain starts.

gaiad tx provider opt-in 115 --from wallet --chain-id provider --gas auto --gas-adjustment 2 --gas-prices 0.005uatom -y

Check if your subscription worked:

gaiad q provider consumer-opted-in-validators 136

while 136 is the consumer-chain-id.

As an opted-in Validator, you and all your stakers will earn network rewards from the nRide network.

Inscribe your ICS chain into the provider chains registry

You may use the

sh update_create_ICS_Subscription.sh script to create a .json file that can be submitted to the Security-Providing Network.

This creates a file:

/.gaia/config/created_ICS_Subscription.json

that you can broadcast

gaiad tx provider create-consumer created_ICS_Subscription.json --from wallet --chain-id provider --gas auto --gas-adjustment 2 --gas-prices 0.005uatom -y

Notice: When editing .json files, check for empty spaces and obsolete carriage returns, because they are likely to cause parsing errors during TX message creation. I recommend you to use VS code or similiar applications to edit the json files. Furthermore you need to use the "--output json" flag when exporting states from the Binary

Check the correct creation of the ICS inscritpion message by using the "--generate-only" flag. Check if the Spawn Time and the Power Shaping parameters are parsed correctly. Check if the Spawn time is later than the Genesis Time

Submit the Inscription:

gaiad tx provider create-consumer ICS.json --from wallet --chain-id provider --gas auto --gas-adjustment 2 --gas-prices 0.005uatom -y

Update the Inscription:

gaiad q provider consumer-chain 136 --output json > 136.json

modify the .json file, and submit again:

gaiad tx provider update-consumer 136.json --from wallet --gas auto --gas-adjustment 2 --gas-prices 0.005uatom -y

Run a local nRide Node on your machine

If you want to run a nRide Node on your machine too, you will need to install the "nrided" binary:

• git clone https://github.com/rattadan/nRide_testnet.git * Clone the Repository

• make install

copy the genesis_after_spawn.json into your config folder and start your nRide Node

Setting up the nRide Node (not necessary if you only want to opt-in...)

please join the given Telegram Group, if you like to opt-in into our testnet https://t.me/nride_official

• nrided init <your_moniker> --chain-id nride-1 *creates the config folder and initializes the node change gas prices in app.toml: minimum-gas-prices = "0.25unride" change chain-id = "nridetestnet-1" in client.toml backup your priv.validator and node key savely

copy the provided genesis file into this folder:

cp nride_fresh_genesis.json ~/.nridetestnet/config

Adding Seed to config.toml

To connect your node to the network, add the following seed to your config.toml file:

[SEED]
[email protected]:27656

Chain Startup:

After the spawn time has passed, you migrate the CCV state from the underlying provider chain into your ICS chain:

As long as you don't have a valid CCV state within your genesis and try to start the node, you will encounter this error:

failure when running app err="error during handshake: error on replay: validator set is empty after InitGenesis, please ensure at least one validator is initialized with a delegation greater than or equal to the DefaultPowerReduction ({824641568320})"

So lets go on:

After Spawn time has passed, you can export the CCV state from an active Node synced with the Security Providing Network

Collect the Cross-Chain Validation (CCV) state from the provider chain.

gaiad q provider consumer-genesis <consumer-id> -o json > ccv-state.json

Update the CCV state with the reward denoms. Set the Chain native denom: jq '.params.reward_denoms |= ["<your chain denom>"]' ccv-state.json > ccv-denom.json

Set the provider reward denon:

jq '.params.provider_reward_denoms |= ["uatom"]' ccv-denom.json > ccv-provider-denom.json

Update the genesis file with the CCV state jq -s '.[0].app_state.ccvconsumer = .[1] | .[0]' <consumer genesis without CCV state> ccv-provider-denom.json > <consumer genesis file with CCV state>

Explanation of Commands

The commands you provided are using jq, a lightweight and flexible command-line JSON processor, to manipulate JSON files. Here's what each command does:

First Command:

jq '.params.reward_denoms |= ["<your chain denom>"]' ccv-state.json > ccv-denom.json

This command takes the ccv-state.json file and updates the reward_denoms field within the params object to be a list containing "<your chain denom>". The result is then saved to a new file called ccv-denom.json.

Second Command:

jq '.params.provider_reward_denoms |= ["uatom"]' ccv-denom.json > ccv-provider-denom.json

This command takes the ccv-denom.json file and updates the provider_reward_denoms field within the params object to be a list containing "uatom". The result is saved to a new file called ccv-provider-denom.json.

Third Command:

jq -s '.[0].app_state.ccvconsumer = .[1] | .[0]' <consumer genesis without CCV state> ccv-provider-denom.json > <consumer genesis file with CCV state>

This command uses the -s option of jq, which reads all inputs into an array. It takes two JSON files: a consumer genesis file without CCV state and ccv-provider-denom.json. It assigns the content of ccv-provider-denom.json to the ccvconsumer field within the app_state object of the first file. The modified genesis file is then saved to a new file, which is the consumer genesis file with the CCV state added.

If you have a Gaia node and a nRide node on the same machine, you can use the script here:

##Add Script here

Helpful Commands

Obtain nRide node ID:

• nrided tendermint show-node-id
• nrided tendermint show-address
• nrided keys show wallet --bech val (show your valoper address)

Inscribe your chain into the permissionless ICS module:

• gaiad tx provider create-consumer create_consumer_tx.json --from wallet --chain-id provider --gas auto --gas-adjustment 2 --gas-prices 0.005uatom -y

Query if your chain has been subscribed:

• gaiad q provider list-consumer-chains (remember correct pagination, as the result shows only chain-id 1-99)

• gaiad q provider consumer-chain 115

A validator can opt in to a consumer chain by issuing the following message:

interchain-security-pd tx provider opt-in <consumer-id>

Consumer ID for Testnet = 115

Where:

• consumer-id is the identifier of the consumer chain the validator wants to opt in to.
• consumer-pub-key corresponds to the public key the validator wants to use on the consumer chain, and it has the following format: {"@type":"/cosmos.crypto.ed25519.PubKey","key":"<key>"}.

gaiad tx provider opt-in 115 --from wallet --chain-id provider --gas auto --gas-adjustment 2 --gas-prices 0.005uatom -y

nRide Genesis Configuration

This repository contains the configuration files and scripts for setting up the nRide blockchain network.

Modify your Genesis File, set chain parameters like total supply, inflation rate, community pool, Genesis Adress Allocations, Genesis Validators Delegations accordingly.

check for consistency:

nrided genesis validate nride_fresh_genesis.json

generate sha256 checksum

Files

• nride_fresh_genesis.json: The main genesis file for the nRide blockchain without CCTV states.
• create.json: Contains configuration parameters for creating a new consumer chain.
• gaiad tx consumer create-consumer.sh: Shell script for executing the consumer chain creation command.
• checksums.txt: Contains checksums for verifying the integrity of binaries and genesis files.
• Seed.txt: Contains seed information for the network.

Setup Instructions

1. Verify Checksums

   • Ensure that the binaries and genesis files match the provided checksums in checksums.txt.

2. Create Consumer Chain

   • Use the gaiad tx consumer create-consumer.sh script to initialize the consumer chain.
   • Modify the parameters in create.json as needed.

3. Genesis File n

   • nride_fresh_genesis.json

   Notice: You don't need to add a mandatory Validator Information directly into the genesis file, because the ICS consensus module is being linked with the underlying Cosmos Validator Set, not the staking Validator set.

Important Parameters

• Genesis Time: Set in nride_fresh_genesis.json to specify the start time of the blockchain.

update_create_ICS_Subscription.sh

This script is responsible for generating the create_ICS_Subscription.json file based on the current genesis file and binary. It retrieves the necessary parameters, including the chain ID, spawn time, and SHA256 checksums for the genesis file and binary, and constructs a JSON structure that is then saved to the specified output file. The script ensures that the generated JSON is correctly formatted and includes all relevant parameters for the subscription.

How to Run the Script

To execute the script, use the following command in your terminal:

bash update_create_ICS_Subscription.sh

Modifiable Variables

The following variables can be modified manually within the script:

• GENESIS_FILE: Path to the genesis file (default: ./nride_fresh_genesis.json).
• BINARY: Path to the binary file (default: ~/go/bin/nrided).
• EXPECTED_CHAIN_ID: The expected chain ID for validation (default: nridetestnet-1).

Create a Validator on Provider Testnet:

https://github.com/cosmos/testnets/tree/master/interchain-security/provider#bash-script

according to # Gaia v21.0.0 Release Notes

❗You must use Golang v1.22 if building from source.

git clone https://github.com/cosmos/gaia
cd gaia && git checkout v21.0.0
make install

..after you compiled the binary:

either use the setup_gaia_testnet_node.sh script, or:

gaiad init "Your Label Here" --chain-id provider
cd .gaia/config
nano app.toml
minimum-gas-prices = "0.025uatom"

sync your node using this guide from nodestake https://nodestake.org/cosmos set seed, peers and download snapshsot lets sync: gaiad start

create a wallet

gaiad keys add wallet

or recover an existing one

gaiad keys add wallet --recover
gaiad keys list

get some testnet atoms on your wallet (ask in discord or tg)

if you need a custom port mapping, if you are running a gaia node and a nRide node the same time, use the gaia_port_settings.sh script

gaiad tx staking create-validator create_validator_gaia.json --from wallet --gas auto --gas-adjustment 2 --gas-prices 0.005uatom

with

create_validator_gaia.json { "pubkey": {"@type":"/cosmos.crypto.ed25519.PubKey","key":"BcCDlvRODsZCYNi82PJA4h9Xe0+nht6EU5mXOQlmLyE="}, "amount": "100uatom", "moniker": "nRide Validator", "identity": "166879CD027B2772", "website": "www.nride.com", "security": "[email protected]", "details": "nRide.com ICS Testnet Validation Node", "commission-rate": "0.1", "commission-max-rate": "0.2", "commission-max-change-rate": "0.01" }

replace pubkey above value with your own values: gaiad tendermint show-validator

Check if your Validator is somewhere (look in the inactive list) Delegate some Tokens to your Validator

Further resources:

Game of Chains: First ICS Testnet playground https://github.com/LavenderFive/game-of-chains-2022/blob/8b3d2c40b56a30a45e444d65bd9419ad7c0fe1a1/README.md

Nodestake Testnet Snapshot, Seeds & Peers https://nodestake.org/cosmos

Interchain ICS repository: https://cosmos.github.io/interchain-security/consumer-development/app-integration

Spawn Github: https://rollchains.github.io/spawn/v0.50/