Explainer: Starknet Foundation Delegation Program

[AtlasStaking]

Starknet has a diverse, high‑performing validator set. The Starknet Foundation Delegation Program (SFDP) is a key part of that journey, matching validator stake with foundation delegation to accelerate decentralization while keeping performance and security high.​

This post breaks down how the program works, who qualifies, and what it means for validators, delegators, and the long‑term health of the Starknet ecosystem.

If you haven’t read our series that breaks down the Starknet ecosystem in simple terms, click here.

Why Starknet created a foundation delegation program

Starknet needs more than just a handful of large actors running validators. It needs:

• A broad validator set so no single entity or cartel can dominate consensus.

• Enough stake on reliable validators to keep the network secure and running without issue.

• Economic incentives that make it viable for new, high‑quality validators to join and stay.​

The Starknet Foundation Delegation Program is built to address exactly that. They direct foundation stake to:

• Distribute STRK across a more diverse validator set.

• Encourage serious operators from other ecosystems to become long‑term Starknet validators.

• Lower the capital barrier to entry by matching self‑stake with foundation delegation.

HOW THE STARKNET FOUNDATION DELEGATION PROGRAM WORKS

In a nutshell, it’s a stake‑matching program with performance requirements.

1. STAKE MATCHING, 1:1 UP TO 5M STRK

For validators that meet the criteria (see below), the Foundation:

• Matches their self‑staked STRK 1:1, up to a cap of 5,000,000 STRK per validator.​

• Ignores any stake that validator already receives from other delegation programs when calculating the match.​

Examples:

• If you self‑stake 1M STRK (excluding other programs), the Foundation can delegate 1M STRK, plus potential residual pool share.

• If you self‑stake 30M STRK, the Foundation caps the match at 5M STRK, then you may also receive a slice of any remaining delegation pool.​

This design rewards validators who commit real capital and grow organic stake, while keeping any single operator from soaking up too much of the delegation pool.

2. RESIDUAL DELEGATION AND PROGRAM CAP

The Foundation sets aside a fixed pool of STRK for the program. It works like this:​

• Stake Matching: first, the program calculates 1:1 matches for each eligible validator (up to 5M STRK each).

• Residual Delegation: if there’s STRK left after matching, the remainder can be distributed evenly among qualified validators as additional delegation. Even distribution promotes decentralization.​

• Program Cap Adjustments: if the total required for 1:1 matches would exceed the pool, the Foundation scales everyone down proportionally so the program stays within budget.​

This helps prevent giant validators who were early into the program from starving out late entrants or smaller validators.

WHO’S ELIBIBLE FOR THE FOUNDATION DELEGATION?

To qualify for s Starknet foundation delegation, validators must meet a clear set of criteria.​

CORE REQUIREMENTS

A validator has to:

• Run a full Starknet validator node and be active on the network.​

• Maintain high uptime, typically above 99%, showing reliability.​

• Be responsive to the Foundation, answering inquiries within 48 hours.​

• Keep commission at or below 10%, aligning incentives with delegators.​

• Satisfy applicable regulatory and compliance requirements in their jurisdictions.​

The Foundation also monitors validator performance continuously and can rebalance or reduce delegation if a validator falls below standards.​

INTERACTION WITH OTHER DELEGATION PROGRAMS

Validators can participate in multiple delegation programs (for example, from StarkWare or other ecosystem initiatives). However:

• Any stake they receive from other delegation programs is excluded from the base used for 1:1 matching, which makes sense since the match is based on self-stake.

This prevents “double counting” and keeps the focus on self‑stake and organic delegations.

HOW & WHEN TO APPLY

The Starknet Foundation uses **rolling applications with quarterly cutoffs.**​

APPLICATION WINDOWS

Validators can submit their application at any time, but decisions and rebalancing happen on a quarterly schedule:​

• Application cut‑offs:

  • 16 February

  • 16 May

  • 16 August

  • 16 November

• Notification of outcomes:

  • End of February

  • End of May

  • End of August

  • End of November

• Stake rebalancing (delegation adjustments):

  • End of March

  • End of June

  • End of September

  • End of December​

Practically, this means:

• You want your application submitted and your validator in good standing well before a cut‑off date.

• You should expect changes to delegation around quarter‑end, as the Foundation evaluates validators and moves delegations from those that aren’t performing.

Applications are submitted via the official Starknet Foundation form.

HOW THIS FITS WITH STARKWARE’S DELEGATION PROGRAM

Alongside the Foundation’s program, StarkWare operates its own delegation program. The requirements and details are slightly different, but goals are aligned:​

• Encourage a more balanced stake distribution.

• Support small and emerging validators as well as established ones.

• Cap commission and consensus power to avoid centralization.​

Examples of StarkWare’s criteria include:​

• Existing Track:

  • At least 1 month as an active validator.

  • 99% uptime.

  • Minimum 20k STRK self‑stake (excluding delegation programs).

  • The validator cannot have more than 5% consensus power.

  • Commission at or below 10%.

  • Possible testnet participation.
    ​

• New Track:

  • At least 3 months as an active validator.

  • 99.5% liveness.

  • Minimum 1M STRK self‑stake (excluding delegation programs).

  • Same caps on consensus power and commission.

  • Testnet participation expectations from Q2 onward.​

For validators, the important thing is that both programs care about the same fundamentals: uptime, reasonable commission, testnet experience, and not concentrating too much power in any single operator.

WHAT THIS MEANS FOR STRK DELEGATORS

If you’re a STRK holder the Foundation’s delegation program helps you indirectly.​

• More validators have enough stake to be economically viable, so you have more real choices.

• The program’s performance requirements mean that any validator receiving Foundation delegation has to maintain strong uptime and responsiveness.

• 1:1 matching up to 5M STRK pushes validators to commit their own skin in the game instead of relying entirely on external delegation.​

When you choose where to delegate, you can look for:

• Validators who meet or exceed the program’s criteria.

• Transparent communication about their performance and the ability to reach them via email or socials.

• Community participation.

• Reasonable commission and a track record across other networks.

WHAT THIS MEANS FOR VALIDATORS, LIKE ATLAS STAKING

For serious operators, Starknet’s foundation delegation program is both an opportunity and a responsibility:

• It can transform an otherwise marginal validator into a sustainable one by matching self‑stake with up to 5M STRK in delegation.​

• It requires you to treat Starknet as a first‑class chain with high uptime, monitoring, alerting, redundancy, and clear communication with both the Foundation and delegators.

• It incentivizes ongoing testnet participation, governance engagement, and long‑term alignment with the network’s decentralization goals.

A validator that wants to thrive under this model should:

• Run professional infrastructure (multi‑region failover, strict monitoring, tested incident runbooks).

• Keep commission at or below 10%.

• Publish regular updates, staking guides, and clear incident reports when something goes wrong.

• Show up consistently in Starknet governance and community spaces.

HOW STRK STAKERS VIEW THE DELEGATION

If you’re delegating STRK rather than running a validator, here’s a simple checklist:

1. Check eligibility signals

   • Does your validator publicly commit to uptime targets similar to the program’s >99% requirement?​

   • Is their commission at or below 10%?

2. Look for skin in the game

   • Do they disclose meaningful self‑stake or long‑term commitment across other PoS networks?

3. Evaluate communication and education

   • Do they publish guides on how to stake STRK, explain Starknet’s PoS roadmap, and talk transparently about risks?
     ​

4. Consider diversification

   • Spread delegations across more than one validator to reduce operator risk, especially in the early PoS phases.

WRAPPING IT ALL UP

The Starknet Foundation Delegation Program is more than a funding mechanism. It’s a clear statement that Starknet wants a decentralized validator set, with skin in the game and strong operational practices.​

For validators, it’s a chance to step up and be measured against transparent criteria. For delegators, it’s a signal that the network is serious about decentralization and resilience.

Atlas Staking is aligned with the Starknet foundation and is committed to operate in the network’s best interest. If you have questions or comments please let us know.

[tunn1790]

really appreciate this breakdown….clears up a lot of confusion i’ve been seeing in discord about how the delegation programs actually work
couple thoughts after reading through:

on the 1:1 matching up to 5M:
this is smart design tbh. it forces validators to have real skin in the game instead of just running infrastructure with zero capital commitment
the cap at 5M also prevents whale validators from sucking up the entire pool, which i’ve seen happen on other chains where early validators just dominate forever

quarterly rebalancing is key:
the fact that foundation can pull delegation from underperforming validators keeps everyone honest. you can’t just coast after getting accepted
application cutoffs (feb 16, may 16, aug 16, nov 16) with decisions at quarter-end gives clear timelines. no more “when will i hear back?” questions

one thing that stood out:
“Any stake they receive from other delegation programs is excluded from the base used for 1:1 matching”
this makes total sense but i bet it confuses new validators. so if starkware delegates 2M to you, foundation doesn’t count that toward your “self stake” for matching purposes
basically: only YOUR tokens + organic delegations count for the match
prevents double-dipping which is fair
for smaller validators:

the 20k minimum (existing track) vs 1M minimum (new track) in starkware’s program is interesting
emerging validators can start small, prove 99% uptime for a month, then scale up
but the 1M requirement for “new track” is steep - that’s like $50k+ at current prices
wonder if that excludes solo stakers who want to run quality infrastructure but don’t have that much capital

residual delegation distribution:
“if there’s STRK left after matching, the remainder can be distributed evenly among qualified validators”
love this. means even if you don’t max out the 5M match, you might still get extra from the pool if budget allows
encourages validators to apply even if they’re not massive

one question:
when you say “maintains high uptime, typically above 99%” - is that measured per epoch or over a longer period?
because missing attestation = zero rewards for that entire epoch (all or nothing basis), so 99% uptime could still mean multiple zero-reward epochs if you’re unlucky with timing
would be good to know if foundation measures this daily, weekly, monthly, or what
for delegators reading this:

the tldr is: foundation program creates competitive pressure
validators need to maintain 99%+ uptime, <10% commission, good communication, or they lose foundation delegation
this is GOOD for you as a delegator because it means validators in the program are held to actual standards
when choosing where to delegate, look for:
∙ validators who are transparent about their setup
∙ consistent communication (not just “set and forget”)
∙ reasonable commission (10% or under)
∙ track record on other chains if they’re new to starknet

overall take:
this program design feels well thought out. it’s not just throwing money at validators - there are actual performance requirements and rebalancing mechanisms
interested to see how the validator set evolves over the next few quarters as foundation pulls delegation from underperformers and redirects to newer, better operators
should create healthy competition which is what you want in a maturing pos network
thanks for writing this up - bookmarking for when people ask “how does foundation delegation work” in discord

[AtlasStaking]

I don’t know the answer specifically, but validator uptime is generally measured over multiple epochs.

We just hope the foundation isn’t super rigid with the minimum 20k STRK vs 1M STRK. While we are a professional validator, we are small and relatively young so the 1M STRK simple isn’t attainable for us. But, we do have 20K STRK bonded.

[domanost]

I was interested in the 20K STRK amount as I run a node already. It seem the crypto market price out the little guy by moving goal posts based off current spot prices. While price is down this a entry point for me. “Skin in the game” is pretty opaque and subjective upon entry point vs penciling in a USD benchmark threshold because if the spot price drops someone will table a inflated amount of STRK in a future proposal.