-
Notifications
You must be signed in to change notification settings - Fork 782
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
Fix logic bug in txPool.validate #2441
Conversation
Codecov Report
Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more. |
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.
Looks good to me.
467334e
to
1aa30e5
Compare
Fixed the other broken client test here. Should be ready for final review. |
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.
Cool, nice find 🙂, LGTM! 👍
Fixes a logic bug in the
txPool.validate
function where we are retrieving an account balance from the wrong vm and stateManager instance. This caused an issue wheretxPool.validate
would fail when submitting a transaction via the RPCeth_sendRawTransaction
endpoint after restarting the client on an existing stateDB where no transactions/blocks were being run.setStateRoot
was being called on thevmCopy
but the account balance was being retrieved from thevm.stateManager
which had an unknown stateroot and the account might not have the correct balance.