FORKED.gg ← Back to forked.gg
transparency · the $fork token

$FORK Tokenomics,
shown in full

Every number behind supply, allocation, vesting, and emissions, with the math that produces it. No hidden buckets, no founder bag, no insider unlock. Plug in your own assumptions and check our arithmetic.

1Bfixed maximum supply
0%team allocation
50 : 1$LIX converts to $FORK
90 / 10operators / DAO grants
01 the ethos

Zero team allocation, on purpose

Most token projects carve out a slice for the founders and the core team, often 15 to 20 percent, and call it alignment. We took that line to zero. The Forked.gg team holds no $FORK allocation at all. The only way anyone on the team makes money is through equity in the operating company, so the team only wins if the company builds something real that lasts. There is no founder bag to unlock, no team cliff to wait out, no quiet wallet that sells into every rally.

That single decision is what lets the rest of the design stay clean. Sell pressure on $FORK comes from one place, operators claiming the rewards they earned for verified work, and the whole system is engineered to absorb that with real demand from paying customers. When you read the allocation chart below, the zero next to Team is the most important figure on it. The token serves the ecosystem, and nothing is skimmed off the top to fund a payroll. We are honest about the one indirect line that does exist: the 16.3 percent Protocol Treasury is company-held, and the company is owned by the team through equity, so treasury value reaches the team the long way around, through building a real business rather than through a token rake. We would rather state that plainly than imply the team touches nothing.

02 old vs new

$FORK is not $LIX, and here is every difference

Forked.gg was previously Helix Games, and its token was $LIX. The rebrand re-issues the token as $FORK under a smaller, cleaner supply. Legacy holders are honored in full. The table below sets the two side by side, on verified on-chain facts for $LIX and the current proposal for $FORK.

Dimension $LIX · Helix (legacy) $FORK · new
Status Snapshot taken. No longer supported. Do not buy, sell, or transfer. New token, deploying on BNB Chain. Snapshot balances swap automatically.
Maximum supply 50,000,000,000 (50B) 1,000,000,000 (1B), fixed, no minting beyond the cap
Supply minted 17.81B at the 23 Jun 2026 snapshot (35.6% of cap); the rest still issuable Released only on a published schedule from pre-allocated buckets
Conversion Not applicable 50 LIX : 1 FORK (1 LIX = 0.02 FORK), proportion-preserving
Team / insider allocation ~51.6% of minted supply sat in company and insider multisigs 0% to the team. Equity only.
Holder structure 368 holders, ~84% held by contracts and multisigs Each legacy holder keeps the exact same percentage of supply
Base emission rate 0.15% / day of the remaining latent pool 0.08% / day base, declining, topping up only what real revenue does not cover
Demand backing None. No liquidity pool, $0.00 on-chain market. 65% of node-service revenue recycles into open-market $FORK buys
Unsold token sale ~4.76B LIX unsold seed-round pool sat minted Burned, not carried forward into $FORK
Chain BNB Smart Chain (BEP-20) BNB Chain first, chain-flexible by design
03 supply & allocation

Where all 1,000,000,000 $FORK goes

The fixed 1B supply splits into two layers: legacy Helix obligations honored off the top, and a new economy designed fresh underneath. The donut and table below account for every token. Team sits at zero.

1B $FORK
Emissions Reserve31.0%~310M
Community & Ecosystem24.5%~245M
Legacy redemption (Layer A)18.4%~184M
Protocol Treasury16.3%~163M
Liquidity & Price Discovery9.8%~98M
Team0%0

How the new-economy slices are computed: legacy obligations (Layer A, ~184M) come off the top first, leaving ~816M for the new economy (Layer B), which is weighted 38 / 30 / 20 / 12.

# Layer B = total supply minus honored legacy obligations
Layer B = 1,000M − 184M = 816M $FORK

# Layer B weighted 38 / 30 / 20 / 12, then expressed as % of the full 1B
Emissions Reserve = 0.38 × 816M = 310M → 31.0%
Community & Ecosystem = 0.30 × 816M = 245M → 24.5%
Protocol Treasury = 0.20 × 816M = 163M → 16.3%
Liquidity = 0.12 × 816M = 98M →  9.8%
Team = 0.00 × 816M = 0 →  0.0%
04 layer a · the math

