The Solana Foundation’s updated Alpenglow guidance schedules expected mainnet activation for epoch 1064, beginning on 21 October 2026 at approximately 15:00 UTC, or 16:00 BST. Its status table still marks mainnet as not activated.

Alpenglow’s Votor voting protocol replaces TowerBFT consensus. It targets roughly 150-millisecond finality, distinct from the network’s separately shortened 200-millisecond block time. Rotor, a later block-distribution phase, remains unscheduled.

Operators have preparation work

The Foundation instructs validators to use an Agave-based client built on Agave 4.3.0. Firedancer and Frankendancer are unsupported during the migration. Operators must keep at least 0.8 SOL above the rent-exempt minimum in the vote account to pay the Validator Admission Ticket.

The guidance says ordinary transaction submission and program execution are unchanged. Data consumers face changes including bank identifiers and the removal of vote transactions from blocks. It directs operators to Anza’s documentation for the authoritative checklist.

NetNapz assessment: verify activation, not just the calendar

Assessment: an epoch-based transition should be monitored as a network event, not treated as an appointment guaranteed to occur at an exact wall-clock minute. Readiness involves client compatibility, participation and successful consensus handoff. The scheduled date does not prove those conditions have already been met.

Operators should use official instructions for their particular client and role. This report is not a substitute for a release checklist, and NetNapz has not tested a validator migration. Ordinary holders should not infer that a protocol upgrade requires sending tokens to a migration address.

Metrics need careful interpretation

Assessment: if a dashboard counts consensus votes as transactions, removing those votes changes its reported total even if user activity is unchanged. Comparisons across the transition should separate user transactions from consensus overhead and use consistent definitions.

Likewise, faster finality is a technical capability rather than a demonstrated increase in commercial adoption. Payment reliability, application performance, costs and sustained usage still need measurement. None of those outcomes follows automatically from a latency target.

Sources and timing

Solana Foundation: Alpenglow upgrade and operator guidance, updated October 2026, checked 14 October. Solana Compass reporting, published 13 October, cites Anza’s earlier approximate 14:50 UTC timing. This report uses the Foundation’s epoch-1064 estimate of approximately 15:00 UTC and does not describe either estimate as completed activation.