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

Configure multiple mev-commit chain IDs for devnet/testnet/mainnet #338

Open
shaspitz opened this issue Aug 13, 2024 · 0 comments
Open

Configure multiple mev-commit chain IDs for devnet/testnet/mainnet #338

shaspitz opened this issue Aug 13, 2024 · 0 comments

Comments

@shaspitz
Copy link
Contributor

shaspitz commented Aug 13, 2024

17864 has been the only chain ID we've been using for instances of the mev-commit chain. Now that we're nearing mainnet, we should make all contracts, clients, etc. able to handle different chain IDs for the mev-commit chain, corresponding to different environments.

For example we could keep 17864 for devnet cluster environments, and use a different chain ID for our user-facing testnet chain, and another chain ID for mainnet mev-commit chain. This is common practice to prevent txes being replayed across multiple chain instances.

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

1 participant