Stay Vaults

Stay Vaults are token-specific allocations intended to fund additional liquidity as a token survives.

The per-token accounting and eligibility gates are implemented. The complete acquisition, liquidity-deposit, approval and verified-lock execution service remains planned.

The intended processCopy section link

1. Eligible trades generate fees.
2. Verified collected proceeds create a token-specific survival allocation.
3. The token qualifies for a survival milestone.
4. A real DAMM v2 graduation is verified.
5. A reviewed portion of an eligible snapshot can be considered for deployment.
6. Required token inventory is acquired under approved execution limits.
7. Paired assets enter a supported liquidity position.
8. A supported lock is applied and its actual restrictions are verified.
9. Transaction signatures, position identity and accounting effects are recorded.

No step is permission to skip the next check. The current worker cannot execute this sequence or move assets.

A 20 SOL snapshot exampleCopy section link

If a hypothetical token has an eligible 20 SOL snapshot, the first three proposed milestone portions total 70% by the 30-day checkpoint: 2 SOL, then 5 SOL, then 7 SOL. That is up to 14 SOL of conditional budget, with 6 SOL remaining for Legacy.

What the example does not establishCopy section link

The example does not estimate acquisition slippage, asset proportions, network/rent costs or actual liquidity units. A real deployment would need its own simulation and approved limits.

There is no real position address or transaction signature in this example. Principal must not be described as permanently locked until the actual supported mechanism and resulting position are verified.

Custody and purposeCopy section link

V1 allocations are held through operator-managed shared custody and separate ledger classifications. The purpose is potential market-depth improvement, not guaranteed price growth, a price floor or protection from loss.