Run Citrea Full Node

Running a Citrea node is permissionless - anyone can run a full node for development & security purposes.

The easiest way to get started is to use the Citrea full node Docker image.

Step 1: Install Docker

Follow instructions to install Docker herearrow-up-right.

Step 2: Run Citrea Full Node (mainnet)

docker run -d \
  -e NETWORK=mainnet \
  -e NODE_URL=<your_bitcoin_node_rpc_url> \
  -e NODE_USERNAME=<your_bitcoin_rpc_username> \
  -e NODE_PASSWORD=<your_bitcoin_rpc_password> \
  -v citrea-data:/mnt/task/citrea-db \
  -p 8080:8080 \
  chainwayxyz/citrea-full-node:latest

This starts a Citrea mainnet full node. You must provide a fully synced Bitcoin mainnet node running with -txindex=1 for NODE_URL

circle-info

Please note that there are no financial incentives to run a Citrea Full Node. It's for your own development setup and security practices.


Mainnet manual setup (binary or source)

If you prefer to avoid Docker or need to customize your setup, use one of the options below.

Option 1: Pre-built binary

  1. Download the latest binary for your OS from the Citrea releases page.

  2. Download mainnet config and genesis files:

  1. Run the node (example for macOS):

Option 2: Build from source

  1. Clone the repository and checkout the latest tag:

  1. Build and run:

Step 3: Check the sync status

You can check the status with the following command (you may need to arrange the URL at the end based on your setup):

A sample response (fields may vary based on the sync status):

Hardware Requirements for running a node

A Linux/Mac/Windows system with a configuration of

  • 8 GB RAM

  • 2 TB SSD (NVMe recommended)

  • 4 core CPU (if you're using cloud)

  • 25+ Mbps network connection

should satisfy the minimum requirements to run a Citrea node. Allocating more resources improves the syncing speed.


If you encounter any problems during the node running even though you have a system that fits the requirements, please visit our Discordarrow-up-right and let us know by opening a ticket.

Testnet4

If you need a Testnet4 setup, keep using the Testnet4-specific guides:

Last updated

Was this helpful?