Sonic Mainnet - Chain 146New network

Sonic Chain token creator and ERC-20 launch tools

Deploy an ERC-20, build Equalizer V2 liquidity and continue into supply, metadata, distribution, vesting and LP controls from one connected Sonic workflow.

Use SolCreate when you need a Sonic token creator that keeps the deployment, liquidity, mint, burn, ownership and distribution steps separated. The route is designed for builders comparing a Sonic ERC-20 launch with other supported EVM chains and choosing the exact action they are ready to sign.

Open Sonic Creator Open Sonic Equalizer Liquidity

10 S fixed SolCreate feeWallet-confirmedSonicScan links

Sonic token operations network connecting creation, liquidity and token controls

CreateLiquidityControl

Sonic launch stack

One connected path from contract to LP

Each tool checks Sonic chain ID 146 and keeps the connected wallet as the final approval layer. The creator route is for contract deployment, the Equalizer route is for token/wS pool movement, and the mint and burn routes are for existing-token supply changes.

Bridge assets to Sonic

01Deploy Sonic ERC-20Use the live creator only for a fresh wallet-confirmed Sonic contract with a fixed 10 S SolCreate fee.->02Equalizer V2 liquidityAdd or remove a volatile token/wS pool position after the token address and pool ratio are ready.->03Sonic mint allocationIssue a reviewed recipient allocation only after live owner-wallet and mint-permission checks.->04Burn wallet-held supplyReduce wallet-held ERC-20 token supply after amount, balance and decimals are checked.->05Sonic owner controlsReview Sonic metadata, freeze behavior, mint permission and ownership before a wallet-confirmed control update.->06MultisenderDistribute S or compatible ERC-20 tokens to many wallets.->07Token vestingCreate an on-chain token release schedule for a beneficiary.->08LP lock and burnLock, release or permanently burn Equalizer V2 LP tokens.->

Network

Sonic mainnet

Chain ID 146 - S gas

Token model

SolCreate ERC-20

Supply and authority controls

Liquidity

Equalizer V2

Volatile token/wS pairs and ERC-20 LP

Sonic token creator checklist

Before opening the Sonic ERC-20 creator, prepare the token name, ticker, decimals, starting supply, recipient wallet, owner wallet and launch note. SolCreate keeps the fixed 10 S service fee, Sonic chain ID 146 and wallet confirmation visible so builders can review the deployment before signing.

This is the only Sonic route in the cluster that is built for the create-token wallet task. The other Sonic live pages intentionally avoid deployment language and focus on liquidity, owner-authorized mint allocations, wallet burn reductions, controls, distribution or LP custody.

Sonic liquidity and LP path

After a token address exists, move to Sonic Equalizer liquidity for token/wS pair planning, reserve checks and LP output review. The LP tools route is reserved for lock, release or burn decisions on the Equalizer V2 LP token, which is different from burning project token supply.

Use this route when the builder is preparing Sonic liquidity, Equalizer V2 pool setup, LP output, reserves, slippage or LP custody handoff; do not describe it as a token creator, mint page or burn page.

Sonic allocation and distribution controls

Use Sonic mint only for owner-authorized recipient allocations, Sonic burn only for wallet-held balance reduction, Sonic owner controls for metadata and ownership review, multisender for immediate recipient batches and vesting for transparent release schedules.

Supply-control tools should answer owner-action queries such as Sonic mint allocation or burn Sonic ERC-20 balances, while multisender and vesting pages support recipient-list and unlock-schedule searches.

Sonic launch route map

Keep the Sonic token launch record readable after each wallet action

A Sonic ERC-20 launch is easier to review when the contract, liquidity, supply, owner-control, distribution and LP-custody decisions are documented as separate steps. Use this route map to choose where each SolCreate Sonic record belongs before the wallet signs.

Read the Sonic ERC-20 creator, mint and burn workflow guide

Sonic ERC-20 deployment record

Use the Sonic Chain token creator for the first contract only. Save the contract address, owner wallet, recipient, starting supply, decimals, mint status and the transaction hash before moving into liquidity or supply tools.

Create Sonic ERC-20 token

Sonic Equalizer liquidity record

Use Sonic Equalizer liquidity after the token address exists and the team can review token/S amounts, reserve context, slippage comfort and LP output. Keep pool setup separate from contract creation and wallet-held token burns.

Review Sonic liquidity route

Sonic mint and burn supply record

Use Sonic mint for owner-approved recipient issuance and Sonic burn for wallet-held ERC-20 balance reduction. Record the amount, decimals, wallet role and reason so supply changes do not look like liquidity or LP custody actions.

Check Sonic supply routes

Sonic controls and distribution record

Use Sonic token controls for ownership and metadata state, multisender for immediate batches and vesting for delayed release schedules. These pages help a launch team separate authority updates from recipient movement.

Open Sonic token controls

Sonic LP custody and scanner record

Use Sonic LP tools when the Equalizer V2 LP token needs a lock, release or burn decision, then pair the transaction hash with scanner review notes so holders can read pool custody, supply and owner choices together.

