Skip to content
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 sync/fix verkle kaustinen5 #3343

Merged
merged 9 commits into from
Apr 11, 2024
Merged

Conversation

g11tech
Copy link
Contributor

@g11tech g11tech commented Apr 3, 2024

test and fix issues against the next iteration of verkle kaustinen5 as a stateless client

How to run:

  1. clean the client datadir (/data/k5data) and start the client providing where to save payload of invalid blocks (/data/k5data/invalidblocks):
    npm run client:start:ts -- --ignoreStatelessInvalidExecs /data/k5data/invalidblocks --dataDir /data/k5data --network kaustinen5 --rpcEngine --rpcEngineAuth false --logLevel warn

the loglevel is kept warn so that only failures so unexpected warns/errors show up to reduce noice while syncing

  1. clean the lodestra quickstart datadir's lodestar folder (here k5data/lodestar and run the following:
    /setup.sh --dataDir k5data --network kaustinen5 --justCL
    to start lodestar

TODOs:

- [ ] remove hacks for making 2935 work

  • fix block15 run

Copy link

codecov bot commented Apr 3, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.25%. Comparing base (4be68d2) to head (1930eab).
Report is 3 commits behind head on master.

Additional details and impacted files

Impacted file tree graph

Flag Coverage Δ
block ?
blockchain ?
client ?
common ?
devp2p ?
evm ?
genesis ?
statemanager ?
trie ?
tx ?
util ?
vm ?
wallet 87.25% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Copy link
Contributor

@acolytec3 acolytec3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants