stayers.funLiquidity Milestones
Fixed snapshots, separate cohorts and conditional execution budgets.
Code exists; Stayers production behavior is not yet verified.
The accounting layer supports fixed allocation snapshots and deterministic milestone portions. This is distinct from a working automatic liquidity service.
Snapshot boundaries
At an eligible financial evaluation, a cohort can capture the available unassigned survival receipts. Its balance is fixed. The same receipts cannot be included in another cohort.
Initial timing is anchored to launch; later accrual cohorts have their own recorded anchor. Newly collected fees are not retroactively counted in a previously fixed snapshot.
| Stage | Minimum age | Conditional snapshot portion |
|---|---|---|
| Genesis | Launch | None |
| Rooted | 24 hours | 10% |
| Established | 7 days | 25% |
| Survivor | 30 days | 35% |
| Legacy | 90 days | 30% |
Before a deployment
The token must satisfy the relevant checks and have a verified DAMM pool. Funds must be sufficient and properly reconciled. An execution plan also needs approved cost, size, slippage, price-impact and rate limits, plus a supported lock.
The complete execution flow remains planned and financial deployment is disabled.
Reservations and incomplete results
The ledger can represent a reserved attempt separately from confirmed deployed liquidity. Ambiguous submitted attempts must be investigated rather than automatically released for another spend.
If an approved transaction eventually uses less than its reservation, only actual confirmed spending should move to deployed accounting; the unspent portion remains pending.
What a milestone promises
A milestone provides a conditional checkpoint. It does not promise that trading fees will accumulate, that funds will be deployed at a specific time, or that a liquidity contribution will improve price.