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

Step by Step manual README needed #728

Open
BlueShells opened this issue Aug 1, 2024 · 1 comment
Open

Step by Step manual README needed #728

BlueShells opened this issue Aug 1, 2024 · 1 comment

Comments

@BlueShells
Copy link

Hi I am trying to follow the guide to shadow fork mainnet/sepolia/testnet to do test
Kurtosis is easy to start , one command will do the work, but this make it hard to debug when run into issue (I run into issue a few times , the repo keep changes everyday ), also hard to hack some change like :
I want to shadown mainnet to do test ,but the contract on mainnet is multi sig , so I need to hack to change the owner from multisig to EOA ,so I could do contract related test on the shadow fork , but currently its hard to hack this

so , if someone could provide another doc to split the what Kurtosis like :

  • how to Generate Execution Layer (EL) & Consensus Layer (CL) genesis information using the Ethereum genesis generator.
  • how to Configure & bootstrap a network of Ethereum nodes of n size using the genesis data generated above
  • how to Spin up a transaction spammer to send fake transactions to the network
    ....

this will help to debug issue and help us understand how this Kurtosis works

thanks

@barnabasbusa
Copy link
Contributor

I do not see how a step by step manual is needed for the ethereum-package repository.
We have a quick note that helps you understand how shadowforks supposed to work: https://notes.ethereum.org/@parithosh/shadowfork-tutorial
Each project like the ethereum genesis generator and transaction spammer has an individual readme that describes how the given tool is supposed to work, and thus I don't understand which parts are you missing.
As mentioned in the other issue as well, we do not plan to support public mainnet shadowforks using our snapshots, as these would require immense amount of bandwidth.

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

No branches or pull requests

2 participants