Token lifecycle & time
The explicit lifecycle states a token moves through, and the six independent ages the system tracks.
Every token moves through an explicit lifecycle. Not every token passes through every state, and each state change creates an immutable event.
Lifecycle states
DISCOVERED → CONTRACT_DEPLOYED → WAITING_FOR_LIQUIDITY → EARLY_TRADABLE → LAUNCHPAD_ACTIVE → MIGRATING → DEX_ACTIVE → CEX_ANNOUNCED → CEX_ACTIVE → ESTABLISHED → INACTIVE → FAILED → RUGGED
Six independent ages
Clawlas never relies on a single generic “token age.” It stores several timestamps and computes these ages dynamically at every evaluation:
| Age | Definition |
|---|---|
| Contract age | now − deployed_at |
| Launch age | now − launch_started_at |
| Liquidity age | now − first_liquidity_at |
| Tradable age | now − first_trade_at |
| Pool age | now − pool_created_at |
| Listing age | now − cex_trading_started_at |
Ages are computed, never stored
Token ages are derived at evaluation time, not persisted as fields that drift. The timestamps are the source of truth — see the token_launches table in the early-token schema.