The Arc Mainnet FAQ: launches, fees and fixes

Arctools is a suite of onchain tools for Arc Mainnet, the stablecoin Layer 1 where USDC pays the gas. It covers the whole life of a token: deploying it with a standard launch or an atomic bundle launch, airdropping it with a multisender, creating and managing Uniswap liquidity, then updating taxes, taking holder snapshots, burning supply and renouncing ownership.

A wallet that supports custom EVM networks, the Arc network added to it — chain id 5042 — and a USDC balance on Arc. That one balance pays both the service fee and the network gas, because USDC is Arc's native gas token. There is no account to create, no email to confirm, and nothing to bridge if you already hold USDC on Arc.

No. Arctools has no account system, no email capture and no custody layer. Connecting a wallet is the only identity the site needs, and the only things kept in your browser are that connection and your theme preference — page views are counted in aggregate rather than per visitor.

If you hold a token and are deciding whether to trust it, start with the free Token Checker — it costs nothing and submits nothing. If you are launching, Token Launch is the plain path: one deploy, full control afterwards. Reach for Bundle Launch when you want the deploy, the pool and buys from up to 40 wallets to land in a single transaction so nobody can trade in front of your liquidity.

Yes. Desktop browser wallets connect directly — Arctools discovers them through EIP-6963, so MetaMask, Rabby, Coinbase Wallet, Rainbow and OKX appear without extra configuration. Mobile wallets connect through WalletConnect, where the session is approved in the wallet app rather than in the browser.

No. Every tool is a form. You set the parameters, review exactly what the transaction will do, and sign once — the contract templates and the wiring are already deployed. Nothing here requires a compiler, a build pipeline or a node of your own.

Every service that submits a transaction costs a flat 50 USDC, charged once per use. There is no percentage of your token supply, no per-wallet or per-recipient charge, no subscription and no gas markup. Read-only tools — the Token Checker and holder Snapshots — are free.

Inside the same transaction as the work it pays for. The service contract forwards the flat fee to the Arctools treasury before it does anything else, so the fee and the work succeed or fail together. If the transaction reverts, the whole call is unwound and no service fee is taken — you only lose the gas the network had already spent.

No. Arc network gas is paid separately to the network and is also denominated in USDC, so both costs come out of the same balance. At Arc's 20 Gwei minimum base fee, 1,000,000 gas costs about 0.02 USDC, which makes gas a rounding error next to the service fee for most operations.

The fee is a value stored on each service contract, readable before you sign by calling its fee() function, and it cannot be raised above a hard ceiling of 10,000 USDC that is compiled into the contract. Because the price lives onchain, the exact amount is always visible in your wallet's confirmation screen before you approve it.

Surplus is refunded to you inside the same transaction. Launch and liquidity functions expect fee plus capital, and the multisender subtracts the fee from what you send before distributing — anything left over is returned rather than kept.

No listing fee, no priority queue, no protocol token and no upsell. The only other cost is whatever the transaction itself moves: the capital you put into a pool or into bundle buys, and the swap fee Uniswap takes on those buys — 0.30% on a V2 pair.

Arc is Circle's stablecoin Layer 1. Its native asset is USDC rather than ETH, it is EVM compatible — Solidity, viem and standard wallets work unchanged — and it targets Ethereum's Osaka hard fork as its execution baseline. Transactions finalise on inclusion, with sub-second, deterministic finality.

No. USDC is the gas token, so the stablecoin you already hold pays for gas, for swaps and for the Arctools service fee. There is no wrapped USDC involved and no second asset to acquire before your first transaction.

It should not, and neither does Arc. There is one USDC balance with two interfaces: a native interface at 18 decimals, used by gas, msg.value and your wallet balance, and an ERC-20 interface at 6 decimals, used by pool math and transferFrom. Divide the native figure by 10 to the 12th to get the ERC-20 figure. If a tool presents them as two separate assets, the tool is wrong.

Arc enforces a minimum base fee of 20 Gwei, and a transaction whose maxFeePerGas is below that is silently dropped by the mempool: no error, no receipt, nothing in a block. Arctools caps every write up to the floor for you, which is why transactions sent from this site do not disappear.

