Solana warns Cherry-hosted validators to check logs, rotate keys, and review credentials after a security incident. Solana Foundation has warned some validators to inspect their systems after a Cherry Servers security incident. The warning applies to validators hosted on Cherry Servers and linked to its legacy monitoring system. Validators were advised to review Sensu logs, rotate identity keys, and check exposed credentials. The notice comes as Solana also weighs performance changes tied to its planned Alpenglow upgrade. Solana Issues Security Warning to Validators Solana Foundation said validators using Cherry Servers should inspect their Sensu logs for possible exposure.  The warning followed Cherry’s disclosure of a security incident involving its older monitoring system. The notice focused on operators whose validator systems may have used that service. New: @Solana Foundation says validators hosted on Cherry Servers should inspect their Sensu logs after Cherry disclosed a security incident affecting its legacy monitoring system. Potentially affected validators are advised to rotate identity keys, review exposed credentials,… pic.twitter.com/30MfEpYCjL — SolanaFloor (@SolanaFloor) June 26, 2026 Validators were also advised to rotate identity keys and review any exposed credentials.  In some cases, operators were told to rebuild hosts if they could not rule out compromise.  These steps are meant to reduce risk after possible access to sensitive validator data. Identity keys help identify validators on the Solana network during normal operations.  Therefore, exposed keys can create security concerns for operators and network participants.  The Foundation’s notice asked validators to take direct action based on their own checks. Cherry Incident Puts Validator Hosts in Focus The Cherry Servers incident drew attention because validators help run the Solana network.  They process blocks, verify transactions, and support network records. As a result, security around validator hosts remains closely watched by the community. However, the warning did not state that Solana’s core protocol was breached. Instead, it pointed to risk around hosted systems connected to Cherry Servers.  This makes the issue separate from Solana’s base blockchain design. Even so, validator operators must still review their systems carefully.  They were asked to search logs, check credentials, and replace exposed keys where needed. If a system cannot be cleared, rebuilding the host may be the safer step. Read Also: Solana Crosses $10B Tokenized Stock Milestone After 180% Monthly Volume Jump Alpenglow Upgrade Adds Speed Debate Meanwhile, Solana is also discussing network changes after the Alpenglow upgrade.  One proposal would remove block size limits and let stronger validators process heavier blocks. Weaker validators could skip difficult blocks for a short time and rejoin later. ⚡️ Solana is considering removing block size limits after the Alpenglow upgrade. The idea is simple: Stronger validators process more transactions, while weaker validators can temporarily skip heavy blocks and rejoin later. Alpenglow is also expected to reduce finality from… pic.twitter.com/uAufmzdtGb — MS Capital (@MSCapital_X) June 26, 2026 Alpenglow is expected to cut finality from 12.8 seconds to about 150 milliseconds. Finality means the point when a transaction becomes settled on the network.  Therefore, the upgrade could make Solana faster for users and applications. Still, the proposal has raised questions about validator balance.  Larger validators may earn more rewards if they handle heavier blocks more often. At the same time, higher hardware demands could make operations harder for smaller validators. The post Solana Warns Validators of Potential Compromise After Cherry Incident appeared first on Live Bitcoin News.

Read full article on LIVE BITCOIN NEWS