Skip to main content

Create a Token

Flipit's normal creation form is intentionally small.

Required inputs​

  • Token image
  • Token name
  • Ticker
  • Target market cap in zkLTC

Description is optional.

Behind the interface, Flipit persists the image and immutable metadata, creates a pending application record, then asks the connected wallet to submit LaunchManager.createLaunch with the backend-generated metadata URI.

Contract validation​

LaunchManager enforces:

  • name length: 1–64 bytes;
  • symbol length: 1–16 bytes;
  • metadata URI length: 1–512 bytes;
  • target market cap within the deployment's immutable minimum and maximum;
  • exact launch fee payment (currently zero on LiteForge).

What gets created​

A confirmed launch creates:

  1. immutable fixed-supply LaunchToken;
  2. creator FeeVault;
  3. isolated LaunchSale;
  4. canonical token/wrapped-zkLTC Pool in an unbootstrapped state.

The frontend decodes the confirmed LaunchCreated receipt for immediate navigation. The backend independently verifies the same receipt before marking the application record confirmed.

Wallet authority

The backend does not sign the creation transaction. Your wallet submits the transaction directly to the LiteForge contracts.