⚠️ Terms of Use & Disclaimer

Please read carefully before using X1 Validator Headquarters

⚠️ This software interacts with blockchain networks and cryptocurrency. Improper use can result in permanent, irreversible loss of funds. Proceed only if you understand and accept the risks.

1. No Warranty

This software is provided "AS IS" without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose, and noninfringement.

2. Limitation of Liability

In no event shall the authors, contributors, or copyright holders be liable for any claim, damages, or other liability, whether in an action of contract, tort, or otherwise, arising from, out of, or in connection with the software or the use or other dealings in the software. This includes but is not limited to:

  • Loss of funds, tokens, or cryptocurrency
  • Loss of staking rewards or validator income
  • Validator downtime, slashing, or deactivation
  • Unauthorized access to accounts or wallets
  • Any errors, bugs, or vulnerabilities in the software
  • Actions taken based on information displayed by the software

3. User Responsibility

By using this software, you acknowledge that:

  • You are solely responsible for verifying all transaction details before signing
  • You are solely responsible for safeguarding your wallet, keys, and credentials
  • You understand how blockchain transactions, staking, and delegation work
  • You will independently verify any information before acting on it
  • You accept all risks associated with using this software

4. Not Financial Advice

Nothing in this software constitutes financial, investment, legal, or tax advice. All staking decisions, validator selections, and fund management are solely your responsibility. Consult qualified professionals for financial guidance.

5. Open Source Software

This is an open-source community project. The code is publicly available for review. No guarantees are made regarding security, accuracy, or continued maintenance and support.

6. Third-Party Services

This software connects to third-party blockchain networks, RPC endpoints, and wallet providers. We are not responsible for the availability, security, or performance of these external services.

To display the validator world map, this software may send validator node IP addresses (public network infrastructure information, not your personal data) to a third-party geolocation provider (ipwho.is) to look up their approximate location. To display validator logos, it may load avatar images from third-party hosts such as Keybase when a validator lists one in its on-chain configuration. These requests are made by your browser directly to those providers, whose own privacy practices apply. Your wallet address, keys, and personal data are never sent to these services.

7. No Data Collection

This software does not collect, store, or transmit your private keys, seed phrases, or passwords. All wallet interactions occur directly between your browser and your wallet provider.

Terms Version 1.0 • Last Updated: June 10, 2026
X1 Website Launch My Validator GitHub
XNT —

Network Live

Real-time leader-slot tracking · Epoch —

--
Validators
--
Total Stake
--
Total Supply
--
Epoch
--
Slot
--
TPS
--
Active
--
Delinquent
Epoch
0% --
Loading validator locations...
Drag to rotate • Scroll to zoom • Click a country to fly there
Validators by Country
Loading...

Validator Lookup

Search by validator name, or paste a vote account or identity address

Browse all validators to find and add to your Data Center

No validators found. Try searching by name or check the Vote Account ID.

Found 0 validator(s)

Last updated: --

My Data Center

Track all your validators in one place

📊

No validators yet

Add validators to your Data Center to track their performance

🏆 Leaderboards

Top performing validators on the X1 Network

⭐ Top Performance Score

Validators ranked by official performance score (formula v2)

⚖️ Validator Comparison

Compare up to 4 validators side-by-side

+ Add Validator
+ Add Validator
+ Add Validator
+ Add Validator
⚖️

Select Validators to Compare

Search for validators above or browse the full list to add up to 4 validators for side-by-side comparison.

🏛️ Delegation Program

X1 Foundation stake delegation — official criteria and every validator's status

💰 Staking Rewards Calculator

Calculate accurate rewards based on real stake breakdown data

Select a validator or use custom mode
Current price of XNT in USD
Rewards Calculator
💰
Select a validator to see current earnings and simulate growth

🔄 Compound Growth Calculator

See how compounding frequency affects your growth over time

Select a validator or choose custom values
How often you restake rewards
Growth Projection
🔄
Select a validator or choose "Custom Values" to see earnings

⏱️ Unstaking Timeline Calculator

Model your full cooldown — including the per-epoch rate limit

Current Epoch: Loading...
Epoch Progress: --
Est. Time Remaining: --
How much XNT you plan to deactivate.
50%
% of your still-cooling stake that becomes withdrawable each epoch. Depends on how much total stake the network is deactivating at once.
Unstaking Timeline
How the cooldown actually works

X1 (like Solana since the 2024 rate change) limits total network stake deactivation to 9% of currently active stake per epoch. If only a small amount is being deactivated network-wide, your stake fully cools in a single epoch — the best case.

