# Standard Mode Creation

Standard mode is the default, simplest way to create a coin on Base.meme. It uses the platform defaults for funding target and token distribution.

![Standard mode creation screen](/files/Ye2swJKNULYFX4Jaf4hn)

## Step-by-step guide

1. Keep **Standard** selected.
2. Fill in the coin details (see field reference below).
3. Select a **Payment Token** (ETH / USDC / SOL).
4. Configure **Tax** settings (optional).
5. **Initial token purchase** (optional)
   * You have the opportunity to purchase a portion of the token supply in the same transaction to help protect your launch from snipers.
6. When you're finished, click **Create Coin** and approve the transaction prompt from your wallet.

Note: Coin details can’t be changed or edited after creation, choose carefully.

Your coin is now live once creation completes. After your upload has been processed, your coin will be ready to trade and share with your community.

## Field reference

### Coin Name

The name of your coin as displayed across Base.meme.

### Ticker Symbol

Your coin’s ticker (for example, `PEPE`). This is used to identify your coin when trading.

### Description (optional)

A short description of the coin. This is shown on the coin page and helps traders understand what the coin is about.

### Social links (optional)

Links to your project’s social accounts (for example X / Telegram / Website). These appear on the coin page to help your community find the official channels.

### Media

Upload a cover image or video for your coin.

* Supported formats: JPG, PNG, GIF, MP4
* Max size: 2GB

### Payment Token

The token used as the backing currency during the Bonding Curve phase (for example ETH, USDC, or SOL). It also determines the denomination shown for fees and rewards.

### Tax Configuration (optional)

Configure a token tax that is charged on every transfer and trade. Tax is optional — setting the rate to 0% disables it.

* **Tax Rate**: The percentage charged on each transfer and trade (default 0%).
* **Distribution Split**: Allocate the collected tax across four channels:
  * **Funds Recipient** — direct revenue to a designated wallet (or to a Vault, see below).
  * **Holder Dividend** — proportional distribution to all token holders.
  * **Token Burn** — buyback and burn to reduce circulating supply.
  * **Add to Liquidity** — routes tax back into the Uniswap V2 liquidity pool.
* **Funds Recipient Address**: The wallet that receives the Funds Recipient share. Defaults to the creator wallet.

Tax parameters are fixed at creation and cannot be changed afterward. For full details, see the [Tax Token](/fees-rewards/tax-token.md) page.

### Vault Type (optional)

When Tax is enabled, you can optionally select a **Vault** in place of the Funds Recipient address. The Vault is a strategy contract that automatically manages the tax revenue routed to the Funds Recipient channel. The available Vault types are:

* **SnowBall** — All tax revenue is used for continuous buyback & burn, creating pure deflation. [Learn more](/vaults/snowball.md)
* **BurnDividend** — Starts with buyback & burn, then transitions to a dividend model when the first holder burns tokens. Burners earn a proportional share of future tax revenue. [Learn more](/vaults/burndividend.md)
* **Gift** — A designated X (Twitter) account controls where tax revenue goes. Requires posting a management tweet at least once every 7 days; otherwise falls back to buyback & burn. [Learn more](/vaults/gift.md)
* **Split** — Tax revenue is automatically distributed among up to 10 recipients based on pre-configured percentage shares. [Learn more](/vaults/splitvault.md)

Vault selection requires **ETH** as the payment token. The Vault type is fixed at creation and cannot be changed afterward. For a full overview, see the [Vaults](/vaults.md) page.

### Initial token purchase (optional)

If available in your flow, you can optionally buy a portion of the supply in the same transaction to help protect the launch from snipers.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.base.meme/using-base.meme/detailed-creation/standard-creation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.