The Solana Foundation Delegation Program is moving toward a smaller, time-limited role in validator economics. For operators, the immediate question is how much stake and revenue they need to replace if Foundation support ends.
As of November 7, 2026, the Foundation’s public dashboard shows 337 validators receiving Foundation stake. Its participant directory lists 346 approved mainnet identities. Our review of those 346 records found 308 with evidence of meeting at least one of the published tenure or non-SFDP stake retirement conditions, before renewal and transition decisions. Those are different measurements, and the distinction matters.
The validator-level evidence is public. You can inspect all 346 rows and the basis for the 308 classification in our published data and methodology.
Below, we explain the rules, show how we counted exposure, and walk through using the ProStaking Validator Calculator to model the operating impact.
What the current rules say
The Foundation’s official FAQ describes two retirement conditions:
- Twelve months in the program. The clock starts at the first epoch in which a validator was eligible for Foundation delegation on mainnet.
- More than 300,000 SOL of non-SFDP stake. The wording is “exceeds,” so our screen uses a strict greater-than comparison.
The tenure rule is about program eligibility, not the age of a stake account, vote account, or validator identity. An old account does not by itself establish twelve months of SFDP membership. Creating or moving stake accounts does not establish a new program start date, either.
There is a renewal route. The Foundation’s renewal application says a validator may apply once for one additional year. Applicants must meet the current criteria and demonstrate meaningful contributions or exceptional support for the ecosystem. Renewal is an application, not a guaranteed extension.
The documentation is not fully synchronized: the separate delegation criteria page still displays a 1 million SOL threshold, while the FAQ specifies 300,000 SOL. We use the FAQ’s retirement threshold here. Operators should confirm their own status and transition terms with the Foundation rather than infer an individual deadline from this article.
The reported 100-validator cap
Crypto Briefing’s November 6 report and SolanaFloor’s coverage describe a maximum of 100 validators and retirements in weekly tranches. We have verified the tenure, stake threshold, and renewal provisions in Foundation materials. The 100-validator cap and tranche schedule are attributed here to that secondary reporting; we did not independently retrieve the original Foundation announcement.
If the cap is implemented as reported, moving from today’s 337 funded validators to 100 would mean 237 fewer supported slots, a 70.3% reduction. Using the broader directory of 346 approved identities instead produces a difference of 246, or 71.1% of that cohort. Approval and funding are distinct, so this is not a second retirement estimate.
These figures describe the size of the contraction against two different baselines. They do not identify exactly which validators will lose support, establish an individual removal date, or predict how many validators will shut down. Renewal decisions, transition timing, and room for new applicants affect the outcome.
How many validators are in SFDP today?
We captured the public data between 15:36 and 15:46 UTC on November 7, 2026. The official delegation dashboard showed:
- 337 validators receiving Foundation stake.
- Approximately 23.75 million SOL delegated.
- 60 locations across 26 countries.
The official participant directory contained 346 unique approved mainnet identities. Approved membership is broader than currently receiving stake, so 346 should not be substituted for the dashboard’s 337 funded validators.
The dashboard’s latest displayed epoch was 1078, while the chain had advanced to epoch 1080. These are the latest public records available in our capture, not a perfectly synchronized live census. Public status, balance, and aggregate views can update at different times.
Our exposure screen: 308 of 346 approved identities
We reviewed the Foundation’s individual public validator records for all 346 approved mainnet identities. The screen asks whether the records show at least twelve months of mainnet delegation eligibility, non-SFDP stake above 300,000 SOL, or both.
| Observed condition | Approved identities |
|---|---|
| Twelve-month eligibility history only | 284 |
| Both twelve-month history and more than 300,000 SOL | 18 |
| More than 300,000 SOL only | 6 |
| Neither condition observed | 37 |
| Insufficient mainnet and stake data | 1 |
| Total | 346 |
That gives us 302 with observed twelve-month eligibility history and 24 above the non-SFDP stake threshold. Eighteen appear in both groups. Counting each identity once produces 308 of 346, or 89.0%, potentially exposed to at least one retirement condition.
This is an eligibility screen before renewal and transition decisions, not a Foundation removal list. Some approved records already report zero Foundation stake. It also does not mean that 308 of the 337 currently funded validators will be removed: the exposure analysis uses the 346-identity approved-membership cohort.
Tenure drives most of the result. Of the 308 flagged identities, 284 are flagged on observed eligibility history alone. The public stake records also show how many participants remain below the new stake threshold:
| Non-SFDP stake | Approved identities |
|---|---|
| Below 50,000 SOL | 96 |
| 50,000 to less than 100,000 SOL | 126 |
| 100,000 to 300,000 SOL, inclusive | 99 |
| More than 300,000 SOL | 24 |
| Unknown | 1 |
In this cohort, 222 approved identities have less than 100,000 SOL outside SFDP. Losing a Foundation delegation can materially change their economics even when they are nowhere near the 300,000 SOL retirement threshold. The size of that change depends on each validator’s actual delegation, commission, rewards, and costs.
How we measured tenure and stake
For the exact snapshot used in this article, open the 346-row validator-level CSV, full methodology, reproduction instructions, and independent audit. These links are pinned to the reviewed repository revision. The package includes frozen public source fields and offline checks so readers can reproduce the count. It is a point-in-time exposure screen, not a live eligibility determination.
We used the Foundation’s public delegation API and the individual validator records it exposes. Non-SFDP stake is the reported activated stake from the last recorded epoch minus reported Foundation stake, converted from lamports to SOL. This includes self-stake and other non-SFDP sources; it is not necessarily stake from independent third-party delegators.
For tenure, we looked for mainnet epoch history marked Baseline or Bonus, indicating observed delegation eligibility. We compared the earliest such observation with calendar time. Solana’s epoch schedule and block timestamps place the start of epoch 876 at November 7, 2025, 03:25:28 UTC. An observed eligible epoch at or before 876 therefore supports at least twelve calendar months of eligibility by our capture time.
We did not equate twelve months with a fixed number of epochs, use stake-account creation dates, or treat onboarding dates as proof of eligibility. Nineteen older onboarding records had a more recent first visible eligible epoch; counting onboarding alone would have overstated what the visible eligibility history proves.
Historical coverage can be incomplete, particularly after identity changes. A recent first observation does not prove a validator is new to the program, and “neither condition observed” is not a guarantee of continued eligibility. Most individual histories were current through epoch 1078; four were older and one lacked usable mainnet data. This analysis does not resolve renewals, exceptions, or the Foundation’s final decisions.
Model the delegation you could actually lose
Do not model retirement as an automatic loss of only 5,000 SOL plus a matching allocation. The FAQ describes a residual component that starts at 5,000 SOL but is calculated dynamically from the remaining delegation pool. Actual Foundation stake can be much larger.
The FAQ also describes 50% matching, capped at 50,000 SOL, as applying from epoch 893. That is an existing matching rule, not a new November 6 reduction. For a retirement scenario, start with the Foundation stake currently delegated to your validator and model the amount you would actually lose.
The operating effect reaches beyond staking commission. Less active stake generally means a smaller steady-state share of leader slots and associated block rewards. Hardware, bandwidth, monitoring, and other recurring costs may remain largely unchanged. An operator can continue validating after SFDP retirement, but the margin needs to work without assuming indefinite Foundation support.
Use the calculator to plan your next move
We built the ProStaking Validator Calculator to make those trade-offs easier to inspect. Select your validator to load its observed stake and commission, then change the scenario inputs without changing anything on-chain.
- Establish your baseline. Select your validator, review its client and commission settings, and enter your actual monthly hardware and operating costs.
- Model support ending. Subtract your current SFDP delegation from active stake. The calculator does not make an SFDP eligibility decision for you; verify the delegation amount separately.
- Test replacement stake and commission. Adjust active stake, inflation commission, and Jito-tip commission to see how each changes the projected operating result. Keep the distinction between commission streams clear.
- Stress-test the assumptions. Review the manual inputs, client scenario, and results in SOL and USD. Check how much room remains under less favorable reward or cost assumptions.
The model separates staking commission, credited block fees, projected operator Jito-tip share, validator admission ticket costs, and hardware and operating costs. Stake overrides represent a steady-state share of the unchanged network total, not an immediate change to the leader schedule.
Its block-reward baseline is a recent one-hour census of selected operators, not a network-wide census or a promise of future rewards. Client comparisons are not causal. Projected Jito-tip accrual is also different from cash available to spend: settlement happens later, and arrival in the next epoch is not guaranteed. Annual figures are a twelve-month run rate, not a compounded forecast.
SFDP retirement creates an operating-planning problem for each validator. Know your program tenure, know how much Foundation stake you rely on, and work out what replaces the revenue. Run your validator through the calculator before making the next hardware, commission, or growth decision.
Data snapshot: November 7, 2026, 15:36–15:46 UTC. This article is an operational analysis of public program information, not an official eligibility determination or financial advice.
