-
Notifications
You must be signed in to change notification settings - Fork 35
stride (ics) relayer fails to start #629
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Let me have a look. we tested with neutron. |
It seems starship is few major versions behind. Here's a PR to create an image from their latest release: #630 |
@0xpatrickdev @Anmol1696 I learnt today that at this point this most likely a Ref: #631 |
Well yes the issue has been during the handshake for the inital ics creation. |
I am also not finding docs around how to setup stride as a consumer chain. If you have anything on this please share it here. |
We wanted to test with four chains: |
Is there something special we need to do for ICS chains? I just followed the instructions for normal starship setup instructions. |
Well we need to debug the code that we are using to setup the ICS chains. Stride errors out on the hermes relayer. |
Which faucet are you using the it? can you try with |
Uh oh!
There was an error while loading. Please reload this page.
With
yarn starship start --config config.yaml
("@starship-ci/cli": "^3.3.0") and the followingconfig.yaml
:hermes-stride-cosmoshub-0
's status results in a continuedInit:Error
:Looking at the
init-relayer
logs:it seems we don't have a client and are unable to create a connection and channel.
The text was updated successfully, but these errors were encountered: