DevOps engineers
Node upgrades, alerting and on-call response.
Website01/ 10Introduction
Foundation Delegation Program · Cohort 9 application
VALIDEXIS
for Celestia.
Our operations.
Our public contribution.
Renewal of Cohort 6Ecosystem R&D track · 2025
celestia.validexis.com ↗POWERING DECENTRALIZED FINANCE
Products.
Built by the team already running your infrastructure.
Dev 2025CELESTIABRIDGE
celestia.validexis.com ↗More products in the pipeline. Same standard, every time.
Our road in Celestia
March 2025
The First Selection
June 2025
CELESTIABRIDGE Release
July 2025
Ecosystem Delegation Program
November 2025
Foundation Delegation Program
October 2026
Celestia Explorer Release
And our story will continue.
Foundation Delegation Program · Cohort 9 application
VALIDEXIS
for Celestia.
Operators. Engineers.
One shared view of the network.
Operating since early 2025, we combine validator operations with public tools, data and documentation. This application seeks renewal after Cohort 6. Our team connects day-to-day operations with engineering and documentation, turning practical network experience into tools other operators can inspect, reuse and build upon.
Team & experience
DevOps
Nodes, upgrades, on-call operations
Infrastructure
Servers, networking, signing, capacity
Development
Explorers, data feeds, telemetry
Documentation
Guides, methods, operator resources
Experience across 12 Proof-of-Stake networks directly informs our Celestia work.
Celestia Ecosystem Delegation Program
R&D track · 2025Celestia Foundation Delegation Program
Cohort 6
R&D track · 2025Celestia Foundation Delegation Program
Cohort 6
Network & program history
Celestia, Monad, Starknet, Polkadot, Kusama, Cosmos Hub, Lava, Nibiru, ZetaChain, KYVE, Juno and Agoric.
Additional participation: Monad mainnet/testnet delegation; Web3 Foundation Decentralized Nodes, Cohort 3 (September 2025–January 2026), Polkadot and Kusama.
R&D selection ↗Cohort 6 selection ↗Web3 Foundation ↗Infrastructure for Celestia
Three servers.
Clear responsibilities.
Validator
Mainnet validator
Mocha validator · local key
Hardware & role
- CPU
- AMD Ryzen 9 9900X · 12 cores
- Memory
- 64 GB DDR5
- OS
- 2 × 960 GB NVMe · RAID 1
- Chain data
- 1.92 TB NVMe
↔mTLS signing
private gRPC
private gRPC
Fibre
Mainnet Fibre
Mocha Fibre
Hardware & role
- CPU
- AMD Ryzen 9 9900X · 12 cores
- Memory
- 128 GB DDR5
- OS
- 960 GB NVMe
- Shard storage
- Separate 960 GB NVMe
Validator ↔ signer
Mainnet signer
TMKMS softsign · LUKS
Hardware & role
- CPU
- Intel Xeon E5-2630L v4
- Memory
- 64 GB RAM
- Access
- Private VLAN and administrative SSH
TMKMS initiates its TCP connection to the validator. Mainnet signing requests travel back over that established channel. Fibre never connects directly to the signer.
Private VLAN · 1 Gbps
| Server | CPU / memory | Storage |
|---|---|---|
| Validator | Ryzen 9 9900X · 64 GB DDR5 | 2 × 960 GB NVMe RAID 1 OS 1.92 TB NVMe chain data |
| Fibre | Ryzen 9 9900X · 128 GB DDR5 | 960 GB NVMe OS Separate 960 GB NVMe shards |
| Signer | Xeon E5-2630L v4 · 64 GB RAM | LUKS-encrypted key volume |
Dedicated bare metal in Cape Town separates validation, Fibre and mainnet signing. Mainnet and Mocha are separate processes on shared physical hosts. Each Fibre process connects to its matching validator. Public validator/Fibre ports: 1 Gbps.
Connection & capacity details
Fibre signing uses mTLS. Application gRPC is unencrypted inside the private VLAN. Mainnet consensus signing uses the isolated TMKMS host; Mocha uses its own local key. No owned DA bridge nodes are part of this deployment.
2, 5 and 10 Gbps port upgrades are available options, not current capacity. Cape Town adds an operating location outside Europe and North America; no network-share or uniqueness claim is implied.