It is final the moment it is included in a block. Arc's finality is deterministic and sub-second with no reorg window, so a single confirmation is final and Arctools never waits for a second one.

The Arc Explorer at explorer.arc.io. Every Arctools success screen links straight to the transaction, and any contract address can be pasted into the explorer's search box to read its code, events and holdings.

Yes — Arc Testnet, chain id 5042002, RPC rpc.testnet.arc.io, with test USDC from the Circle faucet. Arctools is built for Arc Mainnet: the liquidity tools read Uniswap addresses that only exist on mainnet, so treat testnet as somewhere to experiment with contracts rather than a full rehearsal.

Token Launch deploys the contract and stops there: you own the token, trading stays closed until you enable it, and you create the pool when you are ready. Bundle Launch does the deploy, the Uniswap pool, the initial liquidity and coordinated buys from up to 40 wallets in one atomic transaction, which removes the window in which a bot could buy ahead of your liquidity.

Name, symbol, decimals and supply, an optional hard cap, buy and sell taxes with up to four recipients, burn-on-transfer or deflationary mechanics, maximum transaction and maximum wallet limits, an anti-sniper window that blocks pool buys for the first blocks after trading opens, the trading switch itself, and whether you keep or renounce ownership.

Yes, if you kept the owner role. Token Manager reads your token's live configuration and lets you update tax rates, recipients, limits and exemptions. If you renounced ownership at launch, the configuration is frozen permanently by design — which is exactly what makes a renounced token verifiable.

The launch template caps buy and sell taxes at 10% each — 1,000 basis points — and enforces that ceiling in the contract rather than in the form. A taxed token also needs a fee-on-transfer-aware router function to be sold through a pool, so keep the rate deliberate and disclose it before you open trading.

Up to 40 per launch, with an optional maximum allocation per wallet. Every bundled buy settles in the same transaction as the deploy and the liquidity add, so the whole entry happens at the price you modelled rather than at whatever price the market finds afterwards.

No, and it should not be presented as though it does. The transaction is public: anyone can read the bundle wallets, their amounts and the supply they received on the Arc Explorer. Disclose the percentage you bundled before trading opens — hiding it is the difference between a coordinated launch and a misrepresentation.

You choose. They can stay in your wallet, go to the Liquidity Locker with a public unlock date, or be burned so the liquidity is permanently unrecoverable. Locking or burning is the version traders can verify without having to trust you.

Arctools' liquidity tools build Uniswap V2 pools — constant product, fungible LP tokens, a 0.30% swap fee and the deepest supporting tooling on Arc. Uniswap V3 is also deployed on Arc with 0.01%, 0.05%, 0.30% and 1.00% tiers, but concentrated positions there are managed with different tooling from the V2 tools here.

By the ratio of the two assets you deposit. A constant-product pool has no separate price field: 5,000 USDC against 5,000,000 tokens is a price of 0.001 USDC per token, and every later trade moves along that curve. The creator previews the resulting price and FDV before you sign.

Yes, whenever the LP tokens are in your wallet. Remove Liquidity withdraws any percentage of a position and claims the swap fees it has accrued. If the LP tokens are locked instead, the unlock date is enforced by the locker contract and is visible onchain to anyone who checks.

It is the difference between holding the two assets in a pool and simply holding them in your wallet. When a price moves, the pool has automatically sold some of the asset that rose and bought the one that fell, so the position ends up worth slightly less than the untouched holdings. Accrued swap fees can offset it; a large one-directional move usually is not fully offset.

A proportional deposit does not move the price: you supply both sides in the ratio the pool already holds. A deposit that does not match the current ratio is treated as a swap, which is why the Add Liquidity form quotes the exact token amount your USDC requires before you sign.

Pool math uses the ERC-20 interface of USDC, which has 6 decimals, while gas and msg.value use the 18-decimal native interface. Both are the same balance, related by a factor of 10 to the 12th. An amount that cannot be represented exactly in 6 decimals — anything below 0.000001 USDC — is rejected rather than silently truncated.

