Running a Celestia light node is quickly becoming the preferred entry point for blockchain enthusiasts and developers seeking to participate directly in the data availability (DA) layer. Unlike traditional full nodes, light nodes are engineered for efficiency, requiring minimal hardware while still playing a crucial role in Celestia's modular architecture. By performing data availability sampling (DAS), these nodes validate that block data is accessible to the network without needing to download and store every byte. This not only democratizes DA participation but also underpins the scalability of the broader modular blockchain ecosystem.

Laptop screen showing a terminal window running Celestia light node commands for data availability sampling

Why Set Up a Celestia Light Node?

The growing adoption of Celestia’s DA layer by rollups and Layer 2 networks is fundamentally changing how blockchains scale. As Ethereum Layer 2s and emerging modular chains look for ways to reduce transaction costs and increase throughput, Celestia’s approach to offloading data availability becomes increasingly attractive. Running your own light node means you’re not just a passive observer - you’re actively contributing to network decentralization, security, and censorship resistance.

Moreover, light nodes are designed for accessibility. With requirements as low as 2 GB RAM, a single CPU core, 50 GB SSD storage, and modest bandwidth (56 Kbps up/down), almost any modern device can support one. This opens up DA participation to a wide audience - from independent stakers and hobbyists to professional restakers optimizing infrastructure for yield and resilience.

Step-by-Step Guide: Setting Up Your Light Node

The process of launching your own Celestia light node can be distilled into several clear stages:

How to Set Up a Celestia Light Node on Ubuntu 20.04

A checklist showing a laptop with 2GB RAM, single core CPU, 50GB SSD, and a network cable indicating 56 Kbps bandwidth.
Check Hardware Requirements
Ensure your system meets the minimum requirements: 2 GB RAM, single core CPU, 50 GB SSD storage, and at least 56 Kbps bandwidth for both upload and download. This ensures smooth operation of your Celestia light node.
A terminal window on Ubuntu displaying installation of packages like curl, wget, git, and build-essential.
Install System Dependencies
Update your Ubuntu 20.04 system and install required packages such as curl, wget, git, and build-essential. These are necessary for downloading and building Celestia node software.
A download progress bar for a software binary labeled 'celestia-node' on a Ubuntu desktop.
Install the celestia-node Binary
Download the celestia-node binary from the official Celestia documentation or build it from source. Follow the instructions for Ubuntu 20.04 to ensure compatibility and security.
A terminal running the command 'celestia light init --p2p.network mocha' with configuration files appearing.
Initialize the Light Node
Run the command `celestia light init --p2p.network mocha` to initialize your node for the Mocha testnet. This sets up configuration files and directories necessary for operation.
A terminal showing the command to start the Celestia light node, with network connections visualized.
Start the Light Node
Start your light node by connecting to a validator node's gRPC endpoint. Use the command `celestia light start --core.ip --p2p.network mocha`, replacing `` with the actual IP address. This step connects your node to the network.
A wallet interface displaying a Celestia address and token balance, with a key icon.
Manage Node Keys and Wallet
Upon starting, a wallet key is generated. Use `cel-key list --node.type light --keyring-backend test --p2p.network mocha` to view your node's address. Fund your address with tokens to pay for network transactions.
A folder named 'keys/keyring-test' with a custom key file being added, and a terminal referencing the custom key.
(Optional) Use a Custom Key
To use a custom key, place it in `~/.celestia-light-mocha/keys/keyring-test` and start the node with `--keyring.keyname `. This allows for advanced key management and security.
A network diagram highlighting port 2121 open on a firewall for a server labeled 'Celestia Light Node'.
Configure Network Ports
Ensure port 2121 (TCP/UDP) is open on your firewall and router to allow P2P connectivity. This is critical for your node to communicate with the network.
A settings panel showing a service running in the background with the SystemD logo.
(Optional) Set Up as a SystemD Service
For reliability, configure your node to run as a SystemD service. This enables automatic restarts and easier management. Follow the official Celestia documentation for detailed steps.
A hard drive with a ZFS logo and compression arrows indicating space saving.
(Optional) Enable ZFS Compression
To optimize storage usage, consider enabling ZFS compression on your node's data directory. This is especially useful for large-scale data availability sampling.
A network map showing connections to different endpoints labeled RPC, API, and gRPC.
Connect to Network Endpoints
Refer to the Celestia documentation for available RPC, API, and gRPC endpoints. Proper endpoint configuration ensures your node can submit transactions and query data efficiently.
A user interacting with a dashboard showing successful participation in data availability sampling on the Celestia network.
Begin Participating in the Network
With your light node running, you can now participate in data availability sampling and submit PayForBlob transactions, contributing to the security and scalability of Celestia's DA layer.

You’ll start by installing necessary dependencies on your system, followed by obtaining the celestia-node binary either via source or pre-built release. Once installed, initializing your node for your chosen network (such as Mocha testnet) is straightforward with:

Initialize the Celestia Light Node for Mocha Network

To initialize your Celestia light node and connect it to the Mocha testnet, execute the following command in your terminal:

celestia light init --p2p.network mocha

This command sets up the necessary configuration files for your light node and ensures it is ready to join the Mocha network. Make sure you have the Celestia light node binary installed before running this command.

This command structures all required configuration files and directories. Next, you’ll connect your node to the network using a validator’s gRPC endpoint:

Starting the Celestia Light Node

To start your Celestia light node and connect it to the validator node, use the following command. Replace `` with the actual IP address of your validator node.

celestia light start --core.ip  --p2p.network mocha

This command initializes the Celestia light node, connects it to the specified validator node, and joins the 'mocha' testnet network. Ensure your network configuration allows connections to the validator node's IP.

(Replace and lt;validator-node-ip and gt; with an actual validator IP address. )

Celestia's official documentation provides thorough guidance on each step if you need further detail.

Navigating Key Management and Network Configuration

Your node’s security begins with robust key management. On first launch, a wallet key is generated automatically - but advanced users may prefer importing custom keys for operational continuity or integration with external wallets. The process involves placing your key file in the correct directory (~/. celestia-light-mocha/keys/keyring-test) before starting your node with the appropriate flags:

Starting the Celestia Light Node

To start your Celestia light node and connect it to the Mocha testnet, use the following command. Replace `` with the IP address of your validator node and `` with the name of your key in the keyring.

celestia light start --core.ip  --keyring.keyname  --p2p.network mocha

This command initializes the light node, connects it to the specified validator node, uses your custom key for signing, and ensures it joins the Mocha network for data availability participation.

This flexibility supports both individual experimentation and professional-grade deployments where key management policies are essential.

P2P connectivity requires opening port 2121 TCP/UDP. Proper firewall configuration ensures seamless communication with peers across the global Celestia network. For more granular details on ports or troubleshooting connectivity issues, consult the Celestia troubleshooting guide.