Add Lisk Mainnet to the Superchain Registry

[matjazv]

Adding a New Chain

This PR adds Lisk Mainnet to the registry.

Checklist

• I have declared the chain at the appropriate Superchain Level.
• I have run just validate 1135 locally to ensure all local validation checks pass.
• I have run just codegen to ensure that the chainlist and other generated files are up-to-date and include my chain.

Additional Information

To enable the just add-chain and just codegen commands to function correctly, I had to make a few changes:

1. op-geth (config.go)

• Adding Lisk Mainnet chain ID into the constants:
  LiskMainnetChainID = 1135
• The same will eventually apply to Lisk Sepolia.

2. op-geth (superchain.go):

• The Lisk Mainnet network has custom values for the following variables, necessitating a new case statement:

case LiskMainnetChainID:
    out.Optimism.EIP1559Elasticity = 20
    out.Optimism.EIP1559Denominator = 1000
    out.Optimism.EIP1559DenominatorCanyon = newUint64(1000)

• The same will eventually apply to Lisk Sepolia.

3. check-genesis.go:

• Currently, EIP1559DenominatorCanyon is hardcoded to 250, which does not align with Lisk Mainnet (and Sepolia).
• For now, I have commented out these two lines.

Additionally, the just validate command also fails for some of the unit tests.

[matjazv]

With all recent updates, changes inside Additional Information are not needed anymore to successfully execute just add-chain command.

[geoknee]

With all recent updates, changes inside Additional Information are not needed anymore to successfully execute just add-chain command.

Excellent!

[geoknee]

Can you please double check these changes? The automatic genesis validation check validate-genesis-allocs uses this data, and the existing values were enough to make it pass, the new values cause it to fail.

[matjazv]

I have confirmed the changes with our RaaS provider, which were made when ownership of the chain was transferred from the deployer EOA to a multisig. The values were also adjusted (decreased) for fee withdrawals. As a result, the new values are correct.

This was not the case for Lisk Sepolia so genesis validation check passes inside its PR.

[matjazv]

All those changes were made around 22nd July 2024.

[geoknee]

Got it. For the genesis validation routine, we need the deploy-config as it was at the time the original genesis was generated, we don't actually care about changes that happened after that in this context. So best to revert these changes (the deploy-config.json won't be used for anything else).

[matjazv]

I've reverted the changes inside deploy-config.json file.