neutron-1

The neutron-1 chain will be launched as a consumer chain with Cosmos Hub network as provider chain.

⚠️ If you have not used key assignment for your consumer node yet, please wait until Neutron is live and receiving valset updates from the Hub before you do so.

Upgrades history

Version	Value	Height
v1.0.1	Genesis version	From start
v1.0.2	Security upgrade (more info)	Anytime, not breaks the consensus
v1.0.3	Security upgrade (more info)	Coordinated consensus breaking upgrade without proposal at height 1236300
v1.0.4	Security upgrade (more info)	Anytime before height #1909000, consensus breaking
v2.0.0	Upgrade (more info)	Coordinated consensus breaking upgrade with a proposal 25 at height 5416000
v2.0.1	Upgrade (more info)	Coordinated consensus breaking security upgrade without a proposal on height 5971800 approximately at 3 PM UTC on 10th of January 2024
v2.0.3	Upgrade (more info)	Coordinated consensus breaking security upgrade without a proposal on height 7818500 approximately at 2:30 PM UTC on 5th of March 2024
v3.0.1	Upgrade (more info)	Coordinated consensus breaking upgrade with a proposal 35 at height 9034900
v3.0.5	Upgrade (more info)	Coordinated consensus breaking upgrade with a proposal 37 at height 10525000
v3.0.6	Upgrade (more info)	Coordinated consensus breaking security upgrade without a proposal on height 11298600 approximately at 14:00 UTC on 14th of June 2024
v4.0.1	Upgrade (more info)	Coordinated consensus breaking upgrade with a proposal 41 on height 12255555 approximately at 14:30 UTC on 10th of July 2024
v4.1.0	Upgrade (more info)	Coordinated consensus breaking security upgrade without a proposal on height 12947300 approximately at 14:00 UTC on 30th of July 2024
v4.2.0	Upgrade (more info)	Coordinated consensus breaking security upgrade without a proposal on height 13261400 approximately at 12:00 UTC on 8th of August 2024
v4.2.1	Upgrade (more info)	Coordinated consensus breaking security upgrade without a proposal on height 13711950
v4.2.3	Upgrade (more info)	Coordinated consensus breaking security upgrade without a proposal on height 14638000
v4.2.4	Upgrade (more info)	Coordinated consensus breaking security upgrade without a proposal on height 14970700
v5.0.0	Upgrade (more info)	Coordinated consensus breaking upgrade with a proposal 51 on height 16738000 approximately at 14:30 UTC on 14th of November 2024
v5.0.2	Upgrade (more info)	Coordinated consensus breaking security upgrade on height 17177900 approximately at 14:30 UTC on 26th of November 2024
v5.0.4	Upgrade (more info)	Coordinated consensus breaking security upgrade on height 18015000 approximately on Friday Dec 20th 2024
v5.0.5	Upgrade (more info)	Coordinated consensus breaking security upgrade on height 18125000 approximately at 17:00 UTC on 23d of December 2024
v5.0.6	Upgrade (more info)	Coordinated consensus breaking security upgrade on height 18906877 approximately 13th of January 2025
v5.0.7	Upgrade (more info)	Coordinated consensus breaking security upgrade on 4th of February 2025 approximately at 17:00 UTC.
v5.1.0	Upgrade (more info)	Coordinated consensus breaking security upgrade on 12th of February 2025 approximately at 14:30 UTC on height 19947000.
v5.1.3	Upgrade (more info)	Coordinated consensus breaking security upgrade on 24th of February 2025 approximately at 17:00 UTC on height 20396500.
v6.0.0	Upgrade (more info)	Coordinated consensus breaking security upgrade on 10th of April 2025 approximately at 15:00 UTC on height 22041500.
v6.0.1	Upgrade (more info)	Coordinated consensus breaking security upgrade on 23rd of April 2025 approximately at 15:00 UTC on height 22996000.
v6.0.2	Upgrade (more info)	Coordinated consensus breaking security upgrade on 10th of June 2025 approximately at 15:00 UTC on height 27030500.
v6.0.3	Upgrade (more info)	Coordinated consensus breaking security upgrade on 2nd of July 2025 approximately at 15:00 UTC on height 28886600.
v8.0.0	Upgrade (more info)	Coordinated consensus breaking upgrade on 27th of August 2025 approximately at 15:00 UTC on height 33397000.
v8.1.0	Upgrade (more info)	Coordinated consensus breaking upgrade on 3rd of October 2025 approximately at 15:00 UTC on height 36430000.
v8.2.0	Upgrade (more info)	Coordinated consensus breaking security upgrade on 5th of November 2025 approximately at 16:00 UTC on height 39417500.
v9.0.0	Upgrade (more info)	Coordinated consensus breaking upgrade on 19th of November 2025 approximately at 15:00 UTC on height 40700000.
v9.1.0	Upgrade ([more info][32])	Coordinated consensus breaking upgrade on 10th of December 2025 approximately at 15:00 UTC on height 42568000.

Parameters

Below are the neutron-1 chain parameters:

Name	Value
chain-id	neutron-1
denom	untrn
minimum-gas-prices	0.01untrn
timeout_commit	1s
genesis_time	2023-05-10T15:00:00.000000Z

