Gonka AI · Evidence ledger

Protocol track.

Development, adoption, and the next verifiable milestones.

Epoch—
Total weight—— participants
GNK price—USD · Market data

Research brief for your AI

All events, evidence labels, targets, and sources.

Past → present → future

One protocol timeline

01
Live

Public development begins

The Gonka repository opened publicly, establishing the visible start of protocol development before mainnet.

The project’s build history can be inspected from its earliest public work.

GitHub · Gonka
02
Live

Tokenomics published

The economic paper documented GNK issuance, work-based rewards, vesting, and epoch mechanics ahead of launch.

Network incentives became reviewable before the token went live.

Gonka · Tokenomics
03
Live

Genesis ceremony

Validators submitted genesis transactions and participant records through a public, pull-request-based rehearsal process.

Initial network membership and launch preparation left a public audit trail.

GitHub · Genesis
04
Live

Mainnet launch

Release v0.2.0 launched the main network for distributed AI compute, rewarding participants in GNK.

A live network and verifiable block history.

GitHub · v0.2.0
05
Live

Inference validation v2

v0.2.2 added full-token enforcement, recovery for missed validations, on-chain MLNode upgrades, and a second generation of inference validation.

Verification advanced beyond the launch configuration.

GitHub · v0.2.2
06
Live

CertiK fixes shipped

v0.2.3 incorporated direct remediations from the CertiK audit alongside API transport and transaction-subscription fixes.

External review findings translated into production code.

GitHub · v0.2.3
07
Live

Ethereum bridge introduced

v0.2.5 added a native Ethereum bridge service and the operational path for hosts to run it.

GNK gained infrastructure for movement beyond its native chain.

GitHub · v0.2.5
08
Reported>6,000 H100-equiv.

Compute reaches scale

Bitfury reported more than 6,000 H100-equivalents. This is aggregate compute, not a physical H100 count or proof of paid utilization.

Compute supply expanded rapidly.

Business Wire
09
Reported$50M

$50M investment announced

Bitfury announced funding for protocol and ecosystem development—the first investment under a broader initiative, not a $1B transfer to Gonka.

Institutional backing expanded development resources.

Business Wire
10
Live

PoC v2 enforced

v0.2.9 fully activated PoC v2, consolidated the validation model, gated transfer agents, and added a guardian tiebreaker for unresolved votes.

Compute verification and request control became stricter.

GitHub · v0.2.9
11
Live

New inference architecture

v0.2.11 introduced the subnet package while updating community-sale and liquidity-pool contracts and bridge tooling.

The chain began its transition toward modular inference delivery.

GitHub · v0.2.11
12
Live

DevShard routing arrives

v0.2.12 added versiond and routed DevShard traffic independently from the core API service.

Inference runtimes could evolve separately from chain upgrades.

GitHub · v0.2.12
13
Reported

API relaunched

DevShards separated inference-runtime development from the core network. The team reported throughput near one billion tokens per day in the first weeks.

Developers gained a working compute access layer.

GitHub · Gonka
14
Approved

Roadmap approved

Proposal #57 established three horizons and twelve development tracks. Individual projects still require separate decisions and funding.

Execution gained a shared evaluation framework.

Governance · #57
15
Live

DevShard safeguards

v0.2.13 fixed reward accounting and escrow limits, added an emergency DevShard switch, and reduced early guardian influence.

Operational controls matured as inference volume grew.

GitHub · v0.2.13
16
Live

HackerOne launched

The bug bounty became a permanent channel for finding and resolving vulnerabilities with Bitfury’s support.

Security became a continuous formal process.

Gonka Docs · Security
17
Live

Bridge audit completed

CertiK completed its Ethereum bridge review with no critical findings; four major findings were resolved in the final report.

A key cross-chain component received named third-party review.

CertiK · Final report
18
Approved

WebX Asia activation

Governance funded the community’s conference presence, including partner coordination and broker onboarding activity.

Protocol growth moved from engineering into coordinated distribution.

Governance · #51
19
Live

High-availability shift

v0.2.14–v0.2.15 introduced edge-api, versiond-router, and automatic loading and verification of approved DevShard runtimes.

Infrastructure became easier to upgrade and more resilient.

GitHub · v0.2.15
20
Reported16.5B / day

WebX usage high

The team reported 16.5 billion processed tokens on the conference day—a network record at the time.

Throughput moved well above early API levels.

Product Science · WebX
21
Approved

DevShard v5

Proposal #105 approved mainnet-height synchronization, session recovery, and high-availability improvements alongside a refreshed model set.

Runtime and models can evolve without a full shutdown.

Governance · #105
22
Reported>1T / month

Trillion-token month

The team reported roughly 35 billion tokens per day and more than 2× monthly growth. Usage does not equal revenue.

Paid share and returning customers are the next test.

Network updates
23
Reported≈100B / day

100B-token peak days

The team reported several days near this level and several dozen B300s added. It is not yet a sustained average.

Peak throughput entered a new order of magnitude.

Network updates
24
Live

Production hardening

DevShard 5.0.2 capped Postgres connection pools; 5.0.3 continued stabilization after an issue surfaced in production.

The transparent release-and-fix cycle shows maturity.

GitHub · Releases
25
In progress

TOKEN2049 Singapore

The community approved Gold Sponsorship and up to 100,000 USDT. Participation expands access, but does not imply completed deals.

Impact should be measured through later partnerships.

Governance · #99
Now · epoch 417
26
In progress

v0.2.16 upgrade

Trusted Weight, dynamic model coefficients, fees, and PoC Challenge under Proposal #112.

Completion: Proposal passes and the upgrade activates on mainnet.
Network updates · #112
27
Approved

Community DevNet + test lab

Proposal #82 funds an external test lab, a public multi-node DevNet, observability, runbooks, and independent release validation.

Completion: Pilot deliverables and community handoff are accepted by governance.
Governance · #82
28
In progress

Foundation

Register the legal entity and present its directors, mandate, and first budget. No public completion date is confirmed.

Completion: Entity registered; leadership, spending rules, and approved budget published.
Roadmap · #57
29
Approved

Ledger + security audit

Ledger integration is funded; the Trail of Bits audit is reported as underway. No public delivery date is confirmed.

Completion: Ledger support ships; audit and remediations are published.
Governance · #102
30
Planned

Confidential inference

A TEE-based MLNode class is being explored for enterprise and privacy-sensitive inference workloads.

Completion: A confidential node class and priced private-inference path run on mainnet.
GitHub · TEE proposal
31
Planned

Developer distribution

The approved roadmap targets easier access through SDKs, gateways, aggregators, and AI-agent tooling.

Completion: Supported integrations publish usage, reliability, and developer-adoption KPIs.
Network roadmap
32
Planned

Full CEX listings

The Foundation is expected to remove the legal blocker to major exchange negotiations.

Completion: An exchange enables GNK trading, deposits, and withdrawals.
Network roadmap
33
Planned

Paid inference economics

Usage growth must translate into transparent revenue and recurring demand. The horizon is directional, not committed guidance.

Completion: Paid share, revenue, returning customers, latency, and errors are disclosed.
Network roadmap
34
Planned

Neocloud-scale network

The roadmap’s later horizon targets competitive reliability, utilization, and capacity at decentralized cloud scale.

Completion: Comparable cost, latency, uptime, geographic reach, and sustained paid demand are disclosed.
Network roadmap
25 sourced events9 forward benchmarks · target periods are labeled