Bounty

Earn GNK for Contributions

The Gonka Community Pool allocates rewards for contributions to the project's development. Bug fixes, new features, documentation, and tests — all earn GNK.

How It Works

Gonka uses a community pool — a portion of GNK issuance reserved for rewarding contributors. When your Pull Request is accepted and merged into the main branch of the gonka-ai/gonka repository, the team distributes a reward from the pool based on the complexity and significance of the contribution.

💰

Community Pool

A percentage of GNK issuance is allocated for contributor rewards. The more significant the contribution, the greater the reward.

🔍

Team Review

Every PR undergoes review by Gonka maintainers. Quality code with tests receives priority.

GNK Payout

After merging, the reward is sent to your Gonka.Wallet. The amount depends on the type and complexity of the task.

Types of Contributions

Bug Fixes

Most Frequent

Fixing errors in code, consensus logic, network protocol, and CLI. Bug fixes are the most frequent and in-demand type of contributions.

Reward: 50 — 500 GNK

New Features

High Reward

Developing new functionalities: performance improvements, new CLI commands, PoC verification optimization, integrations.

Reward: 200 — 2,000 GNK

Documentation

Easy to Start

Writing and improving documentation, translations into other languages, examples of API and SDK usage.

Reward: 20 — 200 GNK

Testing / QA

Stability

Writing unit and integration tests, reproducing and documenting bugs, load testing.

Reward: 30 — 300 GNK

Step-by-Step Guide

5 steps from fork to receiving GNK.

1

Fork the Repository

Go to github.com/gonka-ai/gonka and click Fork. Clone the fork locally.

git clone https://github.com/<your-username>/gonka.git
2

Find a Task

Open the Issues tab in the main repository. Look for labels:

  • good first issue — easy tasks for beginners
  • bounty — tasks with confirmed GNK reward
  • help wanted — tasks where help is needed
3

Write Solution + Tests

Create a branch, write code, and be sure to add tests. PRs without tests receive significantly lower priority for review.

Tip: follow the project's code style. Run linters and tests locally before submitting.

4

Create a Pull Request

Open a PR in gonka-ai/gonka. Describe what was fixed/added, specify the linked Issue (#number).

PR Checklist

  • Description of changes
  • Link to Issue
  • Tests passed
  • Linter without errors
5

Review + Merge = GNK

Maintainers will review your code. After approval and merging, the GNK reward will be sent to your wallet.

Average review time: 3-7 days. Complex features may require several iterations.

Reward Sizes

Approximate reward sizes from the community pool. The final amount is determined by the Gonka team based on the review results.

Task Type GNK Range Examples
Bug Fixes 50 — 500 Fixing crashes, memory leaks, incorrect validation
New Features 200 — 2,000 New CLI command, PoC optimization, API integration
Documentation 20 — 200 Docs translation, SDK examples, FAQ, README
Testing 30 — 300 Unit tests, stress tests, bug reports with reproduction
Critical Vulnerabilities 1,000 — 5,000+ Consensus exploits, double-spend, PoC bypass

Rewards for critical vulnerabilities can significantly exceed the stated range.

Ready to Contribute?

Open the Gonka repository on GitHub, find a suitable task, and submit your first Pull Request.