Content
@
0 reply
0 recast
0 reaction
bertcmiller
@bertcmiller
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
2 replies
3 recasts
7 reactions
bertcmiller
@bertcmiller
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
1 reply
0 recast
3 reactions
bertcmiller
@bertcmiller
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.
1 reply
0 recast
3 reactions
bertcmiller
@bertcmiller
I'm working on a network crawler to help identify and plug mempool leaks, more to come later.
1 reply
0 recast
2 reactions
bertcmiller
@bertcmiller
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!
2 replies
0 recast
2 reactions
gakonst
@gakonst
of note we just haven't published docs on this and this is all "unreleased" stuff, so it'll get better in next 1-2 months as we cut 1.0 and go ham on docs and the like
1 reply
0 recast
0 reaction
bertcmiller
@bertcmiller
Mad respect for the cadence that you're shipping at and the number of fronts you're shipping on. Not surprising there are some hangups here or there, and some of the documentation hangsup were on other projects (e.g. a flag being renamed here or there).
0 reply
0 recast
0 reaction
