Cancun spec and config for mainnet

[smartprogrammer93]

Changes

• Cancun spec and config for mainnet

Types of changes

What types of changes does your code introduce?

• Bugfix (a non-breaking change that fixes an issue)
• New feature (a non-breaking change that adds functionality)
• Breaking change (a change that causes existing functionality not to work as expected)
• Optimization
• Refactoring
• Documentation update
• Build-related changes
• Other: Description

Testing

Requires testing

• Yes
• No

If yes, did you write tests?

• Yes
• No

Documentation

Requires documentation update

• Yes
• No

If yes, link the PR to the docs update or the issue with the details labeled docs. Remove if not applicable.

Requires explanation in Release Notes

• Yes
• No

Cancun spec and config for mainnet added

[smartprogrammer93]

@marcindsobczak what do you think about luk's comments?

[marcindsobczak]

Agree with @LukaszRozmej , we have 2048 as default TxPool size for many years and it works well (we tested 1k, 4k and 8k back then and chose 2k), no need to change it now (especially without benchmarking).

About making StorageWithReorgs default - agree as well.
If you @smartprogrammer93 want you can change default value and then adjust every pre-canun config to

  "TxPool": {
    "BlobsSupport": "Disabled"
  },

But if you want, we can merge it as it is (except 1024 for std TxPool) and I will handle it in separate PR

[smartprogrammer93]

@marcindsobczak ill address it in this PR. No problem

[rubo]

Given the TxPool.Size: 1024 for Chiado, don't we need the same for Gnosis?

[smartprogrammer93]

@rubo i think the idea is testnets usually run on lower spec machines. and that is why we have 1024 for testnets and 2048 for "mainnets"

[MarekM25]

LGTM