Skip to main content
This page catalogues op-conductor’s configuration options and its admin RPC methods. For how the service works, see OP Conductor; to add it to a running network, follow the setup guide.

Configuration options

The flag tables below are generated directly from op-conductor’s flag definitions in the monorepo (op-conductor/flags) at the release tag named in the provenance line, and are regenerated when a new finalized release is published, so they cannot silently fall behind. Every flag can also be set through the environment variable listed next to it. Generated from op-conductor/v0.9.4 flag definitions. 61 flags: 9 required, 52 optional.

Required flags

Optional flags

Notes on selected flags

raft.bootstrap

For bootstrapping a new cluster. This should only be used on the sequencer that is currently active and can only be started once with this flag, otherwise the flag has to be removed or the raft log must be deleted before re-bootstrapping the cluster.

paused

There is no configuration state, so if you unpause via RPC and then restart, it will start paused again.

RPCs

Conductor exposes admin RPCs on the conductor namespace.

conductor_overrideLeader

OverrideLeader is used to override the leader status, this is only used to return true for Leader() & LeaderWithID() calls. It does not impact the actual raft consensus leadership status. It is supposed to be used when the cluster is unhealthy and the node is the only one up, to allow batcher to be able to connect to the node so that it could download blocks from the manually started sequencer.

conductor_pause

Pause pauses op-conductor.

conductor_resume

Resume resumes op-conductor.

conductor_paused

Paused returns true if the op-conductor is paused.

conductor_stopped

Stopped returns true if the op-conductor is stopped.

conductor_sequencerHealthy

SequencerHealthy returns true if the sequencer is healthy.

conductor_leader

API related to consensus.
Leader returns true if the server is the leader.

conductor_leaderWithID

API related to consensus.
LeaderWithID returns the current leader’s server info.

conductor_addServerAsVoter

API related to consensus.
AddServerAsVoter adds a server as a voter to the cluster.

conductor_addServerAsNonvoter

API related to consensus.
AddServerAsNonvoter adds a server as a non-voter to the cluster. non-voter The non-voter will not participate in the leader election.

conductor_removeServer

API related to consensus.
RemoveServer removes a server from the cluster.

conductor_transferLeader

API related to consensus.
TransferLeader transfers leadership to another server (resigns).

conductor_transferLeaderToServer

API related to consensus.
TransferLeaderToServer transfers leadership to a specific server.

conductor_clusterMembership

ClusterMembership returns the current cluster membership configuration.

conductor_active

API called by op-node.
Active returns true if the op-conductor is active (not paused or stopped).

conductor_commitUnsafePayload

API called by op-node.
CommitUnsafePayload commits an unsafe payload (latest head) to the consensus layer. This method is typically called by the op-node to commit execution payload envelopes.