Coin Brief ENDE

SIMD-0701 proposes Vote Account v5 at 951 bytes, with location and commission schedules

The Solana improvement documents repository merged SIMD-0701, Vote Account v5, on 6 November with status Idea. Written by Tom Pointon of Firedancer and Umar Bhatty, it supersedes SIMD-0677 and extends SIMD-0185, the Vote Account v4 proposal, and it has no feature gate of its own.

The new layout is built for zero-copy access: every dynamically sized field becomes a fixed-size one, each field starts at a multiple of its own size and there is no padding. The result shrinks a vote account from 3,762 bytes to 951. A mandatory location field, three signed 32-bit coordinates, stores where a validator is, as required by SIMD-0674 for a geography-aware leader schedule. The BLS public key becomes mandatory, the votes array is replaced by a single optional latest_vote, and epoch_credits is renamed accumulated_lamports and keeps only the last five entries. A rank field is added as a placeholder.

The commission change is the one with consequences outside the validator. Under SIMD-0249 a commission change made in epoch E takes effect from epoch E+2, so on-chain programs currently cannot see the effective rate or when a queued change applies. Vote Account v5 stores up to four commission rates per reward type, each with the epoch it takes effect, giving programs the previous rate, the current rate and up to two pending changes. The motivation also cites Alpenglow, under which historical votes are unused and a BLS key is needed for every vote account.

SIMD-0701 proposes Vote Account v5 at 951 bytes, with location and commission schedules
SIMD-0701 proposes Vote Account v5 at 951 bytes, with location and commission schedules — Coin Brief

What it means

For staking pools and delegation programs, being able to read a validator's coming commission on-chain closes a gap that SIMD-0249 opened. The smaller fixed layout matters to every client that reads vote accounts, which is most of them.