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
Osmosis version: v9 or main
OS & Version: Linux ubuntu 22.04
Commit hash: 9165ac2
Expected behaviour
It should be possible to send ICA commands to Osmosis (via MsgCreateBalancerPool for instance), given that the ICA Host controller has already been integrated.
Actual behaviour
When sending the MsgCreateBalancerPool over ICA to Osmosis, the following error is reported: recovered: no concrete type registered for type URL /ibc.applications.interchain_accounts.v1.InterchainAccount against interface *types.AccountI"
Meaning the ICA message codecs are not registered in the Osmosis application.
Steps to reproduce the behaviour
Start chain A (Quasar chain in my case, but can be any)
Start chain B (Osmosis on v9 tag, or main)
Run Hermes relayer connecting the two chains
Register an Interchain Account on Osmosis from chain A
Properly fund the registered ICA on Osmosis to be able to create a pool
Send the MsgCreateBalancerPool from chain A to Osmosis via ICA.
System information
Osmosis version:
v9
ormain
OS & Version: Linux ubuntu 22.04
Commit hash: 9165ac2
Expected behaviour
It should be possible to send ICA commands to Osmosis (via
MsgCreateBalancerPool
for instance), given that the ICA Host controller has already been integrated.Actual behaviour
When sending the
MsgCreateBalancerPool
over ICA to Osmosis, the following error is reported:recovered: no concrete type registered for type URL /ibc.applications.interchain_accounts.v1.InterchainAccount against interface *types.AccountI"
Meaning the ICA message codecs are not registered in the Osmosis application.
Steps to reproduce the behaviour
MsgCreateBalancerPool
from chain A to Osmosis via ICA.Backtrace
Error trace in the relayer (Hermes) output:
When submitting logs: please submit them as text and not screenshots.
The text was updated successfully, but these errors were encountered: