Testnets for Regen Ledger
regen-redwood-1 is an active testnet for the community. It generally runs the same software as mainnet and useful for testing third-party integrations. Also it will be used as a platform for testing mainnet upgrades.
Here are the instructions to run a validator for regen-redwood-1:
- Stop your existing regen validator (if any)
sudo service regen stop- Run the latest setup script
git clone https://github.com/regen-network/testnets
cd testnets
git pull
chmod +x scripts/testnet-val-setup.sh
./scripts/testnet-val-setup.sh <your_key_name> <your_validator_moniker_name>You can find the genesis file and all the relevant information in redwood-testnet directory
To get tokens from the faucet use the following curl command
curl http://<faucet-url>/faucet/<your-regen-address>
- Faucet: (coming soon)
- RPC: http://137.184.24.185:26657/
- LCD: http://137.184.24.185:1317/
- Explorer: http://hambach.regen.aneka.io/
- Chain-id: regen-hambach-2
- Faucet: https://regen.vitwit.com/faucet
- RPC: http://167.71.182.156:26657/
- LCD: http://167.71.182.156:1317/
- Explorer: http://devnet6.regen.aneka.io/
- Chain-id: regen-devnet-6-7
regen-devnet-5 is active now and here are some important details:
- Explorer: https://devnet.regen.aneka.io
- Faucet: https://faucet.devnet.regen.vitwit.com
- RPC: http://18.220.101.192:26657
- LCD: http://18.220.101.192:1317
Persistent Peer: b2679a74d6bd9f89a3c294c447d6930293255e6b@18.220.101.192:26656
Here are the instructions to run a validator for regen-devnet-5:
- Stop your existing regen validator (if any)
sudo service regen stop- Run the latest setup script
git clone https://github.com/regen-network/testnets
cd testnets
git pull
chmod +x scripts/devnet-val-setup.sh
./scripts/devnet-val-setup.sh <your_key_name> <your_validator_moniker_name>The testnets listed below are no longer active but are retained here for posterity. Do not waste your time trying to join them :)
Focus: Application specific testing and simulation of ecosystem service credit creation and trading with production ready MVP blockchain.
*Estimated Dates: Feb 8th — March 15th 2021
Minimum points to be allocated: 1800 $REGEN staking token rewards: 500,000
Aplikigo-1 Testnet is scheduled to start on 8th Feb, 2021. More details here
Testnet Plan: Aplikigo-1 Testnet Plan
TL;DR
- Explorer: https://aplikigo.regen.aneka.io
- RPC: http://public-rpc1.regen.vitwit.com:26657
- LCD: http://public-rpc1.regen.vitwit.com:1317
- Persistent Peers (Feel free to add yours and create a PR)
35d64042e1a5f6466b2b1540fa2e859dfc49666e@public-rpc1.regen.vitwit.com:26656,9082e4d408b0794f884f8c1733d7d11ffb010e38@161.35.51.84:26656,937bbb7a231a870452dd595a442a191d609a26a5@116.203.20.144:26656,
We are also supporting the BigBang-1 Stargate testnet
Focus: Adversarial testnet and network load testing with Regen Ledger running CosmWASM. This testnet may also morph into a Game of Zones testnet, as we are sensitive to the larger community opportunity.
- Testnet schedule: 13th March - 24th Apr, 2020 (6 weeks)
- Total points to be allocated: 1100+
- Gentx submissions: 9th March 1500UTC (start date) - 12th March 0900 UTC (end date)
- Genesis release time: 12th March, 1600UTC (23 hours before genesis time)
- Network start time: 13th March, 1500UTC
Algradigon-1, an incentivized testnet was launched on 23rd Jan at 17:00UTC with 38 validators signing on the genesis block. The validator set was increased to a total of 49 validators and total of 4 upgrades were executed in a span of two weeks by 7th Feb.
Total points allocated: 900
Note The incentive program for the testnet was ended on 12th Feb 2020 at 12:00UTC
Important links
- Postmortem report of the testnet: https://medium.com/regen-network/postmortem-of-algradigon-1-eb2dc7652850
- Testnet results: https://medium.com/@gregorylandua/algradigon-1-testnet-results-d32d8cfca615
congo-1 was the first community-driven testnet between 7th November 2019 and 17th January 2020, at which point it was abandoned in order to prepare for the next incentivised testnet.
regen-test-1001 ran between August and October 2019. It is now defunct, having discovered a cosmos-sdk bug in governance-driven parameter updates logic.
regen-test-1000 hit some weird consensus error on app state at block 2.
Testnet xrn-test-3 started producing blocks at 2019-03-29T19:44:44.571815638Z and is now defunct.
xrncli can be configured to connect to the testnet as follows:
xrncli init --chain-id xrn-test-2 --node tcp://xrn-us-east-1.regen.network:26657Deployed at 2018-12-19T20:40:06.463846Z.
The initial Regen Ledger testnet xrn-1 was deployed on 2018-12-19.
Linking a validator address to your identity is how we ensure the right validator is rewarded for the hard work of participating in our incentivized testnets. Please back up your keys and maintain the same keys throughout testnet operations if possible. If you have a key management issue, please use the same Moniker in generation of new keys and notify the team.
The same validator keys can be used for different testnets, and even for main net (as long as you practice good key management).
Here are instructions for generating keys for regen ledger. This is well-tested on Ubuntu 18.04, if you are using different arch and running into issues, please use manual key generation instructions below
git clone https://github.com/regen-network/testnets
cd testnets
git pull
chmod +x scripts/gen_val_keys.sh
./scripts/gen_val_keys.sh <your_key_name>Step-1: Install Go 1.15.x (Optional)
$ sudo apt update
$ sudo apt install build-essential jq -y
$ wget https://dl.google.com/go/go1.15.2.linux-amd64.tar.gz
$ tar -xvf go1.15.2.linux-amd64.tar.gz
$ sudo mv go /usr/local
$ echo "" >> ~/.bashrc
$ echo 'export GOPATH=$HOME/go' >> ~/.bashrc
$ echo 'export GOROOT=/usr/local/go' >> ~/.bashrc
$ echo 'export GOBIN=$GOPATH/bin' >> ~/.bashrc
$ echo 'export PATH=$PATH:/usr/local/go/bin:$GOBIN' >> ~/.bashrc
$ source ~/.bashrc
$ go version # should print 1.15.2Step-2: Install Regen (from source)
$ git clone https://github.com/regen-network/regen-ledger
$ cd regen-ledger
$ git checkout v0.6.0-alpha6
$ make installStep-3: Create your key (keyname can be anything):
$ regen keys add <your_key_name>Use the address generated from above command to fill your KYC