We finished a 3 hours Whitepaper Reading on AlpenGlow (@anza_xyz ) Notes: (1) Turbine now optional—Rotor handles block relay, simpler but maybe easier to censor (2) relay nodes become incentive-driven (3) certificate signatures cut on-chain bytes, not network traffic (4) Solana’s scaling lever is lower latency; slots fixed at 400 ms (5) PoH clock removed—400 ms leader timeout enforces ordering (6) protocol favors quick cancellations over inclusions, possibly boosting resubmits. Questions: (1) What are the key trade-offs in rolling out Alpenglow? Is it censorship resistance? (2) How are certificates created and verified? (3) How exactly does Alpenglow replace PoH for ordering? (4) As relays are a new middle men, can they direct-message txs to validators they trust and create a fork? Does that create censorship? Any pointers would be great @TheWattenhofer @DiscoKobi @qkniep @brenn @bw_solana