Looking for new testnet participants made from mainnet ledger

Validation33 posts3,696 views24 likesLast activity Oct 2019

bharvestOP

Sep 2019 6

• Purpose • to test export/migrate functionality • to test new binary with real mainnet ledger • Procedure to participate • please reply this post with below items • valconspub(newly made only for testnet, can be multiple) • number of validator to run:you can run multiple validator if you want • contact point(telegram handle): also can dm me. • idea for chain-id • Methodology • export at certain height • replace top validator valconspub to our participants’ new valconspub • we need at least 18 validators, but I think at least 25 is necessary for safe launch with some absent • migrate to new genesis file • compare hash and launch! Launch will be tried right after we have adaquate gaia version including fixed migrate function. • How to create new valconspub : You may want to generate a new pubkey locally offline. Just run gaiad tendermint show-validator will do. If you have a new built gaiad and there is no .gaiad directory in your home, the command will generate a new directory with the priv_validator_key.json. If you want to run multiple nodes, you may backup and move the priv_validator_key.json to another place, then run gaiad…

Excerpt (1194 of 1761 characters). Read the whole post on the forum ↗

FrancescoSVC

Sep 2019 1

I believe this is crucial to plan and go ahead with. Thanks for initiating this!

Telegram: @FrancescoSimplyVC
Validators: 1
Valconspub: cosmosvalconspub1zcjduepqxevl5mrjtvzzh680rsnppastw6a2znh8kpjlxal4gmt3m3j2rn9sljtwha
Chain-ID: ch3-test

A good idea, after learning and going through it for the first time now, is for us to outline this process in the upgrade proposal so as to be a defined test procedure for the upgrade.

kwunyeung

Sep 2019 1

Telegram: @kwunyeung
Validators: 3

cosmosvalconspub1zcjduepqwavta5zhpv0jtl5ln7aw86y2dyjle9xenaqwhe0dq7ffmklmx3ls3ymghk

cosmosvalconspub1zcjduepqc29ujvmafvpccr40xhnl5n7w52qyeez8gwhdk4lhudjlc0nrzfaq2saljt

cosmosvalconspub1zcjduepqfuqpaxmycpzs7gw5qgkwnpmv278ecuneentpnhl993hak22vktlqvuudx5

Chain ID: transformer (we are testing the transformation)

wimel

Sep 2019 1

I’d like to be a part of this and run some tests.

Validators:
2
Valconspub:
cosmosvalconspub1addwnpepq2d5jcffvc8afepyf5d5jxr5tkmc0zem5ytmp8r25cskdw0kay7z6zvqjkp
–
cosmosvalconspub1addwnpepqtt4xgvgax9z94284j6lhhwlz9l548fw887pv7p39djq4u5tn0tegnd3r86
Contact DM.
Chain ID: The two names given above seem fine to me

chris-chainflow

Sep 2019 1

Our gratitude for starting this Count Chainflow in

Telegram: @chris_remus

Validators: 1

cosmosvalconspub1zcjduepq7k9ncsfjz8zvtag9tpcxh68pxyknw2hp5q3fky7e80pyylltj3esckwpan

Chain ID: community-test-hub-1

J_ATEAM

Sep 2019 1

Telegram: @wlsaud619
Validator: 1
Valconspub: cosmosvalconspub1zcjduepqj525fwk8vsrd64lft6cj6xf00ckwe2h7gc0sky455c0mjxm0drzsmgmel7
Chain-id: avengershub-1

ponchik69

Sep 2019 1

Hello everyone! We are ready to support this idea.
Telegram: ponchik69
Validators: 1 (We can do more if it necessary)
cosmosvalconspub1zcjduepqt5f2fjjj63h73lpdhxnm3jpewpzj2m6pzzwnl0n2xsspa7t7njjqrsttkh
Chain ID: comhub-1 (community hub 1)

clawmvp

Sep 2019 1

@clawmvp

cosmosvalconspub1zcjduepqu2tueyjhhy754zxcjr5k64cvuu3csnyk0arsp5n56vym2dqx0d7sjmpm36

Yelong

Sep 2019 1

Thanks @bharvest, please count me in

valconspub: cosmosvalconspub1zcjduepqgta6se8tczzxnvftkw85l8yeu3nkk3f94ywvwg6rmq588q6wml7q6s0au5
number of validator to run: 1
contact point(telegram handle): @Yelong

ping

Sep 2019 1

valconspub: cosmosvalconspub1zcjduepqcssjskt4hvp8menz4vk4wwsugaxg2h0yjalytdc4d4m6lac8jegqffjzx6
number of validator to run: 1
contact point(telegram handle): @ping.pub

bharvest

Sep 2019

valconspub for B-Harvest

cosmosvalconspub1zcjduepq96apq95x43s9zunpm6f37upd6vp22f8evztc6vrv44sl2w3l0kysxpwlm4
cosmosvalconspub1zcjduepqaraq47kraszde9jk8xscev8dgmwh5vn9c7klcxuyrrxjw6rhzmrsxmuytp
cosmosvalconspub1zcjduepqqn47r5flesk9064c7wj4x3ww84x7s66zdnm5awta95cd74ysa7sqeu20sk

chain id idea

transformer-ch2-3

cryptobabybear

Sep 2019 1

Telegram: @Mcry89
Validator: 1
Valconspub: cosmosvalconspub1zcjduepqnxh3dgn4tu570s7yf0d7rhckgmw45gklljkr6r3cm7zkvpjhtuwqz2myye

ChainId: Illiad

andreisid

Sep 2019 1

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

syncnode

Sep 2019 1

telegram: @syncnode

Validators: 2 (or more if required)

cosmosvalconspub1zcjduepqmxfl83u58jvtdd3dtls3720jjc6m5g2pgvekfmfevlgx8xqj405q05eauw

cosmosvalconspub1zcjduepq0kf8suuyme92vgafnq6xnes8x0tztvm237yje8v7nghaytr7w6ks4tlwj5

jacksteroo

Sep 2019 1

Happy to help!

Telegram: @jacksteroo

Validators: 2

cosmosvalconspub1zcjduepqj5nvp9eufd2ualq2239q7qdq9s6qp6cx2dh5575tavl5cx3ge6zq7mpqzw
cosmosvalconspub1zcjduepq3a4ymdddr3ytdrsrnjjaaaxrftcf8ul9yclpscp8dnyk4ce90tdq4qene0

chain-id idea:

cosmos-hub-canary

kris.fish

Sep 2019 1

We are happy to participate

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

melea-trust

Sep 2019

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.

kwunyeung

Sep 2019 1

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.

bharvest

Sep 2019 1

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).

melea-trust

Sep 2019

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.

kwunyeung

Sep 2019

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.

melea-trust

Sep 2019 1

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.

mj_isback

Sep 2019

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

bharvest

Sep 2019

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.

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.

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.

melea-trust

Sep 2019

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.

kphan

Oct 2019

Count us in!

Telegram:
@kwafan

Valconspub:
cosmosvalconspub1zcjduepql4l34spcvcg5ffhdd9tcaxauuy0k7mkr0fpf5f2kedj8zyrmkfyqapu8r0

Validators:
1

Chain-id:
cosama

bharvest

Oct 2019 1

[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