Open Sonic LP custody route

Create Sonic token without coding

A Sonic token launch checklist for builders who need a real contract path

Start with contract creation, then move into liquidity, token controls and launch-review steps only when each wallet action matches the plan. Use this Sonic ERC-20 route when the project needs Sonic mainnet deployment instead of a generic EVM workflow or an isolated control action.

1. Prepare the Sonic ERC-20 settings

Write the name, symbol, decimals, starting supply, recipient wallet and owner wallet before opening the live creator. Keep the owner wallet plan separate from marketing copy so every signer knows what can still change after deployment.

Open Sonic token creator

2. Plan Equalizer liquidity after creation

Do not mix token deployment with LP custody. After the contract exists, use Sonic liquidity for token/S pool setup and use Sonic LP tools only when the LP token should be locked, released or burned.

Review Sonic liquidity

3. Keep mint, burn and ownership pages distinct

Mint expands supply, burn reduces wallet-held tokens, token controls manage permissions and metadata, and vesting documents delayed allocations. Each action deserves its own wallet-confirmed step and internal link.

Review Sonic token controls

4. Compare Sonic with other supported creator routes

If the project actually needs Solana/SPL, Robinhood Chain, Ethereum, BNB, Polygon, Avalanche, TRON or Sui, send the team to the matching SolCreate route instead of forcing the Sonic page to cover every chain.

View supported creator routes

Sonic launch decisions

Pick the Sonic tool by the wallet action you are ready to sign

A Sonic Chain token creator route helps builders choose the right next step without pushing every action into one form. Start with the ERC-20 creator for deployment, then move to Equalizer liquidity, supply controls, distribution, vesting or LP custody only when that specific transaction matches the project plan.

Create Sonic token

Use the live creator when the name, symbol, decimals, starting supply and owner wallet are ready. SolCreate shows the Sonic chain context and fixed 10 S fee before the final deployment confirmation.

Open Sonic ERC-20 creator

Add Sonic liquidity

Use the Equalizer V2 liquidity route when the token address, S amount, token amount, slippage comfort and LP custody plan are prepared. Keep liquidity decisions separate from minting or burning supply.

Open Sonic liquidity tool

Review Sonic allocations

Use mint only when compatible authority exists and a recipient allocation is documented. Use burn only when wallet-held tokens should be permanently reduced after balance, decimals and amount checks.

Review Sonic mint path

Review launch safety

Use token controls for metadata and ownership, multisender for recipient batches, vesting for timed releases, LP tools for Equalizer LP custody and the scanner for public token-risk context after deployment.

Open token scanner

Sonic creator comparisons

Decide whether Sonic is the right ERC-20 route before opening a wallet

SolCreate treats Sonic as a first-class creator route, but the best launch path depends on chain fit. Use this Sonic token creator comparison when a team is choosing between Sonic mainnet, Base, BNB, Polygon, Ethereum or another supported SolCreate network before signing a new contract, liquidity action or supply-control transaction.

Compare Base ERC-20 launches

Pick Base when the project needs Coinbase-aligned distribution, Base gas assumptions or Aerodrome liquidity instead of Sonic mainnet and Equalizer V2.

Open Base creator comparison

Compare BNB deployment

Use the BNB route when BEP-20 chain fit, BNB gas and PancakeSwap-style launch planning fit better than a Sonic token creator path.

Open BNB deployment route

Compare Polygon creator

Choose Polygon when the wallet, community or cost model calls for Polygon PoS rather than Sonic chain ID 146 and S-gas approvals.

Open Polygon creator route

Compare Ethereum ERC-20 guide

Stay with Ethereum when mainnet ERC-20 recognition matters more than Sonic-specific fee review, liquidity routing and post-launch Sonic tool coverage.

Open Ethereum ERC-20 guide

Can SolCreate create a Sonic ERC-20 token?

Yes. The Sonic ERC-20 Token Creator route lets a connected wallet review token name, symbol, decimals, starting supply, owner wallet and the fixed 10 S SolCreate fee before signing deployment on Sonic mainnet.

Which Sonic liquidity route does SolCreate support?

The Sonic liquidity tool is built around Equalizer V2 token/wS pools. Builders can add or remove liquidity, then use the LP tools route for lock, release or burn decisions on the LP token.

How should I compare Sonic with other SolCreate chains?

Choose Sonic when the project needs Sonic mainnet deployment, S gas and Equalizer V2 liquidity. If the launch plan depends on Base or BNB EVM reach, Polygon cost profile, Avalanche C-Chain, Ethereum, Solana SPL tooling, TRON, Sui or Robinhood Chain, use the matching SolCreate route instead of forcing the Sonic workflow.

What belongs in a Sonic token launch record?

A Sonic token launch record should keep the contract address, owner wallet, starting supply, mint status, Equalizer liquidity plan, LP custody decision, distribution path and scanner review notes together so each wallet-confirmed action can be checked later.