chore: increase max proof window

[meyer9]

Increases the max configurable proof window to 1 month. @0x00101010 mentioned this change had already been discussed.

[onbjerg]

What is the motivation here? Noting that increasing the proof window means you can send more and more expensive eth_getProof requests to Reth, which might require really beefy nodes depending on what chain you are running

[meyer9]

What is the motivation here? Noting that increasing the proof window means you can send more and more expensive eth_getProof requests to Reth, which might require really beefy nodes depending on what chain you are running

We're testing these requests currently and we've found it takes a somewhat reasonable time for an account proof from 300k blocks ago, which is the current limit. We'd like to test a longer window.

This doesn't increase the proof window, but does increase the configurable proof window (still defaults to 0).

The underlying motivation is to get reth working with Optimism as an L2 EL client (currently requires debug_dbGet, but is being refactored to use debug_executionWitness and eth_getProof).

@0x00101010 can add some more context if needed I think

[0x00101010]

What is the motivation here? Noting that increasing the proof window means you can send more and more expensive eth_getProof requests to Reth, which might require really beefy nodes depending on what chain you are running

@onbjerg This is to support fault proof programs on op-stack, where we need to be able to call eth_getProof for blocks that are ~month old in extreme cases.

[mattsse]

we can't limit this on a per network basis yet, so this seems fine and since this is opt-in we can do this we need the some reference data for larger ranges anyway