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
We should make sure we don't disallow chain IDs up to a uint256 size (i.e. a really big number) per this update to Pectra Devnet 5 specs
Probably what should happen here is we just add a check in common when setting up genesis parameters to make sure the chain ID isn't greater than 2^32 (or whatever the max uint256 is)
The text was updated successfully, but these errors were encountered:
We could do a monorepo-wide policy of chain-ids fitting in uint256 to be compatible with other clients? This would not be a candidate for the devnet-5 PR though, should have a follow-up PR on this if we want to do that.
Note: we do not have restrictions by default on the chain id size, so by default we would support "all" chain ids, except that we have some checks in for instance the tx package that this is not higher than some value.
We should make sure we don't disallow chain IDs up to a
uint256
size (i.e. a really big number) per this update to Pectra Devnet 5 specsProbably what should happen here is we just add a check in common when setting up genesis parameters to make sure the chain ID isn't greater than 2^32 (or whatever the max uint256 is)
The text was updated successfully, but these errors were encountered: