Interactive Solana Architecture Simulator

Solana Changed Its Engine.

Alpenglow changes how Solana reaches agreement. Celor lets you see the new network model in real time.

Explore it.Break it.See what changes.
01

SLOT

Where this activity is happening.

A ~200ms target interval (SIMD-0525; formerly 400ms) assigned to a specific producing leader.

02

LEADER

The validator currently producing the network's data.

Rotates across 4-slot windows (~800ms tenure). If their window expires, handoff takes over.

03

BANK

The current version of Solana's state being built.

Under Alpenglow, multiple candidate banks can exist per slot simultaneously.

04

STATE

What the network currently believes happened.

Resolved canonically across forks based on cryptographic lineage.

05

FINALITY

When the network agrees this state is final.

Aggregated BLS proof notarizes state in ~150ms instead of 32 TowerBFT slots (~6.4s at 200ms / ~12.8s legacy).

Epoch 1064 Interactive Test Bench

Try Solana 2.0 Before Mainnet

On October 21 at Epoch 1064 (~14:50 UTC), Solana replaces TowerBFT with off-chain Votor BLS certificates on Agave 4.3.0. Test the hardfork cutover live below.

Consensus Transaction Flight
Engine: Votor (Agave 4.3.0)
Preset:
Monotonic Latency Elapsed
0ms
Canonical Target
~153ms BLS Cert
99% Latency Reduction
CONSENSUS PIPELINEReady to dispatch
Fault-Tolerance Stress Lab
40% RESILIENCE
Simulate Offline / Stalled Stake:12% OFFLINE
0% (Perfect)20% (Fast Path Limit)40% (Fallback Limit)50%
ACTIVE VOTING STAKE:88.0%
CONSENSUS PATHWAY:⚡ FAST PATH (≥80%)

80%+ validator stake reached. Off-chain BLS aggregated certificate generated in ~150ms.

Agave 4.3.0 Client QualificationCERTIFIED
The Explorer TPS Metric Shift

Why Reported Explorer TPS Will Drop on October 21

Votes Moved Off-Chain
LEGACY SOLANA (TOWERBFT)
~2,800 Reported TPS
• 2,200 TPS was on-chain vote transactions
• Only ~600 TPS was actual user transactions
• Vote spam bloated state and delayed real trades
SOLANA 2.0 (ALPENGLOW VOTOR)
~600 Clean Real TPS
• 100% of block space dedicated to actual user transactions
• Votes bundled into off-chain BLS certificates
• 99% faster finality with zero vote congestion

Celor is the only infrastructure that normalizes Votor off-chain certificates and multi-candidate banks in real time.

Trade on Pump.fun →
ALPENGLOW BANK GRAPH

One Slot. Multiple Possible States.

Under Alpenglow, more than one candidate state can exist around the same slot. A slot is an interval of time, not an immutable monolithic block.

Candidates:
Active Cluster Slot
SLOT 447809653
Parent Block: Slot 499
BANK A
CANDIDATE
Parent Slot:499
Blockhash:4xMvK...A653
Click to follow
BANK B
✓ CANONICAL
Parent Slot:499
Blockhash:4xMvK...B653
Currently trackingActive Branch
BANK C
CANDIDATE
Parent Slot:499
Blockhash:4xMvK...C653
Click to follow
Why does this matter? In legacy Solana (TowerBFT), people assumed 1 slot = 1 block. Under Alpenglow, validators construct competing candidate banks. If a validator builds on a branch that is superseded, that bank is abandoned. Celor prevents trading systems from treating observed state as final state before canonical consensus resolves.
SUB-SLOT EXECUTION TIMING

Leader Handoff: Why Sub-Slot Timing Matters

One validator's turn ends. Another takes over. If you fire a transaction with only 18ms left in a slot, the old leader drops it. Celor calculates the handoff boundary in microseconds.

CURRENT LEADER
Validator A (dv4AC...RBVJB)
Stake: 2.4%QUIC Ping: 8ms
NEXT LEADER (IMMINENT)
Validator B (7xKXt...Q1L)
Stake: 1.9%Prewarmed TPU
Sub-Slot Budget:160ms remaining / 200ms target
Simulate Buy Request Timing:
"Why Did Celor Choose This?"
ACTION: WAIT

Leader almost changed.

Less than 40ms remaining in slot. Holding packet saves gas and guarantees inclusion on next leader.

