Validators
Validator Profile ComparisonConnecting
Compare operators by who they are, what they charge, and what they actually produce — not by APY noise.
No active validators to chart.
Why these columns: The Aster validator set is a curated group of 7 protocol-allocated partners. APY spread is typically < 0.2 percentage points and stake is auto-distributed evenly, so neither field meaningfully helps you choose. The columns below — operator type, commission, validating-since, and live block production — are what actually differentiate them.
Sort by:
Loading validator profiles…
About this page
- Why no APY column: the spread between validators is consistently < 0.2 percentage points (network avg ~3.8%). Picking by 0.05% APY is meaningless — pick the operator you trust.
- Why no Stake column: Aster auto-distributes user stake roughly evenly across the curated set. Total stake per validator stays within ~14.0–14.5% network share at all times — no signal there either.
- First observed reports when AsterScan's snapshot pipeline first saw the validator — not the actual on-chain join date. Validators that were already present at our first snapshot show as Genesis or earlier (italic) because we can't distinguish between "joined at launch" and "joined before we started tracking". Validators that appeared after we started are dated exactly.
- Blocks (live) is a session-local counter populated by the WebSocket block stream. Numbers reset when you reload — a persistent 24h server-side aggregator is on the roadmap.
- Self-stake vs delegated split is not exposed by the public Aster staking API. Roadmap item if upstream adds the field.