How to Create a Token on Arc Mainnet in One Transaction
Create token on Arc Mainnet in one transaction: set supply, taxes, limits and ownership, then pay gas in USDC. One flat 50 USDC fee, no code, live in minutes.
To create token on Arc Mainnet: connect a wallet, enter the token's name, symbol, supply and rules, and sign one transaction with Arc Token Launch. Deployment settles in under a second, and the network gas as well as the flat 50 USDC service fee are both denominated in USDC, so the entire launch is paid from a balance you already hold. No Solidity, no compiler, no second token to bridge for gas.
That is the whole procedure. What actually determines whether people can trade your token afterwards is the configuration you choose before you sign, and that is what this guide covers.
Create token on Arc Mainnet: what you decide before you sign
Arc Mainnet is EVM compatible and targets the Osaka baseline, so a deployed token is an ordinary ERC-20: it works with every Arc wallet, with Uniswap on Arc, with the Arc Explorer and with any standard EVM tooling. There is nothing Arc-specific inside the contract itself. The Arc-specific parts are the transaction you submit and the asset you pay with — see how the USDC gas token works if the dual 18/6 decimal interface is new to you.
Every launch decision falls into five buckets:
| Decision | What it controls | Changeable later? |
|---|---|---|
| Supply model | Total supply, fixed or mintable, optional hard cap | Only while the owner role exists |
| Taxes | Buy, sell and transfer fee percentages and up to four recipients | Yes, with owner |
| Limits | Max transaction and max wallet, trading delay, anti-sniper blocks | Yes, with owner |
| Deflation | Burn-on-transfer share or scheduled supply reduction | Yes, with owner |
| Ownership | Whether an owner role survives deployment at all | Revoking is permanent |
The important structural point: a parameter you can change later is a parameter a buyer has to trust you about. A parameter you remove at deployment is a fact they can check.
Step 1 — Pick a supply model that matches your story
A fixed supply of 1,000,000,000 tokens is the familiar default, and it is the easiest thing to explain. A mintable supply with a hard cap lets you release tokens over time, but every buyer now has to read the cap and the mint authority before they trust the distribution — which is exactly the kind of friction that shows up in a rug check.
Decide this first, because taxes, allocation and pool capital are all expressed as shares of supply.
Step 2 — Taxes: 0% is the honest default
Taxes transfer value away from traders on every swap. They fund marketing, development, liquidity and burns, and up to four recipients can receive a share. On Arc the mechanics are unremarkable: a tax token is still an ERC-20, and Uniswap V2 pairs on Arc handle tax-on-transfer tokens the same way V2 pairs do elsewhere.
Three practical warnings:
- A high tax is a sellability problem, not just a revenue stream. Stacks of launch failures come down to taxes so aggressive that trading becomes irrational.
- Tax and sniper protection interact. Anti-sniper protection that blocks buys for a set number of blocks is a tax on the first buyers, and competent buyers will wait it out.
- Anything above single digits needs to be justified in public, in advance. "5% buy, 5% sell, 4% to liquidity, 3% to development, 3% to burn" is a sentence you can put in a launch post. "40% sell tax, reasons later" is not.
Step 3 — Limits and trading control
Maximum transaction size and maximum wallet holding are capped during a token's early life to slow down whales and snipers. Both are useful for the first hours and both become restrictive once the token has organic flow; because they remain editable with the owner role, most teams lift them once the pool is stable. Note that Arc has no mempool priority auction for you to game, and no onchain randomness — PREVRANDAO returns 0 — so any randomness-based mechanic you build has to bring its own oracle. See the Arc EVM differences reference for the full list.
Step 4 — Ownership: keep it or revoke it
Keeping the owner role lets you adjust taxes and limits with the Arc Token Manager later. Revoking it at Revoke Ownership removes that ability permanently — no tax changes, no minting, no blacklisting, ever. Both are defensible. What is not defensible is claiming one while doing the other.
Step 5 — Decide the launch shape, not just the token
A token with no liquidity has a contract address, not a market. You have three routes:
- Token only, pool later — deploy with Arc Token Launch, then create the pair with the Arc Liquidity Pool Creator. Simple, but it leaves a gap in which you have broadcast your contract with no market behind it.
- Token and pool, then outsiders buy — the standard sequence. Works well when you are listing quietly.
- Atomic bundle launch — contract, pool, initial liquidity and coordinated buys in one transaction, so no bot can buy ahead of your opening price. This is what Arc Bundle Launch does, and for a token where the opening price matters it removes an entire category of risk.
What it costs
Arc's fee market enforces a minimum maxFeePerGas of 20 Gwei, and transactions priced below it are dropped by the mempool without an error. Because gas on Arc is paid in native USDC at 18 decimals, the arithmetic is unusually readable: at exactly the 20 Gwei floor, 1,000 gas costs 0.00000002 USDC. A deployment consuming 1,500,000 gas therefore costs 0.03 USDC in network fees — a rounding error next to the flat 50 USDC service fee. The exact gas number depends on your configuration; the metering reference is Arc's gas and fees documentation.
A realistic first launch total, including the pool:
| Line item | Cost |
|---|---|
| Arc Token Launch service fee | 50 USDC |
| Deployment gas (~1.5M gas at 20 Gwei) | ~0.03 USDC |
| Liquidity Pool Creator service fee (if you seed a pool) | 50 USDC |
| Pool creation + add liquidity gas | ~0.02 USDC |
| Initial pool capital | Your choice — the real number |
Full breakdown including airdrop and lock costs: how much it costs to launch a token on Arc.
Five mistakes that show up in the first hour
- Deploying with no pool capital decided. The contract deploys in a second; a credible pool does not appear by itself.
- Setting a maximum wallet limit below the pool's own liquidity. The pair contract can trip your own limit if it is excluded from it incorrectly, which blocks trading.
- Announcing a contract address before the pool exists. Anyone can watch for a launch and buy the first swap.
- Revoking ownership before testing taxes and limits. Revoking is a one-way door. Configure, test on a small buy, then revoke.
- Forgetting that Arc finalises in under a second. One confirmation is final; there is no reorg window and no "wait for six blocks" step. Your launch and your buyers' buys are settled as soon as they land, so nothing you do afterwards can be reordered.
After the token exists
The work moves from deployment to operations: redistribute supply with the Arc Token Multisender, export holders with Arc Token Snapshots, reduce supply with Burn Tokens on Arc, or deepen the market with Add Liquidity. Budget the whole sequence, not just the deploy, using the Arc Mainnet launch checklist.
Arctools is not affiliated with Circle or the Arc Foundation. It is a tool suite built for Arc Mainnet, and every tool charges the same flat 50 USDC per use — snapshots and the token checker are free.