Cosmos Hub Testnets

This repository contains current and archived genesis files, scripts, and configurations for Cosmos Hub testnets. Key network information is present here, but for step-by-step instructions on how to join whichever testnet is currently running, please check out the tutorial in Cosmos Hub documentation. You can also find legacy network information here.

Network Information for Active Testnets

Vega Upgrade testnet

This testnet targets validators and integrators who want to test their tooling with Vega. It mirrors the state of mainnet before the Vega testnet with modifications to enable liveness and with convenient parameters to simulate a governance permissioned software upgrade.

• Chain-ID: vega-test
• Gaia Version: release/v6.0.0-rc3
• Genesis File: https://github.com/cosmos/vega-test/raw/master/public-testnet/modified_genesis_public_testnet/genesis.json.gz
• Genesis sha256sum: 89d1cb03d1dbe4eb803319f36f119651457de85246e185d6588a88e9ae83f386
• Endpoints:

Node	Node ID	Public IP	Ports
HYPHA "Coinbase"	99b04a4efd48846f654da25532c85bd1fa6a6a39	198.50.215.1	p2p: 46656, rpc: 46657, api: 4317, grpc: 4090
HYPHA "Certus-one"	1edc806e29bfb380dc0298ce4fded8e3e8554e2a	198.50.215.1	p2p: 36656, rpc: 36657, api: 3327, grpc: 3080
Interchain "Binance" Sentry	66a9e52e207c8257b791ff714d29100813e2fa00	143.244.151.9	p2p: 26656 , rpc: 26657 , api: 1317 , grpc: 9090

• Peers with state-sync snapshots
  • [email protected]:26656
  • [email protected]:26656
  • [email protected]:26656
• Network statistics
• Block Explorer
• Faucet: Please make an issue in the vega-test repsository or ask in the #validator-verified channel in the Cosmos Developers discord

Developer testnet

The developer testnet targets developers who want to test applications against testnet gaia nodes. Unlike the upgrade testnets, this testnet doesn't mirror the state of the mainnet. As of January 2022, it was running gaia version 5.0.8.

Cosmos Hub Testnet Plan

The goals of the Cosmos Hub testnet program are to build confidence among validators and full node operators to test upcoming software upgrades; provide developers with a low-risk production-like environment to test integrations with Cosmos Hub; and to make historical hub software releases and states readily available for testing and querying. Beyond these goals, testnets could also become a site for R&D for new development and governance approaches in a fast-moving and live context.

We are expecting the roll out as follows:

1. Rolling testnets for each gaia upgrade.

These testnets aim to help validators set up robust automation around upgrades using Cosmovisor. This phase includes working directly with validators to understand current pain points and develop tools and processes to support their workflows. The v6-vega testnet was in Q4 2021 and we are currently working on v7-theta testnet for Q1 2022.

Based on learnings from vega, we will configure v7-theta so that:

• Testnet coordinators will operate 4+ validators with combined voting power exceeding 75% total power
• These validators will require an addition of ~550M bonded test ATOM (current bonded ATOM are ~180M) and a corresponding increase in total supply.
• Tesnet coordinators control a faucet with >175M liquid tokens
• Testnet coordinators can reward validators with limited edition secondary tokens that are named after their release (Theta, Rho, Epsilon, Lambda). The testnets will have a fixed supply of 1000 each of such tokens.

2. Persistent testnet.

After the v7-theta testnet we will assess whether we can continue using the same testnets on a persistent basis for future upgrades.