SNIP-45: Staked STRK Vote Delegation to Validators

Summary

SNIP-45 proposes that validators vote on behalf of their delegators by default. Any delegator can take back their vote, or give it to any other address, at any time with one transaction. The staking protocol itself does not change.

This proposal will go to a governance vote on governance.starknet.io from 27 November to 4 December 2026.

Motivation

Staked STRK is the largest pool of long-term STRK, yet it is almost absent from governance. On average, only 0.5% of staked STRK took part in the last six proposals, and delegators, who hold 91% of it, rarely vote.

Low turnout weakens the legitimacy of protocol upgrades, makes governance easier for a small group to capture, and turns polls into a measure of who happened to vote rather than what stakers think.

Delegators already trust their validator with their stake. SNIP-45 extends that trust to their vote by default, while keeping a one-transaction way out. Applied to recent proposals, this would have raised staked STRK turnout as follows:

Proposal Turnout today With validator delegation
Starknet v0.14.3 (Updated) vote 0.33% 2.89%
Post-quantum L1 poll (Oct 2026) 1.76% 11.30%

The proposal

1. Staked Vote Delegation Registry

An immutable registry on Starknet stores voting preferences only. It holds no funds, has no owner, and cannot be upgraded or paused. Each address can only change its own entry. The Starknet Foundation deploys it and publishes its address before the vote.

2. Opt-out default for delegators

You are… By default Your options
A delegator Your validator (or the voting address it names) votes with your staked STRK Keep your own vote or give it to any address with one call, and reset to the default at any time
A validator You vote with your own stake plus your delegators’ stake, unless they opt out Vote from a separate address (e.g. if your staker address is a cold wallet), or decline default delegations so your delegators keep their own vote

A delegation website will let delegators check where their vote goes and change it, and let validators set their preferences.

3. Voting power calculation

Voting power from staked STRK continues to be calculated off-chain at each proposal’s snapshot block, now from the staking contract plus the registry. The result is used for both governance votes (Snapshot X) and polls (Snapshot starknet.eth). For each vote and poll, the Starknet Foundation publishes the list with the script and inputs used, so anyone can reproduce it.

Changes only count if made before a proposal’s snapshot block.

What does not change

  • Staking and pool contracts, rewards and exit windows
  • Other voting power sources: vSTRK, L1 STRK and the delegate whitelist
  • STRK that is not staked in a pool
  • BTC pools, which are excluded

Activation and timeline

When (2026) What
19 – 26 Nov Community discussion on this thread (1 week)
By 27 Nov SNIP finalised; registry deployed and its address published
27 Nov – 4 Dec Governance vote
7 days after a passing vote The new default applies to proposals from then on. Delegators and validators can set their preferences during this period

Feedback

We invite comments on this thread before the SNIP is finalised. We are particularly interested in input from validators, liquid staking protocols and custodians on how they plan to use the registry, and from delegators on what they need from the delegation website.