Skip to content
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

Configuration support fully specified source to destination mapping #53

Closed
michaelkaplan13 opened this issue Oct 4, 2023 · 0 comments · Fixed by #59
Closed

Configuration support fully specified source to destination mapping #53

michaelkaplan13 opened this issue Oct 4, 2023 · 0 comments · Fixed by #59
Assignees
Labels
enhancement New feature or request

Comments

@michaelkaplan13
Copy link
Collaborator

Context and scope
Currently, the relayer configuration contains "source subnets" and "destination subnets", such that the relayer will try to relay all messages from any of the source subnets sent to any of the destination subnets. It will likely be desirable to be able specify the specific point-to-point connections that the relayer should support. This would apply to the following use case of a new subnet being created (call it Subnet XYZ), and the project wanting to provide interoperability with two other existing subnets (call them Subnet A and Subnet B). In this case, they would want to set up a relayer that supports XYZ <-> A, and XYZ <-> B, but not A <-> B

This could be implemented by adding additional configuration options that specify the full definition of the mapping for messages to be relayed, rather than assuming an "all sources to all destinations" mapping.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Archived in project
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants