X1 vote pipeline latency vs UTC

Time from vote creation to on-chain visibility

—

Solana/Tachyon vote pipeline takes ~400-850 ms inherently (signing + gossip + block inclusion). Values in this range are normal — Layer 1 baseline, not clock drift. See methodology.

methodology

Network state

Active validators

—

Voted within last ~7 minutes

Observed (last 24h)

—

All validators in daemon database

Zombie data

—

Stopped voting (likely Capybara cleanup)

All charts and tables below show active validators only. Zombies excluded since 2026-05-06.

Validator pipeline health

Distribution by deviation from foundation baseline

✅

Normal pipeline

—

|deviation| < 500 ms

⚠️

Slow pipeline

—

500 ms – 5 s

🔴

Clock drift

—

|drift| ≥ 5 s — Layer 2

🏛️

X1 Labs

—

baseline reference

Network diagnostic snapshot

Side-by-side: pipeline health vs clock drift outliers

Vote pipeline latency

Layer 1

— ms

—

Baseline: — ms

Network-wide median lag from vote creation to block inclusion. ~400-850 ms is healthy Tachyon protocol behavior.

Clock drift outliers

Layer 2

— validators

—

Worst: —

Validators with |drift| ≥ 5 seconds — genuine NTP/chrony misconfiguration. Full list in the Anomalies section below.

Operating a validator? Find your row in the tables below, then check the step-by-step diagnostic guide for fix instructions.

My clock vs world

…

Wall clock (your browser)

—

Sentinel offset to UTC consensus

—

RMS offset

—

Stratum

—

Reference source

—

Frequency skew

—

Vote pipeline latency over time (5-minute buckets)

Aggregate vote-to-block latency · {bucketLabel} buckets · stable ~-800 ms = healthy Tachyon protocol; sudden swings = stress, deployments, load events.

Show outliers Y-axis: ±5000 ms · ▲ marker = value exceeds range

X1 Labs foundation pipeline trend (14 days)

Tracks pipeline latency for the 12-node X1 Labs foundation cluster. Shifts >100 ms in one bucket indicate X1 Labs changed something operationally — Tachyon config, NTP source, deployment, or load test. NOT clock drift (foundation clocks are tightly synchronized — identical signature across nodes proves this).

Current avg lag —

Change vs 7d ago —

Active foundation nodes —

Anomalies & deviations

Pipeline anomalies

500 ms ≤ |lag| < 5 s · ≥20 samples

Validators with elevated pipeline latency. Causes: slow network, CPU saturation, geographic distance from leaders, suboptimal Tachyon config. Not a chain-time threat — but operator should investigate infra.

Min stake (XNT, optional) Client-side lens. Server keeps all stake levels.

#	tag	pubkey	lag (ms)	jitter (ms)	n	stake (XNT)

page 1

Clock drift (Layer 2)

|drift| ≥ 5 s · ≥20 samples · genuine clock misconfiguration

Validators whose Clock::unix_timestamp deviates from real UTC by 5+ seconds. This IS clock drift — operator needs to fix chrony/NTP. Strontium oracle corrects this at protocol level for chain consumers.

#	pubkey	lag (ms)	jitter (ms)	n	stake (XNT)

Top pipeline efficient validators (top 10)

≥100 samples · |lag| < 5 s · foundation excluded · sorted by ABS(lag) ascending.

Lowest pipeline latency means fastest vote→block round-trip. NOT necessarily the best clock — pipeline depends on network position, leader proximity, and Tachyon configuration. Foundation excluded since its baseline is the protocol baseline.

Min stake (XNT, optional) Client-side lens. Server keeps all stake levels.

#	pubkey	lag (ms)	jitter (ms)	n	stake (XNT)

🏛️ X1 Labs Foundation

Official X1 Labs infrastructure. Shown separately because their drift is operational baseline, not validator misconfiguration.

#	label	pubkey	drift (ms)	jitter (ms)	n	stake (XNT)

Deeper analytics distribution, correlation, signature groups

Validator pipeline lag distribution (all tracked)

Most validators cluster in -800 to -400 ms range (Tachyon Layer 1 baseline). Bins outside this range indicate slow pipeline (amber) or genuine clock drift (red, Layer 2).

Stake vs drift correlation

Each point = validator. Foundation nodes shown in blue. Validators with < 0.01 XNT excluded as testnet noise. Layer 2 outliers (drift < -5 s) clamped to chart edge.

Correlation: — · Slope: —

Identical-drift clusters

Validators sharing identical drift values. May indicate shared infrastructure, common hosting provider, or coordinated NTP source. Filtered to clusters with ≥ 100 XNT total stake to exclude testnet noise.

Detected clusters —

Validators in clusters —

Largest meaningful cluster —

Clusters with < 100 XNT total stake hidden as likely testnet noise.

NTP sources (chrony calibration)

Operator	Country	Hostname	Stratum	State	Offset (µs)	Last RX (s)

How to read this dashboard

Layer 1 — Pipeline latency

~400-850 ms inherent in Tachyon protocol. Sum of signing + gossip + block inclusion times. Identical across well-synchronized validators.

Layer 2 — Clock drift

Validator system time vs real UTC. |drift| > 5 s indicates NTP/chrony misconfiguration. This is what Strontium oracle corrects.

Full details: methodology