-
Notifications
You must be signed in to change notification settings - Fork 1
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
Handle consumed balance #59
Conversation
senderBalance := item.senderState.Balance | ||
|
||
willFeeExceedBalance := futureAccumulatedFee.Cmp(senderBalance) > 0 | ||
willFeeExceedBalance := futureConsumedBalance.Cmp(senderBalance) > 0 |
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.
We don't detect invalid transactions. We always assume that the value to be transferred is actually transferred (even if it isn't, actually, during processing).
We'll stop selecting transactions from a given sender once we detect (under the assumption above) that she doesn't have enough balance to pay the fee for the "currentTransaction".
The base branch was changed.
Make sure we don't select not-executable transactions (at all). Here, we handle transactions whose execution fee cannot be paid (anymore) by the sender.
Integration PR: