CoinYQ Dossier

Golem rewrote the computer market, then left its token migration open

Golem's lasting story is a split ledger. Its compute software moved from Brass to Yagna and its currency moved from GNT to GLM, yet the old token still exists. The code keeps those supplies synchronized; the market still asks two strangers to agree, run and settle work.

A 29-minute sale funded an experiment that outgrew its first machine

Golem's November 2016 crowdfunding created 1 billion GNT and reached its 820,000 ETH cap in 29 minutes. The first production chapter was Brass, a rendering-focused mainnet beta launched in April 2018. Its ambition was broad, but its interfaces and execution model carried assumptions that the team later chose to replace rather than merely polish.

In 2019 the organization also split. Piotr Janiuk and Aleksandra Skrzypczak took responsibility for Golem Factory and the core compute platform; Julian Zawistowski and Andrzej Regulski led the newly created Golem Foundation. The Foundation received part of the original capital to explore other ecosystem uses. That institutional history matters because neither body is simply an on-chain department controlled by every token balance.

The 2020 conversion burns one past before minting one future

GNT launched before ERC-20 became the common interface. Yagna's Ethereum Layer-2 payment plan required an ERC-20 token, so the team deployed GLM and opened migration on November 19, 2020. The door is one-way, 1:1 and has no deadline.

The contracts implement conservation rather than a fresh billion-token issuance. Legacy GNT subtracts the migrated balance and total supply, then calls agent 0xbfad98d76598961827ba832108c21445aa4fee9a. That agent mints exactly the same amount at the GLM contract. At review, the balances were about 796.57 million GLM and 203.43 million GNT, while their token amounts, expressed with the full 18-decimal precision, summed exactly to 1 billion. Calling all 1 billion 'GLM supply' hides the unfinished conversion.

Control is unusually narrow at this layer. GLM is non-proxy code with no pause, freeze or blacklist. Its migration agent is the effective minter, but only the old GNT contract may invoke migration; the agent's owner is the zero address and its target already points to GLM. New GLM therefore follows destroyed GNT rather than an operator emissions schedule.

Yagna sells an agreement before it sells a CPU second

The March 11, 2021 Yagna Beta I mainnet release replaced the old product line with a modular reference implementation. Provider and requestor run the same base service. Providers advertise Offers; requestors publish Demands with resource, runtime and payment constraints. Compatible proposals become a mutually confirmed Agreement, and an Activity becomes the actual VM or service instance on provider hardware.

Billing follows measured use. A provider can send keep-alive debit notes and later a final invoice; the requestor accepts the bill and its payment driver submits or batches GLM transfers. Polygon is preferred because small payments would be uneconomic on Ethereum mainnet, although Ethereum remains available. This sequence corrects a tempting shortcut: there is no universal smart contract that inspects every output and releases a guaranteed reward. Work, billing, acceptance and on-chain settlement are distinct steps.

Decentralized supply does not erase selection services or company stewardship

Providers set their resources and prices, requestors choose criteria and can work with several machines. Yet access can travel through relays, client software is maintained in Golem Factory repositories, and the official reputation API is a curated service. Its success rate covers tasks run by that system, not all requestors, and it excludes some providers. A requestor must deliberately use its returned IDs or SDK helper.

GLM's core role is transfer and payment. A provider earns because an Agreement and invoice exist, not because it holds tokens. The official 2016 GNT creation terms denied ownership, revenue share, post-activation refund and governance influence; they are a historical predecessor baseline, not a newly signed GLM charter. Current platform terms say Swiss Golem Factory GmbH is not party to requestor-provider contracts and create no claims against it. Golem Foundation's Octant separately adds voting and ETH rewards when GLM is locked under Octant rules; that does not govern Yagna.

How the project changed

  1. 2016-11-11
    GNT crowdfunding reaches its cap

    The sale created 1 billion GNT and reached 820,000 ETH in 29 minutes.

  2. 2018-04
    Brass enters Ethereum mainnet

    The first rendering-oriented beta exposed the compute market to production use.

  3. 2019-06-28
    Factory and Foundation divide responsibilities

    Golem Factory retained core platform development while Golem Foundation began ecosystem experiments.

  4. 2020-11-19
    One-way GNT-to-GLM migration opens

    The ERC-20 contract and perpetual 1:1 conversion prepared Yagna for Layer-2 payments.

  5. 2021-03-11
    Yagna Beta I launches on mainnet

    The rewritten market shipped with VM/WASI environments and Ethereum L1/L2 GLM payments.

