-
Notifications
You must be signed in to change notification settings - Fork 766
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
vm: remove backfill of block hashes on 2935 activation #3478
Conversation
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.
Two questions/comments. It also seems that CI is not passing 🤔
@@ -524,28 +522,6 @@ export async function accumulateParentBlockHash( | |||
} | |||
await putBlockHash(this, parentHash, currentBlockNumber - BIGINT_1) |
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.
I think we can now remove this function, since it is only called once.
// More than blocks activation to build, so we can ensure that we can also retrieve block 0 or block 1 hash at block 300 | ||
const blocksToBuild = 300 | ||
const blocksToBuild = 500 |
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.
Do we now need 500 blocks, or can we also "just" create a few blocks (say 5)? We only need to test that the last blockhash is put into the contract at fork activation time.
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.
yes the test tests various scenarios of blockhash as well as the contract code windows as well as activation time
Short note: there is a nice type label |
remove the backfill of the last 256 hashes as it is already removed from the eip following kenya discussions