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
I don't think this is an actual bug, but rather a some tiny misconfiguration on my side or just something that I'm completely missing...But it would be incredibly helpful to get some ideas and insights where the error I'm facing is coming from.
Its about getting a provider to validate a consumer locally on the same machine via relayer. Here are the steps:
I cloned the interchain-security repo (v5.1) created the provider and consumer binaries
I configured the provider and got it running
I created a consumer via ignite scaffold chain ccv --consumer --skip-proto --no-module
I initialise the consumer via ignite init ...
Then I did the necessary steps to add the consumer via proposal, vote for it and await the spawn_time and set the genesis_time > spawn_time
When the spawn_time passes i copy the relevant ccvconsumer parts (exported from the provider) to the consumer's genesis
then I start the consumer and it starts producing blocks via the initial_val_set provided by the genesis.json
Then I added hermes account keys of both provider and consumer to the hermes config
Next I create the connection via hermes create connection --a-chain ccv --a-client 07-tendermint-0 --b-client 07-tendermint-0
And finally I create the channel via hermes create channel --a-chain ccv --a-port consumer --b-port provider --order ordered --a-connection connection-0 --channel-version 1
Until here everything works fine. Now it gets weird:
I noticed when I tried to run the same logic by using the interchain-secuirty-cd binary directly (without using ignite), then all the steps work fine until hermes create connection..., here it always throws the same error:
failed during an operation on client '07-tendermint-0' hosted by chain 'provider': chain provider is missing trusted state smaller than target height 0-36
Then I tried to reproduce the exact same steps as above (i.e. I created another consumer project via ignite) with the exact same provider settings/chain, same proposal logic, etc. and I always get this same error...
When I check the provider's client its always "Active" but also always stuck at the initial height:
So it looks like the relayer is not successfully relaying the consensus state from the consumer to the provider (but only for my second consumer 😅)
I've checked the differences between the codebases of the Cosmos SDKs of the consumers and they are basically the same (just with different chain ids and app names) and also the config folders, (i.e. genesis.json and toml files) are identical (again just name and chain id differs)
Note: Every time i run either one of the chain pairs (consumer1 with provider or consumer2 with provider) I reset the data of both chains and start both chains from block 0.
Also the .hermes config is the same for both consumers except the "id" and looks like this:
Any ideas why this is happening? Is there some weird caching going on where if you configured a connection (or channel) once than it gets a mismatch or something the second time? How could i debug this further?
Any ideas are very welcome 🙏🏻
The text was updated successfully, but these errors were encountered:
Hi there,
I don't think this is an actual bug, but rather a some tiny misconfiguration on my side or just something that I'm completely missing...But it would be incredibly helpful to get some ideas and insights where the error I'm facing is coming from.
Its about getting a provider to validate a consumer locally on the same machine via relayer. Here are the steps:
ignite scaffold chain ccv --consumer --skip-proto --no-module
ignite init ...
ccvconsumer
parts (exported from the provider) to the consumer's genesisinitial_val_set
provided by the genesis.jsonhermes create connection --a-chain ccv --a-client 07-tendermint-0 --b-client 07-tendermint-0
hermes create channel --a-chain ccv --a-port consumer --b-port provider --order ordered --a-connection connection-0 --channel-version 1
Until here everything works fine. Now it gets weird:
I noticed when I tried to run the same logic by using the
interchain-secuirty-cd
binary directly (without using ignite), then all the steps work fine untilhermes create connection...
, here it always throws the same error:Then I tried to reproduce the exact same steps as above (i.e. I created another consumer project via ignite) with the exact same provider settings/chain, same proposal logic, etc. and I always get this same error...
When I check the provider's client its always "Active" but also always stuck at the initial height:
So it looks like the relayer is not successfully relaying the consensus state from the consumer to the provider (but only for my second consumer 😅)
I've checked the differences between the codebases of the Cosmos SDKs of the consumers and they are basically the same (just with different chain ids and app names) and also the config folders, (i.e. genesis.json and toml files) are identical (again just name and chain id differs)
Note: Every time i run either one of the chain pairs (consumer1 with provider or consumer2 with provider) I reset the data of both chains and start both chains from block 0.
Also the .hermes config is the same for both consumers except the "id" and looks like this:
Any ideas why this is happening? Is there some weird caching going on where if you configured a connection (or channel) once than it gets a mismatch or something the second time? How could i debug this further?
Any ideas are very welcome 🙏🏻
The text was updated successfully, but these errors were encountered: