Skip to content

Community Funding Proposal — Gonka Labs — Year One

Authors: Tim, Mike, Artem
Subject to governance vote

A request for 70,000 USDT + 330,000 GNK (180-day vesting) from the Gonka community pool to fund enterprise-grade improvements to our core infrastructure products — aligned with the Gonka Network Development Roadmap.

Overview

Gonka Labs is requesting 70,000 USDT + 330,000 GNK with Vesting from the Gonka community pool. We've already shipped 16+ products — all without external funding. The core of this proposal is taking what we have to enterprise grade, plus two new products: G-Router — an OpenRouter-style layer that unifies access to all Gonka inference providers behind a single endpoint — and MTD (Marketing Transparency Dashboard).

This is not payment for past work. The first 6 months of Gonka Labs — everything you see in the track record — were self-funded. We don't ask for compensation for what's already done. This proposal funds the next 6 months of Gonka Labs building for the ecosystem — together wrapping a full year of us building.

The 6 months are five focused products: gonka.gg V2.0 (new high-performance engine), proxy.gonka.gg (B2B inference portal with analytics), rpc.gonka.gg (multi-provider aggregation, SLA), Gonka App (iOS + Android superapp), and Gonkavote (expanded governance tooling).

70,000 USDT is released in a single payment upon approval — covers server infrastructure and operations for the 6 months ahead. 330,000 GNK vests over 180 days — team payment for future work, verifiable on-chain.

What the network gets

All improvements target Gonka's core goals: accelerating adoption, lowering entry barriers, and institutional maturity. Institutional maturity means the network gains public uptime SLAs, open-source infrastructure layers, enterprise-grade API reliability, auditable governance processes, and transparent accountability — the signals validators, large integrators, and institutional participants need to take Gonka seriously. A more mature network is more valuable for every participant.

Aligned with the Gonka Network Development Roadmap

  • A reliable block explorer for everyone — gonka.gg serves 5,000+ users daily and is usually the first place new users land to understand Gonka. V2 makes it faster, more accurate, and mobile-friendly. Track 4 · Track 11
  • Gonka inference, reachable by businesses — proxy.gonka.gg brings real B2B integrations (Integrity is already live), solving each business's special integration demands, driving token demand and proving Gonka inference is production-ready. Track 2 · Track 11
  • RPC orchestrator, hardened to enterprise grade — rpc.gonka.gg is the default Keplr RPC. SLAs, geo-aware routing, public SLA dashboard, open-source aggregation layer. Track 4 · Track 8
  • Gonka on mobile — Gonka App for iOS and Android: wallet, governance, and AI inference from any Gonka model, in one superapp. Track 2 · Track 11
  • Governance anyone can participate in — Gonkavote and expanded tooling making on-chain decisions accessible, not just for technical users. Track 12
  • MTD (Marketing Transparency Dashboard) — open-source, every marketing initiative gets a public page: goals, deadlines, owner, status, performance analysis. Auditable by anyone. Track 11

