-
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
common: configure and fix kaustinen4 verkle testnet sync #3269
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more. |
* 1. On the saved blocks, comma separated which are limited (345,375,368,467) | ||
* `TEST_SAVED_NUMBERS=345,375,368,467 npx vitest run test/rpc/engine/kaustinen4.spec.ts` | ||
* 2. Directly pull slots from a kaustinen beacon url | ||
* `TEST_ONLINE_SLOTS=345,353..360 PEER_BEACON_URL=https://beacon.verkle-gen-devnet-4.ethpandaops.io npx vitest run test/rpc/engine/kaustinen4.spec.ts` |
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.
This is so cool, just tested this, works like a charm!!! 🔥 👍 🙂
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.
Ok, have deactivated the devp2p tests until we have these reliable again.
Guess we can take this in, right? Will approve and merge. 🙂
DEBUG=ethjs,vm:*,evm:*,statemanager:verkle* npm run client:start:ts -- --dataDir /data/teme --network kaustinen4 --rpcEngine --rpcEngineAuth false
./setup.sh --dataDir k4data --network kaustinen4 --justCL
Comment Line 26 and uncomment Line 25 to prevent lodestar from checkpoint syncing
UPDATE:
Kautinen4 sync works upto block 373, at block 374 an execution witness seems to be missing for extcodesize opcode evaluation on transaction 3, escalated the issue:
fixes:
It seems that a contract which was created, its code read accesses were charged which it shouldn't have been charged as the code was ready from the data, escalled to Guilluame for clarification, fixed in kaustinen4