Skip to main content
op-reth’s flag reference lives in one place: the op-reth CLI reference, imported into these docs from the op-reth source tree and versioned with it. Start there for the command taxonomy and configuration model, or jump straight to the op-reth node flag listing for the full --help output of the command node operators run. This page previously carried a hand-maintained copy of the op-reth flag catalog, pinned to an old release; it has been retired in favor of the single imported surface above so the flag facts cannot drift between two pages.
op-reth is the recommended execution client for new OP Stack deployments. op-node’s --l2.enginekind flag defaults to reth, so no extra engine-kind configuration is needed when pairing the two; set it explicitly only when running a different execution client (geth or erigon). See the op-node configuration options page for the engine-side flags.