Anza researchers Roger Wattenhofer and Quentin Kniep are pitching Solana on a SIMD-0675 redesign of the validator leader schedule that reorganises production windows by geographic proximity. Their simulation models mean handover delay falling from 36.2 milliseconds to 17.0 milliseconds, and the median across all handovers dropping from 23.4 milliseconds to 4.5 milliseconds, by grouping nearby leaders into three-window bins. The catch is that bin membership relies on locations validators register themselves; the protocol cannot independently verify a machine's true coordinates. The companion SIMD-0674 specification would store self-reported coordinates in vote accounts, with signed updates and a geometric surface check that confirms the point is plausibly on Earth but says nothing about whether the validator actually sits there.
Why it matters
Solana's stake-weighted leader schedule has long favoured validators clustered near large stake concentrations, since random succession tends to place the next leader close to operators in those hubs. The new binning rule is intended to give validators outside those centres a fairer share of cheap local handovers, which the authors frame as an incentive to operate away from existing hubs rather than a redistribution of stake. Alpenglow's fast leader handover depends on the previous leader sending the next block over a direct path, and the geographic reordering makes that hop shorter on average. Reducing handover delay is one of the cleanest wins available before slot duration itself moves, so any structural improvement here compounds with other Alpenglow-era changes already on testnet.
Market impact
The proposal is consensus-critical and would require its own feature gate, with the schedule's tracking issues still unfilled and both pull requests open as of October 7. Wattenhofer and Kniep's adversarial case puts a 5% stake attacker alone in Sydney with no other Oceania validator; under the proposed three-window setting, that operator can hold two adjacent bins for six consecutive leader windows, more than double the configured bin size. The draft also flags the risk of regional censorship during a run and of longer skipped-slot sequences if power, network or jurisdictional disruption hits a cluster. Wattenhofer and Kniep's incentive check found that one honest operator, Ashburn's largest validator, could shave 2.7 milliseconds off its mean handover by claiming São Paulo, suggesting the self-reported model has at least one exploitable case worth closing before activation.
Frequently asked questions
-
What does Solana's SIMD-0675 actually change about block production?
It reorders the stake-weighted leader schedule into three-window geographic bins so validators near each other produce consecutively, modelled to cut mean handover delay from 36.2ms to 17.0ms without giving anyone more windows.
-
Why is geographic scheduling risky for Solana?
Bins rely on locations validators register themselves; the protocol can check a point is on Earth but cannot verify the validator's true machine. An isolated 5% attacker in Sydney can fill two adjacent bins and hold six consecutive leader windows.
-
Who wrote SIMD-0675 and where does it stand?
Roger Wattenhofer, Anza's head of research and an ETH Zurich professor, and Quentin Kniep, an Anza and ETH Zurich researcher, opened both the schedule and companion location-registration pull requests on Sept. 29. As of Oct. 7, neither has merged.
-
How does this interact with Alpenglow's fast leader handover?
Alpenglow's fast handover sends the previous leader's block directly to the next. Geographic reordering makes that hop shorter on average by putting nearby validators in the same bin, which is the source of most of the modelled latency reduction.
-
When could SIMD-0675 actually go live on Solana?
The schedule is consensus-critical and would require a feature gate, with tracking issues still unfilled. The draft proposes activating the new algorithm two epochs after the feature gate flips, so the live-network timeline is open.
CryptoSlate