Mainnet Beta ​

Welcome to the guide for Celestia's Mainnet Beta. Mainnet Beta is the culmination of rigorous community testing, upgrades, and feedback. It serves as the platform for deploying Mainnet Beta rollups and unstoppable applications.

Network stability and upgrades ​

Mainnet Beta is a stable network, but will still receive updates and improvements. Any changes or upgrades will be coordinated with node operators and the broader Celestia community to ensure seamless integration and minimal service interruptions.

As we step into unexplored territories with groundbreaking technologies like data availability sampling, it's crucial to remember that Mainnet Beta remains experimental at this stage. While the network is live and functional, users may encounter occasional instability or reduced performance.

Network details ​

Software version numbers ​

Network parameters ​

Transaction size limit ​

As specified in CIP-28, there is a 2 MiB (2,097,152 bytes) limit on individual transaction size. This limit was implemented to maintain network stability and provide clear expectations for users and developers, even as block sizes may be larger.

Block size limit ​

While individual transactions are limited to 2 MiB, a block can contain multiple transactions and has a much larger capacity. The maximum block size is determined by the effective maximum square size.

Given that the current governance maximum square size is 128, the total block size can be slightly less than ~8 MiB, or 7,896,602 bytes to be exact.

The following provides an approximation of the maximum block size:

• The maximum square size is 128x128, which gives us 16384 shares.
• One share is reserved for the PFB transaction, leaving us with 16383 shares.
• The first sparse share has 478 bytes available, and the remaining sparse shares have 482 bytes each.

This can be calculated as follows:

$\text{Total Bytes}=(1\times 478\text{bytes})+(16382\times 482\text{bytes})=7,896,602\text{bytes}$

There isn't a precise upper bound on the maximum total blob size. It depends on several factors:

• The maximum square size, which is determined by a governance parameter and a versioned constant.
• The maximum bytes in a block, which is determined by a governance parameter and a hard-coded constant in CometBFT.
• The number of shares occupied by the PFB transaction share.

These factors can cause the maximum total blob size that can be included in one block to vary.

See the code in celestia-app and celestia-node.

Full network parameters, such as max bytes, can be found in the celestia-app specifications.

Integrations ​

This guide contains the relevant sections for how to connect to Mainnet Beta, depending on the type of node you are running. Your best approach to participating is to first determine which node you would like to run. Each node's guide will link to the relevant network in order to show you how to connect to them. Learn about the different endpoint types in the Cosmos SDK documentation.

Production RPC endpoints ​

These RPC providers are meant to be used in production environments.

If you are using QuickNode or another provider with authentication of endpoints, see the light node guide to learn how to use an endpoint with x-token.

Community consensus endpoints ​

The following table lists community-provided consensus node endpoints that you can use:

Connecting DA nodes to consensus nodes ​

Data availability (DA) nodes need to connect to consensus nodes to sync blocks and access state. When starting a DA node, you'll need to provide a consensus node endpoint using the --core.ip parameter and the port.

celestia <da_type> start --core.ip <consensus_node_url> --core.port <port>

celestia <da_type> start --core.ip <consensus_node_url> --core.port <port>

You can use any of the RPC endpoints from the community consensus endpoints table above. The default port is 9090, where gRPC is used for both block sync and state access.

For example, to connect to the P-OPS endpoint:

celestia light start --core.ip rpc.celestia.pops.one --core.port 9090

celestia light start --core.ip rpc.celestia.pops.one --core.port 9090

Bridge node requirements ​

Not all RPC endpoints guarantee the full block history. Bridge nodes require access to the full historical block data, so you should use an archive endpoint to run your bridge node.

Check the production endpoints or the community dashboard to identify which endpoints are archive nodes with full historical data.

Alternatively, you can run your own consensus node with no pruning for your bridge node.

Archival DA RPC endpoints ​

By default, light nodes prune recent data to save on storage space. Archival data availability (DA) nodes store the entire history of the chain without pruning any data so all data available data is retrievable. You can read more about light vs archival nodes.

Explorers ​

There are multiple explorers you can use for Mainnet Beta:

• https://celenium.io
• https://mammoblocks.io/
• https://celestia.explorers.guru
• https://mintscan.io/celestia
• https://explorer.nodestake.top/celestia
• https://stakeflow.io/celestia
• https://celestia.valopers.com/
• https://mainnet.itrocket.net/celestia/

Community endpoint status dashboard ​

To check the current status, uptime, and health of all community endpoints, visit the RPC stats for Celestia dashboard. This dashboard provides real-time information about:

• Which endpoints are currently online
• Response times and performance metrics
• Which endpoints are archive nodes with full historical data
• Last seen heights for each endpoint

This is an essential resource when selecting endpoints for your nodes or applications.

Analytics ​

The following websites provide analytics for Celestia:

• https://analytics.smartstake.io/celestia
• https://alphab.ai/s/m/celestia/
• https://services.kjnodes.com/mainnet/celestia/slashboard
• https://itrocket.net/services/mainnet/celestia/decentralization/
• https://cosmoslist.co/mainnet/celestia

Network upgrades ​

There are a few ways to stay informed about network upgrades on Mainnet Beta:

• Telegram announcement channel
• Discord Mainnet Beta announcements

See the network upgrade process page to learn more about specific upgrades like the Ginger network upgrade.