Token Documentation
A public overview of CHVToken covering token purpose, on-chain allocation buckets, crowdsale mechanics, contract architecture, and the document hierarchy that governs the sale.
What this page is meant to clarify
CHV is positioned throughout the repo as the utility token for the ChessVerse ecosystem. This page summarizes the contract-backed token structure and the public-sale mechanics without overstating marketing drafts that no longer match the current on-chain implementation.
Utility-first positioning
Public materials describe CHV as the token used across competitive play, rewards, governance signaling, digital items, premium access, and ecosystem campaigns.
The legal pages are explicit that CHV is not equity, not a fund product, and not a guarantee of profit, liquidity, or future listing.
Code-backed summary
The current Solidity implementation centers on a fixed-supply ERC-20 token, a configurable crowdsale contract, a treasury multisig, a team vesting vault, and a long-range operational rewards vault.
Where older marketing drafts describe broader sub-buckets, the token contract itself is the safer public reference for top-level supply allocation.
Core ways CHV is described across the project
Competitive play
CHV is designed for tournament participation, match-based utility, and ecosystem access inside ChessVerse.
Rewards and campaigns
Operational rewards can be distributed through controlled release programs rather than unlimited token emission.
Governance signaling
Public materials position CHV as a governance and community coordination token inside the broader product ecosystem.
Marketplace and premium features
Documentation describes CHV as a payment layer for digital items, premium experiences, and ecosystem services.
Current top-level supply buckets from the token contract
The CHV token contract exposes four allocation buckets totaling the full 1,000,000,000 CHV maximum supply. These are the safest public numbers to present for the current codebase.
Public Distribution
30%Crowdsale and public distribution inventory tracked by the token contract.
Platform Reward Reserve
50%Managed through the operational rewards vault with year-by-year release controls.
Treasury & Strategic Reserve
15%Held for treasury management, strategic operations, and reserve planning.
Core Team
5%Dedicated team allocation with a separate vesting vault and timed unlock rules.
Phase-based sale framework
The crowdsale contract supports three named phases under a 300,000,000 CHV public-distribution bucket. Exact live pricing, timing, payment-token support, and wallet caps should be taken from the live sale interface and active contract configuration rather than fixed marketing tables.
Private Sale
Early allocation phase that can be configured with whitelist requirements, phase-specific pricing, wallet caps, and a dedicated allocation ceiling.
Pre-Sale
Intermediate sale phase that can use separate timing, pricing, limits, and whitelist rules before the public round opens.
Public Sale
General-access phase that still remains subject to live contract configuration, KYC controls, and any operator-set purchase limits.
Payment and access controls
- Payment assets are configurable ERC-20 quote tokens on the published Ethereum deployment rather than hard-coded native coin payments.
- KYC approval can be required before purchase and whitelist checks can be enabled per phase.
- Each phase can define its own allocation, price, start/end windows, and per-wallet contribution caps before activation.
Delivery, refunds, and vesting
- If the soft cap is not met, the sale contract supports refund flows after failure finalization.
- Crowdsale claim logic supports a TGE unlock plus post-cliff linear vesting for purchased tokens.
- The live vesting schedule remains a configurable sale parameter and should be checked in the active sale configuration.
- Other pools such as team and rewards follow separate vault-specific schedules.
Core modules in the repo
CHVToken
ERC-20 token contract with fixed-supply minting at deployment, burn support, pause controls, and allocation metadata.
ChessVerseCrowdsale
Phase-based sale contract with ERC-20 payment token support, KYC/whitelist gating, soft-cap refunds, and claim-based vesting.
OperationalRewardsVault
Rewards reserve controller with a 20-year campaign window and annual release bounds between 10M and 50M CHV.
TeamVestingVault
Dedicated 50M CHV team vault with 10% unlocked at vesting start and 90% unlocking linearly over 12 months.
TreasuryMultisig
Treasury custody layer intended to receive strategic reserve funds and unsold ICO inventory after finalization.
TokenVesting / TrancheVesting
Additional vesting primitives for controlled distribution schedules outside the core crowdsale and team vault flows.
Which documents control if there is a conflict
Binding sale and legal documents
Token Sale Terms, Terms of Use, AML / KYC Policy, Privacy Policy, and other signed or expressly incorporated documents control when there is any conflict.
Informational token materials
This Token Documentation page, whitepaper-style summaries, roadmap copy, FAQs, and marketing materials are explanatory only and do not override binding legal terms.
Live sale configuration
Final payment-token enablement, soft-cap values, KYC controls, whitelists, and active phase timing remain configurable before activation and should be checked against the live sale interface and deployed contracts.
Review the legal terms, then continue to the live sale flow
This page is a public documentation hub, not the final contractual instrument. Review the binding sale terms and compliance policies before connecting a wallet or purchasing CHV.