How legacy Helix converts at 50 : 1

The old 50B LIX cap maps onto the new 1B FORK cap. That is a 50-to-1 redenomination, so every holder converts at 50 LIX to 1 FORK and keeps the exact same percentage of supply, with no dependence on any price. Each claim below is a real on-chain balance divided by 50.

# Redenomination ratio
50,000,000,000 LIX cap ÷ 50 = 1,000,000,000 FORK cap
1 LIX = 0.02 FORK

# Worked example: the on-chain node-reward pool at the 23 Jun 2026 snapshot
5,869,000,000 LIX ÷ 50 = 117,380,000 FORK
Node-reward contract redemption · 5.869B LIX117.4M · 11.74%
Community redemption (362 EOAs) · 2.806B LIX56.1M · 5.61%
Advisors (6 × 0.1%, contractual)6.0M · 0.60%
Early token investors (SAFT, honored)4.86M · 0.49%

Patrick Bergman and Jason Brink are advisors to Forked.gg but do not receive any token allocation.

Layer A totals ~184M FORK (18.4%). The node-reward line is pinned to the 23 Jun 2026 on-chain snapshot of the NodeOperatorsReward pool (5.869B LIX), which is already minted supply, not new issuance. The pool grows by roughly 18M LIX per day while Helix emission still runs, so this line re-pins at the moment $FORK deploys. Every figure here is reproducible from BscScan.

05 vesting

How tokens unlock, with the schedules drawn out

Two different release mechanisms keep supply from hitting the market all at once: a six-month linear vest on all legacy redemptions, and an earn-or-vest pacing on operator rewards. Both are shown below with their formulas.

legacy holders

Six-month linear drip

Every redeemed balance, the node-reward pool and community wallets alike, vests over the same six months under one identical rule. Anyone can emergency-claim early: they receive whatever has vested to that point and forfeit the entire unvested remainder, which recycles to the Emissions Reserve. The earmark stays at full par, so no one is shortchanged on value, only on the speed of a panic exit.

100% 0% day 0 day 180 fully claimable
unlocked(d) = B × ( d ÷ 180 )
# B = redeemed balance, d = days since launch, capped at day 180
node operators

Earn-or-vest, one chunk at a time

Foundation node rewards stack up as an earned balance while the node runs. When the operator chooses to switch to vesting, that accumulated chunk releases linearly over 30 days, the node must stay online the whole time, and no new base rewards accrue during the vest. Only one chunk vests at once, and an operator cannot earn and vest at the same time. Time spent vesting is time not earning, which paces how fast rewards reach the market and lets each operator set their own cadence.

earning (node runs) 30-day vest claimable switch
vested(d) = C × ( d ÷ 30 )
# C = accumulated chunk; node online required; no earning while vesting

Usage-based service rewards run on a separate track

Pay for specific paid work, hosting particular content, a metered workload, an oracle or CDN service, is not subject to the earn-or-vest switch. An operator being paid to host specific content keeps earning it while their foundation rewards sit accumulated or vesting, so real paid service work never gets blocked by the foundation pacing.

06 community · coming with launch

Vesting and claims, out in the open

We are happy to build with suggestions from our community. This one came from Free in our Discord, and it is a sharp question: if people claim and vest tokens, can someone with early sight of those numbers trade ahead of everyone else?

Community suggestion, credited to Free in the Forked.gg Discord.

Free ◆ RGMT in #discussion

[...] As for vesting after claiming rewards... will the token amounts people claim and are currently vested be public knowledge? Scenario: a large amount of tokens get claimed. Who has access to that insider info that can use it to their advantage and dump before those tokens can be sold?

View the original message in Discord

The answer is that there is no insider view to exploit. Every claim and every vesting balance settles on-chain, so the amounts, the schedules, and the day-by-day unlocks are public to everyone at the same time. Nobody at Forked.gg gets an early or private feed of this data. To make that easy to see rather than something you have to dig out of a block explorer, the panel below ships with launch.

preview · live at launch

Live supply status

