Been trying to sync a Base op-reth node for awhile. Here's the config that, after much tinkering, works:
1. standard L1 reth on beta v6 release
2. standard L1 lighthouse
3. op-reth pointed to base with discv5 discovery syncing with --debug.tip

Then it took less than a day to sync.

Remember to use the --enable-discv5-discovery --discovery.v5.port flags, otherwise you won't be able to sync on Base.

I'm working on a network crawler to help identify and plug mempool leaks, more to come later.

I write this up because syncing Base nodes on op-reth was surprisingly hard, the L1/L2 config was not trivial and there were was outdated documentation on a few things. I spent a ton of time figuring out what worked!

Final thing to note is that peering seems to struggle a lot, so you might need to restart your node several times to get it started. And you can't choose a block hash that's too close or too far from the tip to use with debug.tip

I was syncing with op-node before, but it was pretty finky (iirc I needed to do L1 reth archive node on alpha release) and quite slow (20+ days)

You can use --debug.tip to skip the op-node, which is the equivalent of not using a consensus client. It isn't ideal or fully trustless, but it's fine for me right now

cto & general partner @paradigm. working with /rust on /ethereum. building /reth and /foundry. https://gakonst.com

Eng @ Coinbase, working on Base
https://bayardo.org