Arctools is tooling for Arc Mainnet, and nothing else
A small, focused suite of onchain services for people deploying and running tokens on Arc: launch, bundle launch, airdrop, provide liquidity, manage supply, renounce control, check what you are about to buy. One flat fee in USDC, no custody, no supply cut, and nothing that keeps a balance after the transaction ends.
One suite that covers the life of a token
Arctools exists because launching a token on a new chain otherwise means stitching together a deployer, a liquidity tool, a multisender, a locker and a checker, each with its own fee model. The tools here share one wallet connection, one USDC balance and one price.
- Arc Liquidity Pool CreatorCreate a Uniswap pool on Arc Mainnet and seed it in the same flow.
- Add Liquidity on ArcDeepen an existing Arc Mainnet pool without disturbing the price.
- Remove Liquidity on ArcWithdraw part or all of your Arc Mainnet position, including fees earned.
- Arc Liquidity LockerLock LP tokens on Arc Mainnet until a date you choose and prove it onchain.
Six things worth stating plainly
A category full of half-truths deserves an explicit list. None of the following is true of Arctools, and none of it is planned.
Not affiliated with Circle or the Arc Foundation
Arctools is an independent project built on top of Arc. It is not endorsed by, operated by or partnered with Circle Internet Financial or the Arc Foundation, and it does not speak for the network. Arc's own documentation is the authority on how Arc behaves.
Not a launchpad that takes a share of your token
There is no supply cut, no allocation reserved for the project, no vesting schedule pointing at us and no token of ours involved in any launch. The only thing Arctools takes is the flat fee, in USDC.
Not a custodian
Arctools never holds tokens, liquidity or keys, and the service contracts hold no balances between calls. Anything left over is returned in the same transaction that created it.
Not an adviser or a broker
Nothing here is financial, legal, tax or investment advice, and no tool markets a token or arranges a trade. What you launch, and what you do with it, is your decision and your responsibility.
Not audited, and not claiming to be
We do not present a third-party audit we do not have. What we can point at instead is a dependency-free contract set whose deployed bytecode is exactly what the source contains, readable fee and treasury values, and a verification script that checks the live wiring.
Not funded by a token sale
There is no Arctools token, nothing to buy to unlock a feature, and no funding round to announce. The flat service fee is the entire business model.
Non-custodial is a property of the code, not a slogan
Arctools is a form that builds a transaction. There is no account, no deposit address and no server-side wallet that could be compromised, because there is nothing to compromise: the tool pages compute a call and hand it to your wallet.
Your wallet signs everything
Every state change is a transaction you approve in your own wallet, with the parameters and the exact USDC amount shown first. The site cannot sign on your behalf.
Contracts keep nothing
Each service contract finishes and settles inside the call that invoked it. Anything left over — an overpaid amount, an unused fee — is returned to the sender before the transaction returns.
Allowances are reset
Token allowances the contracts take are set back to zero before they return, so a token permission cannot be left dangling for a later transaction to reuse.
Finality cuts both ways
Arc finalises on inclusion, which means a confirmed transaction is genuinely done. That is a benefit until someone makes a mistake, so every form spells out what will happen before it can.
Open Solidity, dependency-free, verifiable before you sign
Every service contract is a standalone Solidity file with no imported libraries, so the deployed bytecode is exactly what the source contains — nothing is inherited from a package you cannot read.
Small and auditable by reading
Six service contracts — a token factory, a bundle launcher, a multisender, a liquidity manager, an LP locker and a fee router — plus a shared base that holds the fee, treasury, ownership and the USDC decimal conversion. Each one is short enough to read in a sitting.
The fee is capped in code
Each contract exposes fee() and treasury(), and refuses to accept a fee above a 10,000 USDC ceiling that is compiled into it. You can read both values onchain before you sign, and the change history is public.
No sharp edges
All value-moving entry points are reentrancy-guarded and finish their accounting before the first external call. Contracts never rely on PREVRANDAO, never use SELFDESTRUCT, never submit blob data and never send native USDC to the zero address — on Arc, that last one would revert.
Deployments are followed by an onchain verification pass that checks bytecode presence, the shared fee and treasury, every cross-reference (router factory, liquidity manager, locker) and the immutables the interface relies on. Nothing is announced as deployed until that pass is clean.
How a flat 50 USDC fee pays for this
The fee is forwarded to the treasury inside the same transaction that does the work, in the middle of the page, where anyone can see it on the explorer. No invoice, no account, no billing relationship to cancel.
What the fee is spent on
- Writing and testing the contracts, and re-verifying every deployment onchain
- Keeping the tool interfaces working as Arc evolves and its libraries change
- Writing the guides, glossary and FAQ that explain how the pieces fit together
- Hosting and running the site — nothing more exotic than that
What it is not spent on
- Advertising, affiliate programs or paid placements
- Selling or sharing data about you — measurement is aggregate and stays on our own server
- Market making, token buybacks or price support of any kind
- A treasury of anyone else's tokens: only USDC arrives, and only for services rendered
Read-only tools stay free because they cost almost nothing to serve and they are how most people should start. The full pricing breakdown sets out exactly what the fee covers.
Questions, bug reports or a missing tool
Support is a person reading email, not a ticket queue. Send a transaction hash if there is one, and you will get a straight answer about what happened.