Community Pool
Community pool. How it is formed and what it is spent on.
🏦 Community Pool in Gonka: where it is stored, how it is funded, and what it is spent on
Community Pool is the network’s common fund, which is replenished automatically and used by community decision (Hosts) through governance.
This article answers the most common questions:
to which address funds are collected,
on what basis we assert this (links to genesis / tokenomics / whitepaper),
what is financed from the pool,
how to check balance and transactions yourself.
If you want to see it with images — here is Community Pool Study (created in NotebookLM. For now only in Russian. 23 MB).
✅ 1) To which address are funds collected?
Technically the Community Pool is tied to the distribution (standard Cosmos-SDK module responsible for reward distribution).
Community Pool address (distribution module account):
gonka1jv65s3grqf6v6jl3dp4t6c9t9rk99cd8h2rzwa
https://gonka.gg/wallets/gonka1jv65s3grqf6v6jl3dp4t6c9t9rk99cd8h2rzwa
Where this is specified in genesis.json
The address is recorded as a ModuleAccount with the name distribution in the section:
auth -> accounts :contentReference[oaicite:0]{index=0}
Example fragment:
This same address also has a starting balance in:
bank -> balances genesis
✅ 2) How much was in the pool at network launch?
At network launch (Genesis) the Community Pool contained:
120,000,000 GNK
In the minimal units ngonka it looks like this:
120000000000000000 (and sometimes in genesis it appears with decimal zeros)
Where this is visible:
distribution -> fee_pool -> community_poolgenesis
the same amount is duplicated in
bank -> balances(see above) genesis
How to understand denom (GNK vs ngonka)
In the genesis.json it is stated that gonka has an exponent 9, and the base unit is ngonka genesis.
So:
1 GNK = 1,000,000,000 ngonka
How much is currently in the Community Pool?
As of 13.02.2026 the pool has about 106M GNK
Information taken from: https://gonka.gg/wallets/gonka1jv65s3grqf6v6jl3dp4t6c9t9rk99cd8h2rzwa
How to view Community Pool wallet transactions?
Transactions from this wallet are not reflected on-chain.
Reason you cannot see transactions: This address is the blockchain’s “reward treasury.” It is transparent system infrastructure. The balance changes without transactions because Cosmos SDK module accounts operate at the consensus level rather than the user-transaction level. Each block mints new tokens automatically and directs 2% of minted tokens here.
You can view the current balance
You can see all transfers in this Dashboard: https://gonka.gg/network/community-fund
There are also links to Proposals where transfer decisions were made.
To view each wallet that received transfers - click here:
We express huge gratitude on behalf of the whole community for the best Gonka Dashboards in the world! Check them out - try them! https://gonka.gg/ There is an API option to export data to your services. 1,000,000 tokens are provided free for testing
At epoch 170 (February 2026) the information is as follows:
Current Distribution module balance 105,862,522 GNK Number of Proposals: 4 (14, 16, 19, 25). Spent via Proposal #14: 20,524,521 GNK Of which - 20,000,000 - BitFury sale - 524,521 - Other activities Total passed through the module: 125,862,522 GNK
In Proposal 19 an amount of 367,538 GNK was allocated as compensation to Mining Pools for losses in one epoch. There may have been other payments, but most were compensation to mining pools.
Attention! Proceeds from token sales from the Community Pool will be recorded in a USDT wallet that also belongs to the Community. As of now (February 2026) this functionality is under development.
✅ 3) Who controls the Community Pool?
Key point: the pool is not “owned by the team”. It is managed by Hosts through decentralized governance.
The tokenomics document explicitly states:
Community Pool (120M) is controlled exclusively by Hosts
its use is determined by voting Gonka tokenomics
The Whitepaper also describes the governance logic: influence in governance is earned through compute-work (PoC) and is strengthened by staking GNK (collateral) Gonka whitepaper.
Important: tokenomics separately emphasizes that the final strategy for pool distribution is a decision of the Hosts community. Gonka tokenomics
✅ 4) Why does the pool continue to be funded? (sources of funding)
4.1. Automatic “community tax”
The genesis sets the parameter:
community_tax = 0.02 (2%) genesis
This means: a portion of distributable rewards automatically goes to the Community Pool.
Fragment:
4.2. Replenishments via protocol rules
In addition to community_tax, the pool can be replenished “from above” (for example, through technical mechanisms: rounding, unclaimed amounts, fines, etc.). Specific replenishment rules depend on the network version and updates (better to record them in a separate “Network Updates” article).
According to update v0.2.7, the following are now automatically directed to this pool:
Unclaimed/expired rewards (Expired/unclaimed SettleAmount).
Rounding remainders from Bitcoin reward calculations.
Miners’ "missed shares."
Example*: In epoch 170 a total of 297K rewards were allocated. Miners received 218K, and 79K went to the Community Pool
*Information taken from this Dashboard: https://gonka.gg/network And here is another dashboard Gonka Community Fund Dashboard: https://gonka.gg/network/community-fund
✅ 5) What is financed from the Community Pool?
The Community Pool is the network’s common resource, and its purpose is to finance what is important for the ecosystem.
Below are the clearest scenarios that follow directly from the documents.
5.1. Support for Hosts’ liquidity (expected goal)
Tokenomics states that it is expected (expected) that part or all of the pool may be directed to support early liquidity for Hosts — until GNK receives widespread listings and P2P/exchange volume becomes sufficiently large Gonka tokenomics Gonka tokenomics.
The idea is simple:
the network grows,
hosts need liquidity,
the pool can be used as an early-stage infrastructural “cushion.”
5.2. Example of an actual expenditure: Bitfury (Governance Proposal #14)
To move beyond theory, here is the first large case of Community Pool spendingthat was actively discussed in the community:
The event: sale (purchase) of 20,000,000 GNK by the company Bitfury
Mechanics: the decision was made through on-chain voting (governance) and approved by the Hosts community
Purpose: an example of how the Community Pool can be used as a tool for strategic liquidity/financing (rather than “someone’s wallet”)
Link to Proposal #14 (dashboard): http://node1.gonka.ai:8000/dashboard/gonka/gov/14
A community sale smart contract was developed that offered BitFury a fixed price of 0.6 USD per 1 GNK.
20M GNK are locked for this sale at the smart contract address gonka18pkq9mwxxlmyq7kr5txhm060wemg2s4u94wvsfd9w2kdc0u99d6spk8pz2
Note: USDT has a contract, the contract has parameters, the USDT decimals parameter equals 6. 1 USDT -> 1_000_000 (I don’t fully understand what this is, but I’ll leave it as is).
Thus the size of BitFury’s investment amounted to 12,000,000 USD.
BitFury’s GNK are held in this wallet: gonka18pkq9mwxxlmyq7kr5txhm060wemg2s4u94wvsfd9w2kdc0u99d6spk8pz2
At the time of writing (February 2026) the full amount (20M GNK) is stored there. I.e., these funds have not been used.
Attention! Proceeds from token sales from the Community Pool will be recorded in a USDT wallet that also belongs to the Community. As of now (February 2026) this functionality is under development.
Links:
5.3. Bounty Rewards (bug bounties)
In the whitepaper / tokenomics the logic is clear: the network should reward useful actions — including security improvements and fixes. In practice such payouts usually come from the common fund (Community Pool) and are approved by governance decisions (since they are “network initiatives”).
Tokenomics also emphasizes: Community Pool allocations relate to network-level decisions and depend on voting Gonka tokenomics.
How to apply for Bounty Rewards is described in the official GonkaAI Discord channel, in this thread: https://discord.com/channels/1336477374442770503/1433818594713669739 We will soon write an article in the Knowledge Base on this topic.
5.4. Compensations / post-incident recovery programs
If the network experiences a serious outage, rollback, or downtime — the Community Pool is often used as a source of compensation (this is a common scenario in Cosmos networks). Again the key: this is done by governance decision, not “at the whim” of individuals Gonka tokenomics.
✅ 6) How to check current balance and transaction history?
6.1. Explorer
Check the address:
gonka1jv65s3grqf6v6jl3dp4t6c9t9rk99cd8h2rzwa
And look at:
current balance,
incoming/outgoing transactions,
transaction purpose (if the explorer shows memos / message types).
Note: Why transactions are not visible. Are there other tools? https://gonka.gg/wallets/gonka1jv65s3grqf6v6jl3dp4t6c9t9rk99cd8h2rzwa
6.1. CLI (if you have access to any network node)
Any Miner can use this method.
Command to get the Community Pool balance:
(the path distribution -> community_pool in genesis confirms that this is the correct entity) genesis
FAQ (quick answers)
Community Pool = whose wallet?
This is not someone’s personal wallet, but a module account of the protocol distribution. genesis
Why can the pool contain “small amounts” or be less/more than expected? Because:
replenishment/distribution rules change,
part may be directed to payouts by governance,
the current state differs from Genesis.
Can you “just take money from there”? No. According to tokenomics and the whitepaper this must be formalized and approved through governance (Hosts’ voting). Gonka tokenomics Gonka whitepaper
🔗 Resources
Gonka Community Fund Dashboard: https://gonka.gg/network/community-fund
genesis.json (official source): https://github.com/gonka-ai/gonka/blob/main/genesis/genesis.json
Gonka Whitepaper: https://gonka.ai/whitepaper.pdf Gonka Tokenomics: https://gonka.ai/tokenomics.pdf
Governance portal / proposals list: https://node3.gonka.ai/dashboard/gonka/gov
Bounty program (rules): https://discord.com/channels/1336477374442770503/1433818594713669739
Knowledge Base article Genesis.json. Initial GNK distribution
Last updated