Code Browser

Use panic in WriteErrorReceipt

fix: add event and event emission for `FLUSHCOMPLETE`

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

build(deps): Bump github.com/CosmWasm/wasmvm from 1.4.1 to 1.5.0 in /modules/light-clients/08-wasm (backport #5117)

Add a helper function to create a mock contract. (backport #5162)

Change to StoreCodeUnchecked in Genesis and snapshotter (backport #5167)

Call `Pin` during app inisitalization (backport #5161)

Add comment when setting the version to counterparty version

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.

Add to docstring with explanation about channel state

Remove incorrect code

Support wasm tests on forks

Remove incorrect code in TimeoutPacket

Allow empty error receipt proof if sender is authorized

refactor: remove unnecessary decrement when fast forwarding upgrade sequence

Reorder call to application callback so it happens after we write state.

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.