Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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!: sync with mainline ABCI #1003
feat!: sync with mainline ABCI #1003
Changes from 8 commits
c863bd9
6ee16a7
84da1ba
444b2f3
b91aaea
69d968f
442d1a8
cee4c8a
499c9a4
842a367
6a6a610
c892ebb
6035fba
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
[question] why is the squareSize set to the number of transactions? I think of these as two distinct values. For example, a block with 100 send transactions could have a square size of 4.
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.
Yeah this is a good point. So I've made the decision here that I want celestia-core to be specific to celestia-app. Concretely, we extend the rules around
PrepareProposal
andProcessProposal
that there must always be two transactions returned and the last and second to last are the squareSize and dataHash respectively. It's obviously somewhat hacky but means we keep within the boundaries of ABCI and are able to use the SDK without requiring a fork.If the rule isn't followed, consensus panics. I could have chosen to simply ignore the rules when an application sends back 0 txs (thus supporting all the test applications in Tendermint) but I felt better to actually enforce the rule thus I had to modify all the test applications including the
BaseApplication
.The square size and hash here are placeholders. I could use the value 0 (which is invalid in the case of Celestia) instead. This should not be used outside of testing
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.
[optional] Thanks for clarifying that they are placeholders. If they are expected to be overwritten by celestia-app, then proposal to do something like: