Discussion about --enable-latest-fork

[dvush]

Currently opstack and l1 recipes support this flag and without this flag we run previous fork of the chain.

This means that without any configuration we are always one version behind current mainnet.
This does not look like the best UX if we need to always specify long cli flag just to use current mainnet version.

On the other hand I can understand the need to check if builder can work through the fork.

In addition we have problem when genesis files are not compatible between forks. For example, this happens with opstack jovian fork. Block extra data format changed because of fork. This makes current setup impossible to work when running --enable-latest-fork 0 (assuming latest in jovian) because we only have one genesis file.

1. I propose to change this flag so it works like this:

• always run latest mainnet version by default.
• reserve --enable-latest-fork only when there is a new fork pending

2. This will not fix the issue with incompatible genesis files between hardforks but at least current setup will and we can fix multiple genesis later. We can prohibit --enable-latest-fork 0 for forks that have incompatible

I wonder if it will break someones setup.

[dvush]

I think it does not work for l2 since they can update separately.