When many people deactivate at once, that 9% capacity is split proportionally across everyone. So for an individual account, only a fraction of the cooling stake unlocks each epoch, and the full unstake stretches across multiple epochs — and withdrawing more than the cooled part fails with "insufficient funds" until the next epoch boundary.

The slider above lets you model it: 100% = ideal best case, the observed preset = the share the last epoch boundary actually released (read from the stake-history sysvar), 25% = heavy congestion. Once each portion has cooled, you must call withdraw to actually move the funds — they don't auto-return.

💸 Validator Break-Even Calculator

Compare your actual earnings against operating costs

Select a validator to see profitability
Include server, bandwidth, maintenance, etc.
Break-Even Analysis
💸
Select a validator to see profitability analysis
TPS · past 60 min
—
avg—
peak—
Current Leader
Loading...
Slot --
Block 1 of 4
Next Leaders
Loading...
🔍
Clean streak —
Last skip —
Trend · live vs hour —
Current Slot
—
head of chain
Skip Rate · Live
—
rolling · last ~10 min
Skip Rate · Last Hour
—
fetching…
Skip Rate · Epoch
—
This
—
Previous
Recent Slots
—
Warming up…
Timeline · oldest → newest click a segment to jump
Produced
Skipped
Hover a cell for details · Click to open the validator
Live Skip Feed
0 events
Waiting for skips…
Top Skippers · This Epoch
—
Loading epoch data…
Your Validators · This Epoch
—
Loading portfolio…
Validator Lookup
Search any validator above
Type a validator name or vote address above to see their live skip stats.
Initializing Terminal
Fetching validator and stake data from api.x1.xyz…

📊 Performance Score Explained

How Scoring Works (v2)

Scores are computed centrally every hour and published for everyone — the score you see is the exact score every other visitor (and your delegators) sees. The formula is size-independent and evaluates pure operator quality over the last 7 epochs plus 7 days of round-the-clock monitoring. Commission and validator age are shown for context but are not scored — commission is a pricing choice, and age isn't something an operator can control. Component scores are continuous: the anchor values listed below are interpolated smoothly, so two validators only share a score when their underlying metrics are genuinely identical.

⚡ Vote Efficiency 30%
Measures how many epoch credits the validator earns compared to the network average over the last 7 completed epochs. This is size-independent since credits are roughly equal for all healthy validators.
Scoring
105%+ = 100 • 101% = 96 • 100% = 93 • 99% = 88 • 97% = 75 • 95% = 65
⏱️ Skip Rate 20%
The percentage of assigned leader slots where no block was produced, aggregated over 7 epochs and confidence-weighted: validators with only a handful of leader slots are blended toward the network average, so a single unlucky skipped slot can no longer destroy a small validator's score.
Scoring (on the confidence-adjusted rate)
~0% = 100 • ≤0.1% = 98 • ≤0.25% = 95 • ≤0.5% = 90 • ≤1% = 85 • ≤2% = 70
📡 Vote Latency 15%
How many slots behind the chain tip the validator's most recent vote lands, sampled around the clock and averaged over 7 days. Fast, well-connected validators vote within 1–2 slots; high latency indicates network or hardware issues even when votes eventually land.
Scoring (7-day average lag)
≤2 slots = 100 • ≤3 = 92 • ≤4 = 85 • ≤5 = 78 • ≤7 = 68 • ≤10 = 55 • ≤15 = 40
🎖️ Uptime 15%
The percentage of hourly checks over the last 7 days where the validator was voting (not delinquent). Monitored continuously by our scoring service — this replaced the old browser-based tracking that caused different viewers to see different scores.
Scoring
100% = 100 • ≥99.9% = 98 • ≥99.5% = 94 • ≥99% = 88 • ≥98% = 78 • ≥95% = 55
🔄 Consistency 10%
How stable the validator's epoch credit earnings are over the last 7 epochs, using Coefficient of Variation. Consistent validators are more predictable and reliable.
Scoring
CV ≤0.5% = 96 • CV ≤1% = 92 • CV ≤2% = 85 • CV ≤3% = 75 • CV ≤5% = 60
🌳 Root Distance 5%
How far the validator's finalized (rooted) slot trails the chain tip, averaged over 7 days. A healthy tower roots ~32 slots behind the tip; a chronically large gap points to replay lag or struggling hardware even when the validator appears active.
Scoring (7-day average distance)
≤45 slots = 100 • ≤60 = 92 • ≤80 = 82 • ≤120 = 70 • ≤200 = 50
💻 Software Version 5%
Whether the validator is running the latest software version in real network use. Staying updated ensures compatibility, security patches, and network improvements.
Scoring
Latest version = 100 • 1 behind = 85 • 2 behind = 60 • 3+ behind = 30 • Major behind = 40
⚠️ Commission-Rug Penalty −15
Commission changes are tracked continuously. A validator that raises commission by 10+ percentage points within a 7-day window takes a flat 15-point penalty and is flagged — protecting delegators from "commission rug" tactics, including raise-then-lower moves timed around epoch boundaries.
Loading slot data…

