01 - Deploy
Create the Base contract
Prepare token identity, supply, recipient and owner. Review retained or revoked authorities before the wallet confirms deployment.
SolCreate
Base Mainnet - 8453Aerodrome launch stack0.001 ETH / action
Base launch control room
Base Token Creator
Create a Base ERC-20 token with a wallet-confirmed deployment path, then keep Aerodrome liquidity, supply, ownership, distribution, vesting and LP controls connected to the same launch record.
Use this Base Token Creator for ERC-20 launches, Aerodrome liquidity and post-launch controls when the project needs its first contract on Base Mainnet, not just a generic token generator or a later mint or burn form.
Native Base workflow
One Base token control room from contract deployment to Aerodrome LP
Choose the Base tool by the transaction you are ready to sign. Creation deploys a new ERC-20 contract, Aerodrome manages token/WETH liquidity, and every administration route first reads the live Base contract state so mint, burn and control pages do not compete with the creator page.
01Create Base tokenDeploy a wallet-confirmed ERC-20 with supply and authority settings.->02Aerodrome liquidityAdd or remove a volatile token/WETH pool position with reserve and LP checks.->03Mint more supplyIncrease compatible supply after live owner and mint-permission checks.->04Burn token balancePermanently reduce tokens held by the connected wallet.->05Token controlsManage metadata, freeze behavior, mint permission and ownership.->06MultisenderDistribute ETH or compatible ERC-20 tokens to many recipients.->07Token vestingCreate an on-chain release schedule for a beneficiary.->08LP controlsLock, release or permanently burn compatible Aerodrome LP tokens.->
Base network
Base Mainnet
ETH gas and wallet-confirmed actions
Creator role
SolCreate ERC-20
Supply and authority settings for the first contract
Liquidity venue
Aerodrome
Volatile token/WETH pools and LP-position context
02 - Market
Establish Aerodrome liquidity
Choose the token-to-ETH ratio deliberately. SolCreate reads the volatile token/WETH pool, reserves and LP position before approval.
03 - Operate
Manage supply and distribution
Use separate wallet-confirmed routes for mint, burn, metadata, ownership, batches, vesting and LP custody with Basescan evidence.
Base ERC-20 launch checklist
Create a token on Base with the contract, wallet and liquidity notes in one place
A useful Base token creator should do more than output bytecode. SolCreate keeps the ERC-20 deployment inputs, Base chain ID, fixed fee, owner choices, Aerodrome handoff and follow-up tool routes together so builders can explain what was signed before they share the contract.
Before deployment
Prepare the Base token name, symbol, decimals, initial supply, recipient wallet and owner plan before opening the live creator. If supply should be fixed, decide that before the first wallet confirmation.
Open live Base creatorAfter the contract exists
Save the Basescan contract link, deployer wallet, recipient wallet, owner state and mint-permission choice. That record supports scanner review, marketplace profiles and community due diligence.
Review scanner signalsBefore liquidity
Plan token/WETH ratio, available ETH on Base, approval flow, slippage tolerance and LP custody before adding an Aerodrome position. Liquidity is a separate wallet action after creation.
Plan Aerodrome liquidityAfter launch operations
Use Base token controls, mint, burn, multisender, vesting and LP tools only when the matching wallet-confirmed action belongs in the public launch record.
Review Base controlsBase ERC-20 route map
Choose the Base token creator when the project needs its first ERC-20 contract
The Base token creator guide is the planning surface for a first ERC-20 deployment on Base. It explains how the live creator, Aerodrome liquidity, mint, burn, token controls, multisender, vesting and LP tools fit together without turning every post-launch action into the same page. Builders preparing a new Base token should start with the creator path; teams with an existing contract should move to the route that matches the exact wallet action.
Base ERC-20 creator route
Use the live creator for token name, symbol, decimals, initial supply, recipient and owner decisions before the connected wallet signs deployment.
Live Base ERC-20 Deployment ToolBase Aerodrome liquidity route
Use the liquidity page when a Base token already exists and the team is ready to review token/WETH pool state, approvals and LP-position records.
Prepare Aerodrome liquidityBase mint and burn routes
Use mint for owner-authorized supply increases and burn for wallet-held token reductions; neither route creates the original Base contract.
Review Base mintingBase controls and distribution routes
Use controls, multisender, vesting and LP tools for documented administration, distribution, release schedules and Aerodrome LP-token custody.
Open Base controlsBase launch evidence
Keep Base contract, Aerodrome and scanner notes connected before the launch link spreads
A Base launch record is easier to trust when it joins the creator transaction, owner choices, token/WETH pool plan and follow-up review notes. SolCreate keeps those steps close together so teams can explain what was deployed, what still needs a wallet action and which risk signals deserve a second look.
Contract record
Save the Base contract address, deployer wallet, initial recipient and owner decision before opening liquidity or distribution routes.
Aerodrome context
Keep pool, reserve, approval and LP-custody notes separate from the original token deployment so the market step is easy to explain.
Authority and supply review
Check whether mint permission, ownership and future supply changes match the public launch plan before new allocations or burns happen.
Scanner follow-up
Use a scanner review after deployment and liquidity preparation so holders can compare contract, wallet and pool signals without relying on slogans.
Base creator comparison
Pick a Base token creator by deployment evidence, not generic generator claims
Generic ERC-20 generators often stop at contract deployment. A serious Base launch plan explains the next evidence trail: who deployed, which wallet owns the token, how Aerodrome liquidity will be handled, and which post-launch controls are still available.
Base deployment evidence
Record the Base contract address, fee confirmation, deployer wallet, initial recipient and owner settings before the token is shared publicly.
Base authority choices
Decide whether mint permission and ownership should remain active, be transferred or be revoked, then keep the explanation close to the creator transaction.
Base Aerodrome readiness
Plan the token/WETH pool path separately from token creation so liquidity approvals, LP custody and pool records do not get mixed with the original deployment.
Base post-launch operations
Use scanner review, multisender, vesting, token controls, mint and burn only when that specific wallet-confirmed action matches the documented Base launch plan.
Base launch questions
Plan the Base creator path before the first wallet confirmation
A good Base ERC-20 launch record names the deploying wallet, recipient wallet, authority choices, liquidity path and evidence links before the contract address starts moving through communities.
What belongs on the guide?
Use this overview to pick the correct Base workflow, compare first deployment with later supply actions and keep the full tool stack close to one launch plan.
When is the live creator enough?
Open the live creator when token settings are ready, ETH for Base gas is available and the connected wallet can review the fixed SolCreate fee plus deployment transaction.
What happens after deployment?
Continue into Aerodrome liquidity, scanner review, token controls, batches, vesting or LP custody only when that specific wallet-confirmed operation matches the launch plan.