Code Browser

Querier Approach for Conditional Clients

add check to make sure upgrade sequences of both channel ends are in sync after `ChanUpgradeTry` succeeds

Use `MetadataFromVersion` when unmarshalling JSON-encoded metadata

ICA host packet failure events not being emitted

Bump `wasmvm` to v2.0

Remove panics in wrapped store

Replace nil querier with error querier

Tutorial for upgrading an existing transfer channel to wire up fee middleware.

Document what application modules need to do to implement the upgrade callbacks.

Document the differences of submitting `MsgChannelUpgradeCancel` signed by a relayer or an authority.

Document usage of authority-gated `MsgChannelUpgradeInit`

Document packet flushing

Document how upgrade timeout works

Document reasoning and use cases for channel upgradability

Ensure versioned docs for 7.3.x and 8.0.x have the required changes for 08-wasm

Allow error receipt to be nil in `ValidateBasic` for `MsgChannelUpgradeCancel`

mismatch between the public key in the key file and the public key in the mnemonic

Proof in `MsgChannelUpgradeCancel` is allowed to be empty (gov override)

Emit an event when we move to `FLUSHCOMPLETE`

Remove setting counterparty upgrade info in upgrade try

Make sure that the error receipt we write always has a sequence greater than the existing one.

Change so that if the counterparty upgrade is found then we execute the code below

In `ChanUpgradeTry` it might be nice to add a note that we explicitly only set error receipts, the upgrade will not be aborted until it is proved to be incompatible in ChanUpgradeAck`.

Add comment to explain what the counterparty upgrade is used for.

`WriteUpgradeAckChannel` should have errors instead of just string (replace `fmt.Sprintf` with `fmt.Errorf`).

Add comment when setting the version to counterparty version

Add comment above or in the godoc (channel state is open, if chain executed init; or flushing, if it executed try).

Return in `MsgChannelUpgradeInitResponse` only the upgrade version and the upgrade sequence.

In `ChanUpgradeTry` move fast forward sequence down below after the call to `ChanUpgradeInit`.

Move events to message server layer instead of core level.