Infrastructure, unseen

The network lives beneath the network.

Mycelium reads a forest floor before anything surfaces. MushCrypto reads your validators the same way.

Every signal, accounted for.

MushCrypto sits alongside your validators and reads their vitals continuously — no dashboards to babysit, no gaps in coverage.

Uptime tracked
99.98%

Across every validator we sense, not a single cherry-picked node.

Alert latency
<120ms

From the moment a vital changes to the moment someone's paged.

Ecosystems
4

Celestia, Axelar, Akash and Shentu — see the full list below.

Missed alerts to date
0

Every anomaly we've caught has reached someone.

Three ways we grow.

Like mycelium, MushCrypto expands in stages — from a single sensor to a network you can finally see.

01 — Spore

Seed a sensor.

A lightweight agent drops onto each validator, sensing conditions without adding load or touching keys.

02 — Mycelium

Grow the mesh.

Sensors link into a dense, connected mesh that shares signal instantly across every network you run.

03 — Fruiting body

See what surfaces.

One dashboard, clear alerts — the only visible part of a system that's watching everything underneath.

The crew grew around the data center.

Lineserve's founder and CTO, Stephen Ndegwa, is part of our team and leads the data center side of our work. Four people, from the data center floor to the governance vote.

  1. Stephen Ndegwa Founder and CTO, Lineserve LinkedIn

    Hardware, network and capacity for our Celestia setup in Lineserve's Nairobi data center.

  2. Lead node operator Validators and keys

    Runs our validators on Axelar, Akash and Shentu mainnet and on Celestia Mocha. Owns key custody, upgrade scheduling and the working relationship with Lineserve.

  3. Infrastructure and DevOps engineer Servers in Nairobi

    Responsible for our servers in the Nairobi data center: the consensus node, the separate Fibre machine and the private link that connects them. Runs Axelar's tofnd and vald services and wrote the monitoring sensor.

  4. Software developer and governance analyst Scorecard and guides

    Maintains the Validator Governance Scorecard, which grades 96 Celestia validators on their voting record and refreshes hourly. Keeps our public node guides current and prepares our governance votes.

Governance, by network.

Real proposals, real turnout — the same reconstruction the Scorecard runs, grouped by the chain that voted.

Celestia 96 bonded validators
02

Pay for IBC Middleware Audits

36%
35/96voted
04

Increase SignedBlocksWindow slashing parameter

46%
44/96voted
08

Increase max square size, block size to 32 MiB

49%
47/96voted
09

Recover IBC clients with KYVE

48%
46/96voted
Cosmos Hub 180 bonded validators
995

Gaia v23.2.0 Upgrade

4%
8/180voted
1044

Gaia v27.5.0 Upgrade

16%
29/180voted
1052

Gaia v28.0.0 Upgrade

29%
53/180voted
1053

Recover IBC Client for Gravity Bridge

28%
50/180voted
Osmosis 30 bonded validators
1008

Recover expired IBC client for Dyson Protocol

10%
3/30voted
1013

Recover IBC light client for EVMOS Network

13%
4/30voted
1042

Migrate Protocol USDC to Alloyed USDC

20%
6/30voted
1045

Recover IBC light client for XRPL EVM

17%
5/30voted
Validator Governance Scorecard — Celestia, Osmosis, Cosmos Hub Open the scorecard

The scorecard is maintained by our software developer and governance analyst. Meet the crew

The ground we grow in.

Our infrastructure is hosted in Lineserve's data center in Nairobi, Kenya, and we work with Lineserve directly.

Site datasheetLineserve, Nairobi data center

lineserve.net/datacenters
Operator
LineserveIn Nairobi since 2018, on its own hardware.
Network
AS329659Lineserve's own network.
Facility
Tier IIICarrier-neutral facilities.
Power
Dual A and B feedsUPS and generator backup.
Cooling
N+1 precisionWith containment.
DDoS
Always-on mitigationOur profile lets P2P and Fibre traffic through without scrubbing delay.
Peering
KIXPThe exchange TESPOK runs across four Nairobi facilities: 141 member networks, 2.9 Tbps of connected capacity.
Subsea
Mombasa, about 480 kmInternational traffic arrives on the TEAMS, SEACOM, EASSy, LION2, DARE1 and PEACE cables landing there.
Agreed on the floor

The practical value is the short distance between decision and hardware.

The private link, the DDoS profile and the move onto Lineserve's dedicated servers for mainnet were each agreed directly with the people who rack the machines.

Mainnet will run in the same data center, on the same network, as our Mocha setup does today.

Two things that don't live on a landing page.

Everything below links to something that actually runs — not a demo, not a mockup.

96 validators, graded on what they actually voted.

Participation reconstructed from full on-chain voting history across every Celestia governance proposal — not self-reported numbers, not a sample.

Clean record 24% Partial 40% Never voted 36%
Open the scorecard
23Clean record — voted on all 7
38Partial participation
35Never voted once

44.5% average participation · live, updated hourly

Eight sections, nothing padded.

Hardware requirements, systemd units, troubleshooting, a glossary that doesn't assume you already know the jargon. Written by people who run the nodes.

Read the docs
4

Setup

Node types, hardware, light & bridge setup

2

Operate

systemd auto-restart, RPC & metrics

2

Support

Troubleshooting, glossary

What the chain itself says.

Pulled live from Celestia mainnet params — not a claim we're making about it.

94.98%
Bonded ratio
179
IBC clients tracked
32 MiB
Max block size

What we run underneath.

Our Celestia setup in Lineserve's Nairobi data center.

Networks we secure.

Each validator below is live on-chain, with signatures and uptime independently verifiable through its native explorer. No proxies, no claims we can't substantiate.

Before you reach out.

If this doesn't cover it, the contact section below will.

Do you need access to my validator's keys?

No. The sensor only reads what's already public or exposed to it — node vitals, peer health, signing behavior. No key access and no control-plane changes, ever.

How fresh is the data on this page?

Node vitals are continuous, not polled on a schedule. The Governance Scorecard recomputes hourly against the chain — nothing here is a weekly snapshot someone forgot to update.

What exactly counts as "never voted"?

A bonded validator with zero recorded votes across every proposal we track, verified against raw chain data — not a self-reported gap, and not an assumption from a missing field.

Do I have to check a dashboard, or does it alert me?

It alerts you. Under 120ms from the moment a vital changes to the moment someone's paged — the dashboard is there for when you want to look, not something you have to babysit.