200 recipients per transaction, the ceiling compiled into the multisender. Larger airdrops are split into as many batches as needed, so 10,000 wallets is 50 transactions. There is no per-recipient charge: the flat 50 USDC covers the service and the only additional cost is the gas for each batch.

Never. Token airdrops pull from your wallet straight to each recipient with transferFrom, and native USDC payouts are forwarded in the same call. The contract holds no balance between calls, and a failure reverts the entire batch rather than stranding value inside it.

The whole batch reverts, which is the safe outcome: nothing is paid, nothing is stranded, and you can fix the row and resubmit. Because a reverted transaction takes no service fee, the cost of catching a bad row is the gas of the failed attempt.

The Snapshot tool. It is free, read-only and never submits a transaction: point it at a token and a block, and it returns every holder with balances, concentration metrics and a CSV that the multisender can read directly.

No. Arctools never holds your tokens, your liquidity or your keys. Deployed tokens go to your wallet, LP tokens are minted to you, and the service contracts hold no balances between calls — anything left over is returned in the same transaction. Every action is signed by you and settles directly on Arc Mainnet.

We do not claim a third-party audit, and we will not present one we do not have. What we can offer instead: the contracts are dependency-free, so the deployed bytecode is exactly what the source contains, every fee and treasury address is readable onchain before you sign, and the repository ships a verification script that checks the live wiring. Treat new onchain tooling as a risk you size yourself.

Ownership and whether it has been renounced, mint authority, buy and sell taxes, whether those taxes can be changed later, maximum wallet and transaction limits, holder concentration, and whether liquidity is locked or burned. It runs read-only against Arc Mainnet, so checking a token costs nothing beyond the RPC request.

No. Each tool does its work and settles inside the same call, and any allowance it takes is reset to zero before the call returns. There is no queue, no escrow and no admin function that reaches into your wallet afterwards.

Your seed phrase or private key, with anyone, ever. Nobody from Arctools will ask for them, and any message, site or wallet popup that does is a theft attempt. A support conversation only ever needs a public wallet address and a transaction hash.

Arc forbids value-bearing transfers to 0x0, to precompile addresses and to accounts that have already self-destructed; sending native USDC to one of those reverts with a readable error. That is a network-level rule rather than an Arctools one, and it exists because burning a native balance would destroy the gas asset. ERC-20 burn() is unaffected.

Almost always the fee floor. A transaction with maxFeePerGas below Arc's 20 Gwei minimum is dropped by the mempool without an error and without a receipt, so your wallet simply waits. Transactions sent from Arctools are capped up to the floor automatically; if you submitted one by hand, set the max fee to at least 20 Gwei and resubmit.

Add Arc Mainnet with chain id 5042, RPC https://rpc.mainnet.arc.io and the symbol USDC, then switch to it. Wallets that do not support a custom gas token may label the balance ETH — the underlying asset is still USDC and transactions sign normally.

Import it by contract address — the address on the success screen, or in your history on the Arc Explorer. Use exactly the decimals you deployed with, which is 18 if you left the default. Wallets that do not index Arc tokens automatically always need that manual import.

Because a taxed transfer delivers fewer tokens to the pair than a router's constant-product check expects, so the standard swap function reverts. The router on Arc has a variant that tolerates fee-on-transfer tokens, and that is the function to use; a token with no sell tax sells through the ordinary path.

Wallets display gas in their own units and often add a buffer, but the number that matters is what the transaction actually moves. On Arc that is always USDC, out of the same balance the fee comes from, and the confirmed amount is on the Arc Explorer.

Some tools talk to an Arctools service contract whose address is configured when the site is built. If the address for that service is not configured, the page disables the write rather than sending a transaction nowhere. Everything read-only keeps working.

No. An Arc transaction is final on inclusion, and nothing — not Arctools, not Circle, not your wallet provider — can reverse one. That is why every Arctools form shows the exact parameters and the full USDC amount before it asks you to sign.

Email support@arctools.tech with the transaction hash, the tool you used and what you expected to happen. A hash lets us read the exact call onchain, which is almost always faster than describing the symptom.