Gaia-9000 Planning thread


#9

Is it possible to keep the current blocks, upgrade the software and replace the chain-id to become gaia-9000?


#10

expect this key moment.


#11

No, we’ve made many breaking changes to the way things are stored in state on both the tendermint and the sdk side.


#12

Since the cosmos sdk still hasn’t been released, maybe ~Monday for gaia-9000


#13

We are deep in simulator bug finding territory on the v0.25 release.

All Hail the Simulator.


#14


how will the new bech32 effect the GoS registration?
some people still use cosmosaccaddr1 for signup


#15

I have a tool for updating the bech32 hrp prefixes. It’s not an issue.


#16

we are waiting for sdk v0.25 and gaia-9000…


#17

The SDK team is planning to cut v0.25 rc0 zero today and start the internal testnet.

How would be people feel about targeting Monday for gaia-9000?


#18

monday is the best! agree!


#19

Monday is perfect!!!


#20

oh, good agree! ㅎㅎㅎㅎ


#21

Monday sounds perfect! Thanks :slight_smile:


#22

Sounds good, agree!:grin:


#23

Any update on gaia-9000


#24

I’m working on the scripts to convert gaia-8001 state to gaia-9000 state but Devcon meetings keep distracting me.


#25

Cool @zaki,I started working on v0.25.0.When I try to run a full node for a new testnet on 0.25,it’s giving me panic about bech32 address.Just wanted to confirm if this has been checked in any of your simulations.


#26

Same here. The error seems to be triggered always from gaiad start but not when executing directly from docker: docker run -vpwd/build:/gaiad tendermint/gaiadnode with a clean state.


#27

This issue might be relevant to you. https://github.com/cosmos/cosmos-sdk/issues/2651

Note gaia-8001 state is not directly compatible with v0.25


#28

The state munging script is mostly complete(https://github.com/cosmos/testnets/blob/gaia-9000/gaia-9000/gaia9000/src/index.ts). Now just waiting on v0.26 release from the sdk team