Skip to main content

Gonka

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

Gonka — an AI/Compute | Infra project that describes a decentralized infrastructure for AI inference and training; it claims its own network and token (symbol: GNK).

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 network/protocol that tries to direct participants’ compute toward useful AI tasks (inference and training) instead of “empty” mining.
  • Who it’s for: developers who need AI inference/training; hardware providers (hosts/nodes) who want to receive rewards for compute.
  • Why onchain/token: onchain is used for coordination/accounting and reward distribution; the token is described as part of the incentives and (optionally) of the collateral/weight in the consensus mechanism.
  • What you can actually touch (Tier‑1): a chat interface claimed to run on top of the Gonka network.

How it works (very briefly)

  1. The developer/user does: sends an AI inference request (or initiates training) via a client/interface.
  2. The network does: routes the task to hosts (compute providers) and collects the results.
  3. Validation does: the described mechanism verifies the correctness of the results (including via sampled/majority verification).
  4. Where the blockchain is: onchain records the state/rules and distributes rewards to participants.
  5. Token role: described as part of the incentives (and of optional collateral for weight/votes).

Quick links: AI thesis fit

Project passport

Field Value
Project name Gonka
Also known as (aliases) Gonka AI
Logo (logo) ../assets/501_gonka_logo.svg
Token symbol (ticker) GNK
Category AI/Compute | Infra
Primary chain (chain) Gonka
Type Appchain
Network status mainnet
Consensus (consensus) —
Launch date (launch_date) —
Project status (status) active
Token (standard) native
Token contract —
Token model (token_type) utility (payments + staking + governance)
Max supply 1,000,000,000 GNK
Issuance Reward Coins: initially 323,000 GNK per epoch; exponential decay (halving ~ every 4 years)
Tokenomics (tokenomics, brief) The tokenomics (Tier‑1) records a supply of 1B and a Bitcoin‑style issuance of epoch rewards; it also describes collateral‑backed influence for governance weight.
Governance onchain governance (PoC‑weighted votes; collateral‑backed influence)
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) decentralized AI inference + training (compute)
Use‑case (use_case) distributed AI compute (training/inference)
DecAI Fit — AI thesis fit 5/6 — high alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 3 / onchain_score 2 / token_score 1 / evidence_score 3
Last verified 2026-02-11

General project overview

Gonka describes itself as a decentralized AI infrastructure that seeks to use the network’s compute resources for “useful” AI tasks (inference/training). The whitepaper emphasizes not spending most of the compute on meaningless work for the sake of security, but instead tying consensus and participants’ weights to computational artifacts similar to transformer computations.

Features/modules

  • AI compute network: a network of hosts (hardware providers) for inference/training tasks.
  • Consensus Sprint (described): a time‑bound competition/mechanism where a participant’s weight is tied to a computational proof.
  • Task validation (described): sampled/majority verification of results and withholding of rewards until verification.
  • Open source code (partial): a public repository with network components (a Cosmos‑SDK stack is claimed in the README).

Typical scenarios

  • Scenario 1: a developer sends an inference request → receives the model’s response via the interface/client.
  • Scenario 2: a host connects compute resources → receives rewards for processing tasks/participating in the network mechanisms.

Getting started (wallet/network)

  • What you need: access to the interface/client and an account/keys (details — in the project documentation).
  • Network/chain: Gonka (mainnet per the project’s claim).
  • Fees: —.

Architecture/tech (non‑AI)

  • Components (per the description in the repository): a chain node and an API layer; a separate ML node for running the AI workload.
  • Participant roles: developers (clients), hosts/nodes (compute providers), validators/verifiers (within the described mechanism).
  • Where logic runs: inference/training computation runs offchain; accounting/coordination/reward distribution — onchain.
  • Dependencies: a Cosmos‑SDK stack is claimed in the official repository; the ML workload is described as a Python/CUDA stack.

Token/economics (expanded, no forecasts)

  • Token utility (per the whitepaper/README): rewards to hosts and (optionally) collateral to increase weight/vote in the Sprint mechanism.
  • Security/incentive mechanisms: rewards are withheld until the results are verified; collateral is described as a tool against dishonest nodes.
  • Issuance/emission (Tier‑1): the tokenomics describes a “Bitcoin‑style” model: a base reward of 323,000 GNK per epoch with exponential decay (halving approximately every ~4 years).

Governance

  • Who makes decisions (Tier‑1): decisions are made via PoC‑weighted votes; influence is not derived from coin ownership alone, and the “activation” of weight is amplified via lock GNK collateral (collateral‑backed influence).
  • Where changes are discussed: proposals/tracks in the repository (see links_* Roadmap).

Security and incidents

  • Audits: —.
  • Bug bounty: not established (there is a link to Discord as a support channel, but no Tier‑1 description of a bug bounty program was found).
  • Incidents: —.
  • Threat model: risks of dishonest task execution and validation; the project describes countermeasures via Sprint/verification/collateral.

Project status and timeline

  • Current status: mainnet (per the claim on the website).
  • Key milestones: —.
  • Roadmap: proposals/plans in the repository (see links_* Roadmap).

Ecosystem/integrations

  • Integrations: —.
  • Partners: —.
  • Where it’s actually used: the available chat interface (App/Demo) as a demo surface.

