How do applications reject invalid transactions? #10047
Unanswered
nathan-at-least
asked this question in
Q&A
Replies: 1 comment
-
The idea is that these bad transactions should be treated (deterministically) as no-ops during the execution of the block that contains them. If you think that the documentation should be improved, I recommend opening a discussion in the CometBFT repo, since Tendermint has been locked and will not be updated. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm studying the ABCI spec and I'm not quite clear on what the safeguards are against malicious or invalid transactions.
My guess is that the exclusion of invalid or malicious transactions from blocks is only guaranteed by an honest threshold of voting weight. Is this correct? (Where can I read more about the security model of tendermint+ABCI?)
If so, then I would assume appchains MUST implement this safeguard by rejecting malicious proposals in
ProcessProposal
. Is there a different/better mechanism? (It seems like rejecting inCheckTx
does not uphold the honest threshold security, since a malicious proposer can insert a txn that no other node ever vets withCheckTx
.)So with these assumptions in mind, I was really confused to read that the app requirements for
ProcessProposal
states:It feels like I'm missing something basic here, but it also seems like that could be clarified better in the app requirements doc.
Beta Was this translation helpful? Give feedback.
All reactions