# Juno IBC Recovery

## The Issue
The juno-1 mainnet halted on block 2578108.
...

## Solution

>As per the IBC documentation [here](https://ibc.cosmos.network/main/ibc/proposals.html)

In the case that a highly valued light client is frozen, expired, or
rendered non-updateable, a governance proposal may be submitted to
update this client, known as the subject client. The proposal
includes the client identifier for the subject and the client
identifier for a substitute client. Light client implementations may
implement custom updating logic, but in most cases, the subject will
be updated to the latest consensus state of the substitute client,
if the proposal passes. The substitute client is used as a "stand
in" while the subject is on trial. It is best practice to create a
substitute client after the subject has become frozen to avoid the
substitute from also becoming frozen. An active substitute client
allows headers to be submitted during the voting period to prevent
accidental expiry once the proposal passes.

## Preconditions
- The chain is updated with ibc-go >= v1.1.0.
- Recovery parameters are set to true for the Tendermint light client (this determines if a governance proposal can be used). If the recovery parameters are set to false, recovery will require custom migration code.
- The client identifier of an active client for the same counterparty chain.
- The governance deposit.

## Submitting Governance Proposal

The <active-client-id> should be a client identifier on the same
chain as the expired or frozen client. This client identifier should
connect to the same chain as the expired or frozen client. This
means: use the active client that is currently being used to relay
packets between the two chains as the replacement client.

## Draft Proposal

#### Details:

As you may know, recently the Juno chain halted at block height `2578108` due to ...

To restart the chain a hard fork was necessary. This action comes with the unfortunate side effect of freezing all IBC light clients between Juno and other chains.

While these light clients are frozen, no packets can travel via IBC which means token transfers come to a standstill. IBC includes mechanisms for unfreezing a light client via a governance proposal that must be passed on both chains. Should the governance proposal pass on both chains the light clients can be updated so that they are no longer in a frozen state and then IBC transfers can resume!

#### Proposal goal:

This proposal is intended to initiate the unfreezing process of the IBC light clients between [SRC-CHAIN] and Juno. Currently both clients lay in a frozen state, which means that every connection and channel associated with those clients are also frozen and as such no packets can currently travel between the two chains on these channels.

To rectify the issue a governance approved update to the client on both chains must be passed. This update will unfreeze the clients utilizing the built-in mechanisms provided by IBC and return full functionality to the channels between both chains.

- By voting `YES`, you are signalling your approval for unfreezing the IBC light client on [SRC-CHAIN].
- By voting `NO`, you are signalling your disapproval for unfreezing the IBC light client on [SRC-CHAIN].
- By voting `NO W/ VETO`, you are signalling your willingness to leave the network if such a proposal is passed.
- By voting `ABSTAIN`, you are signalling that you do not intend to vote in favor or against the proposal but accept the result of the vote.


*This proposal has no effect on [SRC-CHAIN] besides re-enabling the currently frozen IBC light client between the two chains.*
    
## Client List

### Active Clients
> these clients had activity
- Juno <-> Osmosis
  07-tendermint-0 <-> 07-tendermint-1457
- Juno <-> Terra
  07-tendermint-63 <-> 07-tendermint-32
- Juno <-> Cosmos Hub
  07-tendermint-3 <-> 07-tendermint-439
- Juno <-> Sifchain
  07-tendermint-9 <-> 07-tendermint-37
- Juno <-> Comdex
  07-tendermint-92 <-> 07-tendermint-30
- Juno <-> Chihuahua
  07-tendermint-79 <-> 07-tendermint-54
- Juno <-> Secret
  07-tendermint-108 <-> 07-tendermint-23
- Juno <-> Akash
  07-tendermint-80 <-> 07-tendermint-84
- Juno <-> Stargaze
  07-tendermint-44 <-> 07-tendermint-13
- Juno <-> Persistence
  07-tendermint-89 <-> 07-tendermint-49
- Juno <-> Dig Chain
  07-tendermint-100 <-> 07-tendermint-17
- Juno <-> BitSong
  07-tendermint-33 <-> 07-tendermint-9
- Juno <-> KiChain
  07-tendermint-126 <-> 07-tendermint-15
- Juno <-> Bitcana
  07-tendermint-110 <-> 07-tendermint-12
- Juno <-> Axelar
  07-tendermint-150 <-> 07-tendermint-25

### Other Clients
> these clients had what appeared to be no activity
- Juno <-> Umee
  07-tendermint-131 <-> 07-tendermint-11
- Juno <-> Sentinel
  07-tendermint-130 <-> 07-tendermint-100
- Juno <-> Regen
  07-tendermint-13 <-> 07-tendermint-80
- Juno <-> Omniflix
- Juno <-> LikeCoin
  07-tendermint-139 <-> 07-tendermint-32
- Juno <-> Injective
  07-tendermint-127 <-> 07-tendermint-101
- Juno <-> Gravity Bridge
- Juno <-> Fetch.AI
- Juno <-> E-Money
- Juno <-> Cronos  

## Resources

https://github.com/cosmos/ibc-go/blob/484cedcac875e8f96457d245d2eff816901976d5/docs/ibc/upgrades/quick-guide.md

https://ibc.cosmos.network/main/ibc/proposals.html

https://www.mintscan.io/osmosis/proposals/115