-
Notifications
You must be signed in to change notification settings - Fork 760
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
common: configure kaustinen6 network #3355
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more. |
…ation because of missing cache persist
balanceAddress, | ||
0, | ||
BALANCE_LEAF_KEY | ||
) | ||
|
||
gas += coldAccessGas | ||
charge2929Gas = coldAccessGas === BIGINT_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.
What is this check doing?
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.
2929 gas charges to be charged only if there is no "cold" access (so warm costs won't be charged even if warmed by accesslist)
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.
So should the check be coldAccessGas > BIGINT_0
just for clarity? I'm assuming coldAccessGas
can never be negative.
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.
charge 2929 gas, when its not cold w.r.t. access charges (not cold = access charge is zero)
|
||
let charge2929Gas = true | ||
if (common.isActivatedEIP(6800)) { | ||
// TODO: add check if toAddress is not a precompile |
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.
Should this TODO be resolved before we merge? Seems like a relatively simple check.
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.
need to do a precomiple check at lot many places, will do a followup PR for the same if thats ok
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.
LGTM
followup of
test and fix issues against the next iteration of verkle kaustinen5 as a stateless client
How to run:
/data/k6data
) and start the client providing where to save payload of invalid blocks (/data/k6data/invalidblocks
):npm run client:start:ts -- --ignoreStatelessInvalidExecs /data/k6data/invalidblocks --dataDir /data/k6data --network kaustinen6 --rpcEngine --rpcEngineAuth false --logLevel warn
the loglevel is kept warn so that only failures so unexpected warns/errors show up to reduce noise while syncing
k6data/lodestar
and run the following:/setup.sh --dataDir k6data --network kaustinen6 --justCL
to start lodestar