CoinGarden.World · Solana

CGW

The utility layer of CoinGarden.World. Built on Solana.

Connecting plants, gardens, contributors, digital ecosystems and environmental impact — as an optional layer on top of a plant-care product that works perfectly well without it.

CGW statusV1 approved for implementation — not yet deployed on any Solana cluster

There is no CGW token on any Solana cluster. There is no price, no market, no contract address and no sale. What exists is a specification, an economic model and this documentation.

See what is actually deployed
At a glance

CGW at a glance

NetworkSolanaDevnet before mainnet. Nothing deployed yet.
TokenCGWCoinGarden. Replaces the legacy GRDN name.
StandardSPL TokenNo custom transfer logic of any kind.
StatusApproved for V1Decided for implementation. Not deployed on any cluster yet.
Maximum supply1BFixed maximum, approved for V1 — not yet minted anywhere.
Decimals9Approved for V1. Solana and Anchor default.
The economic question

Why CGW exists

CoinGarden.World has a real problem that a token can genuinely help with, and a great many problems that a token would only make worse. CGW is scoped narrowly to the first kind.

The problem

Reliable plant knowledge is expensive to produce and easy to get wrong. Identifying a plant correctly, recording how it actually responded to care, documenting a species or a regional cultivar nobody has covered — that work has real value to everyone who uses the app afterwards, and no ordinary mechanism rewards the person who did it.

The narrow answer

CGW exists to pay for verified contributions to that shared knowledge base, to fund the environmental work the project commits to, and eventually to let the people who built the commons have a say in how it is governed. That is the whole remit.

What CGW deliberately is not

Not a payment rail for ordinary plant care. Not a requirement for using the app. Not a gate on any core feature. Not a yield product. Watering a plant will never cost a transaction fee.

The hard constraint

CoinGarden must remain completely useful to someone who has never heard of Solana and never intends to open a wallet. If CGW ever makes the product worse for that person, the token is wrong, not the person.

Ecosystem

How CGW fits into CoinGarden.World

  1. CoinGardenThe plant-care product. Free, useful, and entirely usable without crypto.
  2. Plants and gardensReal flowers, identified, recorded and cared for over time.
  3. ContributorsPeople who correct identifications and add reliable care knowledge.
  4. Verified contributionReviewed off-chain against the existing moderation pipeline.
  5. CGW rewardsReleased from the ecosystem rewards vault against a published epoch.
  6. Ecosystem utilityOptional premium services, marketplace participation, governance.
  7. Environmental impactA dedicated vault funding verified environmental work.
Utility

What CGW is for

Every area below carries its own status. Most of it does not exist yet, and the page says so rather than implying otherwise.

Verified contribution rewards

PROPOSED

If you help improve the shared plant knowledge base — correcting a misidentified plant, adding reliable care information, documenting a species nobody has covered — that work can be recognised with CGW.

How it actually works

Contributions are validated off-chain against the existing identification and moderation pipeline. Accepted contributions accumulate into an epoch, which is published as a Merkle root. Claiming is an on-chain action against a deterministic PDA drawing from the ecosystem rewards vault. Rewards are weighted by contribution scarcity, so under-covered species and regions pay more than the thousandth photo of a common houseplant.

Ecosystem service access

PROPOSED

CGW can be used to pay for optional extras — deeper plant analysis, specialist reports, marketplace features. Ordinary plant care never costs anything and never requires a wallet.

How it actually works

Service consumption is deliberately not a per-action on-chain transaction. Whether consumption settles directly in CGW or through a non-transferable service-credit balance is an open design question tracked as Garden Credits research.

Marketplace participation

RESEARCH

A future marketplace for flower photography, seeds and garden goods may accept CGW alongside ordinary payment methods.

How it actually works

No marketplace exists. Whether CGW is a settlement asset, a fee-discount mechanism, or simply irrelevant to the marketplace is undecided and depends on the marketplace pilot's outcome.

Environmental impact funding

PROPOSED

A dedicated portion of the supply funds real environmental projects, with the community helping choose which ones and evidence required before money moves.

How it actually works

