Creating tokens

Name and symbol identify the launch in the interface. Symbols are normalized to uppercase. Description, website, X, Telegram, and Discord links are stored in the immutable metadata document, displayed on the token page, and committed by its on-chain hash. A creator should verify every field before signing because a confirmed create transaction cannot be edited like a database draft.

• Use a unique, readable name and short symbol.
• Do not impersonate another project or reuse misleading art.
• Use HTTPS links that you control and expect to remain available.
• Review the creator wallet; it becomes part of the launch record.

The browser resizes the selected image, uploads it to the configured public token-image bucket, and receives a permanent HTTPS URL. Lotus then stores the complete metadata JSON in the same public bucket. Its permanent JSON URL is written on-chain, while the exact JSON is independently committed by hash. An image hint in that URL lets market feeds render artwork without adding another metadata request.

Existing tokens whose on-chain metadata URI starts with lotus:meta: do not contain a recoverable image URL. Their original art cannot be reconstructed from that hash alone.

Lotus creates the token with a zero first-buy value, parses the confirmed TokenCreated event, then performs an optional USDC approval and buy against the newly created curve. This two-step path avoids predicting deployment addresses. If create succeeds but approval or buy fails, the token still exists and the interface reports its address.

Preparing

Image and metadata are being finalized before any wallet request.

Signing

The wallet is waiting for approval or rejection.

Submitted

The transaction has a hash but is not yet confirmed.

Confirmed

The receipt succeeded and emitted the expected event.

Partial

Create succeeded, but the optional first-buy step did not.

Failed

No successful create receipt was found; read the surfaced reason before retrying.