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.
This testnet targets validators who want to test their uprade readiness with Theta before mainnet launch. It mirrors the state of mainnet before with modifications to an exported genesis to enable liveness and with convenient parameters to simulate a governance permissioned software upgrade.
- Launch date: 2022-03-10
- Chain-ID:
theta-testnet-001
- Gaia Version:
release/v6.0.0
- Genesis File:
https://github.com/cosmos/testnets/raw/master/v7-theta/public-testnet/genesis.json.gz
- Genesis sha256sum:
522d7e5227ca35ec9bbee5ab3fe9d43b61752c6bdbb9e7996b38307d7362bb7e
- Block Explorer: https://explorer.theta-testnet.polypore.xyz
- Faucet: Please ask in the
#validator-verified
channel in the Cosmos Developers discord - Endpoints:
- Hypha endpoints: We are running nodes named
sentry-01
,sentry-02
,state-sync-01
, andstate-sync-02
, with endpoints as follows:- RPC:
https://rpc.<node-name>.theta-testnet.polypore.xyz
- REST:
https://rest.<node-name>.theta-testnet.polypore.xyz
- GRPC:
https://grpc.<node-name>.theta-testnet.polypore.xyz
- P2P:
https://p2p.<node-name>.theta-testnet.polypore.xyz
- RPC:
- Interchain endpoints:
- RPC:
https://rpc-theta.interchain.io
- P2P:
[email protected]:26656
- RPC:
- Hypha endpoints: We are running nodes named
- Peers: You can add these in your persistent peer list.
5c9850dc5ec603b0c97ffd8d67bde3221b877acf@p2p.sentry-01.theta-testnet.polypore.xyz:26656
208683ee734ba3cec1cfc0c8bcbc326969641952@p2p.sentry-02.theta-testnet.polypore.xyz:26656
58e9d022962a3875fa22d7146949d0dc34e51ba6@p2p.state-sync-01.theta-testnet.polypore.xyz:26656
6954e0479cd71fa01aeed15e1a3b87c06433d827@p2p.state-sync-02.theta-testnet.polypore.xyz:26656
- Launch date: 2022-03-10
- Chain ID:
theta-devnet
- Software version: We'll be tracking this branch until an RC has been cut: https://github.com/cosmos/gaia/tree/theta-prepare
- Endpoints:
- RPC:
https://rpc.one.theta-devnet.polypore.xyz
- REST:
https://rest.one.theta-devnet.polypore.xyz
- RPC:
This 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.
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:
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.
After the v7-Theta
testnet we will assess whether we can continue using the same testnets on a persistent basis for future upgrades.