# Launch Your First Token

Launch your service-backed token on TokenMesa in four simple steps. Takes approximately 10 minutes with no coding required.

## Prerequisites

**Wallet**: MetaMask or compatible Web3 wallet with \~$5-10 ETH for gas fees

**Capital**: Initial liquidity of 10-30x your expected daily service transaction volume (see Step 4)

**Planning**: Token name, symbol, total supply, initial price, burn rate, and revenue vesting period

***

## Step 1: Create Your Token

Deploy a new ERC20 token or use an existing one.

### Deploy New Token

1. Enter token name (e.g., "Acme AI Credits")
2. Enter token symbol (e.g., "ACME")
3. Set total supply (**10M-100M recommended**)
4. Deploy and approve transaction

**Note**: Total supply is permanent. Choose higher if unsure - you can create scarcity through burns but cannot mint more later.

### Use Existing Token

1. Select "Use Existing Token"
2. Enter contract address
3. Verify and confirm

***

## Step 2: Deploy TokenMesa Contract

Configure your token economics:

**Burn Rate**: Percentage of tokens permanently destroyed per withdrawal (**2-5% recommended**) → [Learn about burn mechanisms](/core-concepts/burn-mechanism.md)

**Revenue Vesting Period**: How quickly USDC revenue unlocks for buybacks (**7-30 days recommended**) → [Learn about revenue vesting](/core-concepts/revenue-vesting.md)

**Slippage Tolerance**: Maximum price impact allowed per buyback transaction (**5-10% recommended**). Each revenue vesting buyback will not exceed this tolerance, protecting against price manipulation.

**Warning**: Setting to 0 disables price impact protection, making buybacks vulnerable to front-running and manipulation.

**Recipient Address**: Wallet receiving service tokens after withdrawal (use secure treasury wallet)

**Owner Address**: Address with permission to modify parameters (use hardware wallet)

### Deploy

1. Review all parameters
2. Click "Deploy TokenMesa Contract"
3. Approve transaction
4. **Save your TokenMesa contract address** for settlement layer integration

**Gas Cost**: \~$1-3 in ETH

***

## Step 3: Create Liquidity Pool

Create a Uniswap V4 pool paired with USDC.

### Configuration

**USDC Pairing**: All TokenMesa pools use USDC for stable value reference

**Initial Price**: Set starting price in USDC (**0.01 to 0.1 USDC recommended**)

**Fee Tier**: 0.3% swap fee (automatically configured, standard rate), goes to liquidity provider (the service provider initially)

### Create Pool

1. Confirm USDC pairing
2. Enter initial token price
3. Click "Create Pool" and approve transaction

**Gas Cost**: \~$1-2 in ETH

***

## Step 4: Add Initial Liquidity

Provide USDC + tokens to activate trading.

### How Much Liquidity

**Formula**: Initial Liquidity = 10-30x Daily Service Transaction Volume

**Examples**:

* $200/day revenue → $2,000-$6,000 liquidity (1,000-3,000 USDC + equivalent tokens at $1/token)
* $1,000/day revenue → $10,000-$30,000 liquidity (5,000-15,000 USDC + equivalent tokens at $2/token)
* $5,000/day revenue → $50,000-$150,000 liquidity (25,000-75,000 USDC + equivalent tokens at $0.50/token)

### Add Liquidity

1. Enter USDC amount
2. Approve USDC spending (first-time only)
3. Approve token spending (first-time only)
4. Click "Add Liquidity" and approve transaction

**You receive**: LP tokens representing pool ownership + proportional share of 0.3% swap fees

**Gas Cost**: \~$0.50 per approval + \~$2-4 for liquidity

**Note**: With upcoming [price stabilization](/core-concepts/price-stabilization.md), you'll be able to bootstrap with <$100 in liquidity.

***

## Post-Launch Checklist

### 1. View Management Dashboard

Connect your owner wallet to the TokenMesa dashboard to monitor:

* Current burn rate and vesting schedule
* Revenue flow and buyback activity
* Transaction history

→ [Managing your token](/getting-started/managing-token.md)

### 2. Test Revenue Flow

1. Send small amount of USDC (e.g., $1) to your TokenMesa contract
2. Execute withdrawal on TokenMesa dashboard
3. Verify automatic token economics:
   * USDC swaps to service tokens
   * Burn executes
   * Service tokens arrive at recipient address

### 3. Configure Settlement Layer

Connect payment processors to your TokenMesa contract:

* x402 Protocol for AI agent micropayments
* Coinbase Commerce for crypto payments
* Other payment processors

**Important**: Use your **TokenMesa contract address** (not your wallet) as payment recipient.

→ [Settlement Layer Integration](/getting-started/settlement-integration.md)

### 4. Share Token Information

Prepare for your community:

* Token contract address
* TokenMesa contract address
* Uniswap pool link
* Initial service token pricing (e.g., "1 token = $1 of API credits")
* Tokenomics parameters (burn rate, vesting period)

***

## Troubleshooting

**"Insufficient gas"**: Add $5-10 ETH to your wallet

**"Insufficient token balance"**: Ensure you have enough tokens for liquidity (calculated in Step 4)

**"Price impact too high"**: Add more liquidity to reduce slippage

**Pool not showing on Uniswap**: Wait 5-10 minutes for indexing

**Cannot approve spending**: Check correct network selected in wallet

**Need help?** Check [FAQs](/resources/faqs.md) or join our [Community](/resources/community.md)

***

**Welcome to TokenMesa!** Your service-backed token is live. Focus on delivering great services - TokenMesa handles the token economics automatically.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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.tokenmesa.com/getting-started/launch-first-token.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.