The minimum-gas-prices parameter must be set to 0.01untrn. At chain launch (and until the end of the Token Generation Event) the only address that will have untrns will be the initial Hermes relayer. This relayer will be configured to only process Transfer messages between Neutron and Cosmos Hub. As soon as the chain starts, some uatoms will be transferred from Cosmos Hub to Neutron and the bridged ATOM denom will be communicated to the validators. After that, the validators will be able to set the minimum-gas-prices in bridged ATOMs.

Binary

The release binary information is provided below:

Item	Description
GitHub repo	neutron-org/neutron
Release	v1.0.1
Reference binary	neutrond-linux-amd64
Checksum (sha256)	b628d3eb1e0e12617b2c905f07dc39bd91d5dd3bd284a2a51d47c04cc3aa2e6d

The neutrond-linux-amd64 binary is only provided to verify the SHA256. It was built with Interchain Security release v1.2.0-multiden. You can generate the binary following the build instructions in the neutron-org/neutron repo.

The Cosmos Hub was recently upgraded to v9.1.0, which bumps ICS to v1.1.0-multiden. This version introduces two new parameters to prevent Replicated Security’s logic for handling rewards to be abused as a DOS vector.

This required a release of a new version of Neutron, v1.0.1, which must be used for the mainnet launch. The only difference between v1.0.0-rc1, which was used in the proposal, and v1.0.1 is the upgrade of Interchain Security to the latest release, v1.2.0-multiden, which is compatible with the new parameters. You can check the difference here.

⚠️ All validators are required to use Neutron v1.0.1 during the mainnet launch. The instructions on how to build v1.0.1 can be found in the How to Join section.

Genesis

The final genesis.json information is provided below:

Item	Description
Genesis	genesis.json
Checksum (sha256)	9496492c81b31befb59a4336d5ae4444c24b863721d21be143d7d4fdf8072c84

⚠️ All validators are required use the genesis.json file provided in this instruction.

If you want to get a better idea of what was changed in the genesis since Proposal 792, please read the sections below.

---

ccvconsumer section updates

Due to the upgrade of the Neutron's ICS dependency to v1.2.0-multiden, and due to using a version of ICS with soft opt-out, there is 3 parameters that were added to the ccvconsumer section of the genesis:

{
  "soft_opt_out_threshold": "0.05",
  "reward_denoms": ["untrn"],
  "provider_reward_denoms": ["uatom"]
}

1. rewards_denoms: rewards denominations from the Consumer chain (e.g. uNTRN or IBC denoms used on the consumer chain);
2. provider_rewards_denoms: rewards denomination from the Provider chain (e.g. uATOM);
3. soft_opt_out_threshold: this parameter was set to 0.05 to allow the smaller validators to opt out of validating Neutron without being slashed.

slashing parameters

In the pre-genesis, we used incorrect slashing parameters. Below you can see the slashing parameters diff:

+ "signed_blocks_window": "140000",
+ "min_signed_per_window": "0.050000000000000000",
+ "slash_fraction_downtime": "0.000100000000000000"
- "signed_blocks_window": "100",
- "min_signed_per_window": "0.500000000000000000",
- "slash_fraction_downtime": "0.010000000000000000"

1. signed_blocks_window was increased to approximately 4 days given a 2.5s block production time that we are expecting. This is done to give the validators more time to recover a failed node;
2. min_signed_per_window was adjusted to match the value used by he Cosmos Hub;
3. slash_fraction_downtime was adjusted to match the value used by he Cosmos Hub.

wasm artifacts

Neutron genesis instantiates dozens of smart contracts that are used by the Neutron DAO and the Neutron Token Generation Event. Since the time when Proposal 792 was published, we fixed some bugs and introduced some improvements to our smart contracts.

We have a script that you can copy to an empty directory and run to get the final genesis. We provide this script for information purposes only, and we do not guarantee that it will work on your machine (although if you have a Mac and the Docker daemon is running, it should produce the final genesis.json within approximately 30 minutes because it will build all the wasm binaries).

⚠️ Please use the genesis.json file provided above during the coordinated launch.

Endpoints

Seed nodes:

1. 24f609fb5946ca3a979f40b7f54132c00104433e@p2p-erheim.neutron-1.neutron.org:26656
2. [email protected]:19156
3. b1c6fa570a184c56d0d736d260b8065d887e717c@p2p-kralum.neutron-1.neutron.org:26656
4. [email protected]:26656
5. [email protected]:19156

Persistent nodes:

1. e5d2743d9a3de514e4f7b9461bf3f0c1500c58d9@neutron.peer.stakewith.us:39956
2. [email protected]:15600
3. [email protected]:2480
4. [email protected]:10083
5. [email protected]:26656
6. [email protected]:26656
7. [email protected]:36656
8. [email protected]:26656

Also you can use this addrbook.json to bootstrap your nodes.

The following state sync node serve snapshots every 2000 blocks:

1. http://rpc-kralum.neutron-1.neutron.org:26657

How to Join

Hardware Requirements

• 4 Cores
• 32 GB RAM
• 2x512 GB SSD

Software Versions

Name	Version
Neutron	v4.2.0
Go	=1.22

Node manual installation

Build and install the Neutron binary.

$ git clone -b v4.2.0 https://github.com/neutron-org/neutron.git
$ cd neutron
$ make install

After installation, please check installed version by running:

$ neutrond version --long
name: neutron
server_name: neutrond
version: 4.2.0
commit: 01b71f7f682b75aec78aecdf5604c914b6421c6a

You can also download binary directly from our official release.