Documentation

Introduction

Overview#

µToken is a decentralized protocol for launching onchain tokens that are linked to onchain data: either a single stored file, or the layer set of a generative collection. Assets are written to contract storage at creation and are immutable afterwards. Tokens trade on a bonding curve and move to a Uniswap v4 pool at graduation.

Background

A standard ERC-20 contract defines a name, a symbol, a supply, and balances. It carries no reference to any underlying content. µToken extends this model: every token launched on the protocol holds a reference to onchain data set at creation, either a stored digital asset or, for collections, the stored layer set from which each piece is generated.

Two token types

Both types use the same bonding curve, the same launch controls, and the same graduation mechanism: liquidity moves to a Uniswap v4 pool and the LP key is burned.

Introduction

Core concepts#

Onchain storage

Assets are written into contract storage on the chain itself, not to a server or a pinning service. Any file format is supported, up to 4 MB per asset. Uploads happen across several transactions for larger files; the app shows the count as they land. Once written, the data is readable directly from the chain without any offchain service.

Anchoring

An anchor is the cryptographic link between a token and its source asset, written into the token at creation. The anchor cannot be altered or removed afterwards. It records the token’s origin onchain: a source hash, an origin block, and a transaction history.

Provenance

Because the asset and its anchor are both onchain, any party can read a token’s source bytes from the chain and verify them against the anchor hash. See Verifying an anchor.

The bonding curve

Every token trades on a bonding curve from its first block. Buys move the price up the curve; sells move it down. The curve has a target in ETH. When the target is reached, the token graduates.

Graduation

At the curve target, anyone can trigger graduation. Liquidity moves into a Uniswap v4 pool and the LP key is burned, locking it permanently.

Launch controls

Launch parameters include a cap on each buy and on each wallet that rises every second after launch, an optional trading delay of up to 7 days, a creator allocation capped at 1% of supply and bought off the curve at launch, an ETH pair, customizable supply, and an adjustable curve target from 1 ETH. All parameters are fixed at deployment.

Token types

Tokens#

A token is created from a digital asset: an image, a video, a document, or any other file. The asset is stored fully onchain and the token is cryptographically anchored to it at creation.

The anchor file

The anchor file is optional at launch. By default, the project’s logo is used as the anchor file, so every token has an anchor from block zero even if you upload nothing else. Any file format is accepted, up to 4 MB, stored fully onchain; larger files are written in 32 KB chunks after launch, one transaction per chunk, and a PDF is stored whole, every page. Instead of uploading, a link can be snapshotted as the anchor. An optional source link is stored next to the file, so the asset and where it came from stay together onchain.

What happens at launch

1. 1

   Deploy the token. One transaction. Name, symbol, supply and curve set permanently.

2. 2

   Upload the anchor file (optional). By default, the project’s logo is used as the anchor file.

3. 3

   Open trading. Buys open. Your creator allocation arrives in your wallet.

4. 4

   Graduate. At the curve target, anyone can trigger it. Liquidity moves to Uniswap v4 and is locked permanently.

Defaults

Token types

Generative collections#

A collection is a fungible token in which every whole token corresponds to a unique generated piece. Pieces are composed by the protocol from the uploaded layer set. The token itself is a standard ERC-20; each piece carries its own traits.

Layers

Upload one folder per layer with one image per variant, for example Backdrop/, Body/, Eyes/. File names ending in _none become the chance that the layer does not show up on a given piece. Art goes onchain across several transactions; the app shows the count. The top layer sits in front; the bottom layer sits behind and renders first.

Minting: whole tokens make items

No pieces exist at launch. A buy mints one item per whole token you receive. Leftover fractions do not mint, and tokens received by transfer do not mint, so a wallet’s item count can sit below its whole token balance. Leftover fractions never add up to an item and there is no way to mint the difference later; only new buys mint. Item counts are read from the collection contract, not derived from the balance.

Reveal

Traits reveal one layer at a time, advanced by trades: each layer first commits an item to a block, and a later transaction reads the layer from it. An item’s appearance is derived from a block produced after its mint, so the outcome cannot be influenced at buy time. Until an item is revealed it has no artwork; the full art and its seed unlock once every layer is revealed.

Anyone can reveal, their own items or the whole collection. Reveals run in passes: a booking pass commits each item to a block, and a second pass about a minute later reads the layers from it. Revealing individually costs one transaction per layer; batch reveal processes items in groups through Multicall3 (currently 50 items per transaction, roughly 135,000 gas per item, paid by whoever runs it). Layers already revealed stay revealed, and a layer that misses its window simply starts over. All layers are stored onchain, so any piece can be rendered from chain data alone.

On an ERC-20 collection reveal is configured at launch: the Sequential trait reveal toggle makes mints start hidden and reveal layer by layer, each unlocked by a later block, and the Reveal delay sets how long a fresh item stays fully hidden after its own mint, which makes rarity mining impractical: re-rolling means burning the item and losing it, with a fresh outcome that is not guaranteed to be better. Each layer also carries its own reveal hold, visible on the Creator controls page.

A kiosk has neither control. Its items always mint hidden and its holds are always zero, so a reveal can be triggered as soon as the item exists — but it still has to be triggered, by the creator or by anyone else.

What happens at launch

1. 1

   Deploy the token. One transaction. Name, symbol, supply and curve set permanently.

2. 2

   Upload art. Goes onchain in several transactions; the app shows the count.

3. 3

   Open trading. Buys open. Your creator allocation arrives in your wallet.