ACTION: CANCEL

Bank abandoned.

UpdateParent observed or fork reorg detected. In-flight order aborted to prevent execution against ghost state.

ACTION: FIRE

Fresh state & leader active.

Bank valid, latency under threshold, healthy telemetry source verified.

ACTION: UNKNOWN

Source missing evidence.

The connected stream does not supply necessary candidate telemetry. Celor refuses to guess.

CONSENSUS FINALITY REVOLUTION

How Fast Does The Network Agree?

TowerBFT required waiting 32 consecutive block lockouts (~12.8 seconds). Alpenglow replaces this with cryptographic aggregate BLS certificates (~150ms).

OLD CONSENSUS MODEL
~12.8s

32 progressive block lockouts in TowerBFT. High reorg risk before root.

CONSENSUS SPEED CLOCK
12.8s
Alpenglow targets ~85.33× faster finality.
ALPENGLOW TARGET
~150ms

Sub-slot BLS aggregate certificate with ≥80% stake fast-path notarization.

Interactive Finality Race
LANE 1: OLD SOLANA (TowerBFT)0 / 32 Lockouts
ObserveWait (Slot 8)Wait (Slot 16)Wait (Slot 24)Final Root
LANE 2: ALPENGLOW (BLS Fast-Path)0%
ObserveBLS Vote AggregationCertificate VerifiedInstant Finality
CRYPTOGRAPHIC CONSENSUS

BLS Certificate: Who Agreed?

A cryptographic proof that enough validators agreed. No blockspace wasted on on-chain votes.

84.6%Stake
Fast-Path Threshold Met (≥80%)
Validator Aggregate Endorsements:
Validator A (dv4AC...RBVJB)✓
Validator B (7xKXt...Q1L)✓
Validator C (3kLmn...90P)✓
Validator D (J1to...Fast)✓
+116 additional validator signatures combined
CRYPTOGRAPHIC CHECKDIRECT
✓ CERTIFICATE VALID

BLS12-381 pairing equation verified. State cannot be reverted by any fork.

Algorithm: BLS12-381 Aggregation (SIMD-0326)
SOURCE TRUTH & PROVENANCE

Public RPC vs Deep Validator Telemetry

Standard JSON-RPC only shows you history after blocks are sealed. Celor hooks into deep validator telemetry to observe candidate banks before execution.

Feature Coverage Audit (Public JSON-RPC)Score: 27 / 100
Consensus MetricStandard RPCCelor GeyserData Provenance
Slot NumberDIRECT
Root FinalityDIRECT
Leader ScheduleDERIVED
Candidate BanksUNAVAILABLE
Bank HashUNAVAILABLE
UpdateParent MarkersUNAVAILABLE
BLS12-381 CertificatesUNAVAILABLE
Pre-Execution DeshredUNAVAILABLE
Celor Invariant: Never simulate or fabricate missing RPC fields.Phase 9 Specification
Pre-Execution Telemetry

See It Before Execution

Turbine broadcasts packet shreds across the cluster. Celor reconstructs transactions from validator deshred hooks before ordinary RPC block announcements exist.

1. Shred Ingestion15ms
2. Pre-Execution Deshred32ms (Celor)
3. RPC Block Event200ms+ (RPC Gossip)
Observed before state commit. Enables algorithmic routing with zero blind spots.
SOURCE TRUTH GAME

Is This Real?

Suppose you are querying a standard Public Solana JSON-RPC endpoint. Can you get the Bank Hash of a candidate bank?

CONSENSUS CHAOS TESTING

Break The Network

Inject intentional failure modes into the simulator. Watch how Celor’s consensus engine protects capital and prevents blind execution.

REAL-WORLD SCENARIOS

Try A Real-World Scenario

See how the new consensus engine alters everyday trading, settlement, and validator interactions.

New Token Pool Launch Workflow

Step-by-Step Architecture Pipeline
Pool Creation Shred
Slot Boundary
Leader QUIC Route
Candidate Bank B
Decision: FIRE
Consensus Invariant: Celor discovers the new pool pre-execution via validator shred telemetry, allowing your execution engine to submit before public RPC indexes the transaction.

Now you understand why the infrastructure has to change.

Traditional RPC infrastructure was built for 12-second block intervals. Celor provides the high-frequency consensus telemetry required for Alpenglow.