-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
What should Tendermint do when a precommit message is received without Extension #8174
Comments
The discussion during yesterday's ABCI++ bi-weekly went around the following three cases: @williambanfield rightly pointed out that, according to the latest vote extension design, if we allow a) as a possibility, an intermediate node in the gossip network could always remove a vote extension from the vote message. Therefore we must exclude a) as a possibility. The second decision taken, which was the initial goal of this discussion, is that In conclusion:
Please feel free to correct any inaccuracy in the text above. I will open a PR to address this in the spec. |
* Clarify 0-length vote extensions in the spec, according to #8174 * Update spec so that Tendermnit can propose more txs than the size limit in * Addressed Manu's comment * Reworded size limit following Manu's suggestion
@sergio-mena is there anything left to do for this issue? |
This should be closed by @thanethomson's PR #8141 |
@thanethomson please make sure we reject a precommit message that does not contain the vote extension AND its signature |
Closed by #8141 |
Problem Definition
When a precommit messsge is received,
VerifyVoteExtension
is called even if the message does not have an extension or the extension has length 0, according to the current version of the ABCI++ specThe question is whether is would make sense to skip the verification in the case of empty or non-existent extension. This probably depends on the use cases for vote extensions. Currently we don't see an obvious reason not skip the verification under such conditions.
Once a decision is reached, we need to adapt the implementation (should be quick). Also, the spec should be updated to clearly describe the approach described (probably in section "When does Tendermint use it")
For Admin Use
The text was updated successfully, but these errors were encountered: