Looking for new testnet participants made from mainnet ledger

Telegram: @andreisid
Validators: 1
Valconspub: cosmosvalconspub1zcjduepq6wtpv8stjhx2exsp4akvf240cpukhlyq5gepsmesqy7ckn9yadtq37djy3
Chain-ID: ch3-replica

1 Like

telegram: @syncnode

Validators: 2 (or more if required)

cosmosvalconspub1zcjduepqmxfl83u58jvtdd3dtls3720jjc6m5g2pgvekfmfevlgx8xqj405q05eauw

cosmosvalconspub1zcjduepq0kf8suuyme92vgafnq6xnes8x0tztvm237yje8v7nghaytr7w6ks4tlwj5

1 Like

Happy to help!

Telegram: @jacksteroo

Validators: 2

cosmosvalconspub1zcjduepqj5nvp9eufd2ualq2239q7qdq9s6qp6cx2dh5575tavl5cx3ge6zq7mpqzw
cosmosvalconspub1zcjduepq3a4ymdddr3ytdrsrnjjaaaxrftcf8ul9yclpscp8dnyk4ce90tdq4qene0

chain-id idea:

cosmos-hub-canary
1 Like

We are happy to participate :slight_smile:

Telegram : @dimiandre
Validators : 3
Valconspub:
cosmosvalconspub1zcjduepq5qhc3ml6cg6tx5kjslxdk5kut8d3vpqld0grvfrhrpfga69yf89qv5phvm
cosmosvalconspub1zcjduepqcfncjlkvjzfwmq27k6n542qx3wwh2a0sxd8pagapgy20ufjeznzqhwurn0
cosmosvalconspub1zcjduepqsv5gm20rq0p36cknhy3ur6tc4h36cwzst40t8vm9aev0cnmsl0lqfhzey5
Chain-ID : chain-llenge

1 Like

I want to thank you for the initiative, and others validators that want help. But.
IMO The correct way is to kill the current testnet 13006, and start a new testnet aka gaia-13007 for the simulations.
https://hubble.figment.network/cosmos/chains/gaia-13006

Im ready for that.

Although setting up another gaia testnet is a way to test, forking the mainnet would be a better testing environment to really test the real upgrade on the Cosmos Hub.

1 Like

I dont want to give validators burden to run this testnet for long time, so I guess I want to stop running this testnet after we feel the launch is successful, running about less than a week.

This is my intention of this testnet(it is mostly for testing upgrade procedure).

1 Like

Option A= Fork cosmos and launch cosmos hub 3 meanwhile is running cosmos hub2.

Option B= kill 13006, start 13007 simulate there .

Option C= Run this testnet where some validators manage more validators. (unreal scenery)

I’m for the option A or B, I don’t see the option C.

Option A: Cosmos Hub 2 and Cosmos Hub 3 should not be running simultaneously. It will be a mess if Cosmos Hub 2 still running when Cosmos Hub 3 is online. This is not an option.

Option B: Testnet is always available to test new software features. Unless there is new major software release, we don’t have to bother new testnet. I agree we need an upgrade simulation.

Option C: To simulate the Cosmos Hub upgrade, @bharvest is suggesting to fork Cosmos Hub 2, start a new network with another chain-id. This is purely a simulation/practice of the upgrade process. If you would like to use your testing node to simulate this upgrade process, you can simply replace the validator key in your testing node to run this. A single validator running multiple validator nodes can be easily achieved. I think we already have enough keys to start this simulation. I don’t see why this is an unreal scenario. If this is smooth, I think we should make this as a best practice for future upgrade.

Option A : IMO is the best option and can be done. If can’t be done, then someone from Tendermint or Cosmos team can confirm I’m Wrong, and says this option CANT be done. But I’m very sure, like 99.99% that can be done.

and when= Option C : To simulate the Cosmos Hub upgrade, @bharvest is suggesting to fork Cosmos Hub 2.

