Main token and ecosystem surface.
Transparency
Trust requires visible surfaces.
A token page can look futuristic and still feel weak if users cannot tell which domain is official, what the contract status is, where docs live, and how rollout posture should be interpreted. This page keeps those cues explicit.
OfficialDomain clarity and docs access.
StatusContract and rollout posture visible.
SafetySecurity habits and verification points.
Technical and protocol documentation surface.
Rollout should stay visible rather than implied.
| Surface | Purpose | Status cue |
|---|---|---|
| challengetoken.io | Primary token and ecosystem site. | Official |
| docs.challengetoken.io | Documentation, protocol detail, references. | Official |
| www.chlg.app | App landing and ecosystem gateway. | Official |
| fitness.chlg.app | Sport & Fitness module. | Official module |
| health.chlg.app | Health module. | Official module |
Official links should be easy to verify.
Keep token launches, docs, and updates tied to owned surfaces so users can confirm what is legitimate before acting.
Do not overstate maturity.
If contract, audit, or deployment stages are still in progress, the site should say so clearly rather than implying full live status.
We never DM first.
That single line matters. Scams often arrive through private channels, while the real protocol should keep updates on official surfaces.