Skip to main content

Grow Token

Grow Token — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).

Grow Token — an AI/Training \| Infra project on the BNB Smart Chain network, token (symbol: GROW).

Disclaimer

Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.

TL;DR (for readers who are not into AI)

  • What it is: a token linked to the Triathon project; in the whitepaper, Triathon describes a platform for Web3 security testing via “gamified testing scenarios” and the use of the collected data for training AI/LLM (claimed).
  • Who it’s for: Web3 users and teams that participate in testing/game scenarios and community work (claimed).
  • Why onchain/token: the GROW token is observable onchain on BNB Smart Chain; the whitepaper claims that the tokenomics is used for incentives (for example, for labeling vulnerabilities/data).

How it works (very briefly)

  1. The user does: participates in testing/scenarios (including testnet tasks) and/or helps flag/label vulnerabilities (claimed).
  2. The system does: aggregates the results/data and uses them as a dataset for training AI/LLM (claimed).
  3. The user gets: participation in the platform mechanics and rewards per the tokenomics (in general terms, no forecasts; claimed).
  4. Where the blockchain is: the GROW token exists onchain on BNB Smart Chain.
  5. Token role: incentives/rewards per the tokenomics (claimed in the whitepaper).

Quick links: AI thesis fit

Project passport

Field Value
Project name Grow Token
Also known as (aliases) GROW
Logo (logo) ../assets/579_grow-token_logo.ico
Token symbol (ticker) GROW
Category AI/Training | Infra
Primary chain (chain) BNB Smart Chain
Type EVM
Network status mainnet
Consensus (consensus) PoSA (BNB Smart Chain; 21 validators)
Launch date (launch_date) —
Project status (status) active
Token (standard) BEP-20
Token contract 0x0C9aD20802E89BeA858ae2E8594843fAfA887CB3
Token model (token_type) —
Max supply 10,000,000 GROW (max total supply)
Issuance fixed
Tokenomics (tokenomics, brief) Max total supply in the Explorer; the whitepaper claims incentives via token economics for labeling vulnerabilities/data used for training AI/LLM.
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) LLM training from labeled security/vulnerability data
Use‑case (use_case) gamified Web3 security testing + AI detection tools
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 1 / onchain_score 1 / token_score 1 / evidence_score 3
Last verified 2026-02-11

General project overview

Grow Token (GROW) is a BEP‑20 token on the BNB Smart Chain network. In this card it is considered together with the Triathon project (website/docs in links_*): in the economic whitepaper, Triathon describes a platform for Web3 security testing (including scenarios on testnets and “game” mechanics), as well as the use of the collected data for training an AI large language model and building detection tools (claimed).

Features/modules

  • Security testing platform (claimed): game testing scenarios for Web3 projects.
  • Data → AI training loop (claimed): vulnerability labeling data is used for training LLM/neural network models and iteratively improving detectors.
  • Token economics (claimed): incentives for users for actions (for example, labeling vulnerabilities/data).

Typical scenarios

  • Scenario 1: a user performs test tasks/attacks on testnets → the system records the results (claimed).
  • Scenario 2: a user labels vulnerabilities/data → the data is used for training LLM/detectors (claimed).

Getting started (wallet/network)

  • What you need: for onchain — an EVM wallet; for participation in the platform — the Triathon website/documentation (see links_*).
  • Network/chain: BNB Smart Chain.
  • Fees: BNB Smart Chain fees (gas) for onchain operations with the token.

Architecture/tech (non‑AI)

  • Components: the token contract (BEP‑20) + the offchain Triathon platform (claimed).
  • Participant roles: users/community; project teams.
  • Where logic runs: participation/game scenarios and AI training — offchain; the token — onchain.
  • Dependencies: —.

Token/economics (expanded, no forecasts)

  • Token utility: the whitepaper claims incentives via token economics; detailed accrual rules/whether the token is mandatory are not established per Tier‑1 sources.
  • Protocol necessity drivers: incentives are claimed for users who label vulnerabilities/data (used for training AI/LLM).
  • Who pays fees: users pay gas on BNB Smart Chain for onchain operations.
  • Where fees go: to the BNB Smart Chain network validators (gas), the general network model.
  • Issuance/burn: fixed supply (see max total supply in the Explorer).
  • Security/incentive mechanisms: incentives via token economics are claimed (see Evidence/whitepaper); detailed parameters are not established per Tier‑1 sources.
  • Distribution and token issuance schedule: not established per Tier‑1 sources.
  • Treasury: not established per Tier‑1 sources.

Governance

  • Who makes decisions: —.
  • How protocol parameters change: —.
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: no Tier‑1 confirmation found.
  • Bug bounty: no Tier‑1 confirmation found.
  • Incidents: no Tier‑1 confirmation found.
  • Threat model: risks of the token contract/integrations and risks of the centralized offchain components of the platform.

Project status and timeline

  • Current status: active (in terms of the token on BNB Smart Chain).
  • Key releases/milestones: not established per Tier‑1 sources.
  • Roadmap: there is a public roadmap update in the official Medium (see links_*); a separate Tier‑1 roadmap document was not found.

Ecosystem/integrations

  • Integrations: —.
  • Partners: —.
  • Where it’s actually used: not established per Tier‑1 sources.