Read straight from the migration and vesting contracts, refreshed on-chain. The figures below are sample data, not real balances.

Unclaimed $FORK 46,200,000 redeemable, not yet claimed
Fully unlocked 21,750,000 claimable now, no forfeit
In vesting 88,940,000 emergency-claimable, forfeits unvested

Next 30 days, day by day. Vesting is linear, so there is no single unlock date. Every day a slice of every position crosses into fully unlocked.

Today +15 days +30 days
Fully unlocked, claimable now (no forfeit) Still vesting, emergency-claimable (forfeits the unvested part)

Each bar is one day. Green grows as amber converts into it, because vesting is linear and a little matures every day. The amber bumps are new claims entering vesting. If a holder emergency-claims a position, it leaves the projection: the amber comes off and the green it would have become never appears, so the chart always reflects what can actually reach the market.

# Public, read-only. No key, no account. Anyone can call it or build on it.
GET https://forked.gg/api/v1/vesting/status

{
  "_note": "sample response, not live data",
  "as_of": "2026-01-01T00:00:00Z",
  "unclaimed_fork": 46200000,
  "fully_unlocked_fork": 21750000,
  "vesting_emergency_claimable_fork": 88940000,
  "forecast_30d": [ { "date": "2026-01-02", "fully_unlocked": 22310000, "vesting": 88120000 } ]
}

A public API endpoint will return these same figures so exchanges, market makers, and any community member can verify the numbers independently or build their own dashboards on top. This endpoint is on the build list and ships alongside the on-chain migration and vesting contracts.

07 emissions · the math

The emission curve retires itself

Emission is a declining, adaptive top-up, not a fixed firehose. Each day the network emits a small fixed percentage of the latent reserve that is left, so the draw shrinks every single day on its own. Real service revenue backfills operator pay, and the reserve becomes a bootstrap subsidy that tapers as the business grows.

Reserve drawdown

Emissions Reserve remaining, 310M → 64M over five years

310M 0 start Y1 Y2 Y3 Y5: 64M

The formula

A fixed rate on a shrinking base is self-retiring

E(t) = r × L(t)
L(t) = L₀ × (1 − r)t

# r = 0.08% / day base draw (0.0008)
# L₀ = 310M FORK starting reserve
# t = days since launch
Year endReserve leftDrawn that year
Start310M·
Year 1226M84M
Year 2165M61M
Year 3120M45M
Year 487M33M
Year 564M23M

The split is locked: every day's emission goes to node operators, with a small DAO Grant Pool slice on top governed through Aegis. The company takes 0% of emissions; it funds itself from the 35% fiat cut it keeps on node-service revenue. We are not going to publish a chart or a forecast telling you what a node will earn, because per-node pay depends on how many nodes are running and on the token price at the time, and both of those move.

08 demand · how it balances

Where the buy pressure comes from

Operator sell pressure is offset by real outside demand. Customers pay fiat for node services, the company keeps 35% to run operations, and recycles the other 65% into open-market $FORK buys that flow back to the operators who did the work. The company only ever buys, never sells.

customer fiat → market-buy $FORK → latent reservoir → re-emitted to operators by attestation → operator

# Per dollar of net service revenue
company operations = 0.35  (fiat, funds the business, no token)
recycle to $FORK = 0.65  (open-market buy, returns to operators)

That 65% recycle is roughly five times the structural buy pressure of the old 12% buy-burn model. Across five years the modeled structural demand is about 2,860M $FORK of buys, and the net token flow turns positive around month 11. The mechanism rests on a real service business rather than on emissions, which is the entire point of the redesign.

Read this before you treat any number as final

Every figure on this page is a proposal for review and is provisional until the new $FORK contract is deployed on-chain and independently audited. On-chain $LIX facts are verified and reproducible from BscScan; the $FORK allocation, vesting schedules, and emission curve are a working design subject to legal review before any external use. Modeled node-income and demand figures assume a flat reference price and are not a promise of value or yield. $FORK and node licenses may lose value or become worthless. Nothing here is financial, legal, tax, or investment advice, or an offer to buy any asset. This page re-pins when the contract deploys. See the full Terms & Conditions.