Wrapped Gonka (WGNK)

Wrapped Gonka: the Ethereum access layer for Gonka’s compute network

WGNK is not a separate application network. It is the Ethereum ERC-20 representation of Gonka’s native GNK coin, designed to connect the project’s decentralized AI-compute economy with Ethereum wallets, contracts, and liquidity venues.

What WGNK represents

Gonka is a decentralized infrastructure network aimed at running AI inference and training across independently operated hardware providers. Its architecture separates blockchain coordination from AI execution: chain nodes maintain consensus, API nodes coordinate jobs and validation, and machine-learning nodes perform inference, training, and Proof of Compute work. WGNK is the Ethereum-side representation of GNK, rather than a second native asset with its own independent utility. The official documentation identifies one Ethereum contract as both the bridge contract and the WGNK ERC-20 token.

The official WGNK contract is 0x972a7a92d92796a98801a8818bcf91f1648f2f68. That address should be treated as an identity check because the project warns that unofficial listings and contracts may present themselves as GNK or WGNK. Native GNK remains the coin used inside Gonka; WGNK gives that coin an Ethereum-compatible form for wallets and smart-contract venues.

How Gonka uses compute as consensus weight

Gonka’s central mechanism is called Proof of Compute. Instead of tying consensus weight primarily to staked coin balances, the protocol measures verified computational contribution. Hosts compete in short, synchronized Sprint windows that determine weight for the next epoch, while most of the epoch is reserved for AI workloads and validation. The project documentation describes epochs of roughly 23 hours and a process in which hosts run and validate inference tasks throughout the epoch.

This design gives WGNK an indirect relationship with network activity. Holding WGNK does not itself provide compute capacity or guarantee rewards. A participant seeking host rewards must operate suitable infrastructure and satisfy the network’s workload, validation, and availability requirements. The repository describes the system as a modular, containerized stack using chain, API, and machine-learning components, which means participation depends on more than a wallet balance.

The bridge mechanism

Moving GNK to Ethereum involves locking native GNK in escrow on Gonka and minting the equivalent WGNK on Ethereum. Returning to Gonka involves sending WGNK to the bridge contract, where it is burned, followed by release of the corresponding GNK on Gonka. The bridge documentation says outbound transfers are authorized through BLS signatures from the Gonka validator set, with a daily group-key sequence used by the Ethereum contract to verify releases.

The bridge also has an address-derivation dependency: the Gonka destination is derived from the public key that signed the Ethereum deposit. The project warns that Ethereum and Gonka accounts derived from the same seed phrase may still use different derivation paths, so users cannot assume that the two addresses correspond automatically. This is a practical operational constraint, not merely a user-interface detail.

What the token does inside the economy

GNK is used for network payments, host rewards, collateral, and governance-related economic incentives described by the project. The tokenomics paper outlines two broad reward channels: developer-funded work rewards and epoch-minted rewards distributed according to active Proof of Compute weight. It also describes vesting, collateral requirements, dynamic per-model pricing, and a community-pool mechanism. These are design components documented by the project, not independent evidence that the full economic model has reached mature production scale.

Governance is not described as ordinary one-token-one-vote control. The FAQ states that voting influence is based on Proof of Compute weight, with GNK collateral used to activate more of that weight. Governance proposals can cover software upgrades, module parameters, inference models, and community-pool transfers. The governance documentation says proposals are approved through PoC-weighted voting, making active compute participation and the validator or host structure important to how control is exercised.

Who the system is for

Gonka identifies developers and hardware providers as its primary network roles. Developers use the distributed infrastructure to submit AI workloads, while hosts supply GPUs or other required resources and participate in execution, validation, and Proof of Compute. The open-source repository includes local build and integration-test instructions, but running a production host still requires compatible hardware, software deployment, connectivity, and ongoing operational attention.

For Ethereum users, WGNK is mainly an access and settlement instrument. It can be held in an ERC-20 wallet and transferred through Ethereum-compatible contracts, then converted back into native GNK for use within Gonka. The project’s bridge documentation also supports other ERC-20 transfers between Ethereum and Gonka, so the bridge is broader infrastructure rather than a contract designed only for WGNK.

Security record and open limitations

The project states that its Ethereum bridge has undergone a CertiK audit, and CertiK’s project page lists separate audit entries for the bridge, inference, and consensus components. An audit is evidence that code was reviewed under a defined scope; it is not a guarantee against future vulnerabilities, governance failures, implementation changes, or operational outages. Cross-chain safety also depends on Gonka consensus, BLS signing, escrow accounting, Ethereum execution, and correct address handling.

The main unresolved questions for WGNK concern practical scale and concentration. Its usefulness depends on demand for Gonka’s AI services, the availability and economics of host hardware, sufficient Ethereum liquidity, and reliable bridge operations. Governance weight tied to compute may reduce the importance of passive token ownership, but it also makes participation dependent on specialized infrastructure. The project’s own documentation and codebase show an active system under development, so specifications, model support, pricing, and governance parameters should be checked against current chain data before use.

Key takeaways

• WGNK is the Ethereum ERC-20 form of Gonka’s native GNK coin, not a separate blockchain.
• Gonka’s consensus weight is designed to track verified computational contribution through Proof of Compute.
• Bridging depends on escrow, BLS authorization, validator consensus, Ethereum execution, and correct cross-chain address derivation.
• GNK’s documented roles include payments, host rewards, collateral, and PoC-weighted governance participation.
• WGNK’s practical value depends on Gonka workload demand, host economics, Ethereum liquidity, and bridge reliability.

Risks and open questions

• Bridge failure, validator-signature problems, escrow-accounting errors, or Ethereum contract vulnerabilities could delay or prevent conversion between WGNK and GNK.
• Incorrect Ethereum-to-Gonka key or address handling can result in operational mistakes during deposits and withdrawals.
• Specialized hardware and continuing uptime requirements may limit who can participate as a host or meaningfully influence governance.
• PoC-weighted governance may concentrate influence among large or highly effective compute operators rather than passive token holders.
• Liquidity and venue availability for WGNK may be limited relative to larger Ethereum assets, increasing execution and exit risk.
• Audit coverage does not eliminate risks from later code changes, undiscovered vulnerabilities, governance decisions, or network outages.