mainnet does not sync "distance to target block exceeds maximum proof window"

[dbeal-eth]

I have set my mainnet configuration as suggested to a local lighthouse consensus node and a reth execution node.

When running, I am getting an error from the consensus client that seems to be blocking sync:

unichain-node-execution-client-1  | t=2025-02-20T03:00:39+0000 lvl=info msg="IPC endpoint opened" url=/data/geth.ipc
unichain-node-execution-client-1  | t=2025-02-20T03:00:39+0000 lvl=info msg="Loaded JWT secret file" path=/shared/jwt.hex crc32=0x66c35601
unichain-node-execution-client-1  | t=2025-02-20T03:00:39+0000 lvl=info msg="HTTP server started" endpoint=[::]:8545 auth=false prefix="" cors=* vhosts=*
unichain-node-execution-client-1  | t=2025-02-20T03:00:39+0000 lvl=info msg="WebSocket enabled" url=ws://[::]:8546
unichain-node-execution-client-1  | t=2025-02-20T03:00:39+0000 lvl=info msg="WebSocket enabled" url=ws://[::]:8551
unichain-node-execution-client-1  | t=2025-02-20T03:00:39+0000 lvl=info msg="HTTP server started" endpoint=[::]:8551 auth=true prefix="" cors=localhost vhosts=*
unichain-node-op-node-1           | t=2025-02-20T03:00:44+0000 lvl=warn msg="Unknown env var" prefix=OP_NODE env_var="OP_NODE_L1_TRUSTRPC=true"
unichain-node-op-node-1           | t=2025-02-20T03:00:44+0000 lvl=info msg="Not opted in to ProtocolVersions signal loading, disabling ProtocolVersions contract now."
unichain-node-op-node-1           | t=2025-02-20T03:00:44+0000 lvl=info msg="Using default bootnodes, none provided."
unichain-node-op-node-1           | t=2025-02-20T03:00:44+0000 lvl=info msg="Rollup Config" l2_chain_id=130 l2_network=unichain l1_chain_id=1 l1_network=mainnet l2_start_time=1730748359 l2_block_hash=0x3425162ddf41a0a1f0106d67b71828c9a9577e6ddeb94e4f33d2cde1fdc3befe l2_block_number=0 l1_block_hash=0x8c799ed21bd97471f76ba48ea54b30f8169c7e4e4a22acfba06951b571e0f4b6 l1_block_number=21116363 regolith_time="@ genesis" canyon_time="@ genesis" delta_time="@ genesis" ecotone_time="@ genesis" fjord_time="@ genesis" granite_time="@ genesis" holocene_time="@ 1736445601 ~ Thu Jan  9 18:00:01 UTC 2025" isthmus_time="(not configured)" interop_time="(not configured)" alt_da=false
unichain-node-op-node-1           | t=2025-02-20T03:00:44+0000 lvl=info msg="Initializing rollup node" version=v1.11.1-rc.1-443e931f-1739544265
unichain-node-op-node-1           | t=2025-02-20T03:00:44+0000 lvl=info msg="Connected to L1 Beacon API, ready for EIP-4844 blobs retrieval." version=Lighthouse/v5.2.1-9e12c21/aarch64-linux
unichain-node-op-node-1           | t=2025-02-20T03:00:44+0000 lvl=error msg="failed to fetch runtime config data" err="failed to fetch unsafe block signing address from system config: failed to fetch proof of storage slot 0x65a7ed542fb37fe237fdfbdd70b31598523fe5b32879e307bae27a0bd9581c08 at block 0xf2eb3ef1dc4f562c94d48187130a368bbf4d4db44aa25edde1dbc5e7fafdca49: distance to target block exceeds maximum proof window"
unichain-node-op-node-1           | t=2025-02-20T03:00:54+0000 lvl=error msg="failed to fetch runtime config data" err="failed to fetch unsafe block signing address from system config: failed to fetch proof of storage slot 0x65a7ed542fb37fe237fdfbdd70b31598523fe5b32879e307bae27a0bd9581c08 at block 0x83b412b669ee7c0794f46d895946f1d5f4ac1e42a7eb4f437e9704a5a793f07d: distance to target block exceeds maximum proof window"

I tried replacing the beacon RPC with the one embedded in the .env.mainnet file, but I get the same error.

I tried setting l1.trustrpc using envvar, but it says its unrecognized.

If I had to guess, the failed to fetch runtime config data" err="failed to fetch unsafe block signing address from system config: failed to fetch proof of storage slot is an error that occurs because of blob pruning, meaning its difficult to sync the node now that some time has passed since the original release of mainnet.