here (This is not a fork neither) this is just one private simulation. not a fork.

BUT hey, here
If you want to do the simulation or others are planning or what someone wants to do, do it, I am not saying that you or others do not do it, I am saying that I will not participate because I do not see it.

in the same way here I am free to say why I do not participate and which in my opinion is the best option.
ant just to finish.
Im not sure if people understand when is a fork and when is not. I have that part very clear.

One more time, thanks for the good intentions.

1 Like

Valconspub: cosmosvalconspub1zcjduepqwzsyfpc80mn3f4zc0juzk3rqcrtlu9y3fd6zzcrwu854dx9xtg9qvajt5r
Validators: 1
Telegram: @marco809
Chain-ID: hub-upgrade-test

  1. upgrading gaia-13006 is not adequate.

Problems on using gaia-13006 is that it is already based on new gaia version so we cannot test migrate function, which transforms genesis from old gaia to new gaia version.

  1. Not a fork to be a mainnet

When we launch hub3, it should be based on proper governance procedure, so, whatever we launch from hub2, it is not a mainnet because it is not based on any onchain governance. Because it is not a mainnet, we should not use cosmoshub-3 as a chain-id.

  1. more real environment testing

The mainnet ledger is the best environment to test the program because the ultimate target of the new software is mainnet. It will give us the best confidence.

Based on above 3 reasons, I think it explains why our approach is reasonable. But, it is not a mandatory to participate. It is a community self-motivated testnet who are not satisfied with last upgrade procedure, so that who wants to make things much more certain by our hands.

Just clarify
When I talk about kill 13006 is for start a new testnet 13007 soft 0.34.6.
That is very clear. And for that is testnet. For public testnet, and test software upgrade before do it on mainnet. Not sure the point of keep running 13006 and start your private testnet.
But like from 100 validators and core dev team and more people, Im the only one talking about this, just ignore me.

Count us in!

Telegram:
@kwafan

Valconspub:
cosmosvalconspub1zcjduepql4l34spcvcg5ffhdd9tcaxauuy0k7mkr0fpf5f2kedj8zyrmkfyqapu8r0

Validators:
1

Chain-id:
cosama

[Announcement] procedure to participate in our testnet

Now we are ready to launch the testnet as below!
Onboard please!

step by step : https://www.notion.so/export-migrate-procedure-5d0cd651d83d4aee89011287943dedc9

valconspub replacement plan : https://docs.google.com/spreadsheets/d/1fIiusivqyPg9JgAbQ2i6yxZuJ6JFCKnY94Lzab2Tcms/edit?usp=sharing

1 Like

B-Harvest nodes : 65d4fba1f075414fdca387682c5168c4b7763f11@211.192.161.41:36656,f22a4bb961f30a78dcbc8a43cacecb31bb4efb87@211.192.161.41:46656,36586a259b9c63085c191180a287ebd6848df775@211.192.161.41:56656

DragonStake:

cosmosvalconspub1zcjduepqpa0mka89peexur9nrhpdcr5zdg79ke2z8eqmnc8t0x9gameqgm0qzum3fz

DelegaNetworks:

cosmosvalconspub1zcjduepq8pqz0d9ty05j8pafhrdetdl0dmwy6w0n7uc89vyzfgw43j4qxthsn8t7cd

peer from marco
0029b3fb59f72971b5a3b827a22f3c38fddd33ce@206.189.52.199:26656

peer from ateam
9edc87c8610786b112c1e1c4191f30ef6a5019e0@49.247.215.16:26656

dd007089b861900dea9ee4280451106c1a4ff41a@35.194.181.217:26656
3489f38abd2b6c480d29e28df6ea2fdb479478df@35.187.195.115:26656
fb6e99658c5d64e2cbd9bf38bfb8569f8576628e@35.201.157.128:26656

moonlet:

baddd32744482043684bec643e21fc539c21bed1@54.171.160.110:26656