Documentation
¶
Overview ¶
Package reth runs op-reth as an external subprocess and exposes it as a services.EthInstance, so op-e2e can use op-reth as the L2 execution layer. The launch/genesis/JWT/readiness machinery mirrors op-devstack/sysgo, which already drives op-reth this way.
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
This section is empty.
Types ¶
type Config ¶
type Config struct {
// GenesisJSONPath identifies an existing genesis JSON file for op-reth.
// InitL2 does not decode or rewrite this file.
GenesisJSONPath string
// SequencerHTTP, when non-empty, wires op-reth to forward transactions to the
// sequencer via --rollup.sequencer-http (sentry tx-forwarding).
SequencerHTTP string
// ProofsHistoryVersion selects the proof-history storage version; defaults to v2.
ProofsHistoryVersion string
// DataDir is the base directory for the op-reth datadir/logs/proof-history.
// Callers should pass t.TempDir() so the test framework owns cleanup even if
// the test panics before Close.
DataDir string
// ExtraArgs are appended verbatim to the op-reth `node` invocation.
ExtraArgs []string
}
Config carries the op-e2e-level EL knobs that translate onto the op-reth CLI.
type Instance ¶
type Instance struct {
// contains filtered or unexported fields
}
Instance is a running op-reth process exposed through services.EthInstance.
func InitL2 ¶
func InitL2(ctx context.Context, lgr log.Logger, name string, genesis *core.Genesis, jwtPath string, cfg Config) (*Instance, error)
InitL2 initializes the op-reth databases, starts the node, and waits for its RPC endpoints. Set exactly one genesis source: genesis or cfg.GenesisJSONPath. The caller must create cfg.DataDir with t.TempDir().
Source Files
Click to show internal directories.
Click to hide internal directories.