duplicated revision number information in the consumer-addition proposal #1269
Labels
S: ImprovingThings
Improving things: Customer requests, performance improvements, reliability and usability
scope: UI
essing UX changes and improvements to user interface
status: waiting-triage
This issue/PR has not yet been triaged by the team.
type: bug
Issues that need priority attention -- something isn't working
Comments
AaronKutch
added
type: bug
mpoke
added
S: ImprovingThings
mpoke
added
the
status: waiting-triage
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When trying to launch a consumer chain on testnet, we made a last minute change to the chain id which added on
-testnet-1, which I didn't believe would possibly break anything. However, I discovered that Hermes could not connect the chains for some reason, and after a lot of hair tearing out and chasing why certain chain ids were causing obscure trusted header mismatch errors, I found that the"revision_number": 0subfield in the consumer proposal clashed with the revision number associated with the"chain_id". Different things were using different revision numbers and making the tendermint clients fundamentally incompatible.Either this field should be deduplicated, or the proposal command should have some kind of check to prevent revision number disagreements.
The text was updated successfully, but these errors were encountered: