EvidenceResearch
Six Solana token designs studied from first-party sources, plus the EU regulatory position. The point was to design CGW correctly, not to imitate anyone.
Every study asks four questions: what works and why, what CGW can learn, what is inappropriate for CGW, and what CGW must explicitly not copy. The fourth is the one that changed the design most.
Studies
Token designs studied
JUP · Jupiter
A launch with no investors, no private sales and on-chain-enforced team vesting. Also the clearest evidence that a project must host its own supply data: aggregators still reported a maximum supply the DAO had voted to reduce years earlier.
docs/token/research/JUP.md
JTO · Jito
A retrospective airdrop with a closed claim window and a permissionless sweep back to the DAO. Also the source of the hard-coded-governance-threshold mistake CGW explicitly avoids.
docs/token/research/JTO.md
PYTH · Pyth Network
The closest structural analogue: paying contributors for accurate real-world data. A named contributor allocation and coverage-weighted rewards are both directly transferable. The staking-and-slashing mechanism is not.
docs/token/research/PYTH.md
RENDER · Render Network
Burn-and-mint equilibrium: how a service keeps a predictable price while the token used to reach it does not. Studied for the Garden Credits question.
docs/token/research/RENDER.md
HNT · Helium
Data Credits, and six years of hard-won evidence on rewarding verifiable real-world contribution — including a second token that was introduced and then reversed, and a coverage mechanism ultimately retired.
docs/token/research/HNT.md
BONK
Studied as a contrast case. Distribution breadth produced real ecosystem integration; the absence of a utility-first design is what CGW must not imitate.
docs/token/research/BONK.md
Findings
Three findings that changed the design
Pay more for scarce contributions
Pyth expands reward capacity for feeds few publishers cover. Applied to CoinGarden, the thousandth photo of a common houseplant is worth far less than the first record of a regional cultivar — and the emission model should say so.
Do not stake-and-slash ordinary users
Pyth’s accountability comes from requiring capital and confiscating it for bad data. Applied to a gardener who misidentified a plant, that is both absurd and fatal to the requirement that the app stay useful without crypto. CGW uses reputation weighting and reward ineligibility instead — never confiscation.
Pay for measured outcomes, not claims
After roughly fifteen governance proposals, Helium’s conclusion was to stop paying for the assertion and pay only for the validated result. CGW rewards accepted, deduplicated contributions that survive review — never the act of submitting one.
Synthesis
Analysis and recommendations
Comparative analysis
docs/token/research/COMPARATIVE_ANALYSIS.md
CGW recommendations
docs/token/research/CGW_RECOMMENDATIONS.md
MiCA requirements
docs/token/CGW_MICA_REQUIREMENTS.md
Garden Credits research
docs/token/GARDEN_CREDITS_RESEARCH.md
These documents live in the repository rather than only on this site, so they are versioned, reviewable and diffable alongside the code that implements them.