[OP Stack Deployment] OP Node is testing very long to sync with L1 Chain Head

[code-xD]

Did you check the documentation?

• Yes

Did you check for duplicate questions?

• Yes

Issue Description

I had recently tried to setup my own testchain on my local machine following this link[https://docs.optimism.io/builders/chain-operators/tutorials/create-l2-rollup#fill-out-environment-variables] and multiple other discussions as well. However, after running syncStatus RPC I find that the L2 processing is lagging being L1 chain by 700-800 blocks. What can be done to speed up this process.

Response for Optimism SyncStatus

{
    "jsonrpc": "2.0",
    "id": 1,
    "result": {
        "current_l1": {
            "hash": "0xbac018f1c8e1614c34065686c3db1c0c546da9892a17572d4f8dc2c5818725ef",
            "number": 6083082,
            "parentHash": "0x5d70390c7ac821c5addef6a9d151b5940a2002e2abd00e807d7370c55ea15406",
            "timestamp": 1718077860
        },
        "current_l1_finalized": {
            "hash": "0x734fec5b9a9628094b5a0479a56c1b586f6228f6dcdf7d12d50c5d7c772d68c1",
            "number": 6082991,
            "parentHash": "0x6434b3777850e541a5473169fe570fdfb6cefe80d4abba8e2b7139a22cc9461a",
            "timestamp": 1718076768
        },
        "head_l1": {
            "hash": "0xec11b5f752afc54ba4782bd63c4fd4b3fc0d440fa5430a457ac78128731f0a70",
            "number": 6083086,
            "parentHash": "0xf08e06785be54380aa093e6e50daee8b662f751d6a3d73980a3d5771b8ad11f4",
            "timestamp": 1718077908
        },
        "safe_l1": {
            "hash": "0x9eb799bcbb0f3f8dca46ca7e823c92928228f56f39c6ecd3bcdb9e1f4011fe6b",
            "number": 6083023,
            "parentHash": "0x0d6f6286a815012d6c3c249a94e7c78e37a589434f28e4fb7bfaabc600406c1b",
            "timestamp": 1718077152
        },
        "finalized_l1": {
            "hash": "0x734fec5b9a9628094b5a0479a56c1b586f6228f6dcdf7d12d50c5d7c772d68c1",
            "number": 6082991,
            "parentHash": "0x6434b3777850e541a5473169fe570fdfb6cefe80d4abba8e2b7139a22cc9461a",
            "timestamp": 1718076768
        },
        "unsafe_l2": {
            "hash": "0x9669a9f9b829fac4976011eebb8da7d2047f449f7a98e99b229ab807e2d743dd",
            "number": 26604,
            "parentHash": "0xf084f6af48e1931f1ae9707eba9d909fbc908ff79a08a44261a19644d83c498f",
            "timestamp": 1718070840,
            "l1origin": {
                "hash": "0x803c594dc92fc329146b0eabe8e652c9215fae023853f9feecc7e56ff7c070d2",
                "number": 6082497
            },
            "sequenceNumber": 0
        },
        "safe_l2": {
            "hash": "0x525b8261939dc525ccce2fa81302bcf513433f0782c6e47f3ae92b8cb9024104",
            "number": 25571,
            "parentHash": "0x35ed2e0bc29684b55ffabcfc1f09ed8ddba4d444c834c526efab6b92717bbbdf",
            "timestamp": 1718068774,
            "l1origin": {
                "hash": "0xf07fde706d7251730d112eda4030a5049fb58ccbd83091df16ec9099aae5711e",
                "number": 6082324
            },
            "sequenceNumber": 5
        },
        "finalized_l2": {
            "hash": "0xace539f1bae41767b30c27b2465d9adeac2ad8e6ccf9be049ad605e75146313f",
            "number": 25234,
            "parentHash": "0x780d364d4a352f93942e6b85bb359a8b65f7302ea034e6d1d50390a9a49129a7",
            "timestamp": 1718068100,
            "l1origin": {
                "hash": "0x26e8373f194c3dd6c9700fc60ae7fe82c4ab4e9fe510f2ab305b403f74668a43",
                "number": 6082268
            },
            "sequenceNumber": 4
        },
        "pending_safe_l2": {
            "hash": "0x525b8261939dc525ccce2fa81302bcf513433f0782c6e47f3ae92b8cb9024104",
            "number": 25571,
            "parentHash": "0x35ed2e0bc29684b55ffabcfc1f09ed8ddba4d444c834c526efab6b92717bbbdf",
            "timestamp": 1718068774,
            "l1origin": {
                "hash": "0xf07fde706d7251730d112eda4030a5049fb58ccbd83091df16ec9099aae5711e",
                "number": 6082324
            },
            "sequenceNumber": 5
        }
    }
}

Logs

No response

Additional Information

No response

Feedback

No response

[Wazabie]

Hi @code-xD, can you share the configuration files, environment details and any startup flags you are using? Also, for how long have you been running the rollup?

[code-xD]

The issue got auto resolved, I had been running the rollup for around 10 hours to keep it on track with the Sepolia chain. Just a suggestion, can we highlight in the documentation somewhere regarding how to keep the lag minimal when setting up a new test chain.

[tynes]

This is fixed if you run with fault proofs enabled

[code-xD]

Is there any documentation for the same? Do I need to spin up some other stack or is it a config for a particular stack?

[sbvegan]

If you want to run with fault proofs enabled you need to use the fault proof smart contract release (op-contracts/v.1.4.0) and when deploying you'll need to use a fault proof rollup configuration. You can see the details on each parameter here and I just added some general deployment documentation here.

[code-xD]

Thanks for the response @sbvegan , this clears my doubt.

[hash1go]

Hello!
I think this discussion will help you.
#68