Skip to main content

GG3

GG3 — 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).

GG3 — an AI‑oriented platform with quests/gamification for communities; token: GGX (BEP‑20, BNB Smart Chain).

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 platform of “quests” (tasks) for users and communities with gamification and rewards.
  • Who it’s for: players/community members and partner communities (operators/brands) that need managed engagement.
  • What you can actually touch (Tier‑1): the platform’s web pages (Home/Quests).
  • Why onchain/token: the token is used as a utility asset for features/payments and (as claimed) governance mechanics within the ecosystem.

How it works (very briefly)

  1. The user does: connects accounts/a wallet and completes tasks (quests).
  2. The system does: forms/verifies quests and user actions, credits progress and rewards.
  3. The user gets: XP/rewards and access to quests/activities.
  4. Where the blockchain is: the GGX token is implemented as BEP‑20 on the BNB Smart Chain network.
  5. Token role (if any): utility (including payments/access to features and staking mechanics within the platform).

Quick links: AI thesis fit

Project passport

Field Value
Project name GG3
Also known as (aliases) GG3.org; GGX
Logo (logo) —
Token symbol (ticker) GGX
Category AI/Agents | Gaming
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 0x7bedaA6e5f43e1d83d667CfE770252a32532369E
Token model (token_type) utility (payments + staking + governance)
Max supply —
Issuance —
Tokenomics (tokenomics, brief) staking for platform “boosters”; payments for packages/campaigns
Governance —
Admins/keys —
Audit yes
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI agents for quests + community
Use‑case (use_case) quests + engagement for communities
DecAI Fit — AI thesis fit 4/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 2 / onchain_score 1 / token_score 1 / evidence_score 3
Last verified 2026-02-11

General project overview

In its docs, GG3 describes the product as an “edutainment” platform where user activity is framed as quests/tasks, and interactions with communities and partners are partially automated via AI agents.

The key point for the DecAIHub assessment: Tier‑1 sources confirm the presence of AI agents as part of the product (a description of where they are applied), and confirm the parameters of the GGX token (ticker, standard, network and contract address). At the same time, the necessity of onchain logic as such, beyond the token, is not established per Tier‑1 sources.

Features/modules

  • Quest system: tasks/quests for users and communities.
  • AI agents: automation of quest creation/monitoring/validation (as claimed in the documentation).
  • Rewards + gamification: XP/rewards and progress mechanics (per the product description).
  • Integrations for login/accounts: Google/Steam/Discord/WalletConnect are mentioned (as part of onboarding).
  • Partner campaigns: the ability to launch campaigns/quest packages for communities (as part of the utility description).

Typical scenarios

  • Scenario 1 (user): enters the platform → completes quests → receives XP/rewards.
  • Scenario 2 (community/partner): launches a quest campaign → gets activity/engagement → reviews the results (as claimed).

Getting started (wallet/network)

  • What you need: an account on the supported platforms (or a wallet via WalletConnect) — per the documentation.
  • Network/chain: for the onchain part of the token — BNB Smart Chain (EVM).
  • Fees: onchain fees arise on token transactions on the network; the details of token usage inside the product depend on the specific features.

Architecture/tech (non‑AI)

  • Components: web platform + integrations with external services; the onchain artifact is the BEP‑20 token.
  • Where logic runs: user actions and the “quest logic” are described as part of the platform; the onchain part is confirmed only for the token.

Token/economics (expanded, no forecasts)

  • Token utility: the documentation lists “platform boosters”, staking‑related benefits and payment options for partners.
  • Protocol necessity drivers: some features are described as plans/possibilities; if a mechanic is not confirmed, it should be treated as an intent.

Governance

  • Who makes decisions: the documentation mentions governance participation, but it is marked as “to be confirmed”, so it is not recorded as a working mechanism.

Security and incidents

  • Audits: the token documentation mentions audits; a public report/link to an audit report is not recorded per Tier‑1 sources.
  • Incidents: — (not established per Tier‑1 sources).

Project status and timeline

  • Current status: the web platform and public documentation are available.