AI component of the project

  • What is real AI here? The Triathon economic whitepaper claims that vulnerability labeling data is used for training an AI large language model and building detection tools.
  • What is truly onchain? The GROW token (BEP‑20) on the BNB Smart Chain network.
  • Why is a token needed? The whitepaper claims incentives via token economics (for example, rewards for labeling vulnerabilities/data).
  • Red flags (based on the information found): there are no Tier‑1 quality metrics for the AI/detectors; the link between specific onchain mechanics and AI training is not disclosed per Tier‑1 sources.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality medium 1
Onchain necessity low 1
Token necessity low 1
Evidence Tier‑1 present 3
Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

  • AI_0 (decision): 0
  • Claim (one line): There are signs of AI reality per Tier‑1 (see AI_1..AI_4), so the AI_0 flag (intent‑only) does not apply.
  • Evidence: Tier‑1 — see Evidence/links in AI_1..AI_4.
  • Why sufficient / why not (one line): AI_0=1 is admissible only when AI_1..AI_4=0; here ai_score without AI_0 = 1.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): AI/LLM models for building vulnerability detection tools based on labeled data are claimed.
  • Evidence: Tier‑1 — https://triathon.gitbook.io/economic-paper/triathon-economic-whitepaper.md
  • Why sufficient / why not (one line): the Tier‑1 document describes the AI component and its purpose.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): a public demo of the AI detector/LLM module was not found per Tier‑1 sources.
  • Evidence: Tier‑1 — https://www.triathon.space/
  • Why sufficient / why not (one line): the Tier‑1 website/whitepaper has no verifiable demo of an AI tool.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: not found per Tier‑1 sources.
  • Context (version/date/how measured): not established.
  • Evidence: Tier‑1 — https://triathon.gitbook.io/economic-paper/triathon-economic-whitepaper.md
  • Why sufficient / why not (one line): the Tier‑1 document contains no reproducible quality metrics for the AI/detectors.
  • Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

  • AI_4 (decision): 0
  • Claim (one line): a tech description of the model/dataset/training pipeline is not established per Tier‑1 sources.
  • Evidence: Tier‑1 — https://triathon.gitbook.io/economic-paper/triathon-economic-whitepaper.md
  • Why sufficient / why not (one line): there is no AI_4‑level specification.
  • Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

  • OC_1 (decision): 1
  • Chain: BNB Smart Chain
  • Addresses/identifiers: GROW token: 0x0C9aD20802E89BeA858ae2E8594843fAfA887CB3
  • Evidence: Tier‑1 — https://bscscan.com/token/0x0C9aD20802E89BeA858ae2E8594843fAfA887CB3
  • Why sufficient / why not (one line): the token address and network are confirmed by the Explorer.
  • Conflict note (if any): —

OC_2 — onchain beyond just a token (1/0)

  • OC_2 (decision): 0
  • What useful logic is onchain: not established per Tier‑1 sources (other than the token).
  • Evidence: Tier‑1 — https://bscscan.com/token/0x0C9aD20802E89BeA858ae2E8594843fAfA887CB3
  • Why sufficient / why not (one line): Tier‑1 sources do not confirm the platform’s onchain logic beyond the token.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: participation/the AI part are described as offchain modules; onchain criticality is not proven.
  • Evidence: Tier‑1 — https://triathon.gitbook.io/economic-paper/triathon-economic-whitepaper.md
  • Why sufficient / why not (one line): there is no Tier‑1 proof that the product is inoperable without the blockchain.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, GROW (BEP‑20).
  • Evidence: Tier‑1 — https://bscscan.com/token/0x0C9aD20802E89BeA858ae2E8594843fAfA887CB3
  • Why sufficient / why not (one line): the token is observable in the Explorer.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 0
  • Claim (one line): payment for the key service with the token is not established per Tier‑1 sources.
  • Evidence: Tier‑1 — https://triathon.gitbook.io/economic-paper/triathon-economic-whitepaper.md
  • Why sufficient / why not (one line): the whitepaper describes the economics at the level of principles, but without clear rules for payments “for the service”.
  • Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

  • TK_2 (decision): 1
  • Claim (one line): the whitepaper claims that token economics are used for user incentives (for example, labeling vulnerabilities), and the data goes into LLM training.
  • Evidence: Tier‑1 — https://triathon.gitbook.io/economic-paper/triathon-economic-whitepaper.md
  • Why sufficient / why not (one line): the document directly links the incentives/tokenomics to the process of data collection and AI training.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): the use of the token in governance is not established per Tier‑1 sources.
  • Evidence: Tier‑1 — https://triathon.gitbook.io/economic-paper/triathon-economic-whitepaper.md
  • Why sufficient / why not (one line): the available Tier‑1 fragment contains no description of governance mechanics via the token.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the replaceability of the token has not been assessed (incentives via token economics are claimed).
  • Evidence: Tier‑1 — https://triathon.gitbook.io/economic-paper/triathon-economic-whitepaper.md
  • Why sufficient / why not (one line): without a specific incentive scheme and alternatives, replaceability cannot be reasonably asserted.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://bscscan.com/token/0x0C9aD20802E89BeA858ae2E8594843fAfA887CB3 The Grow Token (GROW) token: contract and max total supply 10,000,000.
Tier‑1 https://triathon.gitbook.io/economic-paper/triathon-economic-whitepaper.md Claims about token economics (incentives) and the use of data for training an AI large language model.
Tier‑1 https://www.triathon.space/ The Triathon website (context of the project to which the token is linked).
Tier‑2 https://medium.com/@Triathon/triathon-roadmap-2022-h2-a4cae1130c17 A public roadmap update (official Medium), as context on plans/milestones.

No comments to display

Back to top