Burn-and-mint equilibrium

The model, and where the name comes from

Multicoin Capital's 2018 essay on new models for utility tokens introduced burn-and-mint equilibrium as a named design, attributing the underlying idea to Factom.¹ The structure it describes separates two flows that most token models fuse. Users do not hold the token to use the network; they buy it, burn it for a credit, and spend the credit. Providers do not buy the token; they earn it from an issuance schedule for the capacity they contribute.

The separation is the point. It removes the requirement that anyone hold the token in order to transact, which is a real answer to the criticism that a payment token nobody has a reason to hold has weak price support. What it puts in place instead is a requirement that anyone using the network has to buy and destroy the token first, which is a demand sink in the strict sense: acquisition is compulsory, not optional.

How equilibrium is supposed to be reached

The theory runs like this. If usage burns more tokens than the schedule mints, net supply falls. If the schedule mints more than usage burns, net supply grows. Provider rewards are therefore worth more when the network is busy and less when it is idle, which is meant to pull provider capacity toward the level demand actually supports, and the two flows are meant to settle against each other.

The mechanism does describe a real feedback path. What it does not contain is a mechanism forcing convergence. The mint schedule is set by the protocol and runs on a clock. The burn is set by customers and runs on demand. A network with an emission schedule sized for the usage it hoped to have simply runs net-inflationary until usage arrives, and the diagram below is the honest shape of that.

Where it actually runs

Helium is the most cited implementation. Its documentation describes HNT being burned to produce Data Credits, which pay for network data, alongside HNT emissions to the infrastructure providers running the network.² That is the full BME shape in a live system rather than in an essay.

Akash Network is the second, and worth knowing about because it shows the model was adopted beyond its original example. Akash's own materials describe burning AKT to mint a separate unit used for compute payments.³ Two independent protocols implementing the same structure is meaningful evidence that it is a design pattern rather than a one-off.

The equilibrium claim, stated honestly

Here is the part that decks skip. Every source we can cite describes BME as a mechanical pairing of a demand-side burn with a supply-side mint. None of them, including the protocols' own materials, demonstrates that burn and mint have reached a stable long-run balance in a live network.¹² Equilibrium is the design intent and the theoretical claim. Treat any presentation of it as an achieved state as a claim requiring evidence that we have not seen produced.

This matters at design time in a specific way. If you adopt BME, you are choosing a model whose supply outcome is determined by adoption you have not yet won, which means the emission schedule is the variable carrying all the risk. Size it against usage you can defend rather than usage you are forecasting, and build the governance path to lower it before you need to use it.

What the model does deliver, independent of whether equilibrium ever arrives, is a required purchase tied to real service consumption. That is more than most token models have, and it is worth the complexity when there is a genuine service underneath. When there is not, BME produces a burn chart and an emission schedule with nothing between them.