A token needs a reason to exist that survives someone asking twice. Here is the reasoning, including the parts that are still unresolved.
Identifying a plant, recording watering, setting a reminder, browsing your garden — none of these will ever require CGW, a wallet, or a transaction. The product has to work for someone with no interest in crypto whatsoever, and that is a hard constraint rather than an aspiration.
Putting routine plant care on-chain would add cost and latency to something that works fine without it. On-chain actions are reserved for things that genuinely need shared, verifiable state — claiming a reward, voting, disbursing a grant.
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.
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.
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.
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.
A future marketplace for flower photography, seeds and garden goods may accept CGW alongside ordinary payment methods.
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.
A dedicated portion of the supply funds real environmental projects, with the community helping choose which ones and evidence required before money moves.
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.
Over time, CGW holders get a say in ecosystem decisions — which environmental causes get funded, how grants are allocated, which community initiatives get support.
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.
Helium and Render both solve the same problem: a service should have a predictable price even when the token used to reach it does not. Both do it with a non-transferable credit that is produced by consuming the token. Applied to CoinGarden, that would mean CGW converting into Garden Credits that pay for premium analysis or marketplace services.
Helium tried a second tradable token and reversed the decision, citing user confusion and value leakage. And both precedents route the customer’s money through a token purchase, which directly conflicts with CGW’s constraint that a non-crypto user is never forced into one. If a credit layer is ever built, the current recommendation is a non-transferable balance purchasable by card — not a second token.