GoMining, computed.
data as of 2026-08-31The 30-second version. Why does the GOMINING token matter to a miner owner? Because paying maintenance in the token (up to 20% discount on electricity + service) is the biggest cost lever on this site — and the token payment feeds the burn machine documented below: spent tokens are burned weekly, new ones are minted by rule, and locked tokens earn governance votes and a share of the weekly mint. For pure profitability, the maintenance discount is the part that matters. Everything else on this page is the machinery behind it.
Jump to: Burn & Mint · Epochs · veGOMINING & locks · The vote
The GOMINING token is not a share certificate that sits next to the mining business — it is wired into it. Every token a miner holder spends on maintenance is collected all week and burned on Tuesday, and the protocol mints new ones right after, in a ratio set by a schedule called Epochs and by a weekly vote of locked-token holders (veGOMINING). The vendor's own summary: the mechanics are "Epochs, Burn & Mint cycles, veGOMINING locks, and Voting. Together they create a self-regulating system designed to reduce circulating supply over time while rewarding active participants." The mechanism is designed to reduce supply — whether that translates into a higher token price depends on demand and cannot be inferred from supply alone. This page unpacks those four parts from the official documentation — because the token-payment maintenance discount, one of this site's biggest numbers, only exists because of this machine: fees paid in tokens are burned, and the discount is what you get for feeding the burn.
The cycle is weekly — "Each cycle runs from Tuesday to Tuesday" — and its fuel is the maintenance bill: "at the end of which we burn all GOMINING tokens spent on digital miner maintenance and immediately mint new ones." Read that slowly, because it is the whole design: fees paid in tokens are not revenue the company pockets in tokens — they are destroyed, every week, on-chain (the two contract addresses that collect the tokens are even published in the docs). Then new tokens are minted and handed to fixed recipients:
| Share of the weekly mint | Goes to |
|---|---|
| 65% | hashpower service providers (the data centers doing the real mining) |
| 20% | veGOMINING vote holders as rewards |
| 10% | "GOMINING rewards" — an ecosystem pot (mining-mode discount top-ups, the Miner Wars token prize fund, collection power-ups), whose split the voters decide |
| 5% | the GoMining team |
So the loop a newcomer actually walks: you pay fees in tokens to unlock a maintenance discount → your tokens are burned on Tuesday → new tokens are minted mostly to pay the mining infrastructure (65%) and the token lockers (20%) → cheaper maintenance for everyone is one of the things the 10% pot funds. The discount program and the token burn are the same loop seen from two ends.
The mint ratio is not free-floating. It follows the current Epoch, each defined by a mint coefficient C: of every burned token, at most C comes back as a new one. The docs commit to a target: the maximum supply of 436,915,240 GOMINING (at the veTokenomics launch) "should decrease to 100,000,000 by the end of the 20th epoch due to its deflationary model" — a planned fall of about 77%. The published schedule (reproduced verbatim; "to mint" is each epoch's floor, reached only if every vote sits on burning — see the vote formula below):
| Epoch | GOMINING supply | To burn | Mint coefficient | To mint |
|---|---|---|---|---|
| 0 | 436,915,240 | 10,000,000 | 0.80 | 8,000,000 |
| 1 | 434,915,240 | 20,000,000 | 0.81 | 16,200,000 |
| 2 | 431,115,240 | 30,000,000 | 0.82 | 24,600,000 |
| 3 | 425,715,240 | 40,000,000 | 0.83 | 33,200,000 |
| 4 | 418,915,240 | 50,000,000 | 0.84 | 42,000,000 |
| 5 | 410,915,240 | 60,000,000 | 0.85 | 51,000,000 |
| 6 | 401,915,240 | 70,000,000 | 0.86 | 60,200,000 |
| 7 | 392,115,240 | 80,000,000 | 0.87 | 69,600,000 |
| 8 | 381,715,240 | 90,000,000 | 0.88 | 79,200,000 |
| 9 | 370,915,240 | 100,000,000 | 0.89 | 89,000,000 |
| 10 | 359,915,240 | 200,000,000 | 0.90 | 180,000,000 |
| 11 | 339,915,240 | 300,000,000 | 0.91 | 273,000,000 |
| 12 | 312,915,240 | 400,000,000 | 0.92 | 368,000,000 |
| 13 | 280,915,240 | 500,000,000 | 0.93 | 465,000,000 |
| 14 | 245,915,240 | 600,000,000 | 0.94 | 564,000,000 |
| 15 | 209,915,240 | 650,000,000 | 0.95 | 617,500,000 |
| 16 | 177,415,240 | 700,000,000 | 0.96 | 672,000,000 |
| 17 | 149,415,240 | 750,000,000 | 0.97 | 727,500,000 |
| 18 | 126,915,240 | 1,345,762,000 | 0.98 | 1,318,846,760 |
| 19 | 100,000,000 | 0 | 0.99 | 0 |
The schedule reads dry; as a chart it shows what it really is: a slow start, a long middle, and one enormous final stretch. Each bar is an epoch's net withdrawal (burn minus the vote-floor mint); the line is the running total, arriving exactly at the planned reduction — 436.9 million down to 100.0 million — after epoch 19:
Arithmetic check, computed by this site: each epoch's net burn (to-burn minus to-mint at the vote floor) sums to exactly 336,915,240 — precisely the planned fall from 436,915,240 down to 100,000,000. The schedule is internally consistent. Note the scale it implies along the way: cumulatively roughly 6.0 billion tokens burned and at best 5.66 billion minted back — about 14× the starting supply churns through the machine on the road to a 77% net reduction. The docs do not state which epoch is active today, nor the current circulating supply; both are visible only inside the app, so this page quotes the plan, not the present state.
To influence the machine, holders lock tokens and receive votes. "To get votes, you need to lock GOMINING tokens for 1 week to 4 years", and "the longer the lock, the more votes you receive." Locks cannot be broken early: "Tokens can't be unlocked before the end of the lock period." Two details matter more than they look. First, the reward for locking is exactly the 20% share above: "In every cycle, 20% of newly minted tokens are allocated as rewards for veGOMINING holders." Second, votes are not a constant — "From the beginning to the end of your lock, the amount of your veGOMINING votes will decrease." The docs attribute that decay to the Burn & Mint cycle itself; its practical effect is pressure: a locked position that is not topped up slowly loses both its vote share and its slice of the weekly 20%. Voting itself costs nothing — "Voting does not spend your votes; it simply confirms ownership."
The weekly vote decides the mint size: minted = (1 − V% × (1 − C)) × burnt, where V% is the share of votes cast for permanently burning and C the epoch coefficient. The docs give the two ends: "If no one votes in favour of burning (V% = 0), the protocol mints the same number of tokens it burned, maintaining the total supply" — no votes, no deflation, the epoch table irrelevant — and "The more votes in favour, the greater the gap between burned and minted tokens." Deflation here is a governance outcome, not a constant: it happens every week only as far as locked holders actually vote for it (and note what they are voting against — their own future reward pool, since rewards are a share of the mint). The same voters also split the 10% ecosystem pot between the mining-mode discount, the Miner Wars token fund, and collection upgrades.
Why this page sits next to the fee tables. Three numbers elsewhere on this site lean on this machine. The token-payment maintenance discount (each 18-day band of covered fees adds +1%, up to 20%) makes sense only because spent tokens are burned — the discount buys into the burn. The mining-mode discount is partly funded by the 10% pot and steered by the weekly vote. And the 1.34× Simple Earn multiplier belongs to a VIP tier that counts veGOMINING votes among its inputs — the same locks again. Tokenomics is not a separate topic on this site; it is the plumbing under the discounts. What it also means: every discount is paid in a token whose supply is scheduled to shrink ~77%. The mechanism is designed to reduce supply — whether that translates into a higher token price depends on demand and cannot be inferred from supply alone. The rider stands either way: the discount's dollar value rides on the token's price, up or down. See Explained → fees & discounts and Simple Earn → the multiplier.
Everything above is the plan. The reference account is not a spectator of it — it holds two live locks, and its fees are already paid in tokens. Read 2026-08-31 from the account's own API session (figures provided and approved by the account owner; amounts stay unpublished per this site's stated rule — what is published are ratios, dates, and counts). Both locks began in March 2025 with multi-year terms: one in the in-app GOMINING wallet (lock ends 2029-08-16), one on the Ethereum side via the veGOMINING contract (ends 2028-11-16). The decay the documentation promises is visible in the account's own numbers — votes per locked token, today:
| Lock | Started | Ends | Days left | Votes per locked token now |
|---|---|---|---|---|
| In-app (GOMINING wallet) | 2025-03-25 | 2029-08-16 | 1,081 | 0.740 |
| Ethereum (veGOMINING contract) | 2025-03-07 | 2028-11-16 | 808 | 0.553 |
Same starting month, and the lock with less time remaining has already decayed further down the votes-per-token curve — "from the beginning to the end of your lock, the amount of your veGOMINING votes will decrease", observed on real positions, not asserted. On the burn side, the machine's fuel is visible in the payment stream: on 2026-08-31 the account paid maintenance 22 times in GOMINING (one per miner) — every one of those token amounts joins the Tuesday burn pot — while the day before, 28 reinvestment credits converted mining rewards back into tokens (the 2.25%-fee stream documented on the Rewards page). Pay in tokens for the discount → tokens burn Tuesday → the vote decides how many come back, and 20% of those go to exactly these two locks. The account sits inside every loop this page documents.
Verifiable from outside: the schedule above is a public document, and its internal arithmetic checks out to the token (computed above). Two of the involved contracts are published, so the burn/mint flow could in principle be counted on-chain — the Burn & Mint contract address appears verbatim in the docs. Not verifiable from outside: the current epoch, the current circulating supply, this week's actual V%, and the real weekly burn/mint amounts — the docs carry the plan, the app carries the state, and no public page publishes the state. A future phase of this site could pin the epoch and the weekly numbers to a block explorer. One more part became measurable through the account: its own locks and payment streams (above), read 2026-08-31 from the account API — the on-chain burn itself remains the unmeasured step. Whether the deflation target holds is a claim of the vendor, backed here by arithmetic, not by observed on-chain history.
By schedule, yes — by vote, conditionally. The plan: burned tokens return only at the epoch coefficient (0.80 falling to 0.99), and the vendor's table targets 436.9→100.0 million tokens across 20 epochs. But the actual mint each week is (1 − V% × (1 − C)) × burnt: if locked holders do not vote for burning (V = 0), everything minted back returns 1:1 and nothing shrinks. The schedule's internal arithmetic is exact (computed above); whether it plays out is a governance outcome nobody can verify from outside.
Four mechanics: Epochs (the mint-back schedule), Burn & Mint (weekly burn of every token spent on miner maintenance, Tuesday-to-Tuesday), veGOMINING locks (lock tokens 1 week–4 years, receive decaying votes), Voting (locked holders steer the mint ratio and split the 10% ecosystem pot). The weekly mint is distributed 65% to hashpower providers, 20% to lock holders, 10% to the ecosystem pot, 5% to the team. All four are documented above with the vendor's own words.
This page deliberately does not answer that — it documents the mechanics with retrieval dates. What the numbers do say: the token's price case rests on the deflation plan holding (a governance outcome, not a constant), and the discount program gives the token a real in-platform demand. What they also say: the platform's Terms let it change any parameter, the deflation is not verifiable from outside, and every "supply narrative" you read elsewhere quotes a state nobody can check from outside either. Here is the fee-and-discount context and the method behind everything on this site.