Solana Integration

Coming Soon!

◆ Manage Solana validators
◆ Stake & delegate SOL
◆ Track performance & rewards
◆ Same great interface you love
X1

Validator Forensics // hardware & fleet analysis

Benchmarks every validator on the work that actually costs money — producing blocks under a deadline — and cross-references operator fleets by co-location, shared performance trajectories, and sibling delinquency. Built to separate real infrastructure from cheap VPS farms collecting delegation.

Idle.
Lag sampler polls every 10s while this view is open. Mean lag ≈ network distance + hardware; variance and max ≈ hardware. Let it run 15+ min before trusting the numbers.
Starting…
Analyzing on-chain history, then benchmarking block production. This runs a full pass so results appear all at once.

Hardware signal map — low efficiency + high instability = the suspect corner (top-left)

Top suspects — highest farmer risk · click a row to filter the table

Validators

Farmer risk v4 combines evidence with noisy-OR rather than averaging: P = 1 − Π(1 − wᵢ·vᵢ), so independent signals compound and silent ones contribute nothing. (Averaging was the earlier flaw — one damning signal divided by a dozen quiet ones came out a whisper.) Each signal takes the WORSE of (a) an absolute anchor and (b) a robust outlier score — how many noise-widths (median±MAD, floored at measurement resolution) the value sits above the field's own baseline. Identical hardware still scores identically, a uniform field still scores ~0, but validators running 3–10× the field's jitter baseline now register even when the chain is too quiet for absolute thresholds to trip. Weights: shared IP 25% (2 validators on one IP → 70/100, 4+ → max — co-location is the purest farmer signal), efficiency deficit vs the field's p90 20%, epoch instability σ 20%, worst-epoch sag 10%, Slow block production (0.85) and thin blocks (0.50) dominate: the leader benchmark auto-runs with every probe and is the only measurement of the validator doing expensive work under a deadline, taken inside its own 4-slot window so geography cancels — hardware class is the point of the whole exercise, so it carries the most evidence any signal can. Then vote jitter tail 14% (votes missing the next slot — the shared-vCPU fingerprint), arrival jitter 12% (σ of position among each block's votes — sub-slot latency stability that never saturates; distance shifts the mean, only unstable hardware inflates the σ), vote cadence 12% (missing/bunched vote transactions), epoch-boundary stress 12% (late votes during the ~400 slots after rollover — the quiet chain's only guaranteed load spike), slot-1 fumbles 8% + skips 6% (leader-window forensics over ~4.5h — slow boxes disproportionately miss the first slot of their window), clock drift 4%, live stalls/lag 14% (when the live watch has ≥5 min). Trajectory twins (identical multi-epoch damage pattern at 4 decimals, outside the saturated band) score coloc-grade inside the co-location component — independent machines never share exact damage. Fleet mortality 15% (standalone): the delinquency rate of this validator's fleet group (name / style / /16 / trajectory groups of ≥4) — a half-dead fleet indicts its healthy-looking survivors, which is precisely what snapshot metrics can never show. Fleet evidence 15% (matching name pattern after digit-stripping, matching name STYLE template — e.g. one scheme like "X1-" + all-caps word across many different words, identical birth epoch, or ≥3 in one /24 subnet — each capped, since a signal shared by half the chain is demographics, not a fleet; identical self-stake is recorded in the CSV as corroboration but deliberately excluded from scoring) is an amplifier, scaled by the hardware subscore — a fleet of good boxes gains ~nothing, a fleet of weak boxes gets pushed hard. Weights renormalize over available data; hover any risk pill to see which components are driving that score. A ~ marks scores resting on fewer than 3 epochs. A lead for investigation, not proof.
Read-only — makes no transactions, signs nothing. Evidence-based scoring: findings are investigative leads, not proof of misconduct.