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

BEP Idea: Punish proposers who propose bad blocks #84

Open
ttmc opened this issue Sep 13, 2018 · 0 comments
Open

BEP Idea: Punish proposers who propose bad blocks #84

ttmc opened this issue Sep 13, 2018 · 0 comments
Labels
BEP idea An idea for a new BEP, seeking feedback

Comments

@ttmc
Copy link
Contributor

ttmc commented Sep 13, 2018

For background, see tendermint/tendermint#2175 (comment) including that whole issue, not just the comment.

We must be careful, since proposing a bad block might not mean that a proposer (node) is malicious. In fact, our current code for CheckTx allows a double-spending transaction to get into the mempool, if it came after the last block, and once a transaction gets into the mempool, it soon ends up in a proposed block.

The reason is that our current code for CheckTx assumes the "state of the world" is the state at the end of the last block, not including transactions that have been added to the mempool since then. That will have to be changed if we want to have any hope of detecting truly malicious block-proposers.

@ttmc ttmc added the BEP idea An idea for a new BEP, seeking feedback label Sep 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BEP idea An idea for a new BEP, seeking feedback
Projects
None yet
Development

No branches or pull requests

1 participant