the work of $YOM: what the token does

The current explanation of licenses, capacity and earnings: from slots to capacity: every license becomes two.

The $YOM token launched on June 5, 2026. The date matters, but the date is not the story.

The story is what the token does on a normal Tuesday, six months from now, when a player in São Paulo clicks “play” on a game streamed from a gaming PC sitting in a bedroom three kilometres away. That single click sets off a chain of compute, latency, and reward settlement, and at the end of it, $YOM is what makes the math work.

This is a plain-English explainer of what the token is for, what it actually does inside the network, and what it is not.

why a token at all?

A decentralized GPU network has to pay strangers for work it cannot verify by hand, and $YOM is how that settlement happens.

A decentralized compute network has a coordination problem.

Every independent GPU operator has to be metered, paid and held to transparent rules, without a central operator holding the books in private. You can solve coordination with a database, but you cannot solve it the way YOM needs to: in a way that is verifiable, automated, and tied to programmatic rules that nobody, not the company, not a single operator, not a single user, can quietly change.

That is the job $YOM does. It turns network activity into on-chain settlement, with audited contracts, transparent rules, and no single point of authority.

If you take the token away, you do not get a faster network. You get a centralized one.

what the token actually does

The $YOM token does four connected jobs inside the network: metering and settlement, the programmatic burn, network access, and contract administration under timelock.

Metering and settlement. The settlement contract reads the sessions each node served and pays the operator’s fixed share of each session fee, set in dollars and paid in $YOM. No invoicing. No off-chain spreadsheets. The contract handles it on Avalanche, on-chain, and every settlement is verifiable.

Programmatic burn. A portion of network usage triggers a burn that is wired directly into the contract. Real demand on the network removes tokens from circulation, automatically, on-chain. The burn is not a marketing event scheduled by the team. It happens because usage happens.

Network access. Publishers, services and white-label partners use the network to stream their games and experiences. They pay in their own currency; the network settles each session’s split in $YOM, which closes the loop between the people consuming compute and the people providing it.

Contract administration under timelock. Privileged access to the contracts sits behind a 2-of-3 multisig with a 48-hour timelock delay. Any administrative change is visible publicly before it is executed. The contract rules are not adjustable in private, and they are not adjustable quickly.

The short version: $YOM is what allows the network to operate itself. Operators are paid because the contract metered their work. Burn happens because usage happened. And when the contracts need to be administered, those changes are delayed and visible. Never private, never instant.

what $YOM is not

It is worth stating plainly what the $YOM token does not do, because a utility token is easy to oversell.

Worth being direct here, because the standards we hold ourselves to require it.

$YOM is a utility token. It is the unit of account inside the YOM network. It is not designed as an investment instrument, and we do not communicate it as one. We do not publish targets. We do not discuss price action. We ask anyone speaking on behalf of YOM to redirect those conversations back to what the network actually does.

Node rewards are variable. They depend on how many sessions a node serves, which follows uptime, region, demand and network conditions. There is no fixed earnings figure, and any number circulating that promises otherwise is not from us.

If you want to understand $YOM, look at the network it settles. The token is downstream of the work.

There is no single-wallet control. Privileged access is handled through a 2-of-3 multisig behind a 48-hour timelock, making administrative changes publicly visible before execution. The contract parameters are visible on Avalanche for anyone to inspect.

the home chain, and how to verify the rest

$YOM’s home chain is Avalanche C-Chain. The official home-chain contract is 0xb6314518b61b4864162c7aE7fdc36261e0A14C4b, published above and at yom.net/tge.

$YOM lives on Avalanche C-Chain, and its LayerZero omnichain design extends it to Base next. Treat any cross-chain version of $YOM as official only if it traces back to YOM’s LayerZero deployment and is verified through YOM’s official sources: the website, the docs, and the verified social channels.

If you see a token claiming to be $YOM on any chain and you cannot tie it back to those sources, do not trust it. Lookalike contracts and unofficial deployments are not us.

the loop, in one paragraph

A gamer plays. A node serves the session. The network meters that session. The settlement contract on Avalanche routes rewards to the operator in $YOM. Usage triggers a programmatic burn. Administrative changes to the contracts are delayed and visible. That is what the token does. Everything else is downstream of that loop.

The token is not a campaign. It is the part of the network that makes the network work.

---

About YOM

YOM runs the session edge: GPU capacity next to every user, sold per session from $0.04, for games and live AI. YOM is backed by Outlier Ventures, Borderless Capital, the Avalanche Foundation, Protein Capital, CV VC, Blockraise VC and Simms Capital. It won Best Tech Startup at Gamescom 2025 and is a member of NVIDIA Inception.

Information is provided for general purposes and may change. $YOM is intended for utility within the YOM ecosystem. Nothing herein is investment advice. Node rewards are variable and not guaranteed; outcomes depend on demand, uptime, region, and network conditions. Availability and functionality may vary by jurisdiction and are subject to compliance requirements.