-
Notifications
You must be signed in to change notification settings - Fork 267
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
feat!: move evidence back to Tendermint block #897
feat!: move evidence back to Tendermint block #897
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGMT, we might need a tag for super-mega-breaking.
This looks like it was resolved after accounting for the varint plus ceasing to double the data, no?
This may be resolved by updating the calculation used to determine maxDataBytes.
It's also possible the proxy app in the test isn't respecting the maxDataBytes param.
Agreed. I just created and added the label "proto breaking". I infer that a celestia-app release with this change won't be compatible with existing testnets so we may need a strategy meeting on how to upgrade all testnets after we cut a celestia-app release with this change. |
Closes: #894
The CI check proto-breakage is expected to fail (here) because this PR makes breaking changes to the protobuf definitions.