Tzero
Launch
Documentation

Technical specification for T0dotfun — from token deployment to TzeroSwap liftoff.

Token Supply Allocation and Factory Deployment Mechanics

800 Million Bonding Curve Tokens and 200 Million DEX Reserve

When a creator submits the launch form on Tzero (t0dotfun.com), the factory contract deploys a new ERC-20 token with 1,000,000,000 units (18 decimals). Exactly 800,000,000 tokens are placed into the bonding curve for public trading, and 200,000,000 tokens are reserved inside the contract to pair with raised ETH at liftoff.

On-Chain Metadata and Atomic First-Buy Protection

Mission artwork and metadata (description, X handle, Telegram link, and website) are pinned and referenced by the mission registry. If the creator specifies an initial ETH buy amount, the factory executes the token creation and the first bonding curve buy in the same atomic transaction so bots cannot front-run the launch block.

Immutable Security Guarantees for Every Launched Token

Zero Admin Keys and Standardized ERC-20 Compliance

All Tzero mission contracts inherit from a hardened, minimal ERC-20 implementation with no owner state variable, ensuring every token behaves predictably across wallets, aggregators, and TzeroSwap pools.

Frequently Asked Questions (FAQ)

How is the 1,000,000,000 token supply divided at launch on Tzero?

Eighty percent (800,000,000 tokens) is available for trading on the bonding curve, and 20 percent (200,000,000 tokens) is locked for the TzeroSwap liquidity pool at liftoff.

How does the optional creator first buy prevent bot sniping?

Because the creator's first purchase is bundled inside the same transaction that deploys the token contract, it is guaranteed to execute at index zero before any external transaction can interact with the curve.

Can token metadata or social links be added during launch?

Yes. Creators can attach an image, project description, website URL, X profile, and Telegram link directly in the /launch workflow.