Grants are disbursed from the Environmental Impact Vault against verified milestone evidence, not paid out on announcement. CGW makes no claim that holding or buying the token has any environmental effect in itself.

Progressive governance

PLANNED

Over time, CGW holders get a say in ecosystem decisions — which environmental causes get funded, how grants are allocated, which community initiatives get support.

How it actually works

Governance is introduced progressively and starts from a deliberately narrow scope. Security-critical parameters, program upgrade authority and user-data policy are explicitly outside governance control. Voting thresholds must be expressed as percentages computed from on-chain supply, never as hard-coded constants.

Tokenomics

Approved V1 allocation

Decided for V1, not yet deployed. The six-way split below is the approved allocation this repository’s code is being built to match exactly — it is not a draft. What has not happened yet is deployment: no vault, mint or program exists on any Solana cluster. The alternative scenarios on the tokenomics page are a modelling tool for stress-testing this approved split, not evidence that the split itself is undecided.
Approved V1 CGW allocationEcosystem & contributor rewards 45%, Ecosystem treasury, development & grants 20%, Core team 15%, Liquidity & ecosystem integrations 10%, Environmental impact initiatives 5%, Early community & launch distribution 5%1,000,000,000CGW · NOT DEPLOYED
  • Ecosystem & contributor rewards45% (450M)
  • Ecosystem treasury, development & grants20% (200M)
  • Core team15% (150M)
  • Liquidity & ecosystem integrations10% (100M)
  • Environmental impact initiatives5% (50M)
  • Early community & launch distribution5% (50M)
Approved V1 CGW allocation by percentage and token count
AllocationShareCGWStatus
Ecosystem & contributor rewards45%450,000,000APPROVED FOR IMPLEMENTATION
Ecosystem treasury, development & grants20%200,000,000APPROVED FOR IMPLEMENTATION
Core team15%150,000,000APPROVED FOR IMPLEMENTATION
Liquidity & ecosystem integrations10%100,000,000APPROVED FOR IMPLEMENTATION
Environmental impact initiatives5%50,000,000APPROVED FOR IMPLEMENTATION
Early community & launch distribution5%50,000,000APPROVED FOR IMPLEMENTATION

Percentages sum to exactly 100. That invariant is enforced by a unit test, not by proofreading.

Supply timeline

How supply would become available

Circulating supply here excludes tokens that have been released by a schedule but are still sitting in a project-controlled vault. Counting those as circulating is the most common way a supply chart flatters the project publishing it.

Approved V1 CGW supply over ten yearsStacked bands over 120 months. Circulating supply begins at 15% of maximum supply at the token generation event and reaches 75% by year ten, with the remainder held in treasury-controlled vaults. Locked supply falls to zero by month 120.0250M500M750M1BTGEY1Y2Y3Y4Y5Y6Y7Y8Y9Y10CGW
  • Circulating
  • Treasury-controlled (released, not circulating)
  • Locked

Approved V1 schedule, modelled from the token specification — not observed from any chain.

Circulating, treasury-controlled and locked supply at milestone months
MilestoneCirculating CGWCirculatingReleasedTreasury-controlledLocked
TGE150,000,00015%15%0%85%
Year 1 end244,786,41824.47%30.47%6%69.52%
Year 2 end336,422,08833.64%45.64%12%54.35%
Year 3 end425,080,29542.5%60.5%18%39.49%
Year 4 end510,924,80051.09%75.09%24%24.9%
Year 5 end556,610,35555.66%80.66%25%19.33%
Year 10 end750,000,00075%100%25%0%
Open the simulatorDistribution detail
Trust

What is actually true today

Nothing is deployed

NOT DEPLOYED

No mint exists on mainnet-beta or devnet. No program has been deployed. No treasury multisig has been created. The transparency page lists every one of these as not deployed and will show real addresses only when real addresses exist.

No audit has happened

PLANNED

An external audit is a prerequisite for mainnet, not a formality afterwards. It has not started, because there is not yet a program stable enough to audit.

The regulatory position is open

RESEARCH

EU analysis under MiCA is documented and unresolved on several points that could materially change or prevent the design. Those questions are listed openly rather than assumed away.

Security modelRead the researchRoadmap to mainnet