Highlights

  • Funding: 70,000 USDT (single payment for 6 months of infra & ops) + 330,000 GNK (180-day linear vesting — team's forward compensation).
  • 5 core products brought to enterprise grade: rpc.gonka.gg, proxy.gonka.gg, gonka.gg, Gonka App, Gonkavote — plus two new products: G-Router (multi-broker inference router) and MTD (Marketing Transparency Dashboard).
  • rpc.gonka.gg multi-provider aggregation is already live — aggregates 6block, Hyperfusion, PS and others behind a single endpoint. The official default RPC for Gonka in the Keplr wallet. Addresses community request #521.
  • B2B inference integrations are already underway — proxy.gonka.gg is being actively overhauled to support them. First public example: Integrity — an Israeli-American startup ("#1 Product of the Day" on Product Hunt, $1M+ raised) running Gonka models in production beta.
  • 16+ products, 15 open-source repos — built entirely without external funding since December 2025.

Built for the ecosystem, not for profit

We built Gonka Labs products as non-commercial builders — no ads, no third-party product placements, no PR slots for sale. Any fees cover infrastructure and operational costs only — no commercial margins, no revenue extraction. All current ecosystem products will remain non-commercial. Where pricing exists, it stays at the average level across the Gonka network.

Who We Are

Gonka Labs is a three-person engineering team — Tim, Mike, and Artem — that has been building infrastructure for the Gonka ecosystem since December 2025. We stumbled upon an interview with the Gonka founders, and their enthusiasm was astonishing. On December 12, 2025, we launched gonka.gg — the first blockchain explorer for Gonka.

We asked the community: "What tools and services do we lack the most?" — and then built them. One by one. Every single product started as a community request.

Track Record

In under 6 months, with zero external funding, we shipped 16+ products and published 15 public open-source repositories. Here's what's live today:

Gonka.gg

Block explorer + analytics platform. 5,000+ daily users, 2M+ API requests/day, 270M+ transactions indexed. A single home for everything Gonka, with nine sub-products inside: Block Explorer, Transactions, Participants, Inference Map, Slashing Monitor, Faucet, Reward Calculator, Node Tracker, Full GPU History.

rpc.gonka.gg

Managed RPC infrastructure. 400+ endpoints across 6 surfaces. ClickHouse-indexed, up to 110x faster than raw RPC.

Proxy

Cloud-hosted OpenAI-compatible API for Gonka inference at proxy.gonka.gg. 1–2B tokens served daily.

Gonka App

Open-source Chrome extension wallet with GNS integration, governance, IBC tokens, and dApp provider. 700+ users. gonkalabs/ggwallet

Gonka Name Service

On-chain human-readable .gnk names. 4,000+ registered. Integrated across all our products. gonkalabs/gns

OpenGNK

Self-hosted OpenAI-compatible proxy for Gonka inference. 400+ installs. Tool calling, privacy sanitization. gonkalabs/opengnk

Gonkablocks

No-code AI tools platform on Gonka inference at blocks.gonka.gg. Pick a ready-made tool — Hive-Research, translator, summarizer, transcriber, and more — paste input, hit Run. No API keys, no registration, free for everyone.

Gonkavote.com

Pre-vote governance signaling tool at gonkavote.com. Gauge community sentiment on a proposal before it goes to on-chain vote. gonkalabs/prevote

G-Meter

Network performance metrics dashboard at meter.gonka.gg. Real-time latency, throughput, and health monitoring across the Gonka network. gonkalabs/gmeter

Feather

Lightweight, open-source Gonka RPC node anyone can run. Designed for low-resource hardware and self-hosted setups. gonkalabs/feather

Tx-Scanner

Open-source blockchain indexer that accumulates millions of Gonka transactions and serves them with sub-second API latency. Powers gonka.gg. gonkalabs/tx-scanner

Gonka Agent

Open-source agent toolkit for building autonomous workflows on top of Gonka inference. gonkalabs/gonka-agent

Contract Playground

Write, compile, simulate, and deploy CosmWasm smart contracts entirely in the browser. gonkalabs/wasm-cloud-compiler

GonkaClaw

One-command AI agent setup powered by Gonka inference. gonkalabs/gonkaclaw

Ready Set Gonka

Community project directory for the Gonka ecosystem at readysetgonka.com.

Gonka Restitution Committee (GRC)

Gonka Labs serves on the GRC — the community body investigating incidents where miners lost rewards and facilitating their restoration. We build open-source tooling for case intake, auditing, and resolution, and publish all findings publicly.

Miner Restitution · Open Audits · Community Work — GRC-intake-form, GRC-e267-kimi_shortfall, GRC-e247-preserver-audit

Built in the open

15 public repositories at github.com/gonkalabs — over 80% of our code. Inspect, fork, run, and contribute. The infrastructure powering the Gonka ecosystem is yours to audit.

Why This Proposal

Everything we've built so far has been self-funded. We've been running on personal savings and enthusiasm. That model works for prototypes — it doesn't work for enterprise infrastructure.

We built Gonka Labs products as non-commercial builders. No ads, no third-party product placement, no PR slots for sale. All current ecosystem products will remain non-commercial — just tools the ecosystem needs.

The Gonka ecosystem is growing. rpc.gonka.gg is the default Keplr wallet RPC. proxy.gonka.gg serves 1–2B inference tokens daily — and growing. gonka.gg is the biggest block explorer in Gonka, serving 5,000+ users daily — it is usually the primary entry point where new users first land when they want to understand or onboard into the Gonka network. The services are real, the load is real, and the quality bar needs to match. We want to:

  • Move to enterprise-grade reliability — SLAs, multi-provider failover, monitoring with on-call response, zero-downtime deployments.
  • Ship first-class mobile apps — Gonka App on iOS and Android, and beyond the wallet: a Gonka superapp that puts convenient Gonka services — wallet, governance, network data, and AI inference from any Gonka model — on the phone.
  • Build B2B-grade inference infrastructure — proxy.gonka.gg is already the #1 provider on Gonka by daily inference volume. Serving businesses at commercial scale takes a full commercial layer: analytics, org-level API management, multi-region presence, escrow tooling, and infrastructure refactored for commercial loads.
  • Grow the team sustainably — from 3 to up to 5 engineers, matched to actual production load.

We're not asking for money to start building — we're asking for money to keep building at a higher standard. The track record speaks for itself.

The Ask

70,000 USDT + 330,000 GNK 6 months of infra & ops / 180-day vesting

From the Gonka community pool · Subject to governance vote

Both components — USDT and GNK — are forward payment for work ahead, not payment for the past. The USDT covers 6 months of server infrastructure and operational costs. The GNK is the team's primary payment — vesting linearly over 180 days. Both are transparent and on-chain from day one.

This is the minimum for enterprise-grade infrastructure, service quality at the level we're committing to, and team payment for the work ahead.

Disbursement Mechanism

The proposal uses a two-component structure. The USDT portion is released immediately on approval to cover infrastructure and operations. The GNK portion vests linearly on-chain over 180 days — this is the team's primary payment for their work and directly aligns our incentives with the health of the network.

1. Half a year of infra and ops — 70,000 USDT

Released to Gonka Labs immediately after governance approval. Covers 6 months of bare-metal hosting (ClickHouse clusters, CDN, RPC node bandwidth), monitoring stack, operational expenses, and a portion allocated directly to the team as a guaranteed stablecoin payment for their work.

2. GNK locked in 180-day linear vesting — 330,000 GNK

Locked in vesting. Released over 180 days. This is the team's payment for future work — paid in GNK, vested, verifiable on-chain. The longer the network grows, the more our GNK payment is worth. That's the alignment.

Budget Breakdown

USDT — 70,000 USDT total

57% — Server Infrastructure — 40,000 USDT 6 months of bare-metal and cloud hosting: ClickHouse indexer clusters (270M+ transactions), CDN, RPC node bandwidth (rpc.gonka.gg), seriously refactored proxy.gonka.gg infrastructure to handle commercial loads, uptime monitoring, DDoS protection, SSL. These costs are fixed and non-negotiable for any production service.

43% — Development & Operations — 30,000 USDT CI/CD pipeline costs and build minutes. AI coding tools and subscriptions (used daily across the entire engineering workflow). Security scanning and vulnerability tooling. Load testing infrastructure for the proxy and RPC layers. Domain management, SSL, and certificate automation. Legal and compliance overhead. Community support tooling and documentation platform. Communications and project management for a distributed team over 6 months. App Store and Google Play developer accounts. A portion of this budget is allocated as a direct stablecoin payment to the engineering team — a small guaranteed base on top of GNK vesting, because we believe Gonka will thrive but we still have real bills.

Where the monthly USDT goes

70,000 USDT over 6 months is roughly 11,600 USDT per month. The majority covers infrastructure and operations. A portion of the 30,000 USDT Development & Operations budget goes directly to the engineering team as a guaranteed stablecoin payment — a small stable base on top of GNK. The rest funds the full dev and ops stack below:

Line Item Description
Servers & cloud (IaaS) Bare-metal and cloud compute for indexers, RPC nodes, and API backends. The biggest hidden line item is data egress — outbound traffic is billed per GB, and we serve 2M+ API requests per day.
Managed databases ClickHouse clusters with replication — 270M+ indexed transactions and growing daily. Storage, RAM, and query compute scale with the chain.
Network & CDN Cloudflare and edge caching in front of every public endpoint.
Security WAF, DDoS protection, SSL certificates, secrets management. Non-negotiable for services that wallets depend on.
Observability Uptime monitoring, alerting, log aggregation, error tracking. Quietly becomes the second-largest cloud expense in most production setups — ours included.
Development & DevOps GitHub organization, CI/CD runners, build and staging environments.
SaaS & operations Communication, helpdesk, mail, and productivity tooling for the team and community support.
Backups & disaster recovery Off-site snapshots of every database and config, with tested restores. Boring until the day it isn't.

GNK — 330,000 GNK (180-day linear vesting)

100% — Team Payment — 330,000 GNK Payment for the future work of Tim, Mike, and Artem over 180 days. Distributed in GNK with linear vesting. The GNK structure means our economic outcome is directly tied to network performance and ecosystem health — we win when Gonka wins.

Roadmap & Deliverables

Five core products hardened to enterprise grade. Six months. Plus two new products: G-Router — a multi-broker inference router (OpenRouter-style experience across all Gonka inference providers — a direct implementation of Track 2, Project 2 from the Gonka Network Development Roadmap) and MTD — Marketing Transparency Dashboard. Each product below has specific, concrete deliverables. This roadmap is not final — priorities will be re-evaluated with the community each month based on actual network needs.

rpc.gonka.gg — Multi-provider RPC aggregation & enterprise reliability

Gonka Roadmap: Track 4: Network reliability & observability · Track 8: Enterprise workloads

  • Already live — multi-provider load balancer aggregating all available Gonka RPC providers (6block, Hyperfusion, PS and others) behind a single rpc.gonka.gg address, with latency-based routing and automatic failover. Shipped ahead of this proposal in response to community issue #521: wallets keep working even when individual providers go offline.
  • gRPC & WebSocket full support — expand beyond HTTP/REST to cover all RPC surfaces that wallets and node operators use.
  • Geo-aware serving — route every request to the nearest healthy region so responses are fast regardless of where the requester is located.
  • Public SLA dashboard — uptime history per provider, latency percentiles (p50/p95/p99), incident log. Every metric publicly visible.
  • Open-sourcing the aggregation layer — publish the multi-provider router so anyone can audit it or run their own instance.

proxy.gonka.gg — B2B inference portal with analytics

Gonka Roadmap: Track 2: Developer & AI agent access · Track 11: Demand activation · Track 8: Enterprise workloads

  • Already live — business analytics portal, API key management, and the first round of performance optimization. proxy.gonka.gg is our product and is already #1 on Gonka by daily inference volume, serving 1–2B tokens per day.
  • B2B integrations are already happening — some non-public, like provisioning 100 API keys with 300M tokens each for a company to test Gonka at scale; and some public, like Integrity — an Israeli-American startup ("#1 Product of the Day" on Product Hunt, $1M+ raised) now running Gonka models in production beta.
  • Broker-level fixes for every integration — each B2B integration surfaces real issues at the broker level, and we solve them inside proxy.gonka.gg itself — payments, key provisioning, stability — so Gonka inference gets seriously utilized, not just demoed.
  • Go-to-market analytics system — a two-tier internal analytics layer built for distribution. Actors create UTM-tagged links (source, medium, campaign, content, referral term) to track any channel — Telegram, paid ads, influencers, partner integrations. Analysts get a dashboard with multi-dimensional filtering across all UTM dimensions and date ranges: unique visitors, first action conversion, requests by model with error-rate breakdowns, token consumption over time, and deposited funds. Every metric sliceable by any combination of UTM parameters. Powers referral programs, partner attribution, and campaign testing.
  • Multi-region deployment — geographic endpoints across EU, US, and CIS to cut round-trip latency for users and businesses worldwide.
  • Escrow monitoring utility — built into the product for easier escrow rotation when consuming Gonka inference at commercial scale.
  • Devshard proxy optimizations — reduce per-request overhead as commercial load keeps growing.

gonka.gg — V2.0 — new high-performance engine

Gonka Roadmap: Track 4: Network reliability & observability · Track 11: Demand activation

  • The Etherscan of Gonka — every V2 improvement serves one goal: making gonka.gg the leading explorer for the network, the default place everyone goes for on-chain data.
  • Pre-computed data pipeline — V2 puts more compute behind the explorer: heavy queries and analytics are pre-computed ahead of time instead of on demand, targeting 3–5× faster API responses under production load. We can finally afford the hardware to do it right.
  • Better UI — cleaner layouts, faster navigation, redesigned data views across the whole explorer.
  • Real-time WebSocket feeds — live block, transaction, and validator event streams. Currently everything is polled; V2 pushes updates the moment they land on-chain.
  • Improved GPU and inference metrics accuracy — current GPU history data has edge cases and gaps. V2 fixes the underlying data pipeline and adds full history backfill.
  • Mobile-responsive redesign — gonka.gg was built desktop-first. V2 is mobile-first with a rebuilt layout that works on all screen sizes.
  • Search improvements — cross-entity search (address, tx hash, block, validator, GNS name) from a single input, sub-50ms response time.

Gonka App — iOS & Android — a Gonka superapp

Gonka Roadmap: Track 2: Developer & AI agent access · Track 11: Demand activation

  • A superapp, not just a wallet — one app that puts convenient Gonka services on the phone: wallet, governance, GNS, network data. The mobile home for the entire ecosystem.
  • AI inference from your pocket — chat with any model on the Gonka network directly from the app. No API keys, no setup — just pick a model and go. The full power of Gonka inference, accessible to anyone with a phone.
  • Built with Expo — single codebase shipping to both the App Store and Google Play, with native modules where performance demands it.
  • Trust Wallet–level wallet — full feature parity with the Chrome extension and beyond: governance voting, GNS resolution, IBC transfers, dApp provider protocol.
  • Biometric authentication — Face ID / Touch ID on iOS, fingerprint on Android. Secure enclave key storage, never exposed in plaintext.
  • Push notifications — new governance proposals, transaction confirmations, GNS name expiry warnings. Opt-in per notification type.
  • WalletConnect support — connect to dApps from the mobile wallet, not just the browser extension.

Gonkavote — Governance tooling improvements

Gonka Roadmap: Track 12: Community coordination

Already live at gonkavote.com · open-source on GitHub. This proposal expands it further.

  • Historical governance analytics — full participation history for all past proposals: voter turnout, YES/NO/ABSTAIN breakdown over time, validator voting patterns. Currently this data is not available anywhere on the Gonka network.
  • Multi-wallet integration — sign and submit pre-vote signals from all major wallets, not just one.
  • Proposal tracking and notifications — follow specific proposals, get notified when voting opens, closes, or results are published.
  • Delegation-aware voting — show how much voting power is behind each signal, not just raw address counts.

GNS — Names marketplace & ecosystem deepening

Gonka Roadmap: Track 2: Developer & AI agent access

  • Public names marketplace — buy, sell, and transfer .gnk names between wallets on an open market. Names have real value: short names, brand names, and vanity addresses are already scarce. A marketplace makes that value liquid.
  • Scam labeling & safety layer — community-driven flagging of suspicious names and addresses, surfaced everywhere GNS is resolved: explorer, wallet, and dApps.
  • Deeper integration — GNS resolution in every product we touch: gonka.gg search, Gonka App send-to-name, governance profiles, and Gonkavote voter identity. Already officially integrated with hex.exchange.

Transparency — MTD — Marketing Transparency Dashboard

Gonka Roadmap: Track 11: Demand activation & ecosystem growth

  • Context — Gonka has seen 300k+ USDT worth of marketing proposals. The community has no unified way to track whether any of it delivered results. We will build the tool that changes that.
  • Deliverable tracker — every marketing initiative or proposal gets a public page: stated deliverables, deadlines, owner, and current status. Updates are timestamped and immutable.
  • Performance dashboard — key metrics per initiative: reach, engagement, on-chain activity correlated to campaign windows, and cost-per-outcome where measurable. No cherry-picking — all campaigns visible.
  • Open-source — the entire system is published on GitHub. Anyone can deploy it for their own Cosmos chain, verify the data pipeline, or propose improvements.

G-Router — Multi-broker Gonka inference router

Gonka Roadmap: Track 2, Project 2: Adapter for OpenRouter / aggregators — direct 1:1 implementation · Track 11: Demand activation

  • Context — right now, developers integrating Gonka inference must choose a specific provider manually (a devshard, a proxy, etc.). There is no unified routing layer. This creates friction, single points of failure, and prevents Gonka from appearing in OpenRouter-style aggregator directories — a major discovery channel for AI developers. Track 2, Project 2 of the Gonka Network Development Roadmap explicitly calls for this: "An adapter for OpenRouter and/or a similar routing aggregation layer."
  • Single unified endpoint — one API address that routes to the best available Gonka inference provider based on model availability, latency, and load. Developers never need to manage provider selection manually.
  • OpenAI-compatible API — drop-in replacement for any OpenAI-compatible SDK. Change one line: the base URL. Everything else — model names, streaming, function calling — works as-is.
  • Multi-provider load balancing — distribute traffic intelligently across all active Gonka inference providers. No single provider is a bottleneck or single point of failure.
  • Fallback and retry logic — if a provider returns an error or times out, the router transparently retries on another without the client ever seeing it.
  • OpenRouter listing — once stable, submit Gonka to OpenRouter as a provider. This unlocks access to thousands of developers who already use OpenRouter for model routing and discovery, without ever having heard of Gonka.

Roadmap is community-driven — and other products aren't abandoned

This list is a working draft. Every month we'll publish a progress report on GitHub Discussions and re-evaluate priorities based on community feedback and on-chain signals. If the network needs something more urgently, that's what gets built next. And if the community asks for something directly — the way they asked for the RPC aggregator, the block explorer, the faucet — we build it. That's always been how we work.

Gonkablocks, meter.gonka.gg, and every other project we've shipped will continue to receive bug fixes and maintenance. If any of them gains serious traction, it moves up the priority list — this proposal gives us the runway to act on those signals without scrambling for resources.

Team Growth

We started as three engineers and shipped 16+ products. Imagine what we can do with a larger team.

Current team (3): Tim, Mike, Artem — full-stack engineers who built everything from scratch.

Target team (3–5 by end of 2026): Up to two additional engineers — backend and mobile — to support growing infrastructure.

A larger team means faster iteration, better uptime, more products, and dedicated support for the community.

Accountability

We believe in transparency and accountability. Here's how we'll keep the community informed:

  • Monthly progress reports — public updates on GitHub Discussions detailing what we shipped, what we spent, and what's next.
  • Open-source everything — all new products maintain our 80%+ open-source commitment. Code is auditable at any time.
  • On-chain transparency — all GNK vesting is on-chain and verifiable by anyone. USDT payment is a single traceable transaction.
  • GNK vesting — 330,000 GNK in vesting over 180 days. Every release is visible and verifiable by anyone.

We're not asking you to trust us blindly — we're asking you to judge us by our work. We've shipped 16+ products in 6 months. The code is open. The metrics are real. And we're just getting started.

Your Vote Matters

This proposal can only move forward with your vote. Gonka is a decentralized network, and every decision about how community funds are spent belongs to the community.

Vote YES if: You believe Gonka Labs has demonstrated consistent value to the ecosystem and deserves continued funding to scale its impact.

Vote NO if: You think the ask is too high, the roadmap isn't convincing, or you'd prefer to see funds allocated differently. Your voice matters either way.

Voting is now live

On-chain voting for this proposal is open. View and vote on gonka.gg/network/proposals/74.

Vote Now · Proposal #74 on gonka.gg

Summary

Item Detail
USDT request 70,000 USDT (single payment)
GNK request 330,000 GNK (180-day linear vesting)
USDT breakdown 40,000 server infrastructure + 30,000 dev & ops
GNK breakdown Team payment, linear vesting over 180 days
Vesting transparency Public on-chain contract, verifiable by anyone
Focus products rpc.gonka.gg · proxy.gonka.gg · gonka.gg · Gonka App · Gonkavote
Duration 6 months (180 days from approval)
Decision Community governance vote

Reports

Gonka Labs — Monthly Report No.1 · Open as separate page

Дата публикации: 2026-07-18 18:31 UTC

Источник: Discussion #1477 — Gonka Labs - Monthly Report No.1

Hey! Gonka Labs here.

On June 12th the community passed Proposal #74. That vote funded the next stretch of work - infra, ops, and shipping products for the ecosystem.

This is the first public progress report we promised in the proposal (monthly updates on GitHub Discussions). Short version of what landed so far:

  1. OpenBroker - new product, live
  2. Pulse - new product, live
  3. gonka.gg - ~240 QA bugs closed + big product updates (devshards / inference, network analytics, mobile)
  4. proxy.gonka.gg - B2B inference proxy scaled hard + public status/analytics + DevShards v3
  5. Infra move - Whole infra migrated (explorer + indexer stack, all dbs, all backend, new frontend and analytics stack) onto the new production setup.

1. OpenBroker

We already announced the launch here: OpenBroker - broker for brokers or Devshards as a service (Jun 23).

Quick recap: OpenBroker is managed DevShards-as-a-service. Register, deposit GNK, get an obk-* key, point any OpenAI client at https://api.openbroker.gonka.gg/v1 (UI at https://openbroker.gonka.gg). No wallet whitelist dance, no running your own escrow rotation. GNK billing with no markup. Public stats at https://openbroker.gonka.gg/stats.

Since launch (numbers as of Jul 18)

  • 33 active brokers - 48 registered orgs

  • ~3.2GNK deposited into broker ledgers
  • ~15M requests logged in usage (~15M lifetime hits through the dual-gateway router)
  • ~11.8B tokens served (8.5 logged since migration) across MiniMax, Kimi, GLM, Qwen (usage window since early July; launch load test already pushed past 1B tokens in ~1 hour)
  • Peak observed throughput around ~100 req/s (busiest minutes ~5.7k req/min; busiest day ~1.06M requests)
  • DevShards v3 live on both production gateways - image mainnet-v0.2.13-v3-post1, route prefix /devshard/v3, 50/50 sticky split behind the router. OpenBroker was already on the v1/v2 path at launch; we completed the network-mandated v3 cutover ahead of the v0.2.14 deadline so brokers do not fall off when classic /v1/devshard goes away
  • Real brokers / relays already pointing parts or all traffic at OpenBroker (public org names): gonkarelay.com, Gonka24.com, Gonka-API.org, gate.joingonka.ai,Vitarum, etc, plus several private / internal accounts.

Ops + product work after launch

  • Moved production off the early Railway pilot (where we landed after Qupra DC issues in end of June) onto a dedicated server. Same public domains, more headroom under load
  • Dual-gateway HA with live traffic drain/switch (used for the v3 migrate - one gateway at a time, verify, then the other)
  • Broker dashboard: per-request usage, participant / redundancy attempt breakdown, cost reconciliation
  • New broker APIs: GET /v1/usage and GET /v1/usage/{id} so integrators can pull request-level cost/token data without scraping the UI
  • Hardening under real load (connection pooling to the gateway router, escrow rotation / capacity ops, model-aware capacity after governance model changes)

Feedback thread (git discussions)

Thanks for the sharp measurements. Where we landed so far:

  • Billing / hung requests - usage logging + GET /v1/usage/{id} so you can see whether a request settled, what tokens/cost we recorded, and the FinalCost snapshot when the gateway returns it
  • /v1/models /v1/models /v1/models - still on the polish list (model ids are also in docs / 400 text); not blocking chat completions
  • ~10s fixed overhead - largely protocol / escrow path (block times), not OpenBroker markup. Dual gateways + v3 cutover keep us on the current network path; further shaving depends on protocol-side escrow UX
  • Large-prompt hang band - treated as a gateway/host-path issue; we keep feeding failure modes back to core while brokers route production traffic through us

OpenBroker is also doing what the launch post promised: shake out new DevShard versions at production scale. v3 on our gateways was exactly that - migrate, smoke /devshard/v3, keep MiniMax brokers online through the cutover.

Links:

2. Pulse

Pulse is the live media + sentiment dashboard for Gonka (see it as a backbone and a part of proposal item named MTD / Marketing Transparency Dashboard - we shipped essential part that does data gathering first). It pulls public Gonka coverage from X, Instagram, YouTube, and the web into one place, scores tone via Gonka LLMs (proxy.gonka.gg), and shows activity / reach / engagement next to GNK market data. Built so anyone can see what the ecosystem is saying without opening ten tabs.

Live: https://pulse.gonka.gg

What shipped

  • Full Pulse app on Railway (API + web + Postgres), collectors on a ~2h cadence
  • Sources: X, Instagram, YouTube, curated web / press
  • Dashboard: last-24h activity / reach / engagement charts, general sentiment gauge + 14-day tone chart, GNK market (Uniswap v3 + HEX OTC), market Fear & Greed, top creators, content feed, EN + RU ui translations
  • Sentiment analysis runs on LLMs running in Gonka (same network we all are building for) - not a closed SaaS LLM
  • Embedded on the gonka.gg homepage (sentiment, Fear & Greed, latest news, link out to Pulse)
  • Public read API for stats / market / feed / news / creators so gonka.gg and others can reuse the data. Some dashboards are already ingesting it alongside basic network info.

Numbers (as of Jul 18)

  • ~2,600 posts indexed
  • ~11.9M total reach and ~149K engagement across indexed content
  • Sentiment: 100% of indexed items analyzed (latest daily reading in the mid-50s / Neutral)
  • Last 24h snapshot (volatile): ~43 new posts, ~784K reach gained, ~4.5K engagement gained

Why this matters

Proposal #74 called out demand activation and making Gonka easier to follow for non-technical users. Pulse is a part of that "transparency layer" - a public pulse of coverage, tone, and creators, wired into gonka.gg and backed by Networks collective inference stack.

3. gonka.gg - bugs + product work

Explorer side of the proposal was "gonka.gg V2.0" - faster engine, better UI, mobile, accurate GPU/inference metrics. We are not done with that part of roadmap yet, but a lot of the painful day-to-day stuff is already fixed and several new surfaces shipped.

QA bug smash (~240)

We ran a dedicated desktop + mobile QA pass with an external unbiased audit, and closed on the order of ~240 tracker bugs (desktop tracker version into the 170s, mobile into the 60s - still an ongoing flow since we ship new features that are getting QA tested as well).

Rough shape of what that covered:

  • Mobile layouts and basic UX reorganizations
  • charts, maps, tooltips escaping the viewport on touch
  • table, card alignments, repositionings, restructuring
  • status badges, filters, i18n gaps
  • reward / weight tooltips and incomplete-epoch edge cases
  • block / tx / wallet polish
  • Updated indexers (28k less load on the network)
  • Devshards V3 flow alignment for inference data ingestion
  • A lot of backend work to make page load time go down

Shipped across a long streak of QA PRs and multiple levels of sanity checks. Not glamorous, but this is the difference between "works for some people" and "works for 70% of 10k+ people a day on phones".

Product / data updates on gonka.gg (since the vote)

Inference after DevShards (v0.2.12+)

  • Built and run a dedicated devshard-poller that ingests off-chain session diffs into ClickHouse (the chain no longer emits per-inference txs the old way) and is properly aligned with V3 flow, and is optimized to not make heavy load for the network (overall produced load caused by data ingestion went down X27k).
  • /network/inference (Inference tab) is driven from that pipeline - 24h stats, gateway traffic, timelines.
  • Added DevShards v3 support in the poller (v2 and v3 coexist on hosts during migration; we probe /devshard/v3 and union live shard inventories so traffic does not silently drop when gateways switch).

Network analytics

  • Model Weight Share on /network - weight distribution across AI models per epoch, with an all-epochs view (Redis-cached so it stays fast).
  • GPU / reward-per-weight chart polish for in-progress epochs.
  • Live Devshard flow tightened to recent epochs so the UI stays honest under load.

Token holders

  • Supply fetch fallbacks when LCD nodes flake.
  • Prune stale holder rows so rankings do not keep wallets that dropped under the qualification threshold.

Infra behind the explorer (also see section 4)

  • Proper Frontend serving with lowest ttfb possible, API with horizontal auto-scaling, archive ClickHouse + tx-scanner + devshard-poller on dedicated server.
  • Continuous deploys for explorer fixes without taking the archive down.

Explorer: https://gonka.gg
Inference: https://gonka.gg/network/inference
Network: https://gonka.gg/network

Why it matters

Faster deploys, less risk of a bugfix taking down indexing, room to run the heavier pre-compute work from the V2 explorer roadmap.

4. proxy.gonka.gg - B2B inference + public status

proxy.gonka.gg is our OpenAI-compatible inference proxy on top of Gonka DevShards - API keys, balances, usage, docs, chat playground. Public API at https://api.proxy.gonka.gg/v1. Pulse (and other Gonka Labs apps) call the same stack for LLM work, so when we harden the proxy we harden half the product surface too.

Numbers (as of Jul 18)

Measured window below is since the Jul 4 dedicated-server migrate (usage DB moved with the stack - earlier Railway and even earlier Qupra DC history is not in this series). The product itself was already live before Proposal #74.

  • ~29.0B tokens served (~5.2M requests, ~96.8% OK)
  • ~23.6B tokens in the last 7 days (~3.5M requests)
  • ~7.3B tokens in the last 24 hours (~1.1M requests)
  • Peak recent days ~4.8-5.0B tokens / day; peak hour observed ~823M tokens in a single hour (~270k requests)
  • Model mix (token share): MiniMax-M2.7 ~25.6B, Kimi-K2.6 ~3.4B, plus residual Qwen / other
  • Accounts: +10-30 new accounts daily.

What shipped since the vote

  • Dedicated production box for the API (api.proxy.gonka.gg) - moved off the flaky VPS / and too unreliable Railway path onto a tuned server with local Postgres, own DevShard gateway, Proxy edge for the API. Frontend stays on other host at proxy.gonka.gg with rewrites into the API.
  • Own DevShard gateway ops - escrow rotation, capacity-aware concurrency limits, admin tooling. Gateway now on DevShards v3 (mainnet-v0.2.13-v3-post1, route /devshard/v3) ahead of the network v0.2.14 deadline - blue/green cutover with a temp gateway + drain so in-flight MiniMax traffic survived the switch. Currently 32+32 (64 inflight escrows) active v3 escrows (MiniMax + Kimi)
  • Public status / analytics page at https://proxy.gonka.gg/status - aggregate capacity %, load, in-flight vs cap, active shards, network participant counts, error-rate history + reason breakdown. Deliberately no escrow ids / host IPs (safe to share with customers)
  • Usage honesty - requested-vs-served model on usage logs when fallback fires, so dashboards show what the client asked for and what actually ran
  • Product surface kept current for B2B: models page, docs, partner paths, top-up flows, password reset, etc. (dashboard UX work continued alongside the infra move)

Why it matters

Proposal #74 called out proxy.gonka.gg as the B2B / analytics lane. This stretch was less "new landing page" and more "make the pipe carry real load": multi-billion token days, a public status surface customers can trust, and staying on the current DevShard protocol so keys do not die when classic /v1/devshard goes away. Same gateway lessons feed OpenBroker - one network path. More "b2b" work ahead.

Links:

We are still heads-down on the rest of the Proposal #74 checklist - hardening infra under real load, polishing what already shipped, and building the next products on the list. More updates as they land. Stay tuned.

Feedback welcome in the thread - what should we prioritize next month from the proposal list?

Gonka Labs — Monthly Report No.2 · Open as separate page

Дата публикации: 2026-08-19

Источник: PTD — Report #740002

Gonka Labs Monthly Progress Report No.2

Сегодня мы публикуем наш второй ежемесячный отчет о проделанной работе за отчетный период (с 18.07 по 19.08) в рамках proposal #74 по развитию инфраструктуры Gonka Labs и запуску новых продуктов.

Краткое саммари:

  1. proxy.gonka.gg продолжает развиваться и удерживает роль лидирующего провайдера Gonka AI. Мы внедрили полноценные рабочие пространства: появились Chat, Docs, Slides и Sheets, поддержку MCP и загрузку файлов, а также новую модель — DeepSeek. За отчётный период через Proxy прошло более 60 млрд токенов, зарегистрировалось более 3 тыс. новых пользователей.

  2. OpenBroker получил поддержку DeepSeek на обоих production-шлюзах, автоматическое пополнение escrow, обновления биллинга и пользовательского интерфейса. За месяц сервис обработал более 50 млрд токенов, а число зарегистрированных брокеров выросло до 70.

  3. Запущен новый продукт PTD — Proposal Transparency Dashboard. Он собирает прошедшие ончейн-предложения и позволяет командам публиковать задачи, обновления и отчёты по профинансированным инициативам. Читать материалы можно без регистрации.

  4. Мы продолжаем активную работу и развитие Gonka.gg: появились карта распределения держателей, расширенные метрики аккаунтов и транзакций. Исправили ряд неточностей в GPU- и inference-метриках, вернули live-карту инференса, завершили китайскую локализацию и улучшили мобильную версию.

  5. В Pulse были интегрированы Reddit и TikTok, аналитика сентимента Telegram-сообществ, улучшена фильтрация нерелевантного контента. На данный момент платформа проиндексировала более 3 тыс. публикаций, связанных с Gonka, с суммарным охватом свыше 11,4 млн просмотров.

  6. Для rpc.gonka.gg был запущен публичный gRPC, архивная инфраструктура перенесена на новые серверы и повышена общая устойчивость — максимально гладко, без остановки работы кошельков и Explorer.

  7. В G-Meter добавили мониторинг DeepSeek и OpenBroker, улучшили сравнение провайдеров, отображение цен, AI summary и мобильный интерфейс.

Полный отчет доступен по ссылке: https://ptd.gonka.gg/reports/74#report-740002

Благодаря фидбеку от комьюнити, мы продолжаем работу над улучшением текущих продуктов и новыми приоритетными направлениями, важными для развития экосистемы Gonka.

Спасибо за внимание!

С уважением, Команда Gonka Labs

Чат: @gonka_gg Анонсы: @gonkalabs Все сервисы: https://gonkalabs.com

Gonka Labs — Monthly Report No.3 · Open as separate page

Дата публикации: 2026-09-19

Источник: Discussion #1815 — Gonka Labs - Monthly Report No.3

Proposal #74: Gonka Labs - Monthly Report No.3

image

Hey! Gonka Labs here.

Last updates: Report No.1 (Jul 18) and Report No.2 (Aug 18).

On June 12 the community passed Proposal #74 (full text). That vote funded six months of infra, ops, and product work. This report is month 3 of 6 - about halfway through the window we raised for.

Report #1 was launches (OpenBroker, Pulse) plus the explorer QA / inference pass and the proxy box move. Report #2 was Workspaces, PTD, holders / inference honesty, DeepSeek, rpc gRPC. This one is what landed since Aug 18.

Short version since Aug 18:

  • 300.000.000.000 (300B) tokens processed by Proxy and OpenBroker in a month.
  • gonka.gg - homepage AI Tokens widget, participants show this epoch's nodes, proposals list/detail + Featured widget actually renders, wallet heatmap opens the day's txs, IBC holder channels, /snap, tx share cards
  • proxy.gonka.gg - GLM on the pipe, v4.1 path, persist-through-rate-limits, OAuth login, file ingest now $0, 171B+ tokens in a month
  • OpenBroker - DevShards v4.1, GLM live, public /status, cabinet escrow line, 129B+ tokens in a month
  • Pulse - chart units, sentiment faces (not Fear & Greed), news mix, catch-up without a fake 24h spike. 4.3k posts / 28.4M reach as of Sep 19
  • rpc.gonka.gg - wallet JSON-RPC failover (one 503 no longer blanks GG Wallet / Keplr balances), honest health checks, second phone pass on the site
  • PTD - Report #2 hosted on PTD itself, a proposal page lists every report (not only the latest), markdown + screenshots actually render
  • G-Meter - eterial.ai in the probe set, GLM-5.3 Flash as the new active model, compare uses the cheapest Gonka rate (not the average)
  • Gonka Chat - new product, live. Wallet-to-wallet mailbox (GG Wallet / Keplr). DMs, groups, channels, invites / replies / mentions. Message button + unread badge on gonka.gg wallet pages
  • x402 - new product, live. Public facilitator at x402.gonka.gg. Agents / apps pay an HTTP route in GNK or bridged USDC. No accounts, no API keys. Source on GitHub.

1. gonka.gg

Explorer side of the proposal is still "V2.0": faster, honest numbers, usable on a phone. Report #1 closed the big QA pile and stood up inference after DevShards. Report #2 added holders charts / bubble map, Confirmed/All on the inference tab, Chinese, a phone pass.

This month is smaller surfaces that people actually click, plus a few numbers that were still lying.

Homepage - AI Tokens

The four growth cards on the home page include AI Tokens. Click it: chart modal, Confirmed / All, 10 / 30 / 90 days / All, jump to the Inference page.

Same rules as /network/inference (and the same ClickHouse feed the poller writes):

  • Confirmed (default) - billed tokens after finish: actual in + actual out
  • All - Confirmed plus claimed prompt size on Gonka Labs requests that are accepted but not finished yet
  • We do not pour other brokers' unfinished claimed / STARTED / heartbeat probes into All. That pile is synthetic and would smear gateway shares (same reason Dahl drops synthetics before counting tokens)

Widget number is the last 24 hours. Chart is UTC days; last point is that same 24h number so hover matches the card. Y-axis is compact (7.5B, not 7,500,000,000 clipped off the left).

Participants

Expand a row on /network/participants (All / current epoch). You get this epoch's ML nodes, not last epoch's confirmation list. Hosts that added a node after confirmation were missing it in the table. Weight on the list follows the live epoch the same way.

Proposals

  • Featured Proposals on the homepage was not rendering. It does now.
  • /network/proposals list + detail restyle (chips, vote strip). Titles wrap on a phone instead of getting cut.
  • Prevote tab dropped from this surface.
  • Finished proposals stay put (no live-tally flicker after the vote ended).

Wallets / holders / calculator

  • Wallet activity heatmap: click a day, see that day's transactions (not only a hover count).
  • Holders: IBC balances by channel on hover; IBC grouping so one wallet is not split into junk rows.
  • Reward calculator: minus amounts display correctly; HEX sell price on the USD hint.

Other

  • Gateway Traffic tooltip on the inference tab rewritten for the public page (no internal notes).
  • gonka.gg/snap - landing for the GG Wallet MetaMask snap.
  • Share a tx link and the card now has a short summary (not a blank title). Example: 0634bfaf…

Links: Explorer · Inference · Participants · Proposals · Holders

2. proxy.gonka.gg

Report #1 was the dedicated-box migrate, public /status, DevShards v3. Report #2 was Workspaces, MCP in chat, DeepSeek, and the agent/tool-schema repairs. This month is the next protocol step, a fourth model, a status page you can send to a customer without lying, and a couple of settings that stop common client 400s / 429s.

Quick recap: OpenAI-compatible proxy on Gonka DevShards. Keys, balances, usage, Workspaces. Public API at https://api.proxy.gonka.gg/v1. UI at https://proxy.gonka.gg. Status at https://proxy.gonka.gg/status.

Numbers (since Aug 18 / as of Sep 18):

  • 171B tokens in a month
  • Peak day ~10.2B tokens
  • +2k users

What shipped

Serving path moved onto DevShards v4.1. Same public URL. Keys did not have to rotate. Same job as the v3 cutover in report #1: stay on the protocol the network actually runs.

GLM-5.3-Flash came on (zai-org/GLM-5.3-Flash). Docs, /status, and the models page list it. Public /v1/models still only lists a model when the live pool can take it, so a quiet GLM hour can drop the id off that list. That is pool state, not a delist.

Public status got an honesty pass: incoming vs served, host 429s vs our own errors, in-flight vs cap, confirmation PoC when hosts leave inference mid-epoch. Incoming is a thin line so an over-capacity band does not paint the whole chart red. Kimi is off that page - it still accepts tools and then returns no tool_calls, which is a capability miss, not a Proxy outage.

We raised concurrency caps on the live gateway. DeepSeek was sitting on our own in-flight ceiling, not on empty network weight. After the bump, the concurrent-429 pile mostly went away. Caps help until you push past what hosts will take.

Persist through rate limits is a Settings toggle (off by default). Hosts still return too many concurrent requests (24/24) when every slot is full. With the toggle on, the proxy keeps that request open and retries under the hood for up to two minutes. You should almost always get a response; it may just take longer. API and Chat.

DeepSeek reasoning compatibility (off by default): official reasoning_effort / thinking: {type: enabled} get mapped onto what the hosts actually honor, so reasoning_content comes back instead of leaking into content and breaking tool harnesses.

MCP on the API, not only in Chat. Opt-in in Settings. /v1/chat/completions can list and run remote HTTPS MCP tools and return the final answer. Local npx/stdio stays in the client.

Login with proxy.gonka.gg shipped: OAuth 2.0 Authorization Code + PKCE, consent screen, scopes profile / usage / api_key. Client registration is manual. We mint a fresh revocable key for that connection; we never hand out an existing user key. Docs: https://proxy.gonka.gg/docs#login. Settings has a Connected Apps row so you can revoke it.

Also this window: public models page (context, tools, reasoning, live rates), shareable Workspace URLs.

File ingest is free now - no separate attachment line. Docs (md / txt / csv / html / pdf / docx / xlsx / odt / ods) are $0. Images are $0 inside the account caps (5 files per request, 20/min, 200/day). Settings → File ingestion has the toggle and the remaining quota. MCP in chat and web search (chat + API) stay $0. Inference is still the network rate.

Links: Product · API · Status · Models · Workspaces · Docs

3. OpenBroker

Launch was discussion #1363 and Report #1. Report #2 already had DeepSeek on both gateways, refill-to-target, deposit copy, and password reset. This month is the next protocol step, a new model, and a public status page brokers can actually send to customers.

Quick recap: OpenBroker is managed DevShards-as-a-service. Register, deposit GNK, get an obk-* key, point any OpenAI client at https://api.openbroker.gonka.gg/v1 (UI at https://openbroker.gonka.gg). GNK billing with no markup. Public stats at https://openbroker.gonka.gg/stats.

https://openbroker.gonka.gg · https://api.openbroker.gonka.gg/v1 · https://openbroker.gonka.gg/stats · https://openbroker.gonka.gg/status

Numbers (as of Sep 18):

  • ~129B tokens and ~32M requests in a month
  • Peak day ~7.1B tokens (Sep 12)
  • Last 7 days: ~30B tokens / ~8.9M requests
  • Last 24h: ~2.7B tokens / ~1.0M requests
  • Mix in that window: DeepSeek ~95B, MiniMax ~26B, Kimi ~3.3B, GLM ~1.9B (GLM only came on late)
  • Brokers: 142 registered (was 70 on Aug 18) - +74 signups since report #2. 77 active ledgers, 65 still pending first deposit
  • Live pools: 40 MiniMax / 40 DeepSeek / 24 GLM shards on the current path

What shipped

Serving path moved onto official DevShards v4.1 (/devshard/v4.1). Same public URL. Brokers did not have to rotate keys. That is the same job as the v3 cutover in report #1: stay on the protocol the network actually runs.

GLM-5.3-Flash is live (zai-org/GLM-5.3-Flash). Docs, /v1/models, maintainer targets, and the status page all list it. Public lineup right now is MiniMax, DeepSeek, and GLM.

Public status shipped: incoming vs served, error rate by model, reason breakdown, in-flight vs cap, shard counts. No host IPs, no escrow ids. Incoming is drawn as a thin gray line so an over-capacity band does not look like the whole chart is on fire. When the network is in confirmation PoC, capacity drops on the same page - that is hosts leaving inference, not OpenBroker going dark.

We raised concurrency and token caps on the live gateway, and lifted escrow targets (DeepSeek 22 to 40, GLM 12 to 24, MiniMax stays 40). DeepSeek was sitting on our own in-flight ceiling, not on empty network weight. Caps help until you push past what hosts will take - the gateway scales itself down if you get greedy, so we stopped there.

Register: you cannot jump to the OTP step with a password under 8 characters. The API already rejected it; the form was sending the email anyway.

Cabinet got a desktop / phone pass. Billing now shows the network cost of opening new escrows we raise for traffic, plus leftover lock only on shards we cannot settle back on-chain. If an escrow settles, the remainder is not billed - that line is Epoch escrow, split by your share of successful tokens that epoch. Inference is still no markup; the cabinet just stopped hiding those network fees. Updates also go to t.me/openbroker_gg. Docs: https://openbroker.gonka.gg/docs.

Still the same promise as the launch post: run new DevShard versions and new models at production scale so relays do not find the bugs first.

Links: Product · API · Stats · Status · Docs · Register · Launch

4. Pulse

Report #1 launched it (X / Instagram / YouTube / web + sentiment on Gonka LLMs). Report #2 added Reddit, TikTok, Telegram, and the "What people are saying" digest. This month is less new sources and more "can you read the board without guessing."

Live: https://pulse.gonka.gg

Numbers (as of Sep 19):

  • 4,348 posts indexed (was 3k+ on Aug 18)
  • 28.4M total reach · 232K engagement (was 11.4M / 129K)
  • Sentiment: still 100% analyzed. Latest reading 75 (was ~65)
  • Last 24h (volatile): 22 posts, ~491K reach, 414 engagement
  • Sources same as #2: X · YouTube · Instagram · web · TikTok · Reddit, plus Telegram / discourse on the side

What shipped

The big chart numbers used to be bare digits. People had to guess if 13.2K was views or posts. Activity / reach / engagement now say posts, views, engagements. Sentiment chart says index.

General sentiment gauge got sad / happy faces on the ends so it does not look like the market Fear & Greed widget sitting next to it. Dropped the "N items analyzed" line under the gauge - it was just repeating the hero count.

In the news: one publisher's weekly digest was eating the list. We still keep a couple of those posts. The rest of the slots go to other outlets (Product Science, Coin Edition, BlockchainReporter, etc.).

Founder / investor X timelines (official accounts + BitfuryGeorge) get a deeper pull. Top Creators was overweight a single viral clip.

If collectors miss a stretch, the next run updates stored view counts. It does not dump weeks of growth onto today's 24h chart. That is how you get a fake spike.

Same public read API as before (stats / feed / news / creators / telegram / discourse). Sentiment still runs on Gonka inference via proxy.gonka.gg.

Links: Pulse

5. rpc.gonka.gg

Public RPC / LCD gateway. Still free, no key required. Report #2 already had gRPC on rpc.gonka.gg:9090, the live-host cutover, archive + indexer move, Feather drain/restore, /health that does not hang on a dead sub-service, and the first mobile pass.

This month the wallets broke. Then we fixed the path they actually use.

https://rpc.gonka.gg · https://rpc.gonka.gg/endpoints · https://rpc.gonka.gg/health

What shipped

GG Wallet, Keplr, and CosmJS POST CometBFT JSON-RPC (status, abci_query) to /chain-rpc/. That is a different pool than the GET Feather path. Mid-September one community backend started answering 503. The gateway forwarded the first 503 and never tried the next node. Balances went blank even though other backends were fine.

Pool now walks every backend on 502/503/504 before it fails. broadcast_tx 500 is still not retried - we do not want a double submit. Health checks for that pool look at the real JSON-RPC status path, not a webpage that is always 200.

Phone: second layout pass on the landing / health pages after a screenshot that was still ugly (hero buttons, "how traffic flows" stack, Powered-by cards).

As of Sep 19 public /health shows 5 backends up (2 Feather + community). Same docs, same optional /access key if you want usage tracking. gRPC still rpc.gonka.gg:9090.

Geo-aware routing from the proposal list is still open. Failover and the public health page are what we spent this window on.

Links: Gateway · Docs · Health · gRPC: rpc.gonka.gg:9090 · Access (optional)

6. PTD

Proposal text called this MTD. We shipped it as PTD. Report #1 was Pulse (the media slice). Report #2 launched the dashboard: claim a passed proposal, tasks, append-only updates, Core GitHub reports ingested for claimed and unclaimed pages. This month is the report surface, not a second product.

Live: https://ptd.gonka.gg · https://ptd.gonka.gg/reports · https://ptd.gonka.gg/reports/74

What shipped

Report #2 went up on PTD on Aug 19 (/reports/74). Same public report URL as everyone else. No login. GitHub Discussions still has the thread (#1612); PTD is the copy you can share if you only want the dashboard.

A proposal page used to show one ingested thread. It now lists every report for that id, newest first. #74 shows No.2 on top and No.1 under it. Cards on the home strip and /reports jump to the right report (#report-…).

Bodies can start with a screenshot (<img>) and still parse as markdown. First time we posted #2 that way, headings / bold / links printed as raw ** and ##. Fixed the same day.

Core ingest is still the same path as report #2. As of Sep 19 the public list also has #82, #77, #51, plus both #74 reports. We did not add a separate MTD app this window.

Links: PTD · Reports · Proposal #74 reports · GitHub source

7. G-Meter

Report #2 already had DeepSeek and OpenBroker in the probe lineup, plus the AI status notes. This month is a new broker, a new active model, and a couple of honesty / speed fixes on the public page.

Live: https://meter.gonka.gg

As of Sep 19: 11 brokers on the dashboard (eterial.ai is the new one). Active models we probe: MiniMax M2.7, DeepSeek V4 Flash, GLM-5.3 Flash. Kimi is marked deprecated - the network dropped it as a PoC model. GLM-5.2 stays optional.

What shipped

eterial.ai added to the monitored set. Same checks as everyone else: uptime, latency, price, limits.

GLM-5.3 Flash is in the active lineup (catalog, probes, compare, Limits). Limits used to hide a model until the hourly run finished; now a newly added model shows up as "not measured" instead of missing.

Compare / price ladders use the lowest Gonka broker rate, not the average. That was making Gonka look more expensive than the cheapest public quote.

Dashboard loads faster - we stopped pulling the heavy live-price payload on every home-page refresh.

proxy.gonka.gg probes now hit the API host, not the marketing site. Those checks were failing for the wrong reason.

Links: Dashboard · Compare · Get started

8. Gonka Chat

New product this window. Not on the original five-item list - same extra-ship pattern as OpenBroker and Pulse in report #1.

Gonka Chat is a mailbox for Gonka wallets. Connect GG Wallet or Keplr, then write any gonka1 address or .gnk name. No gas. Identity is the address; a name is optional. Messages and files encrypt in the browser before they leave. If the other side has not opened Chat yet, they can still read after they sign in.

Live: https://chat.gonka.gg

What shipped (late August through mid-September)

  • Direct chats, groups, and channels (share a handle like @squad)
  • Files, replies, @mentions (a person or the whole room)
  • Invite flow: add-to-room creates an invite in their inbox. The room does not show up until they hit Join. Open invites sit in Incoming Invites
  • Push notifications are less flaky
  • UI pass on the open-chat window, new-chat flow, and phone layout
  • First-run safety note; a Labs system note in the inbox is read-only so it does not look like a random DM you can argue with
  • Public unread count (GET /api/<address>/count) so explorer wallet pages can show Message plus a badge. Click goes to Chat.

Numbers (as of Sep 18)

  • First wallets signed in Aug 28
  • 49 signed-in wallets · 76 devices
  • Rooms: 29 DMs, 53 groups, 42 channels
  • 225 live messages (not counting one-time Labs notes)
  • 5 wallets active in the last 7 days

Still early. The point this month was to get a real mailbox on the same identity people already use on gonka.gg, not a second login.

Links: Chat · App · wallet pages on gonka.gg already have the Message control

9. x402

New product this window. Not on the original five-item list - same extra-ship pattern as OpenBroker, Pulse, and Chat.

x402 is an HTTP payment standard for agents. Coinbase started it; the x402 Foundation under the Linux Foundation runs it now. Usual story on other networks: agent hits a URL, gets 402 Payment Required, pays a USDC micropayment in the same request, gets the resource. No signup, no API key, no checkout page.

Gonka did not have that rail. We shipped a public facilitator so the same flow works here, in native GNK or Ethereum-bridged Circle USDC.

Live: https://x402.gonka.gg Source: https://github.com/gonkalabs/x402-gonka

Quick wording, because this sentence gets read wrong: "agents settle on Gonka" does not mean the agent is hosted on the chain. An agent is just a program. What it means is they pay for a product that accepts GNK or USDC on Gonka.

What shipped (late August through early September)

  • Public facilitator: /supported, /verify, /settle, /discovery/resources, paid /demo
  • Docs on the same host (EN / RU / ZH): get started, sellers, CLI, protocol, HTTP API
  • CLI in the repo: pay (sign locally, retry with PAYMENT-SIGNATURE), keygen, serve
  • GNK (ngonka, 9 decimals, MsgSend) and bridged USDC (CW-20, 6 decimals, contract transfer)
  • x402 v2, network cosmos:gonka-mainnet, scheme exact, transfer signed-tx, flow upfront
  • Open source on GitHub (Sep 3). git clone + go run

How it works, short:

  1. Client hits a paid URL.
  2. Server answers 402 with network, asset, amount, payTo.
  3. Client signs a Gonka transfer and retries with PAYMENT-SIGNATURE.
  4. Seller calls POST /settle here. Tx goes on-chain. Then the resource is served, plus a PAYMENT-RESPONSE with the hash.

Settlement is upfront: money moves first. The client signs the full tx. We only broadcast. We do not hold funds.

Sellers do not talk to the chain themselves. Return 402 with your accepts, then POST /settle on x402.gonka.gg after the client retries. Same hook for a shop, another agent, or a broker that wants agents to buy from it.

As of Sep 19: /health is ok, /demo still returns HTTP 402 with GNK + USDC accepts. One live GNK pay already landed.
Paid /demo · 1000 ngonka (0.000001 GNK)
Payer gonka150c4lsmsdr23vly466lskajkfhqh7eghmyjern
Height 5745133 · code 0
Tx 23B76D1281F9EFCC7AFC90659480CF3219A7099959C0513720769F700E9B73B2 
git clone https://github.com/gonkalabs/x402-gonka.git
cd x402-gonka
go run ./cmd/x402-gonka pay --key "$GONKA_PRIVATE_KEY" --url https://x402.gonka.gg/demo

The key stays on the signer. For USDC add --asset usdc. We did not publish a USDC settle in this window - the path is there; the proof tx above is GNK.

Still early. The point this month was to put the rail on Gonka, not to wire every Labs API behind it yet.

Links: Product / docs · Get started · Sellers · Source

Proposal checklist

Keeping the proposal list honest. Status is halfway (month 3 / 6).

Item Status Notes
gonka.gg V2 (engine, mobile, inference accuracy) in progress Inference + holders in #1/#2. This month: AI Tokens widget, current-epoch nodes, proposals UX, wallet heatmap, IBC holders, /snap, tx share cards. More V2 still open.
proxy.gonka.gg B2B / analytics in progress GLM, v4.1, status honesty, persist retries, OAuth login, file ingest $0. 171B tokens / +2k users since #2
rpc.gonka.gg geo / SLA / aggregator in progress Aggregation + public /health already live. This month: wallet POST failover + honest JSON-RPC probes. Geo routing still open.
OpenBroker shipped / ongoing v4.1 path, GLM, public /status, cabinet Epoch escrow line. 77 active / 142 registered; ~129B tokens since report #2
Pulse shipped / ongoing Live since #1. This month: units on charts, sentiment vs F&G, news mix, catch-up without a 24h spike. 4.3k posts / 28.4M reach as of Sep 19
PTD (proposal item: MTD) shipped / ongoing Pulse = media, PTD = governance. Live in #2. This month: host reports on PTD, stack all reports per proposal, markdown + screenshots render. No second MTD app.
Gonka App iOS/Android [FILL] [FILL]
Gonkavote expansions [FILL] [FILL]
GNS marketplace / scam labels [FILL] [FILL]
G-Router [FILL] [FILL]
Gonka Chat (extra) shipped / early New this window. Wallet mailbox at chat.gonka.gg. Invites / replies / mentions / push. 49 wallets / 225 live msgs as of Sep 18. Explorer Message + unread badge.
x402 (extra) shipped / early New this window. Public facilitator at x402.gonka.gg. GNK + bridged USDC. Open source Sep 3. Live GNK /demo settle.

Still in the second half of the six months: harden what is live, finish the checklist items that are not. Next report around mid-October.

Feedback in the thread is fine - what should we push in the second half from the proposal list?