> For the complete documentation index, see [llms.txt](https://services.validexis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://services.validexis.com/celestia-infrastructure.md).

# 🏗️ Celestia Infrastructure

VALIDEXIS operates Celestia **Mainnet Beta** and **Mocha testnet** validators together with their **Fibre** data-availability servers. This section documents how our production setup is built and operated: which roles exist, how they connect, how keys are protected, and how the stack is monitored.

The guides are written from our own operations and follow the official Celestia documentation. Every guide links to the upstream source it builds on.

### At a glance

| Item              | Detail                                                                                                |
| ----------------- | ----------------------------------------------------------------------------------------------------- |
| Location          | Rackzar Cape Town DC1, Cape Town, South Africa — one site, outside Europe and North America           |
| Networks          | Celestia Mainnet Beta (`celestia`) · Mocha testnet (`mocha-5`)                                        |
| Physical servers  | 6 dedicated servers, one role per server                                                              |
| Private network   | Dedicated private VLAN between all servers                                                            |
| Remote signing    | TMKMS `v0.15.0` with `softsign`, key on a LUKS-encrypted volume, `SignRawBytes` support for Fibre     |
| Fibre ↔ validator | Signing over the privval gRPC endpoint with mutual TLS; application gRPC only inside the private VLAN |
| Monitoring        | Prometheus, Grafana, OpenTelemetry for Fibre, an off-site watcher, on-call escalation                 |

### Server roles

Each network uses the same three-role pattern, so Mainnet and Mocha are operated with one procedure set.

| Role      | Mainnet  | Mocha    | What runs there                         | Public exposure                    |
| --------- | -------- | -------- | --------------------------------------- | ---------------------------------- |
| Validator | 1 server | 1 server | `celestia-appd` (consensus validator)   | P2P only                           |
| Fibre     | 1 server | 1 server | `fibre` server for the matching network | Fibre client port (default `7980`) |
| Signer    | 1 server | 1 server | `tmkms` holding the consensus key       | None                               |

### How the roles connect

```
                         Rackzar Cape Town DC1 · private VLAN
 ┌────────────────────────────────────────────────────────────────────────────┐
 │                                                                            │
 │   ┌──────────────┐   privval gRPC (mTLS) ──────────►  ┌────────────────┐   │
 │   │ Fibre server │   application gRPC (private) ──►   │ Validator node │   │
 │   │  fibre :7980 │                                     │ celestia-appd  │   │
 │   └──────┬───────┘                                     └───────▲────────┘   │
 │          │                                                     │            │
 │          │                       TMKMS dials the validator     │            │
 │          │                       (secret connection, :26658)   │            │
 │          │                                             ┌───────┴────────┐   │
 │          │                                             │ Signer · TMKMS │   │
 │          │                                             │ softsign · LUKS│   │
 │          │                                             └────────────────┘   │
 └──────────┼─────────────────────────────────────────────────────────────────┘
            │
   Fibre clients (public, TLS endorsed by the validator key)

      Same pattern for Mainnet and for Mocha — 2 × 3 servers.
```

**1. Signer → validator.** TMKMS opens the TCP connection to the validator's `priv_validator_laddr` and keeps it alive. The validator never connects to the signer; the signer has no public services. Over this connection the validator sends consensus signing requests (votes, proposals) and, since app version 10, `SignRawBytes` requests.

**2. Fibre → validator.** The Fibre server uses two connections to its validator:

* **Privval gRPC** (`priv_validator_grpc_laddr`, default port `26669`) — used for payment-promise endorsements and for Fibre's TLS identity. Because Fibre runs on a separate server, this connection is protected with **mutual TLS**. The node refuses to expose this endpoint on a non-loopback address without mTLS.
* **Application gRPC** (`[grpc]` in `app.toml`, port `9090`) — chain state for Fibre. It is not encrypted by Celestia, so it is reachable only from the Fibre server inside the private VLAN.

**3. Fibre → signer: no direct link.** Fibre never talks to TMKMS. Its signing requests go to the validator, which forwards them over the existing TMKMS connection. The consensus key therefore exists in one online place only: the signer.

**4. Clients → Fibre.** Clients reach the registered public host on the Fibre client port. Client connections are always TLS; the certificate is endorsed by the validator's consensus key and verified against the validator set, so no public certificates are needed.

### Why this layout

* **One role per server.** A disk filling with Fibre shards cannot stop consensus, and a Fibre restart never touches the signing path. The official guide requires separate disks for Fibre and celestia-app data; separate servers go one step further.
* **Signer isolated from the internet.** The signer accepts no inbound connections from the public network; it only dials its validator over the private VLAN.
* **Low signing latency by colocation.** Celestia requires median remote-signing latency at or below 10 ms. All servers share one site and one private VLAN, and we alert at 5 ms.
* **Identical pattern on both networks.** Mocha runs the same roles as Mainnet, so upgrades, signer changes and incident procedures are rehearsed on Mocha first.
* **Geographic diversity.** Cape Town adds a location outside the European and North American concentration of Celestia infrastructure.

### Guides in this section

* [🧵 Fibre Server: Setup and Operations](https://services.validexis.com/celestia-infrastructure/fibre-server-setup-and-operations)
* [📡 TMKMS for Celestia v10 and Fibre (SignRawBytes)](https://services.validexis.com/validator-security-our-approach-and-protection-measures/tmkms-for-remote-signing/tmkms-for-celestia-v10-and-fibre)
* [🔑 Key Custody and Signer Change Procedure](https://services.validexis.com/celestia-infrastructure/key-custody-and-signer-change)
* [🚨 Monitoring Celestia Validators and Fibre](https://services.validexis.com/monitoring/monitoring-celestia-validators-and-fibre)
* [📐 VALIDEXIS Celestia Platform and Methodology](https://services.validexis.com/celestia-infrastructure/validexis-celestia-platform-and-methodology)

### Sources

* Celestia — [Run a Fibre server](https://docs.celestia.org/operate/consensus-validators/fibre/)
* Celestia — [Fibre monitoring](https://docs.celestia.org/operate/consensus-validators/fibre/metrics/)
* celestia-app `v10.4.0` — [release notes, Key Management Systems](https://github.com/celestiaorg/celestia-app/blob/v10.4.0/docs/release-notes/release-notes.md#key-management-systems-kms)
* celestia-core — [Securing the PrivValidator gRPC endpoint with mutual TLS](https://github.com/celestiaorg/celestia-core/blob/main/docs/guides/privval-grpc-tls.md)
* iqlusion — [TMKMS changelog, 0.15.0](https://github.com/iqlusioninc/tmkms/blob/main/CHANGELOG.md)
