You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have found a bug at the rom from this issue: #1073
The bug will be fixed for fork 10, 11 and so on, but we will need to reject from Erigon's side those transactions that trigger the bug at fork 9 😕
The transactions are those calls (not deploy) where the last opcode of the calldata is a PUSH or calls calling a contract where the last opcode of the bytecode is a PUSH
The text was updated successfully, but these errors were encountered:
Opened this #1159 to help stop this from executing. A local test with the same code example from #1073 does return an "invalid code" response when attempting to call the contract.
Rationale
We have found a bug at the rom from this issue: #1073
The bug will be fixed for fork 10, 11 and so on, but we will need to reject from Erigon's side those transactions that trigger the bug at fork 9 😕
The transactions are those calls (not deploy) where the last opcode of the calldata is a PUSH or calls calling a contract where the last opcode of the bytecode is a PUSH
The text was updated successfully, but these errors were encountered: