Closed kakucodes closed 1 week ago
inside of ict i'm having issues sending a vaa across ibc utilizing the postMessage method. it's seemingly having a problem with the channelId of the new ibc channel being accepted and potentially being seen from the relayer queries
postMessage
Error: rpc error: code = InvalidArgument desc = failed to execute message; message index: 0: dispatch: submessages: packet failed basic validation: invalid destination channel ID: identifier cannot be blank: invalid identifier: invalid request
the channel queries look like
Osmosis channels: [{STATE_OPEN ORDER_UNORDERED {transfer channel-1} [connection-0] ics20-1 transfer channel-0} {STATE_INIT ORDER_UNORDERED {wasm.wormhole14hj2tavq8fpesdwxxcu44rty3hh90vhujrvcmstl4zr3txmfvw9srrg465 } [connection-1] ibc-wormhole-v1 wasm.osmo14hj2tavq8fpesdwxxcu44rty3hh90vhujrvcmstl4zr3txmfvw9sq2r9g9 channel-1}] Wormchain channels: [{STATE_OPEN ORDER_UNORDERED {transfer channel-0} [connection-0] ics20-1 transfer channel-0} {STATE_OPEN ORDER_UNORDERED {transfer channel-0} [connection-1] ics20-1 transfer channel-1}]
it seems that on the wormhole side we should have our ibc-wormhole-v1 channel as channel-2
took longer than i would like to admit to realize that the new channel isn't getting past the init state and isn't becoming open
Last step: Trying to validate tx on wormchain side
inside of ict i'm having issues sending a vaa across ibc utilizing the
postMessage
method. it's seemingly having a problem with the channelId of the new ibc channel being accepted and potentially being seen from the relayer queriesthe channel queries look like
it seems that on the wormhole side we should have our ibc-wormhole-v1 channel as channel-2