AI component of the project

  • What is real AI here? the project positions the network as an infrastructure for AI inference/training and describes the redistribution of compute toward transformer workloads.
  • What is truly onchain? the network/blockchain is used for consensus, accounting and reward distribution; there is a public explorer.
  • Why is a token needed? described as an incentive mechanism and (optionally) collateral for the weight/vote/accountability of nodes.
  • Red flags (based on the information found): quality/cost/throughput metrics are not standardized in Tier‑1; some of the claims about “almost 100% of compute on useful tasks” require verifiable onchain/offchain metrics.

DecAI Fit component summary

  • DecAI Fit: 5/6 — high alignment with the Decentralized AI thesis
Component Level Score
AI reality high 3
Onchain necessity medium 2
Token necessity medium 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): AI is described as the main operating layer of the product (a compute network), not as a “plan for the future”.
  • Evidence: Tier‑1 — https://gonka.ai/whitepaper.pdf
  • Why sufficient / why not (one line): We do not single out AI intent separately, since Tier‑1 already describes the purpose of the network as AI compute.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): The network is intended for running AI inference and training (training/inference) on distributed compute resources.
  • Evidence: Tier‑1 — https://gonka.ai/whitepaper.pdf ; https://github.com/gonka-ai/gonka/
  • Why sufficient / why not (one line): The whitepaper and README describe the AI workload as the target function of the network.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): There is a public chat interface (App/Demo) claimed to run on top of the Gonka network.
  • Evidence: Tier‑1 — https://gonka.ai/ ; https://chat.gonka.ai/
  • Why sufficient / why not (one line): The existence of a public interface is the minimally sufficient “what you can touch”; it does not replace quality metrics.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://gonka.ai/whitepaper.pdf
  • Why sufficient / why not (one line): No reproducible set of quality/speed/cost metrics/benchmarks was found in Tier‑1 sources.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): There is a whitepaper describing the Sprint/verification mechanism and a public implementation repository.
  • Evidence: Tier‑1 — https://gonka.ai/whitepaper.pdf ; https://github.com/gonka-ai/gonka/
  • Why sufficient / why not (one line): The existence of a tech description and code is the sufficient minimum for the “tech context present” flag.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Gonka
  • Addresses/identifiers: — (within this card we record the existence of a public explorer)
  • Evidence: Tier‑1 — https://gonkascan.com/
  • Why sufficient / why not (one line): A public explorer is the minimal confirmation of the onchain component.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: coordination/accounting of participation and reward distribution for compute tasks.
  • Evidence: Tier‑1 — https://gonka.ai/whitepaper.pdf
  • Why sufficient / why not (one line): The whitepaper describes consensus/weights/validation and the network economy as onchain‑related elements.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: not established per Tier‑1 that the product breaks down without the blockchain (rather than shifting to a “centralized orchestrator” model).
  • Evidence: Tier‑1 — https://gonka.ai/whitepaper.pdf
  • Why sufficient / why not (one line): OC_3=1 requires an explicit justification of the irreplaceability of onchain; this was not found per Tier‑1.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The whitepaper mentions GNK as a token/collateral, so a token is claimed.
  • Evidence: Tier‑1 — https://gonka.ai/whitepaper.pdf
  • Why sufficient / why not (one line): The mention of GNK as collateral/a network parameter means that a token exists in the project’s model.
  • 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 inference/training with the token as a mandatory protocol mechanism is not established per Tier‑1.
  • Evidence: Tier‑1 — https://gonka.ai/whitepaper.pdf
  • Why sufficient / why not (one line): TK_1=1 requires an explicit specification of pay‑for‑compute with the token; not found per Tier‑1.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): The whitepaper describes rewards for task execution and (optionally) collateral in GNK for weight/accountability.
  • Evidence: Tier‑1 — https://gonka.ai/whitepaper.pdf
  • Why sufficient / why not (one line): The token is directly tied to incentives and honest‑behavior mechanisms (collateral/verification).
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): The governance mechanism is described as PoC‑weighted; the use of GNK as a “vote token” is not confirmed as a separate onchain voting mechanism per Tier‑1.
  • Evidence: Tier‑1 — https://gonka.ai/whitepaper.pdf
  • Why sufficient / why not (one line): TK_3=1 requires an explicit specification of token‑based governance logic; not found per Tier‑1.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): The replaceability of the token is not established per Tier‑1.
  • Evidence: Tier‑1 — https://gonka.ai/whitepaper.pdf
  • Why sufficient / why not (one line): TK_4=1 requires an explicit argument “it can be replaced without loss of meaning”; not found per Tier‑1.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://gonka.ai/whitepaper.pdf Describes the purpose of the network (AI training/inference) and the Sprint mechanism (transformer‑based PoW) + verification/collateral.
Tier‑1 https://gonka.ai/tokenomics.pdf Tokenomics: fixed total supply of 1B GNK; epoch rewards (323,000 GNK initial) + exponential decay; collateral‑backed influence for governance weight.
Tier‑1 https://github.com/gonka-ai/gonka/ Public repository: project description and component structure (chain/api/ml).
Tier‑1 https://gonkascan.com/ The existence of a public explorer (the network’s onchain component).
Tier‑1 https://chat.gonka.ai/ Demo surface: the claimed chat interface as a usage example.
Tier‑2 https://coinmarketcap.com/currencies/gonka/ Token profile/metadata (for reference, not proof).

No comments to display

Back to top