Base Node (Consensus)
=====================

.. note::
    The configuration is managed through the ``base_node.env`` and ``base_node.service``
    files in the ``/host_vars/files`` folder.

.. warning::
    The Base consensus node (``base_node``) must be paired with an execution client.
    Use ``base_reth`` or ``base_geth`` for the execution layer.
    The JWT secret must match between the consensus and execution layers.

Base Node is the consensus client for the Base L2 network (OP Stack).
It connects to an Ethereum L1 RPC and communicates with the execution layer
via the Engine API.

For additional information see `Base Node docs <https://docs.base.org/guides/run-a-base-node>`_

Deployment Vars
---------------

Secrets
*******

``base_node_jwt_secret``:
    * Optional
    * Must match the JWT secret used by the paired execution client (``base_reth`` or ``base_geth``)

Host variables
**************

``base_node_custom_git_url``:
    * Optional, default to the official ``ethereum-optimism/optimism`` repository
    * Override the git repository used to build the base-consensus binary

``base_node_custom_git_branch``:
    * Optional, default to ``develop``
    * Applies only when a custom git URL is set

Configuration File
******************

The ``base_node.env`` file in ``/host_vars/files`` controls runtime configuration,
including the L1 RPC endpoints, Engine API URL, P2P listen ports, metrics, and logging.
Edit that file to change ``BASE_NODE_L1_ETH_RPC`` and ``BASE_NODE_L1_BEACON`` before deploying.