Skip to content

docs: link docker setup to consensus endpoints with RPC and gRPC #2440

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
jcstein wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

docs: link docker setup to consensus endpoints with RPC and gRPC #2440

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 6 additions & 5 deletions app/operate/getting-started/docker/page.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,18 +80,19 @@ Choose [the network](/operate/networks/overview) you would like to run your node
</Tabs.Tab>
</Tabs>

### Configure the RPC endpoint
### Configure the consensus endpoint

Set an RPC endpoint for either [Mainnet Beta](/operate/networks/mainnet-beta#integrations),
[Mocha](/operate/networks/mocha-testnet#rpc-for-da-bridge-full-and-light-nodes), or
[Arabica](/operate/networks/arabica-devnet#integrations)
Set a consensus endpoint that has both RPC (26657) and gRPC (9090) for either
[Mainnet Beta](/operate/networks/mainnet-beta#integrations),
[Mocha](/operate/networks/mocha-testnet#community-consensus-endpoints), or
[Arabica](/operate/networks/arabica-devnet#community-consensus-endpoints)
using the bare URL (without http or https):

```bash
export RPC_URL=this-is-an-rpc-url.com
Comment on lines 89 to 92
Copy link

Copilot AI Mar 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The doc now describes configuring a “consensus endpoint”, but the instructions and variable name still call it RPC_URL and describe it as a “bare URL (without http or https)”. Since the value is actually a hostname used for --core.ip, consider renaming the env var (e.g., CORE_IP/CONSENSUS_HOST) or adjusting the wording to consistently call this a host/endpoint (not a URL) to avoid confusion.

Suggested change
using the bare URL (without http or https):
```bash
export RPC_URL=this-is-an-rpc-url.com
using the consensus endpoint host (without `http://` or `https://`):
```bash
export RPC_URL=consensus.example.com

Copilot uses AI. Check for mistakes.
```

Then set the port for the RPC_URL:
Then set the gRPC port for the `RPC_URL` host:

```bash
export RPC_PORT=9090
Expand Down
4 changes: 2 additions & 2 deletions app/operate/networks/arabica-devnet/page.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,11 +75,11 @@ history, such as:
| --------- | ----------------------------------------------------------------------------------------- |
| QuickNode | [https://www.quicknode.com/chains/celestia](https://www.quicknode.com/chains/celestia) ([docs](https://quicknode.com/docs/celestia)) |

### Community RPC endpoints
### 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) or your own node.

RPC endpoints and types of nodes you can run in order to participate in Arabica devnet:
Consensus endpoints and node types you can run in order to participate in Arabica devnet:
Copy link

Copilot AI Mar 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The section heading was renamed to “Community consensus endpoints”, but the intro sentence now says “Consensus endpoints…” while the table includes multiple endpoint types (Consensus RPC, API, gRPC, and direct hostnames). Consider rephrasing this line to clarify that these are consensus-node endpoints and that the table lists RPC/API/gRPC options, so readers don’t interpret it as “consensus-only” endpoints.

Suggested change
Consensus endpoints and node types you can run in order to participate in Arabica devnet:
Consensus-node endpoints and node types you can run in order to participate in Arabica devnet, including RPC, API, gRPC, and direct hostnames:

Copilot uses AI. Check for mistakes.

| Node type | Endpoint type | Endpoint |
| ---------------------------------------------------------------- | -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
Expand Down
20 changes: 12 additions & 8 deletions app/operate/networks/mocha-testnet/page.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,7 +88,17 @@ Several community providers offer comprehensive node setup tools, installation s
| -------- | -------------------------------------------------------------- | ------------------------------------------------------------- | --------------------------------------------------------------- |
| ITRocket | [Setup guide](https://itrocket.net/services/testnet/celestia/) | [State sync](https://itrocket.net/services/testnet/celestia/) | [Chain status](https://itrocket.net/services/testnet/celestia/) |

### Community bridge node endpoints
### Community consensus endpoints

Use these consensus endpoints for `--core.ip` when your DA node needs both
RPC (26657) and gRPC (9090) available from the same host.

| Provider | Endpoint for `--core.ip` | RPC port | gRPC port |
| ---------------------------- | ------------------------------------------------------------------ | -------- | --------- |
| Numia | `public-celestia-{{constants['mochaChainId']}}-consensus.numia.xyz` | 26657 | 9090 |
| Celestia Labs (full) | `full.consensus.{{constants['mochaChainId']}}.celestia-mocha.com` | 26657 | 9090 |
| Celestia Labs (consensus) | `consensus-full-{{constants['mochaChainId']}}.celestia-mocha.com` | 26657 | 9090 |
| ITRocket | `celestia-testnet-consensus.itrocket.net` | 26657 | 9090 |

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

Expand All @@ -109,13 +119,7 @@ to their respective DA node.

> **Tip for bridge nodes:** Community RPC endpoints do not guarantee full block downloads. If you are running a bridge node, also run a local [consensus node](/operate/consensus-validators/consensus-node) to download full blocks.

- `public-celestia-{{constants['mochaChainId']}}-consensus.numia.xyz`
- `full.consensus.{{constants['mochaChainId']}}.celestia-mocha.com`
- `consensus-full-{{constants['mochaChainId']}}.celestia-mocha.com`
- `rpc-mocha.pops.one`
- `celestia-testnet-consensus.itrocket.net`
- RPC port: 26657
- gRPC port: 9090
Use one of the `--core.ip` values from the [community consensus endpoints](#community-consensus-endpoints) table above to ensure both ports are available.

## Community RPC endpoints

Expand Down
Loading