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

Request for information about the policy according to future updates #756

Closed
entertainment-veks opened this issue Sep 4, 2024 · 1 comment

Comments

@entertainment-veks
Copy link

Hello! Currently my team launches a start-up and we need to use L2 private network.
As far as Lighthouse is not supporting private networks anymore and in open words recommend to use Kurtosis for private networks instead: sigp/lighthouse#6123.
We currently thinking about choosing kurtosis as our production approach, but a single thing our strategy team worries about is upgrading network with future forks.

How would we be able to merge future forks with Kurtosis?
Thanks!

@barnabasbusa
Copy link
Contributor

Kurtosis is not meant to be ran as a production software. We plan to keep the ethereum-package as up to date as possible with future ethereum forks. Ideally none of the future releases will break anything major, however there is no assurance for this.

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