Composable joins the Replicated Security Testnet today! It’s been over two months since we last launched a consumer chain, so today’s rehearsal involved a bit of shaking off some dust. The Composable testnet chain, banksy-testnet-3, will remain online for about a week so the dev team can run some tests.
Today’s rehearsal timeline was as follows (all times in UTC):
- 14:52 - Composable upgrade proposal submitted
- 15:03 - First cc addition proposal submitted on provider chain
- 15:22 - Composable upgrade proposal passed
- 16:12 - Composable upgrade height reached, chain paused
- 16:15 - Consumer chain banksy-testnet-3 offboarded from provider chain
- 16:20 - Second cc addition proposal submitted on provider chain
- 16:27 - Spawn time for banksy-testnet-3
- 18:12 - Enough Composable validators upgraded to reach quorum, Composable chain starts the “three block” countdown
- 18:23 - Blocks on consumer chain
- 18:29 - Relayer up, interchain secured
We had to resubmit the consumer-addition proposal on the provider side because > the proposal was initially configured with incompatible parameters for the chain ID suffix and the revision number (“banksy-testnet-3” and revision_number: 1). For consumer chains, the integer suffix of the chain ID must match the revision number ("chain_id": "banksy-testnet-3" and "revision_number": 3), otherwise IBC connections cannot be established. Before resubmitting, we had to offboard the improperly-configured banksy-testnet-3, which also triggered a cleanup of all consumer key assignments, so we asked validators to temporarily provision their validator keys to help get blocks going. We’re updating our runbooks to make sure we don’t run into this hiccup again!
We learned a lot from today, and we’re glad that we were able to pull together a rehearsal on a relatively tight timeline for the Composable team. Looking ahead towards the Composable mainnet process and potentially future rehearsals, we’ll be sure to align earlier on communications strategy and the exact timings of when each step will happen. Every practice rehearsal makes us better at coordinating and operating, which will help Cosmos Hub become a bigger, more secure, and more inclusive ecosystem. Massive thank you to all the Cosmos Hub Testnet validators and the Composable validators who participated in today’s event!
Shout outs:
- KrEwEdk0 from CitadelOne for helping to answer questions and debug in both the Cosmos Hub Discord and the Composable Discord
- 20/20 from VirtualHive for teaching us new things about jq today