Skip to content

Repository files navigation

External Test Lab & Community DevNet

Community-owned testing function for the Gonka network: protocol upgrades, DevShards, inference flows, host/broker operations, and geographically distributed network behavior — validated before governance decisions and production rollout.

This repository hosts the public artifacts of the 4-month pilot approved by Gonka governance.

Key links

Proposal discussion gonka-ai/gonka#1388
Governance proposal #82 — passed 2026-07-10
Escrow contract (funds) gonka1g57f45qjvn0529vpgj8x8mzt8r5k4audchm3pp9pezywxwf4rexqlj8ayw
Escrow source & verification paranjko/testlab-devnet-escrow
Issue tracker Issues — defects, validation requests, DevNet access
Task board Gonka External Test Lab — planned, active, and completed work
DevNet status & dashboards gonka-dev.net · grafana.gonka-dev.net
Security reports See SECURITY.mddo not open public issues for vulnerabilities

What is being built

Component Purpose
Community DevNet Small always-on geographically distributed network for protocol, node, DevShard, and operational testing. Hosts connecting their own nodes are welcome.
Burst GPU testing Temporary rental of large GPU capacity for release-candidate, model-compatibility, and load tests. Usage itemized in monthly reports.
External Testing Team Two QA / infrastructure testing engineers validating pre-release builds, DevShards, and deliverables from external teams. See the role archive.

Broker OpenAI compatibility

skills.sh

Specs for each broker's OpenAI HTTP proxy, before the inference gateway. Two independent skills (folder names match YAML name):

Chat Completions host-compat skills/openai-host-compat/
Responses adapter (POST /v1/responses) skills/openai-responses-adapter/

Install (one or both; not --all as the default):

npx skills add paranjko/external-test-lab --skill openai-host-compat
npx skills add paranjko/external-test-lab --skill openai-responses-adapter

Human catalog pointers: broker-compat/.

Broker gateway operations

DevShard gateway 4.1.1 — standalone setup guide (fresh slot, settings, mint, smoke, cutover, public accounting link) broker-ops/v411-gateway-setup-guide.md

Team

Role Owner
Project Lead Sergii Paranko (@paranjko)
Infrastructure Lead Mikhail Chudinov (Mitch)
QA Engineers 2 hired (2nd started Sep 7) — posting kept in jobs/

Repository roadmap

Artifacts appear in this repository as the pilot milestones deliver them, per the approved proposal. Status is updated in place.

Milestone Artifact Location Status
M1 DevNet architecture note devnet/architecture.md published
M1 QA hiring jobs/ filled — 2 engineers
M1 Initial test strategy testing/test-strategy.md published
M1 Node deployment runbook net-deployment-runbook/ published — 1.0.0-alpha.0
M1→M2 Monthly public report #1 reports/monthly/2026-08-month-1.md published
M2 Monthly public report #2 reports/monthly/2026-09-month-2.md published
M2 Join guide, regional layout net-deployment-runbook/ROLE-JOIN.md, devnet/regions.md published
M2 Smoke & regression checklists, live task board testing/smoke-checklist.md, testing/regression-checklist.md, task board published — task board live
M2 Broker OpenAI host-compat + Responses adapter broker-compat/ published
M2 DevShard gateway 4.1.1 broker setup guide broker-ops/ published
M2 External join opening (genesis params, seeds) devnet/ in progress — public JOIN path exists; independent lifecycle not yet stable
M3 Test automation scripts (smoke-level) automation/ planned
M3 Incident log, participant onboarding guide runbooks/incidents/, devnet/ planned
M4 Final reports, lessons learned, handoff package reports/, docs/ planned

Folders are created together with their first real artifact — an absent folder means the milestone that delivers it has not been reached yet.

Reporting and transparency

  • Monthly public reports cover deliverables, incidents, spending by budget line, remaining balance, and next-month plan. Reports are posted here and linked in discussion #1388.
  • Release-readiness and DevShard validation reports are published when testable artifacts are provided per the handoff requirements in the proposal.
  • Security-sensitive findings follow the private disclosure process in SECURITY.md.
  • Unused funds at the end of the pilot are returned to the Community Pool, per the proposal and the escrow contract terms.

Ownership and handoff

This repository is community-owned by intent. It is planned to be transferred to the gonka-ai organization (or another community-designated home) as part of the pilot handoff. Owner model, emergency access, and handoff procedure will be documented in docs/handoff.md during the pilot.

License

Apache-2.0 applies only to Test Lab artifacts in this repository (plans, runbooks, reports, scripts, and other materials authored by the pilot).

It does not apply to Gonka network software, protocol code, or chain state. This repository contains no Gonka source code. The Gonka network and its codebase are licensed under separate terms.

About

External Test Lab & Community DevNet for the Gonka AI network: public artifacts

Topics

Resources

Security policy

Stars

2 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages