-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
for same path, channel with different client and connection possible? #1311
Comments
In rly, a path embodies a single pair of clients, connections, and then the channels (one to many) on top of that connection pair. To relay channel(s) on a different pair of clients/connections, you should configure a separate path. However, it is usually best practice to use the canonical pair of clients and connections between chains for all channels. rly will give a warning when creating new clients if a client already exists. |
As far as I understand a client refers to 2 chains. Like chain A and B. So if a connection and channel is created - here also it refers to chain A and B. Afaik, clients are updated e.g. on each relay. So the more connections there are, the likely hood of clients staying active is even higher with channels using same connections, right? Isn't this a good practice? So in case of rly I have to setup an extra path for this case? |
How does
client
,connection
andchannel
related to each other? Like for this path example:What happens if I create a new channel with a new client and connection? So I'd have 2 channels in
config.yaml
. Seems like in config for each path only ONE client-id and connection-id can be configured.Guess relayer would still relay both channels, but for what are client-id and connect-id used then? Was looking into this doc, but can't find much info about this: https://github.com/cosmos/relayer/blob/main/docs/create-path-across-chain.md
The text was updated successfully, but these errors were encountered: