You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: fix migration/docs for ICA controller middleware (#2737)
* update docs/migration with the change to middleware for ICA controller
* improve variable naming
* alignment
Co-authored-by: Carlos Rodriguez <crodveg@gmail.com>
ibcRouter.AddRoute(icaauthtypes.ModuleName, icaControllerIBCModule) // Note, the authentication module is routed to the top level of the middleware stack
Copy file name to clipboardexpand all lines: docs/migrations/v3-to-v4.md
+12-1
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,18 @@ No genesis or in-place migrations required when upgrading from v1 or v2 of ibc-g
18
18
19
19
## Chains
20
20
21
-
### Fee Middleware
21
+
### ICS27 - Interchain Accounts
22
+
23
+
The controller submodule implements now the 05-port `Middleware` interface instead of the 05-port `IBCModule` interface. Chains that integrate the controller submodule, need to create it with the `NewIBCMiddleware` constructor function. For example:
where `icaAuthIBCModule` is the Interchain Accounts authentication IBC Module.
31
+
32
+
### ICS29 - Fee Middleware
22
33
23
34
The Fee Middleware module, as the name suggests, plays the role of an IBC middleware and as such must be configured by chain developers to route and handle IBC messages correctly.
0 commit comments