Chapter 01

Introduction

INFERNO is a launchpad where a token is named after an AI model, and a slice of every trade is spent buying that token back and destroying it. It holds no view on price, it pays nobody, and it earns nothing when nobody is trading.

What INFERNO is

Anyone can launch a token here. A launch deploys three things in one transaction: an ERC-20 with a fixed supply, a Uniswap V2 market with the entire supply in it, and a vault that holds ETH for that one token. The liquidity is burned as it is created, so the pool cannot be withdrawn by the creator, by us, or by anyone else.

After that the token is ordinary. What makes it different is the fee: a trade routed through this interface pays 1% of its ETH side into the token's vault, and the vault's only ability is to spend that ETH buying the token on its own pair and burning what it buys.

That is the entire loop. Trading is the input, a smaller supply is the output. There is no emission schedule, no reward pool and nothing to stake.

What it is not

  • It is not equity in anything. The model belongs to whoever built it. They are not party to the token, receive nothing from it, and have not endorsed it.
  • It is not a yield product. Nothing is distributed to holders. The vault cannot pay anyone — its only outward path is a swap followed by a burn.
  • It is not an inference service. You cannot call a model here, and holding a token grants no access to one.
  • It is not a bonding curve. There is no curve, no graduation and no migration. The full supply is in a Uniswap pair from the first block.
  • It is not audited. The contracts have been through internal review, unit tests and invariant testing, and that is not the same thing. The Security chapter says exactly what was and was not done.

Who it is for

Two roles. Someone who wants to launch a token for a model they think people will trade, and someone who wants to hold one because they expect that trading. A third exists by accident: anyone who trades, whose fee funds the burn whether they care about it or not.

How to read this

The next chapter walks the whole mechanism end to end without detail; everything after it covers the same ground slowly. If you read two chapters, read that one and the risks. If you are integrating, skip to /docs/integrate.