SIMD-0676: epoch stake snapshots your program can read logoSIMD-0676: epoch stake snapshots your program can read
Current epoch plus seven earlier. 160-byte entries. No deployed program. Updated 12 Nov 2026.
devrels.xyz/a/388SIMD-0676 would publish each epoch's stake and vote-account snapshot in an account keyed by epoch number. Pull request solana-improvement-documents#676 is open. Updated 12 Nov 2026. Title: On-Chain Epoch Stakes. X @SolanaFndn.
The snapshot taken at the start of epoch E applies to consensus in E + 1. The runtime keeps the current snapshot plus seven earlier ones. Entries are 160 bytes. The eight-account window is 2.44 MiB in the PR. Fields named there: stake, identity, raw commission, accumulated rewards, latest vote, root slot, BLS keys and signer indices. Canonical BLS signer index is a separate SIMD-0326 amendment (PR 727).
Accounts sit under a dedicated owner with no deployed program. Activation requires SIMD-0326 and SIMD-0357 and would publish only that epoch's snapshot. Reward rules, RPC, and snapshot loading stay unchanged. Stake pools, delegation scoring, and validator dashboards could read this on-chain instead of an off-chain indexer. Proposal only. LinkedIn company/solana-foundation.
Keep reading
Still open. Last updated 4 Nov 2026. Not live. Keep the SPL Stake Pool piece.
Today a failed Solana swap pays the full priority fee. That is why searchers route through Jito bundles and third-party tip services: tips only pay on success. A new proposal in the SIMD repo wants to make success-conditional fees a first-class protocol feature, a flat lamport amount debited only when the transaction status comes back OK. Here is the mechanism, the economics it changes, and the sharp objection that might sink it.
No removal date. About six months after a replacement is ready. Only nonce users act.
Get new articles in your inbox
Technical deep-dives on Solana tooling, infrastructure, and ecosystem. No noise.
