From 8caaab679a33529eca9fc4ba9e8e117185860002 Mon Sep 17 00:00:00 2001 From: Carlos Rodriguez Date: Mon, 20 Mar 2023 13:15:24 +0100 Subject: [PATCH] add reasoning for migration to enabled localhost --- docs/migrations/v7-to-v7_1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/migrations/v7-to-v7_1.md b/docs/migrations/v7-to-v7_1.md index c01c8a05375..da2bf051921 100644 --- a/docs/migrations/v7-to-v7_1.md +++ b/docs/migrations/v7-to-v7_1.md @@ -20,7 +20,7 @@ In the previous release of ibc-go, the localhost `v1` light client module was de An [automatic migration handler](https://github.com/cosmos/ibc-go/blob/09-localhost/modules/core/module.go#L133-L145) is configured in the core IBC module to set the localhost `ClientState` and sentintel `ConnectionEnd` in state. In order to use the 09-localhost client chains must update the `AllowedClients` parameter in the 02-client submodule of core IBC. This can be configured directly in the application upgrade handler or alternatively updated via the legacy governance parameter change proposal. -We __strongly__ recommend chains to perform this action. +We __strongly__ recommend chains to perform this action so that intra-ledger communication can be carried out using the familiar IBC interfaces. See the upgrade handler code sample provided below or [follow this link](https://github.com/cosmos/ibc-go/blob/09-localhost/testing/simapp/upgrades/upgrades.go#L85) for the upgrade handler used by the ibc-go simapp.