You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: