Skip to main content
A summary of each component’s configuration options. For the complete list, refer to --help or the example configurations in the repositories.

leafage-evm

Common parameters of the standalone subcommand:

Basics

State updates

Performance and concurrency

Archive mode

Historical forwarding and observability

Kafka + S3 configuration

Passed to --kafka-s3-config; can be an absolute path or inline JSON:

etcd registration

--etcd-config accepts JSON:
meta is the ip:port registered with etcd; it can also be specified separately with --meta.

pipeline

Passed in through the execution client’s tracer configuration (geth’s --vmtrace.jsonconfig):
Exactly one of is_backup and etcd_endpoints must be set. Setting both or neither causes an immediate exit at startup.

consistency-checker

YAML configuration; -config specifies the path, and -listen can override the listen address.
check_num is deprecated and no longer takes effect. Replica polling is time-limited by check_timeout_ms.

nodex-proxy

YAML configuration; -config specifies the path, and -listen overrides the RPC port.

Top level

proxy_config

proxy_config.processor

proxy_config.observability

See config/config.example.yaml in the repository for a complete example.

Write node

Using the go-ethereum fork as an example, the flags Leafage adds: The remaining flags match upstream geth. To enable trace_debankBlock, include trace in --http.api.