Re-enable IBCs to Osmosis, Juno, and Crescent

Governance & Proposals
102

Big Yes! Thank you.

103

Yes let’s go

104

as always ed comes thru

105

Let’s do it as it sounds to help us in a big way!

106

Absolutely Yes.

107

Yes from me. Thanks to all and keep up the great work! :+1::+1:

108

Let’s do it Ed! YES

109

Yes from me

110

Please can you provide some answers to the following points:

  • Which testnet is being used to test these changes?
  • Who is involved in the testing?
  • Can you provide a link to the test plan you are working to and test results achieved so far?
  • Is the testing simulating the effects of any trapped liquidity that is present in the classic mainnet closed IBC channels?
  • Do you know the precise amounts of liquidity that is trapped in the closed IBC channels?
  • What do you expect the effects to be once the IBC channels are opened and that trapped liquidity is released into classic mainnet?
2 Likes
111

Big Yes

1 Like
112

Yes!!!

1 Like
113

Oc Yes, let’s move forward.

114

Yes from Bali, Indonesia

115

Un voto Yes :cowboy_hat_face::+1::+1::+1:

116

Sure here are the details
Testnet IBCs are running between grad-1 (osmosis testnet), rebel-2 (terra testnet), and rebel-3 (my local machine)
Prelim testing the code has been by Notional , integration testing is done by me; however code review sign off has been done is Notional, Osmosis, Terra Rebels, and Interchain
I don’t have a link, but here is what happened.

  • (pass) Setup clients, connections, and channels between the three testnets
  • (pass) Transfer lunc to osmo, and vice versa via IBCs
  • (pass) Close the channel via code on the lunc side (channel.State = ibcchanneltypes.CLOSED)
  • (pass) Ensure no chain halt required
  • (pass) Ensure that the app SetChannel state is now closed via LCD
  • (pass) Ensure IBC transfer cannot happen via closed channel (ERROR the requested port/channel (‘transfer’/‘channel-0’) on chain id ‘rebel-3’ is in state ‘CLOSED’; expected ‘open’ state)
  • (pass) Open the channel via code on the lunc side (channel.State = ibcchanneltypes.OPEN)
  • (pass) Ensure no chain halt required
  • (pass) Confirm that the app SetChannel state is now open via LCD
  • (pass) Transfer lunc to osmo, and vice versa via IBCs

There are some other things I want to hammer out regarding what happens to a validator that doesn’t upgrade, and unfreezing of the tendermint clients, and i’ll report what happens with them once I do.

As for the liquidity trapped, it is heavily on the Osmosis side, 41B lunc 158M ustc. I think everywhere else is nearly negligible. I cannot speculate on what will happen once the IBCs are open. I assume there may be arbitrage (I think this is already normalizing); however, there are a number of additional steps that need to happen (like unfreezing clients on both sides, setting up relayers, etc) before anything can flow back and forth.

5 Likes
117

朋友你好 :wink:

118

Yes definitely, let’s start this glory train.

119

Thanks very much for the comprehensive reply @ek826, looks good to me!

120

Why did the lunc I pledged “cancel the entrustment” for no reason?What’s going on?Is this terra station still secure?

121

osmosis as in frontier osmosis? because they have moved lunc there