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

Investigate: Connection's RawCounterparty.connection_id can be "" in the spec, but not our impl #175

Closed
plafer opened this issue Oct 12, 2022 · 1 comment · Fixed by #360
Assignees
Labels
A: good-first-issue Admin: good for newcomers S: specs Scope: related to IBC protocol specifications
Milestone

Comments

@plafer
Copy link
Contributor

plafer commented Oct 12, 2022

This issues serves as a reminder to investigate the following.

The spec actually allows ConnectionEnd.counterpartyConnectionIdentifier to be "" (even though this is an illegal value for Identifier) - see issue. Our implementation disallows empty strings when converting from RawCounterparty -> Counterparty. This probably fine and due to the interplay between ibc-go's proto files using (gogoproto.nullable) = false, and how prost's code generation. We also successfully opened connections with basecoin-rs & hermes, which tells me it's right.

However, I want to convince myself that this code is correct, and document the reasoning somewhere.

@plafer plafer added the A: good-first-issue Admin: good for newcomers label Oct 12, 2022
@Farhad-Shabani Farhad-Shabani added the S: specs Scope: related to IBC protocol specifications label Jan 19, 2023
@plafer
Copy link
Contributor Author

plafer commented Jan 19, 2023

Coming back to this issue, I see that I simply misread this expression. We indeed correctly don't disallow empty strings.

@github-project-automation github-project-automation bot moved this to 📥 To Do in ibc-rs Feb 2, 2023
@Farhad-Shabani Farhad-Shabani moved this from 📥 To Do to ✅ Done in ibc-rs Feb 2, 2023
@Farhad-Shabani Farhad-Shabani added this to the v0.28.0 milestone Feb 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A: good-first-issue Admin: good for newcomers S: specs Scope: related to IBC protocol specifications
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants