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
Objective:
Test if a developer on a source - chain S - can send an inference request to a destination chain - chain D - Warden via an IBC on Chiado, verify and fetch the result.
Assumptions & Remarks
The source chain C has an IBC connection to the Hub.
The destination chain D has an IBC connection to the Hub.
The user making the request has gas fees on both chain S and chain D.
Hypothesis
Eureka is not yet released, but there are four routes I want to investigate.
Note, it may be that none or all of these are possible. It's exploratory.
Cosmwasm contracts deployed on the Hub (Hub <> Warden)
Cosmwasm contracts deployed on S connected to the Hub (e.g. Osmosis <> Hub <> Warden)
Solidity contract deployed on an ETH L2 (e.g. GMX on Arbitrum <> Hub <> Warden)
DoD
Create a single IBC connection to the Hub on Chiado
Test transaction for each of the four Routes
Prior work
It may be that it's cosmos hub <> ethereum that needs the IBC eureka connection, and warden <> cosmos hub can even stay on an older IBC connection; needs investigation.
Objective:
Test if a developer on a source - chain S - can send an inference request to a destination chain - chain D - Warden via an IBC on Chiado, verify and fetch the result.
Assumptions & Remarks
The source chain C has an IBC connection to the Hub.
The destination chain D has an IBC connection to the Hub.
The user making the request has gas fees on both chain S and chain D.
Hypothesis
Eureka is not yet released, but there are four routes I want to investigate.
Note, it may be that none or all of these are possible. It's exploratory.
DoD
Create a single IBC connection to the Hub on Chiado
Test transaction for each of the four Routes
Prior work
It may be that it's cosmos hub <> ethereum that needs the IBC eureka connection, and warden <> cosmos hub can even stay on an older IBC connection; needs investigation.
We've investigated a similar ticket before with fewer routes, but without a comprehensive testing.
See test setup here: https://github.com/orgs/warden-protocol/projects/19/views/1?pane=issue&itemId=86875251&issue=warden-protocol%7Cwardenprotocol%7C1064
Eureka is a work in progess and not everything may be fully available / working
https://skip-protocol.notion.site/EXT-IBC-Eureka-Fast-Cheap-and-Seamless-Interoperability-between-Cosmos-and-Ethereum-1968c17818cb80b880d6f2c3b917ae79
https://github.com/cosmos/solidity-ibc-eureka
cosmos/ibc-go#6985
The text was updated successfully, but these errors were encountered: