# Mainnet Beta

![Mainnet Beta](/img/Mainnet-Beta.png)

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

| Detail        | Value                                                                                              |
| ------------- | -------------------------------------------------------------------------------------------------- |
| Chain ID      | `celestia`                                                                       |
| Genesis hash  | `6BE39EFD10BA412A9DB5288488303F5DD32CF386707A5BEF33617F4C43301872`                                 |
| Genesis file  | <a href={`https://github.com/celestiaorg/networks/blob/main/$celestia/genesis.json`}>genesis.json</a> |
| Peers file    | <a href={`https://github.com/celestiaorg/networks/blob/main/$celestia/peers.txt`}>peers.txt</a>       |
| Validators    | 100                                                                                                |
| Block time    | [Approximately 3 seconds](https://cips.celestia.org/cip-048.html)                                      |

The happy-path cadence is approximately 2.6 seconds, so integrations should
treat 3 seconds as an approximate target rather than an exact interval.

## Software version numbers

| Software       | Version                                                             |
| -------------- | ------------------------------------------------------------------- |
| celestia-node  | [v0.34.3](https://github.com/celestiaorg/celestia-node/releases/tag/v0.34.3) |
| celestia-app   | [v10.5.0](https://github.com/celestiaorg/celestia-app/releases/tag/v10.5.0)   |

## Network status

For real-time network status information, including uptime, incident reports,
and service availability, visit the
[official Celestia Mainnet status page](https://status.celestia.dev/status/mainnet).

## Network parameters

### Transaction size limit

The maximum transaction size on all networks is 8 MiB (8,388,608 bytes). See [CIP-38](https://cips.celestia.org/cip-038.html) which activated at [the v6 upgrade height](/operate/maintenance/network-upgrades#matcha-network-upgrade).

Previously, in [CIP-28](https://cips.celestia.org/cip-028.html), there was a 2 MiB limit on 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 8 MiB as of v6, a block can contain multiple transactions and has a much larger capacity. The maximum block size is determined by the effective maximum square size.

The current maximum block capacity on Mocha and Mainnet Beta is 32 MiB. On
Mainnet Beta, the governance square size is 256 (a 32 MiB square) and the
consensus encoded-block limit is also 32 MiB; the effective capacity is the
smaller of the two.

The following provides an approximation of the maximum blob capacity:

- The maximum square size is 256x256, which gives us 65,536 shares.
- One share is reserved for the PFB transaction, leaving us with 65,535 shares available for blob data.
- The first sparse share has 478 bytes available, and the remaining sparse shares have 482 bytes each.

Approximate capacity:

```
First share:       1 x 478 bytes
Remaining shares:  65,534 x 482 bytes
Total bytes:       31,587,866 bytes
```

There is no precise, static 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](https://github.com/celestiaorg/celestia-app/blob/v9.0.4/pkg/appconsts/initial_consts.go#L13).

Full network parameters, such as [max bytes](https://github.com/celestiaorg/celestia-app/blob/v9.0.4/specs/src/parameters_v9.md?plain=1#L41),
can be found in the
[celestia-app specifications](https://celestiaorg.github.io/celestia-app/parameters_v9.html).

## Network constants

For the current Mainnet Beta network constants, see
[celenium.io/constants](https://celenium.io/constants).

## 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](/operate/getting-started/overview). 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](https://docs.cosmos.network/sdk/v0.53/learn/advanced/grpc_rest).

### Production RPC endpoints

Use production RPC providers for workloads that need reliable service, such as:

- Applications that need bridge node endpoints with uptime commitments and SLAs
- Submitting blobs in production settings (free RPC endpoints have no guarantees, even for submitting transactions)

| Provider  | URL                                                                                       |
| --------- | ----------------------------------------------------------------------------------------- |
| Quicknode | [https://www.quicknode.com/chains/celestia](https://www.quicknode.com/chains/celestia) ([docs](https://quicknode.com/docs/celestia)) |

If you are using Quicknode or another provider with authenticated endpoints,
see [the light node guide](/operate/data-availability/light-node/advanced#optional-start-light-node-with-consensus-endpoint-authentication)
to learn how to use an endpoint with x-token.

### Public RPC endpoint

For development, testing, and documentation examples, use the public Quicknode
endpoint:

| Interface | Endpoint |
| --------- | -------- |
| HTTP RPC and REST | `https://public-endpoint.celestia-mainnet.quiknode.pro` |
| WebSocket | `wss://public-endpoint.celestia-mainnet.quiknode.pro/websocket` |
| gRPC over TLS | `public-endpoint.celestia-mainnet.quiknode.pro:9090` |
| DA JSON-RPC | `https://public-endpoint.celestia-mainnet.quiknode.pro` |

This shared endpoint does not provide a production SLA. Use a [production
provider](#production-rpc-endpoints) or your own node for production workloads.

### Node setup and tools

For paid archive RPC reads, indexed data APIs, and MCP access, see
[community services](/build/rpc/community-services).

Several community providers offer comprehensive node setup tools, installation scripts, and monitoring services to help node operators get started quickly:

| Provider | Installation guide                                             | State sync                                                    | Monitoring tools                                                |
| -------- | -------------------------------------------------------------- | ------------------------------------------------------------- | --------------------------------------------------------------- |
| ITRocket | [Setup guide](https://itrocket.net/services/mainnet/celestia/) | [State sync](https://itrocket.net/services/mainnet/celestia/) | [Chain status](https://itrocket.net/services/mainnet/celestia/) |

### Community consensus endpoints

> **Warning:** Do not rely on the free community endpoints listed below for production deployments. Production deployments should rely on [service providers with SLAs](#production-rpc-endpoints).

You can also find the list of official Celestia bootstrappers in the [celestia-node GitHub repository](https://github.com/celestiaorg/celestia-node/blob/a87a17557223d88231b56d323d22ac9da31871db/nodebuilder/p2p/bootstrap.go#L39).

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

| Provider        | RPC Endpoint                            | API Endpoint                            | gRPC Endpoint                             | WebSocket Endpoint                                       |
| --------------- | --------------------------------------- | --------------------------------------- | ----------------------------------------- | -------------------------------------------------------- |
| AlphaB          | `rpc-celestia.alphab.ai`               | `api-celestia.alphab.ai`               | `rpc-celestia.alphab.ai:9090`             | -                                                        |
| CitizenWeb3     | `rpc.celestia.citizenweb3.com`          | `api.celestia.citizenweb3.com`          | `grpc.celestia.citizenweb3.com:443`       | -                                                        |
| Cumulo          | `celestia.cumulo.org.es`                | `celestia.api.cumulo.org.es`            | `celestia.grpc.cumulo.org.es:443`         | `wss://celestia.cumulo.org.es/websocket`                 |
| ITRocket        | `celestia-mainnet-rpc.itrocket.net:443` | `celestia-mainnet-api.itrocket.net:443` | `celestia-mainnet-grpc.itrocket.net:443`  | -                                                        |
| kjnodes         | `celestia.rpc.kjnodes.com`              | `celestia.api.kjnodes.com`              | `celestia.grpc.kjnodes.com:443`           | -                                                        |
| lunaroasis      | `rpc.lunaroasis.net`                    | -                                       | `grpc.lunaroasis.net:443`                 | -                                                        |
| Noders Services | `celestia-rpc.noders.services`          | -                                       | -                                         | -                                                        |
| Numia           | `public-celestia-rpc.numia.xyz`         | `public-celestia-lcd.numia.xyz`         | `public-celestia-grpc.numia.xyz`          | `wss://public-celestia-rpc.numia.xyz/websocket`          |
| P-OPS           | `rpc.celestia.pops.one`                 | `api.celestia.pops.one`                 | `grpc.celestia.pops.one`                  | -                                                        |
| Stakin          | `celestia.rpc.stakin-nodes.com`         | `celestia.rest.stakin-nodes.com`        | `celestia.grpc.stakin-nodes.com:443`      | -                                                        |
| deNodes         | `celestia-mainnet-rpc.denodes.xyz`      | `celestia-mainnet-api.denodes.xyz`      | -                                         | `wss://celestia-mainnet-rpc.denodes.xyz:443/websocket`   |

> Live latency benchmarks for public no-key Celestia RPC endpoints (PublicNode, Polkachu, LavenderFive — Tendermint status p50/p90/p99, 3 probe regions, updated every 60 s): [OpenChainBench Celestia RPC](https://openchainbench.com/benchmarks/celestia-rpc)

### 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.

Example command for starting a DA node with a consensus endpoint:

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

You can use the [public endpoint](#public-rpc-endpoint) or any of the RPC
endpoints from the [community consensus endpoints](#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 public Quicknode endpoint:

```bash
celestia light start \
  --core.ip public-endpoint.celestia-mainnet.quiknode.pro \
  --core.port 9090 --core.tls
```

### Bridge node requirements

Bridge nodes run in pruned mode by default. Both pruned and archival bridge
nodes can use a non-archival consensus endpoint. Provision it to retain blocks
within the storage window (`169h`);
the live block listener still fetches newly announced blocks from consensus.
Older header ranges come from the header peer exchange. Header fetches can
also fall back to peers when consensus lacks a requested height, and the
data availability sampler (DASer) retrieves share data from DA peers.
Full historical availability depends on peers retaining that history.

To retain full history locally, start the bridge node with `--archival` and
provision the [archival hardware requirements](/operate/getting-started/hardware-requirements#archival-data-availability-nodes).

### Archival DA RPC endpoints

By default, light nodes prune data outside their sampling window to save
storage space. Archival data availability (DA) nodes retain historical headers
and original data, while trimming redundant erasure-coded data outside the
storage window. This trimming preserves the original data for retrieval. You can
[read more about light vs archival nodes](/learn/celestia-101/retrievability/).

| Provider                         | Endpoint                                                                                  | RPC Port | Gateway Port |
| -------------------------------- | ----------------------------------------------------------------------------------------- | -------- | ------------ |
| Quicknode                        | [https://www.quicknode.com/chains/celestia](https://www.quicknode.com/chains/celestia) ([docs](https://quicknode.com/docs/celestia)) | -        | -            |
| Mzonder                          | `celestia-da-full-storage.mzonder.com`                                                    | 27758    | 27759        |
| Noders Services                  | `celestia-archive-da.noders.services`                                                     | 26658    | 26659        |
| ITRocket                         | `celestia-mainnet-da-full-storage.itrocket.net`                                           | 26658    | 26659        |
| See the Brightly Stake dashboard | [https://celestia-tools.brightlystake.com/](https://celestia-tools.brightlystake.com/)                                               | -        | -            |

## Explorers

There are multiple explorers you can use for Mainnet Beta:

- [https://celenium.io](https://celenium.io)
- [https://celestia.explorers.guru](https://celestia.explorers.guru)
- [https://celestia.valopers.com/](https://celestia.valopers.com/)
- [https://explorer.nodestake.top/celestia](https://explorer.nodestake.top/celestia)
- [https://mainnet.itrocket.net/celestia/](https://mainnet.itrocket.net/celestia/)
- [https://mammoblocks.io/](https://mammoblocks.io/)
- [https://mintscan.io/celestia](https://mintscan.io/celestia)
- [https://stakeflow.io/celestia](https://stakeflow.io/celestia)

## Community endpoint status dashboard

To check the current status, uptime, and health of all community endpoints, visit the [RPC stats for Celestia dashboard](https://celestia-tools.brightlystake.com/). 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.

For a multi-region view of public consensus RPC endpoints, use
[Cumulo's check_d Endpoint Scan](https://cumulo.pro/services/celestia/rpcscan.php).
It shows endpoint health, block height, historical reliability, and response
latency from probes in the United States, Europe, Canada, and Singapore.

## Analytics

The following websites provide analytics for Celestia:

- [https://alphab.ai/s/m/celestia/](https://alphab.ai/s/m/celestia/)
- [https://itrocket.net/services/mainnet/celestia/](https://itrocket.net/services/mainnet/celestia/) - Node setup, monitoring, and chain status tools
- [https://itrocket.net/services/mainnet/celestia/analytics/consensus-signal-tracker/](https://itrocket.net/services/mainnet/celestia/analytics/consensus-signal-tracker/) - Consensus signal tracker
- [https://itrocket.net/services/mainnet/celestia/decentralization/](https://itrocket.net/services/mainnet/celestia/decentralization/)
- [https://services.kjnodes.com/mainnet/celestia/slashboard](https://services.kjnodes.com/mainnet/celestia/slashboard)

## Node maps

The following websites provide visual maps of Celestia DA nodes:

- [https://probelab.io/celestia/](https://probelab.io/celestia/) (community contribution)

## Network upgrades

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

- Telegram [announcement channel](https://t.me/+smSFIA7XXLU4MjJh)
- Discord [Mainnet Beta announcements](https://discord.com/channels/638338779505229824/1169237690114388039)

See the [network upgrades page](/operate/maintenance/network-upgrades) to learn more
about specific upgrades like the [Ginger network upgrade](/operate/maintenance/network-upgrades#ginger-network-upgrade).