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

Counterparty Address mapping must contain channelID #822

Closed
AdityaSripal opened this issue Feb 1, 2022 · 1 comment
Closed

Counterparty Address mapping must contain channelID #822

AdityaSripal opened this issue Feb 1, 2022 · 1 comment
Assignees
Labels

Comments

@AdityaSripal
Copy link
Member

AdityaSripal commented Feb 1, 2022

Currently the counterparty address is only a mapping from: <address> -> <counterparty_address>.

However, a relayer will have multiple counterparty addresses for a given address, since their counterparty address will be different for each counterparty chain.

Thus, we must map from (address, channelID) => (counterparty_address).

Action Items:

  • Include ChannelID in MsgRegisterCounterpartyAddress
  • Change the SetCounterpartyAddress and GetCounterpartyAddress to take in a channelID
  • Map Counterparty address to a key that contains tuple: address/channelID

Thanks to @soareschen for pointing out the issue.

@colin-axner
Copy link
Contributor

closed by #937

CosmosCar pushed a commit to caelus-labs/ibc-go that referenced this issue Nov 6, 2023
When validating the Signed Header in Validate Basic we should check if
the aggregator hash corresponds to the hash of the validator set.

Closes: cosmos#820
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

No branches or pull requests

3 participants