Skip to article
Stayers S leaf logostayers.funDOCSTrading terminal
STAYERS DOCS

Getting Started

IntroductionWhy Stayers ExistsHow Stayers WorksConnect Your Wallet

Launching Tokens

Create a TokenToken Supply & MetadataBonding CurvesBuying & SellingGraduation

The Stayers Economy

Economic OverviewTrading FeesCreator RevenuePlatform RevenueSurvival AllocationsPost-Graduation Economics

Survival Mechanics

Survival StagesStay VaultsLiquidity MilestonesSecond WindStay ScoreFailed Tokens

Why Stayers?

Stayers vs Traditional LaunchpadsCreator IncentivesTrader BenefitsOur Philosophy

Transparency & Security

TransparencyProtocol AddressesFee RecipientsLiquidity OwnershipSmart Contract SecurityRisks & Limitations

Developers

Technical ArchitectureMeteora IntegrationAPI Reference
Built for the long gameAnyone can launch.
Not everyone can stay.
Docs/Survival Mechanics
ImplementedUpdated Oct 27, 2026

Stay Score

The exact implemented market-health methodology and its limits.

Code exists; Stayers production behavior is not yet verified.

Stay Score is an informational 0–100 indicator. The evaluator is implemented, but its experimental rules and real mainnet behavior are not approved or verified for production qualification.

Four components

ComponentMaximum pointsImplemented calculation
Liquidity health35Up to 20 for active SOL liquidity relative to 20 SOL; up to 15 for 24-hour liquidity retention
Trading continuity30Active complete daily windows divided by covered days, up to the lesser of age and 90 days
Holder distribution20Up to 10 for qualifying holders relative to 150; up to 10 for reduced largest non-exempt holder concentration
Market resilience15Up to 10 for lower active-liquidity drawdown; up to 5 for retention

Each subterm is independently floored to integer points and clamped to its range. The implementation does not reward market-cap appreciation.

The current version is experimental-health-v1-2026-10-27. For complete, verified observations, the exact component formulas are:

text
P(basisPoints, weight) = floor(weight × clamp(basisPoints, 0, 10000) / 10000)
Liquidity = floor(20 × min(activeLiquidityLamports, 20000000000) / 20000000000)
            + P(retentionBps, 15)
Continuity = P(activeDayCoverageBps, 30)
Holders = floor(10 × min(qualifyingHolders, 150) / 150)
          + P(10000 - largestNonExemptHolderBps, 10)
Resilience = P(10000 - reserveDrawdownBps, 10) + P(retentionBps, 5)
Stay Score = Liquidity + Continuity + Holders + Resilience

These normalizations describe existing experimental code, not approved financial reward thresholds. Changes require a new evaluation-policy version and a corresponding documentation review.

Liquidity and history

Active liquidity uses verified pool reserves: SOL quote reserve plus token-side spot value capped at the quote reserve. Unsolicited vault deposits are not automatically treated as active reserves.

Retention compares current liquidity with the window's starting value, capped at 100%. Resilience measures peak-to-trough active-liquidity drawdown. The same active pool needs sufficient reserve observations across approximately a day; migration restarts that pool-specific coverage.

The current collector requires at least 230 prior observations within the trailing 24 hours, with the earliest at least 23 hours old. Observations older than 600 seconds at evaluation, or dated in the future, fail freshness checks. Continuity uses complete covered UTC daily windows, up to 90 days; fewer than one complete day produces insufficient continuity data.

Holders and continuity

Balances aggregate by owner. Known pool vaults, burn/exempt addresses and program-controlled accounts are excluded where supported. A qualifying holder currently needs at least one whole token. The resulting count is not a count of humans.

An experimental 0.01 SOL quote-turnover floor defines active day/window observations. This is a discovery measurement, not an approved financial reward threshold.

Missing data and integrity

Incomplete backfills, missing holders, unreliable attribution, stale observations or missing reserve history return INSUFFICIENT_DATA with a null score. Missing data never receives full points.

Age and graduation affect separate qualification checks; they are not direct bonus points. There is no separate creator-commitment bonus in this four-component algorithm. A high score never establishes that a token is safe.

PreviousSecond WindNext Failed Tokens
STAYERS.FUN · Build longerCheck the evidence ↗

ON THIS PAGE

Four componentsLiquidity and historyHolders and continuityMissing data and integrityBack to top ↑
On this pageFour componentsLiquidity and historyHolders and continuityMissing data and integrity