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.

Sign up for GitHub

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

Jump to bottom

Default beacon/execution services are able to reach out by default. #887

Open

0xTylerHolmes opened this issue Feb 3, 2025 · 0 comments

Labels

bug

Contributor

0xTylerHolmes commented Feb 3, 2025

Issue

By default, when running local experiments, the beacon and execution services are allowed to connect to external networks.

Risks

While the risk of actual network interference is currently low (due to differing genesis hashes), users may not be aware that a locally tested network could still reach out to other networks.
This also adds additional noise to some of the clients logs causing confusion during repro/RCA-ing that occurs post experiment.

Plausible Solutions

Restrict the beacon/execution services/containers to only use the network provided by Kurtosis. This would eliminate unintentional external connections and clearly communicate to users that testing is isolated by default.
Use the beacon/execution launchers to restrict the networks via CL args to the services themselves.

0xTylerHolmes added the bug label

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