Ecosystem/integrations

  • Integrations: login via external platforms (Google/Steam/Discord/WalletConnect) and social channels (X/Discord/Telegram).

AI component of the project

  • What is real AI here? AI agents that are used for automation and personalization of quests/interactions on the platform (per the description in the documentation).
  • What is truly onchain? the GGX token as a BEP‑20 asset on the BNB Smart Chain network.
  • Why is a token needed? it is claimed as a utility token for platform features (including payment/staking mechanics and governance participation rights).
  • Red flags (based on the information found): some utility features (for example, governance) are marked in the documentation as “to be confirmed”; without confirmation of implementation this should be treated as an intent, not a proven mechanism.

DecAI Fit component summary

  • DecAI Fit: 4/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality low 2
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: a separate roadmap claim of “AI as a future plan without a working component” was not recorded, since AI is described as part of the current product.
  • Evidence: Tier‑1 — https://docs.gg3.org/
  • Why sufficient / why not: AI is described as a functional component of the platform, so the intent flag is not used.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim: AI agents are used for automation/personalization of quests and interactions on the platform.
  • Evidence: Tier‑1 — https://docs.gg3.org/
  • Why sufficient / why not: the documentation describes the role of the AI agents and their application in the product at the level of “what they do”.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim: there are platform web pages (Home/Quests) available on the project’s domain.
  • Evidence: Tier‑1 — https://gg3.org/home
  • Why sufficient / why not: there is a Tier‑1 “what you can touch” artifact (the web platform).
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — —
  • Why sufficient / why not: no numerical metrics/benchmarks of the AI component were found in Tier‑1 sources.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim: no Tier‑1 tech description of the architecture/versions of the AI models was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not: there are descriptions of functionality, but no engineering details sufficient for the flag.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: BNB Smart Chain
  • Addresses/identifiers: 0x7bedaA6e5f43e1d83d667CfE770252a32532369E
  • Evidence: Tier‑1 — https://docs.gg3.org/ggx-tokenomics/token-description
  • Why sufficient / why not: the documentation specifies the ticker/network/standard and the GGX contract address.
  • 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 (beyond the token).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not: the presence of a token by itself does not prove useful onchain logic of the product.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: it is not established that a key property of the product breaks down without the blockchain.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not: there is no justification of “why the product does not work without onchain”.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim: the project has a token, GGX (BEP‑20).
  • Evidence: Tier‑1 — https://docs.gg3.org/ggx-tokenomics/token-description
  • Why sufficient / why not: the documentation explicitly specifies the ticker/standard and address.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim: the token is used for payments/options within the platform (including “one‑time payment options” for partners).
  • Evidence: Tier‑1 — https://docs.gg3.org/ggx-tokenomics/token-utility
  • Why sufficient / why not: the utility section explicitly lists payment options.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim: protocol collateral/penalties/slashing are not identified per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not: staking mechanics for “boosters” are described, but without an explicit protocol mechanism of collateral/penalties.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim: governance features are described as “to be confirmed”, so we consider them not confirmed as a working mechanism.
  • Evidence: Tier‑1 — https://docs.gg3.org/ggx-tokenomics/token-utility
  • Why sufficient / why not: this looks like an intent/plan, not proof of functioning governance.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim: no conclusion about the replaceability of the token with an alternative mechanism is recorded.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not: without engineering details, replaceability/irreplaceability cannot be strictly asserted.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.gg3.org/ describes the product and the role of AI agents on the platform
Tier‑1 https://gg3.org/home web pages of the GG3 platform (Quests/Home) as “what you can touch”.
Tier‑1 https://docs.gg3.org/ggx-tokenomics/token-description GGX ticker, BNB Smart Chain network, BEP‑20 standard and contract address
Tier‑1 https://docs.gg3.org/ggx-tokenomics/token-utility lists the claimed utility scenarios of the token (including payment/staking options)
Tier‑2 https://www.coingecko.com/en/coins/gg3 reference profile of the token/project
Tier‑2 https://coinmarketcap.com/currencies/gg3/ reference profile of the token/project

No comments to display

Back to top