Will Solana activate the Alpenglow (SIMD-0326) consensus on its public testnet by Sept 8, 2026? - Predict on WahooPredict
Will Solana activate the Alpenglow (SIMD-0326) consensus on its public testnet by Sept 8, 2026?
17,253 Vol.in 28 days (Sep-08-2026 11:59:59 PM UTC)
DescriptionAlpenglow is Solana's largest consensus redesign — the Votor consensus plus the "Alpenswitch" that replaces TowerBFT and Proof of History, approved via governance vote SIMD-0326 (98.27% yes). It has run on an isolated community test cluster since May 11, 2026; Anza's stated next step is to package it into an Agave client release and activate it on Solana's public testnet, ahead of a staged mainnet rollout guided to late Q3 / early Q4 2026.
This event resolves YES if, on or before 2026-09-08 23:59:59 UTC, the SIMD-0326 (Alpenglow / Votor) feature gate reaches "activated" status on the public Solana testnet (testnet-beta) feature-gate list, i.e. it is assigned a testnet activation epoch.
This event resolves NO if no such public-testnet activation occurs by the deadline.
1. Specificity: Only SIMD-0326 reaching activated status (an assigned testnet activation epoch) on the public Solana testnet counts as YES. Rotor is a separate later SIMD and is NOT required. If SIMD-0326 rolls out in phases, the Votor-portion activation on testnet counts.
2. Exclusion: Activation on the isolated community/dev cluster, a private devnet, or on mainnet-beta does NOT count. A mere Agave release, blog post, or roadmap without on-testnet feature-gate activation does NOT count.
3. Source Hierarchy: On-chain public testnet feature-gate list at explorer.solana.com/feature-gates?cluster=testnet plus official Anza/Solana Foundation announcements are priority. Solana engineering changelog is secondary. Reputable crypto media is tertiary.
4. Timing: Must occur on or before 2026-09-08 23:59:59 UTC. Post-deadline activation resolves NO.
5. Cancellation Rule: YES requires actual on-testnet feature-gate activation, not just an announcement. Announcement alone resolves NO. If activated then rolled back before the deadline, resolves YES based on first activation.