CGW Whitepaper#

CoinGarden.World helps people identify plants, keep a record of their gardens and care for what they grow. World of Flowers brings identification, observations, care history and reminders into one application. Users review and can correct identification suggestions before relying on them.

CGW is the ecosystem's optional Solana token. Its infrastructure supports governed distribution, contribution rewards and scheduled releases. Plant care does not require a wallet, a token balance or a blockchain transaction.

A deployed token does not make every potential token service available. Marketplace purchases, token voting and environmental-project delivery are separate from the mint and release programs. Published reward allocations and the current application determine what a user can actually do.

The original supply was minted at genesis. SPL Token burns permanently reduce current supply; the original issuance is not a current balance. Mint authority was then permanently revoked, so this mint cannot issue additional CGW. Freeze authority is absent: CGW has no issuer-controlled account-freezing mechanism. Transfers use Solana's standard token program rather than custom CGW transfer logic.

The mint address identifies the asset. A matching name, symbol or icon does not. Verify the address on Transparency before adding CGW to a wallet or interacting with a token account.

The original genesis supply was divided into distinct allocations, each with a dedicated vault and release policy. The figures below describe the allocation at genesis, not current balances or an individual user's entitlement.

Unlocked does not mean distributed. An allocation can be available under its release policy while still held in a project-controlled account. Likewise, the existence of a liquidity allocation does not establish an exchange, trading pair or purchase service.

Distribution separates allocation figures from current release accounting. Transparency reports observed balances and the method used to calculate circulating supply.

The published CGW deployment configuration records a Squads multisig with an expected 3-of-5 signature threshold. This reference is not a live membership check. The multisig controls program upgrades and token metadata, and directly owns the Liquidity and Community vaults. Team, Treasury and Environmental vaults are controlled by the vesting program. The Ecosystem Rewards vault is controlled by the rewards program.

Treasury and Environmental lock schedules are established on-chain. As amounts vest, the multisig can claim them into the corresponding operational accounts. These accounts separate released funds from the locked balances. Spending a released balance is a separate multisig action.

The Team allocation follows the release policy in the allocation table. Each beneficiary needs an individual on-chain schedule. A published allocation or schedule model does not itself create a claim for a person.

The current vesting program has no instruction to accelerate or cancel a schedule. Its program upgrade authority remains with the multisig, however: an authorized upgrade can change program behavior. Current program enforcement must not be confused with permanent immutability.

Rewards distribute existing CGW from the Ecosystem Rewards vault. A published epoch records a Merkle root, budget and claim window. An eligible wallet proves that its allocation belongs to that root when it submits a claim. The program verifies the proof and prevents the same allocation from being claimed again.

The reward specification uses a weekly UTC cadence and a 90-day claim window. The published epoch's actual opening and deadline govern whether a claim can be made. The per-claimant cap is 1% of the epoch budget.

Connecting a wallet, submitting a plant observation or recording care does not automatically earn CGW. Eligibility depends on an accepted contribution and a published allocation for that wallet. Rewards shows the epochs currently published; Claim checks the connected account's available claims.

The rewards program also supports a separately approved burn of unallocated inventory through SPL Token BurnChecked. A burn permanently reduces the rewards reserve and mint supply; historical published budgets remain reserved under the program’s conservative accounting limit.

Unclaimed allocations remain in the Ecosystem Rewards vault when an epoch closes. They do not automatically become a new allocation, a team payment or a burn. Current published totals and claim outcomes are reported separately from the long-term emission model.

Use a Solana wallet that supports the site's connection and signing methods. Connect the wallet you intend to use, verify its address and review each request in the wallet. Linking a wallet to an account proves control of that address; it does not transfer ownership of the wallet to CoinGarden.

A sign-in message proves wallet ownership without transferring tokens. A claim or token-account action is a transaction and can require SOL for network fees and account rent. Inspect the transaction before approving it. CoinGarden never needs your seed phrase or private key.

On a phone, a wallet's built-in browser can provide the connection and signing interface. Returning from a wallet does not by itself prove a transaction succeeded: wait for the recorded result and check the transaction link. If a request fails or is cancelled, inspect the current state before retrying.

The mint, program addresses, vaults and multisig are published on Transparency. Internal review, reproducible build records and independent on-chain checks form the engineering evidence for the deployment. No independent external security audit has been completed.

Custom CGW programs govern release and eligibility; ordinary token transfers remain within the standard Solana token program. Account-ownership checks, configured-vault checks and deterministic claim records constrain which assets a program can move and which claims it will accept.

The multisig is still an authority. Its signature threshold protects against a single compromised key but does not establish that the people controlling those keys are independent. Program upgrades and metadata changes remain possible through that authority. Review the current authorities and program information before relying on an earlier copy of this document.

Program and custody risk. Tests and verification reduce uncertainty but cannot establish that software is free of defects. An error in a program, a compromised signing device or an authorized malicious upgrade could affect assets or releases. A multisig threshold does not prevent collusion or common control of multiple keys. No external audit opinion is available.

Wallet and transaction risk. A malicious website, incorrect mint address or misleading wallet request can cause a user to authorize the wrong action. Blockchain transactions may be irreversible. Keep recovery material private, verify destinations and use the transaction details shown by the wallet rather than an icon or token name alone.

Eligibility and product risk. A token balance does not guarantee access to a marketplace, voting system or future service. Contribution review can reject a submission, and an eligible allocation can expire unclaimed. The allocation table is not a promise of a payment to any particular user.

Network and information risk. Solana congestion, RPC outages or stale data can delay a transaction or prevent the portal from showing a current balance. An unavailable reading is not a zero balance. Treat explorer confirmations and the current on-chain account state as separate from a cached page or model.

Legal risk. CGW has not received qualified legal review and its regulatory classification remains undetermined. This published technical reference is not a crypto-asset white paper within the meaning of Article 6 of Regulation (EU) 2023/1114. It is not an offer to buy or sell CGW and does not certify regulatory compliance. No price, future value or financial return is promised.

Transparency is the reference for the canonical mint, program and vault addresses, current authorities and observed token state. It distinguishes original genesis issuance from current on-chain supply and project-controlled balances. The amount outside tracked project accounts is an accounting measure, not independently verified circulating supply. Release eligibility is not the same as a completed transfer into circulation.

Distribution reports allocation and vesting accounting. Rewards reports published reward epochs. Where data is unavailable or a reader has limited coverage, those limits must remain visible rather than being replaced with an estimate.

The figures in this whitepaper come from the same token specification and deployment manifest used by the portal. Live balances, claim totals, individual schedules and transaction history can change after publication and should be checked on their corresponding pages.

• CoinGarden.World — project website
• World of Flowers — plant-care application
• CGW Token Portal
• Canonical mint and on-chain transparency
• Allocation and release accounting
• Published reward epochs
• Wallet connection and claims

Use these official destinations to find current information. Neither CoinGarden nor a support contact needs your seed phrase or private key to verify a wallet, investigate a failed request or explain a claim.