What Is Rotor in Solana?
Rotor is the block propagation protocol proposed as part of the Alpenglow upgrade for Solana. It is designed to replace Turbine with a more efficient data distribution mechanism that reduces block propagation latency across the validator network.
Rotor vs Turbine
Turbine distributes shreds through a layered tree structure. Rotor improves on this with optimizations to the propagation topology and data encoding, aiming for faster and more reliable delivery of block data to all validators.
The specific improvements target reducing the number of hops between the leader and the most distant validators, and improving resilience to packet loss.
Rotor and Votor
Rotor handles block propagation (getting block data to validators). Votor handles consensus (validating and finalizing blocks). Both are needed to achieve Alpenglow’s goal of sub-second finality — faster propagation means validators can vote sooner, and faster consensus means fewer voting rounds.
FAQ
Will Rotor change how I receive data via RPC? No. Rotor is a validator-to-validator protocol. RPC users and application developers interact with the same RPC methods regardless of the underlying propagation protocol.
Is Rotor deployed yet? Rotor is part of the Alpenglow proposal. Check the Alpenglow page for current status and timeline.
Updated: