stayers.funRisks & Limitations
A clear boundary between implementation, evidence and financial safety.
Code exists; Stayers production behavior is not yet verified.
Tokens can lose most or all of their market value. The Stayers design does not remove volatility, concentrated ownership, manipulation, sniping or the possibility that liquidity becomes inadequate.
Current feature coverage
| Feature | Status | What exists |
|---|---|---|
| Reusable Stayers mainnet configuration | Live | Finalized CreateConfig2 receipt and full configuration policy verified. Token launches and fee execution remain separately unverified. Verified transaction ↗ |
| Wallet connection and DBC launch preparation | Implemented | Explicit wallet approval, cost simulation and confirmation paths; submission remains gated. |
| DBC buying and selling | Implemented | SDK quotes and swaps exist. Real Stayers executions remain unverified. |
| Fee-claim construction and verification | Implemented | Core SDK builders and receipt verification exist; public/admin claim signing is not exposed as a completed flow. |
| Per-token financial accounting | Implemented | PostgreSQL ledger, asset denominations, reconciliation and exact rounding are fixture-tested. |
| Indexer and survival evaluation | Implemented | Historical replay, finalized trades, candles and experimental qualification exist. Target N95/live operation remains unverified. |
| Second Wind discovery | Implemented | Milestone and comeback event logic exists. Production promotion is disabled. |
| Complete Stay Vault liquidity execution | Planned | SDK construction audits and accounting gates exist; acquisition, approved execution and lock verification are not an end-to-end service. |
| Website trading after DAMM graduation | Unavailable | The current website swap path rejects migrated DBC pools. DAMM trade indexing is a separate implemented capability. |
| Exact native 31.25% DBC creator share | Unavailable | The installed encoding uses whole percentages. V1 uses a zero-direct-creator collection route and ledger entitlements. |
| $STAYER token, buybacks and burns | Planned | Future concept only. No active mechanism or promised allocation. |
Shared custody and incomplete execution
V1 survival and creator allocations are ledger classifications within operator-managed shared custody. They are not independently protected vault assets.
The complete Stay Vault acquisition/deposit/locking flow remains planned. Public claim/payout controls and website trading after DAMM graduation are not completed end-to-end features.
Data quality and inference
RPC outages, missing history, delayed indexing, failed holder scans and capacity limits can leave analytics stale or unavailable. The system should expose those gaps rather than substitute invented values.
Stay Score is informational. Second Wind heuristics cannot conclusively identify organic demand or detect every form of wash trading. Neither is a safety rating.
Evidence and approvals
Available automated tests use fixtures and offline SDK construction. Docker operation on the target N95, the live tunnel and real Stayers mainnet activity still require verification.
No feature is labeled Live here solely because it compiles, has a UI, uses a known protocol or passes a simulation. Check Transparency for actual observed data and its timestamp.