GIWAForgeProject Lifecycle
GIWAForge proposes lifecycle states that make a project's trading and exit conditions visible. A state label describes the relevant phase; it is not a certification of project quality, solvency or future returns.
The six states
| State | Intended behavior |
|---|---|
| New | A project has just been created and appears among launches |
| Active | Internal trading operates under the final pool rules |
| Near graduation | Defined graduation metrics are approaching their targets |
| Graduated | The finalized graduation conditions have been satisfied |
| Burn window | Internal trading is paused; eligible holders can choose voluntary redemption |
| External pool | Community activity may continue in a separately created external market |
The demo includes examples of these states. No chain transaction or timer moves these examples between states. External pool activity is an optional community path, not a compulsory next step after redemption.
Graduation
The proposal allows graduation criteria to consider market cap, liquidity, volume, holder count and a minimum observation period. The exact thresholds, combination of criteria and valuation sources are not finalized.
A progress indicator is illustrative. It does not mean a project has satisfied deployed conditions. Graduation does not currently execute a pool migration, list a token on a DEX or guarantee additional liquidity. Those actions require an explicit contract and integration specification.
Low-value trading pause
The proposed mechanism can pause internal trading after a project remains below an agreed valuation threshold for a defined duration. Low pool liquidity and any protected or disputed period may also affect eligibility.
The project brief mentions 6 or 24 hours as possible observation periods. Neither is a live rule. Thresholds, measurement windows, price sources, manipulation resistance, who can trigger a transition and any challenge process remain pending.
Entering a burn window
The intended transition stops internal trading and opens a voluntary claim period for eligible holders. Before deployment, the design must specify the remaining assets, eligible supply, relevant snapshot or accounting basis, and how each claim changes the remaining allocation.
Window duration, expiry behavior, unclaimed assets, and the ability to resume internal trading are all unresolved. The demo does not assert a live deadline or automatic forfeiture of a user's tokens.
Community continuation
Holders who do not burn may keep their tokens and seek external liquidity. A later return to GIWAForge's listings is a possible future feature, not an implemented entitlement. Any relisting conditions and review process must be published separately.
Read Burn & Claim for the allocation example and External Pools for the limits of external continuation.