[Feedback] Mention the potential need for --l1.trustrpc flag in op-node docs

[datanexus-vincent]

Feedback

I was having trouble getting a bedrock OP node up and running because I was using our own Erigon nodes as the L1 backend, and when you're doing that you apparently need to add the --l1.trustrpc flag to get it working.

That would probably be a good thing to mention in this section of the docs: https://docs.optimism.io/builders/node-operators/tutorials/mainnet#start-op-node-with-the-following-command

Thanks!

Additional Information

No response

[sbvegan]

Thank you @datanexus-vincent, I've just flagged this internally. We'll work on getting this information in the docs!

[cpengilly]

agreed! issue can be tracked in docs repo here: ethereum-optimism/docs#304

[sbvegan]

PR here: ethereum-optimism/docs#312

[PierrickGT]

I had to use --l1.trustrpc flag too when using my own Nethermind node as the L1 backend to be able to sync in snap sync mode.
@sbvegan is this a known issue or I may have improperly configured my op-geth node?