-
Notifications
You must be signed in to change notification settings - Fork 115
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
Gas usage consensus error at Mainnet block 6001128 #868
Comments
jlokier
changed the title
Gas usage consensus error at Mainnet block 6001128
Oct 19, 2021
SELFDESTRUCT
of created contract gas error at Mainnet block 6001128
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On Mainnet, sync progress stops at block 6001128. After that point, trace output repeatedly shows
gasUsed neq cumulativeGasUsed
messages and does not feed blocks to the database, and the peer is disconnected. The gas message means it looks like a consensus logic error.Similar output is seen at many blocks in the range 6001128..6001204.
Like EIP-170 related consensus error at Goerli block 5080941 #867 "EIP-170 related consensus error at Goerli block 5080941", this is due to behaviour on
CREATE
orCREATE2
. But it's a different cause, and this message doesn't mention EIP-170.This was fixed accidentally by a fix for Goerli block 5080941 which refactored the logic in
writeContract
. Because of this overlap, these two issues were thought to be the same bug at first.But it wasn't fixed by the other fix for Goerli block 5080941 in commit 6548ff9 "fixes
CREATE
/CREATE2
's returndata bug", which changes handling of receivedreturnData
from calling a nested contract instead of changingwriteContract
.This is how we know there's more going on.
From the diffences between those two patches, we can see the issue is connected to
SELFDESTRUCT
interaction withCREATE
orCREATE2
, inwriteContract
.The text was updated successfully, but these errors were encountered: