Tools for trustless
mining in Gonka.
We’re gonka24, an inference broker on Gonka. We’re now launching Gonka Forward, our first smart-contract tool.
Forward lets hosts and buyers agree deals on future GNK rewards, with settlement governed by smart-contract rules instead of personal trust. Our longer-term direction is a trustless marketplace.
External transactions advance the deal.
Gonka’s vesting schedule stays in place.
Agree the terms ahead of time.
Execute the deal by the rules of code.
For hosts
Sell future rewards.
Get paid before vesting ends.
Agree a sale price for future GNK rewards and receive payment after the rewards are confirmed, without waiting for the full vesting period.
For buyers
Agree a GNK price.
Receive coins as they unlock.
Agree a purchase price for a selected epoch. The actual purchase amount depends on the host’s rewards and the deal’s capacity.
Settlement terms are fixed in the contract. The host is not paid at deal creation, and the buyer does not receive all GNK immediately after settlement.
From agreed terms to GNK payments
- 01
Agree terms
The host creates a Deal for a selected epoch with fixed terms and designates the contract as that epoch’s reward recipient.
- 02
Fund the deal
The buyer deposits the agreed budget before the epoch begins.
- 03
Provide compute
The host supplies computing power. After the epoch starts, a separate transaction locks proof of reward routing into the Deal.
- 04
Settle the claim
After Gonka confirms the claimed rewards, the contract calculates the purchase, host payment, fee and any buyer refund. USDT transfers require separate transactions.
- 05
Receive GNK
GNK is distributed as it unlocks in the network. The network’s vesting schedule stays in place.
Today, required operations are initiated through external transactions. The contract does not run them on a schedule.
The separate operations behind settlement
The host’s native reward claim is a Gonka network operation. SettleClaim records the resulting obligations; it does not transfer USDT. WithdrawUsdt transfers each role’s payment separately. ReleaseUnlockedGnk distributes available GNK as it unlocks.
What happens to my deal?
Choose your role and situation to see how the contract handles the funds, what action is available, and how the behavior was checked.
A guide to V1 contract behavior. It does not read or diagnose your live Deal.
Which situation would you like to understand?
E is the target epoch. Unit tests use mock Gonka responses; cw-multi-test models contracts and transfers with synthetic native responses. Native E2E and mainnet results are not attested in this evidence set, and a match to deployed bytecode has not been verified.
Terms used in the scenarios
D is the agreed USDT budget; P is the price in contract units; C is the GNK purchase limit; T is total confirmed rewards; B and H are the buyer and host entitlements. Proportional uses the fixed shares B/T and H/T; HostOnly assigns future GNK to the host.
First USDT payouts. GNK still vesting.
Escrow Mining created the Deal and provided computing power for epoch 423. The buyer funded a 140 USDT budget at 0.20 USDT per GNK.
USDT payments complete · GNK still vesting
Funding and Lock are confirmed. The deal received 607.284849111 GNK in rewards and SettleClaim was executed. The host and operator have been paid, and the unused budget has been returned to the buyer. No USDT obligations remain unpaid.
GNK remains in vesting; delivery to the buyer is not yet complete. The full deal lifecycle is still in progress.
All payments shown here use wrapped USDT (CW20) inside Gonka. This case does not confirm withdrawal of those payments to Ethereum.
Editorial snapshot · checked
This page does not monitor the deal live.
Visit Escrow Mining
Settlement results
- Reward received
- 607.284849111 GNK
- Paid to host
- 119.635115 USDT
- Operator fee paid
- 1.821854 USDT
- Returned to buyer
- 18.543031 USDT
- Unpaid USDT obligations
- 0 USDT
Original deal terms
- Host
- Escrow Mining
- Target epoch
- 423
- Buyer budget
- 140 USDT
- Price
- 0.20 USDT / GNK
- Maximum purchase
- 700 GNK
- Fee
- 1.5% of the actual purchase amount
Verify on-chain
Live contract queries
Read-only API queries above; confirmed transaction receipts in the links above them.
Deal address
gonka1kxlsujae…ts9cdejs · full address
gonka1kxlsujae2mgahx2grd8hq8clhsk2zwsqk8q8esx6n2cpj426sdts9cdejsSelect the full address to copy it.
What you can use today
Deployed contracts support individual deals between one host and one buyer for a selected epoch.
A transaction interface and ready-made monitoring are not available yet. Using the contracts requires technical preparation: track the deal’s state and submit the required operations within their permitted windows.
What “trustless” means here
Custody and settlement follow the contract’s code. A deal still depends on Gonka’s data and operation, the settlement token, and submission of the necessary transactions.
The team can help explain the tools. It cannot arbitrarily change an existing deal’s terms or reverse confirmed transactions. Compensation by the team is not provided.
The settlement asset
Inside Gonka, settlement uses wrapped USDT in the CW20 format. According to the team, the pilot’s USDT was transferred from Ethereum through Gonka’s standard bridge. Cross-chain transfers and any return withdrawal are separate from Forward settlement.
From pilot to production readiness
Priorities and timing will evolve with usage and community feedback. The next question is which deals and tools people actually need.
Our main development question
One deal. More possible scenarios.
Planned1 buyer → N buyers
Shared funding
Explore several buyers participating in one deal, with smaller individual contributions.
Same terms for every buyer? What minimum contribution works? What should happen if the budget is only partly funded?
1 epoch → N epochs
Longer agreements
Explore deals spanning more than one epoch, with clear pricing, budget allocation and accounting for each epoch’s results.
One price or terms per epoch? Consecutive epochs or a selected set? Separate settlement for each epoch?
Specialized tools or a more universal contract?
Both paths are open: a set of contracts for specific scenarios, or a more universal contract with flexible terms. Your use cases will help determine which mechanics belong together and which should develop separately.
A clear user interface
Create and fund deals, understand their terms before signing, and view settlement and payments without a command line.
Deal automation & monitoring
Infrastructure to track deals and submit permitted transactions to advance them and deliver payments. Monitoring will show outcomes and situations needing attention. Only operations allowed by the public contract interface can be automated; participant signatures, control of funds and native claims retain their own authorization requirements.
Marketplace & referrals
Publish and discover offers; compare prices, volumes and periods. A planned referral system would help community members and partner platforms bring in both hosts and buyers. Referral terms are still to be defined.
Hosts & platform partnerships
Explore real use cases, joint pilots and integrations with hosts, platforms and communities that help buyers find offers.
Ongoing technical & security support
Improve documentation and tools, maintain compatibility with network updates, check contract scenarios, and review vulnerability reports and proposed fixes. This is continuous work across all development directions.
What kind of deal do you need?
We especially want to understand demand for multiple buyers and multiple epochs in one deal. Real scenarios will help us choose the next mechanics.
Hosts
How many epochs? What share of your rewards would you sell? Would you work with several buyers in one deal?
Buyers
What contribution size works for you? A specific host, a longer period, or purchases spread across several hosts?
Platforms
Which tools and terms would help you attract buyers and integrate Forward? What collaboration would be useful?
A simple tool for one scenario, or a universal contract with flexible terms?
Share your use case ↗support@gonka24.comDocumentation, checks & code
Developers are welcome to study the implementation and propose improvements. Report potential vulnerabilities privately through the Security Policy; product suggestions can be discussed openly.
Settlement mechanics
Formulas, fees, refunds and payments
Validation methodology
Validation and compatibility requirements
Acceptance runner
Separate end-to-end verification tooling
All documentation
Architecture, operations and network requirements
Forward tools
CLI and instructions for the current pilot version
Contract implementation
Code available for study and review · BUSL-1.1
Security Policy
Report potential vulnerabilities privately
Published code and validation methodology are resources for review, not evidence of an independent audit or a successful check of a particular deployed version.