$SOL Solana PoH Clock Attack Vulnerability Revealed: Transition-Phase Risks Remain Unresolved
USENIX Security researchers have publicly disclosed a clock-based attack targeting Solana's Proof-of-History (PoH) mechanism; the issue was initially reported privately to the development team in December 2025.
🔸 Attackers could manipulate the PoH clock to slow down logical time, gaining extra time to select transactions and isolate blocks produced by honest validators.
🔸 The stake threshold required to execute the attack is below 33%, mirroring a 51% attack scenario under certain conditions.
🔸 The "Alpenglow" security competition (with a 50,000 SOL prize pool) concluded on August 19 but excluded this vulnerability from its scope, as it affects only the legacy system.
👉 Solana has been aware of this vulnerability since December 2025 and has confirmed that it is difficult to exploit under current conditions. However, while the Alpenglow code is included in Agave 4.2, it has not yet been activated on the mainnet; official rollout is expected with Agave 4.3. During this transition period, the associated risks have not yet been fully analyzed or addressed at the public deployment level. This creates a potential "window of opportunity" for sophisticated attackers, though the likelihood of such an attack remains low.
💬 Do you think Solana should accelerate the Alpenglow activation schedule to close this vulnerability?
News is for reference, not investment advice. Please read carefully before making a decision.
USENIX Security researchers have publicly disclosed a clock-based attack targeting Solana's Proof-of-History (PoH) mechanism; the issue was initially reported privately to the development team in December 2025.
🔸 Attackers could manipulate the PoH clock to slow down logical time, gaining extra time to select transactions and isolate blocks produced by honest validators.
🔸 The stake threshold required to execute the attack is below 33%, mirroring a 51% attack scenario under certain conditions.
🔸 The "Alpenglow" security competition (with a 50,000 SOL prize pool) concluded on August 19 but excluded this vulnerability from its scope, as it affects only the legacy system.
👉 Solana has been aware of this vulnerability since December 2025 and has confirmed that it is difficult to exploit under current conditions. However, while the Alpenglow code is included in Agave 4.2, it has not yet been activated on the mainnet; official rollout is expected with Agave 4.3. During this transition period, the associated risks have not yet been fully analyzed or addressed at the public deployment level. This creates a potential "window of opportunity" for sophisticated attackers, though the likelihood of such an attack remains low.
💬 Do you think Solana should accelerate the Alpenglow activation schedule to close this vulnerability?
News is for reference, not investment advice. Please read carefully before making a decision.