SequenceRoadmap
Nine stages, and the project is at the third. The stages after security exist to make it difficult to skip them.
Current position: Stage 3. Specification is approved for V1 implementation and the whitepaper is published. Solana program source (cgw-vesting, cgw-rewards) and the wallet-identity backend are written but not yet compiled or tested against a real toolchain. No code has been deployed to any Solana cluster and no audit has begun. Stage 8 is not authorised.
Stages
From research to a possible launch
Research
Complete
- Ecosystem research across six Solana token designs
- Definition of the token's economic purpose
- EU regulatory requirements research
Stage 1
APPROVED FOR IMPLEMENTATIONSpecification
Substantially complete
- Machine-readable token specification as the single source of truth
- V1 tokenomics decided and approved for implementation
- Interactive economic simulator
- Treasury, vesting and rewards architecture
Stage 2
APPROVED FOR IMPLEMENTATIONWhitepaper
Draft published
- Technical and product design paper
- Economic model
- Risk factors
- Regulatory mapping
Local Solana development
In progress — source written, not yet compiled or tested
- Local validator mint
- cgw-vesting implementation (source complete)
- cgw-rewards implementation (started)
- Adversarial test suite against every documented invariant
Devnet
Not started
- Devnet mint
- Vesting and rewards on devnet
- Treasury multisig rehearsal
- Public testing with real users
Security
Not started
- Internal review
- Fuzz and property testing
- External audit by an independent firm
- Remediation and re-review
- Full publication of findings
Governance preparation
Not started
- Multisig established with real signers
- Authority transition plan executed and verified
- Transparency dashboard showing live on-chain data
Mainnet readiness
Not started
- Final legal review by qualified counsel
- Final tokenomics approval
- Deployment runbook rehearsed on devnet
- Genesis ceremony documented and witnessed
CGW launch
Requires explicit approval — not authorised
- Only after every preceding stage is complete
- Only after explicit sign-off
- This stage has not been authorised and will not proceed by default
Gates
What has to be true before each jump
Before devnet
- Both programs implemented and passing an adversarial local-validator suite
- Tokenomics approved rather than merely modelled
- Anti-Sybil design reviewed against the Helium precedent
- Rewards epoch and Merkle publication pipeline working end to end
Before mainnet
- External audit completed, remediated and published in full
- Legal review by qualified counsel, with the MiCA questions resolved
- Treasury multisig live with real, independent signers
- Genesis ceremony rehearsed on devnet and documented step by step
- Explicit written approval to proceed