4. 4

   Graduate. At the curve target, anyone can trigger it. Liquidity moves to Uniswap v4 and is locked permanently.

Defaults

Using the protocol

Launching#

Open Launch in the app and pick a type: Token (the token is backed by a file, stored fully onchain) or Collection (every whole token bought on the curve mints a unique piece from your layers).

Token details

Market settings

Creator allocation is bought for you off the curve when trading opens, paid from your wallet, up to 1% of supply. The purchase happens in the launch transaction at the same starting price as everyone else; no extra tokens are minted. The form shows how many tokens you will receive and the approximate ETH cost. Advanced holds the curve target, supply, buy cap settings, trading delay, and the reveal toggle for collections.

There is currently no fee to launch, so launching costs gas only. The pair is ETH; the swap fee is 1%, and metadata is fixed at launch. After launch, the project page’s banner, logo, description and links can be edited; the name, ticker and everything anchored onchain stay as launched.

Using the protocol

The curve and graduation#

Tokens trade on a bonding curve from the first block. The registry shows each token’s progress as Bonding % toward its ETH target.

Fair distribution

Fair distribution caps each buy at launch, settable from 0.01% to 0.5% of supply. Every launch also carries a max wallet — how much one address may hold at all, never below the max buy — so a series of buys can’t get around it. Anything above the current cap is rejected until launch limits are lifted. The cap rises every second (settable 0.003% to 0.01% of supply per second; at the default 0.003%/s it is fully off after roughly 9.2 hours), so the market widens on a fixed schedule. The wallet cap also paces graduation: while it is low, nobody can buy the curve out, so the token page counts down to the moment the limits lift. The creator allocation is capped at 1% and is bought off the curve in the launch transaction at the same starting price as everyone else. Creators can also delay the start of trading by up to 7 days; the token page shows a countdown, and trading opens in the launch transaction.

Buying and selling

For collections, a buy mints one item per whole token you receive; leftover fractions and tokens received by transfer never mint. Selling burns items only when your remaining balance no longer covers them, newest first, so supply always matches the art. Both buys and sells process up to 100 items per transaction.

Graduation

When the curve reaches its target (default 4 ETH; settable from 1 ETH), any account can trigger graduation. Liquidity moves into a Uniswap v4 pool and the LP key is burned, locking the liquidity permanently. Graduation does not affect stored assets, anchors, or minted items.

Using the protocol

Fees#

Each project carries a 1% trading fee, on the curve and after graduation.

There is currently no fee to launch; launching costs gas only. There are no listing or reveal fees. A kiosk mint is the one exception, and by construction: its price splits between the collection’s reserve, the creator fee and a 0.3% protocol fee. Creator earnings accrue per project and are shown on the Creator controls page; fee recipients are recorded in a fee registry, and tokens launched before the registry existed pay no creator fees.

Using the protocol

The marketplace#

Every collection item trades on its own card, with no external marketplace involved. From an item’s card the owner can list it at a price or transfer it; any account can buy a listed item outright or place an offer. Sales and offers settle in ETH.

An offer can be canceled 30 minutes after it is placed. Until then it stands, and the owner can accept it at any time.

The app

The Registry#

The Registry lists every token on the protocol. Filter by All, Tokens, or Collections, by status, and sort by newest.

The header strip shows the connected network with its live block height, total tokens, and combined market cap. Press / anywhere to search tokens; the palette lists the top five by market cap.

The app

Scanner#

Live trades and transfers across the protocol. Leave the filter empty to watch the whole registry, or paste a wallet address to follow one account. My wallet jumps to your own activity. Tabs narrow the feed to buys, sells, or transfers.

Each row shows the wallet, the action, the amount and token, the share of supply it represents, the ETH and dollar value, and when it happened. Rows expand for detail.

The app

Portfolio#

Your wallet’s view of the protocol: portfolio value, open positions, tokens launched by you, and collectible items held. Tabs filter between everything, tokens you hold, and tokens you created.

Balances are read from the chain, not a database. Item counts come from the collection contract, not from the balance: a buy mints one item per whole token you receive, while leftover fractions and tokens received by transfer never mint, so items can sit below whole tokens.

Tokens launched on an earlier generation of the contracts carry a legacy badge. They still exist onchain and balances are real, but they are not listed or tradable from the site, and the figures shown are the last ones indexed.

The app

Creator controls#

Every project you launch has a Creator controls page, linked from its token page. It shows the collection’s layers, elements onchain, canvas size, and whether the art is locked, alongside sample mints with a reroll.

Once trading opens the art is locked and every row is final. The page also shows creator earnings accrued from the 1% trading fee (the creator share is 70% of it) and the project’s fee recipient as recorded in the fee registry. From here you can edit the project page or open the token page.

Reference

Verifying an anchor#

Any party can verify a token’s source as follows.

1. 1

   Read the contract. The token exposes its source (the anchor hash), its origin (the genesis block), and its history.

2. 2

   Read the asset. The anchored file lives in contract storage and can be read back from the chain, byte for byte, by anyone.

3. 3

   Compare. Hash the recovered bytes and compare against the anchor. The Registry does this continuously; a check mark next to the hash means the onchain asset verifies.

Because the anchor is written at creation and cannot be altered or removed, a matching hash confirms that the stored bytes are the asset the token was created from.

Reference

Parameters at a glance#

Reference

FAQ#

Reference

Glossary#

Reference

Links#

• Apputoken.pro
• Xutokendotpro
• telegramBUY $µ ON UNISWAP