Evidence and primary sources

Last evidence review: 2026-09-05

What is Golem?

Golem Network links requestors who need computation with providers who offer machines. Both sides run Yagna, the open-source reference node maintained by Golem Factory. A provider publishes an Offer; a requestor publishes a Demand, negotiates an Agreement, starts an Activity on the provider and settles usage in GLM.

GLM is the ERC-20 payment currency at 0x7DD9c5Cba05E151C895FDe1CF355C9A1D5DA6429. It replaced the pre-ERC-20 GNT through a one-way 1:1 migration that began on November 19, 2020 and still has no deadline. Holding GLM alone does not supply compute, guarantee a task, earn a provider invoice or confer ownership of Golem Factory or Golem Foundation.

What problem does Golem solve?

Idle machines and buyers of burst computation do not automatically trust, discover or pay one another. Golem turns this coordination problem into machine-readable offers, demands and bilateral agreements, then isolates workloads in provider execution environments and records usage for billing.

The design is not a trustless cloud guarantee. Providers perform work before final settlement, requestors choose market and reputation filters, and off-chain messages, nodes and relay paths remain operational dependencies. The official reputation service currently measures only a selected subset and its own paid tests; it is an optional requestor filter rather than a consensus score.

How does Golem work?

Yagna matches compatible Offers and Demands. After both nodes confirm an Agreement, the requestor creates an Activity, transfers its workload or image and sends commands to the provider environment. The provider measures agreed coefficients such as activity duration and CPU use, issues periodic debit notes where negotiated, and sends a final invoice. The requestor accepts it and Yagna's ERC-20 driver broadcasts or batches payment. Polygon is preferred for cost; Ethereum mainnet is also supported.

Token migration is a separate Ethereum path. Calling legacy GNT's migrate function subtracts and destroys that GNT, calls the fixed migration agent, and mints the same amount of GLM to the holder. On the review date, the displayed balances were about 796.57 million GLM and 203.43 million GNT; their full 18-decimal contract units summed exactly to 1 billion.

Key facts

  • Canonical Ethereum GLM contract: 0x7DD9c5Cba05E151C895FDe1CF355C9A1D5DA6429; legacy GNT: 0xa74476443119A942dE498590Fe1f2454d7D4aC0d.
  • The one-way 1:1 GNT-to-GLM migration opened on November 19, 2020 and has no published deadline.
  • On 2026-09-05, contract supply was about 796.57 million GLM plus 203.43 million GNT; the full 18-decimal contract units summed exactly to the 1 billion combined cap.
  • The only effective GLM minter is migration agent 0xbfad98d76598961827ba832108c21445aa4fee9a; its owner is zero and target is fixed to GLM.
  • The deployed GLM token is not a proxy and exposes no pause, freeze or blacklist path.
  • Yagna is the Rust reference implementation used by both requestors and providers.
  • Offers and Demands become Agreements; Activities represent running provider environments.
  • Providers bill after measured use through debit notes and invoices; software payment flow is not automatic proof that a computation result is correct.
  • Polygon is the preferred GLM payment rail; Ethereum mainnet remains supported.
  • The documented reputation service tests only selected providers and can be applied as an optional requestor-side filter.
  • Golem Factory develops the compute network; Golem Foundation was split out in 2019 to explore other GLM ecosystem uses.
  • Core documentation defines GLM as payment currency, not a protocol-wide equity, redemption, revenue-share or voting claim.

Official links

Categories

Related coins

Frequently asked questions

Why is GLM supply below 1 billion if the cap is 1 billion?

Because migration is opt-in. Each migrated GNT is removed from legacy supply and the same amount is minted as GLM. The two live supplies, not GLM alone, sum to the 1 billion cap.

Does Yagna pay a provider automatically when a result is verified?

Yagna records usage, carries debit notes and invoices, and submits accepted blockchain payments. The published flow does not promise universal result verification or eliminate requestor non-payment risk.

Is the Golem reputation score a decentralized consensus record?

No. The documented service tests a selected provider subset with its own paid tasks and exposes scores through an API or experimental SDK helper. A requestor may use it as a market filter.

Does GLM grant governance over Golem Network?

The reviewed core docs define GLM as payment currency and do not establish protocol-wide token voting. Octant uses locked GLM for its separate public-goods process, which does not turn every GLM balance into control of Yagna, Golem Factory or Golem Foundation.

External trackers

Choose a tracking site for Golem: