We believe validators owe their delegators more than a green status dot. This is the first in a series of partner transparency reports: a plain accounting of what we've done on each network we validate. The numbers, the votes, and the infrastructure we contribute beyond the validator itself. First up: Lumera Protocol, where we've been a genesis validator on both testnet and mainnet.
About Lumera, briefly
Lumera is a Cosmos SDK chain focused on decentralized AI-powered asset infrastructure: verifiable storage, provenance and intelligent handling of digital assets, with sense-and-cascade primitives that let applications register, authenticate and preserve assets on-chain. For validators, that profile means two things: standard CometBFT consensus duties, plus supernode-style service workloads that reward operators who can run more than just a bare validator binary.
The numbers
| Metric | Value | Notes |
|---|---|---|
| Validating since | Genesis | Testnet first; carried into mainnet cohort |
| Signing participation | 99.9% | Trailing 6 months, from public chain data |
| Slashing incidents | 0 | No downtime jailing, no equivocation, ever |
| Governance votes cast | 100% | Every proposal in the period, with rationale on request |
| Chain upgrades executed | All | Each rehearsed on testnet before mainnet window |
Everything in that table is verifiable from public chain data. That's the point of the report. If any number here disagrees with what you find on-chain, we want to know about it.
Beyond the validator
Consensus participation is the visible part. The larger share of our Lumera work is ecosystem infrastructure that any user or developer can pick up:
- Public RPC and REST endpoints: rate-limited but free, targeted at developers and wallet integrations that need a reliable non-personal endpoint.
- Daily chain snapshots: compressed, checksummed, retained on a rolling window. A new node operator syncs from our snapshot in minutes instead of replaying days of blocks.
- State-sync provider: for operators who prefer trust-minimized bootstrapping over snapshot downloads.
- Upgrade guides: for every mainnet upgrade we publish the exact runbook we used internally, including the rollback plan nobody hopes to need.
Why we do free infrastructure: a network where only validators can afford reliable endpoints centralizes quietly. Public infrastructure is the cheapest decentralization money can buy, and it's how we'd want every network we delegate on to be treated.
Governance record
We voted on every proposal in the reporting period. Our standing policy on how we vote:
- Protocol upgrades: we test on our own infrastructure before voting yes. A yes vote from Helios means "we ran it."
- Parameter changes: we model the impact on small delegators, not just on validators, and publish our reasoning when we vote against.
- Spend proposals: we vote for measurable deliverables and against open-ended funding, consistently, even when it's unpopular.
Delegators inherit our governance power. If you disagree with a vote we've cast, our policy is to explain it or override it per-proposal where the chain supports weighted voting. Email us and a human answers.
What's next
- Evaluating Lumera's supernode service roles as they mature: running the asset-processing workloads, not just consensus.
- Expanding snapshot coverage to include archive-grade data for indexer teams.
- Quarterly cadence for these reports, with Pharos and Cosmos Hub next in the series.
A genesis validator's job isn't to be early. It's to still be boring, reliable and accountable six months later. This report is what accountable looks like.
Stake on Lumera through Helios on our networks page, or read the engineering behind our zero-slashing record in The Anatomy of Slashing.