Full guide to on-chain trading on Arc

What Arc is — and what is live

Arc is a Circle-built Layer 1 for stablecoin activity and financial applications. Circle announced its public mainnet on 16 September 2026. Its EVM-compatible execution uses Reth; Malachite handles consensus. The validator set is permissioned. This is a public network with third-party applications, not a guarantee that Circle endorses every token or trading bot.

Official references: network and wallet setup · architecture · fee design · dated mainnet announcement. Reviewed 18 September 2026.

Wallets, accounts and custody

A wallet controls signing authority. A bot account gives access to an interface; the relationship between account access and signing authority varies by provider. Before depositing, learn who holds the key, how recovery works, whether export is possible and how withdrawals are authorised. A label such as non-custodial does not remove phishing or compromised-device risk.

The official connection guide includes MetaMask, Rabby, Coinbase Wallet and Rainbow. Follow the provider’s current setup instructions and the Arc network reference. A Telegram bot may create a wallet rather than connect your existing one. Do not paste a recovery phrase into a website, chat or unsolicited support conversation.

Move assets to Arc using an official entry point

Start at Arc Portal or a provider’s documented bridge interface. Confirm that Arc mainnet is the destination and that the received asset is usable USDC on Arc. A deposit address alone does not prove that a service supports that network.

1. Open the official service from a bookmarked or verified domain.
2. Select the source chain, asset and destination Arc mainnet.
3. Check the receiving address, estimated USDC received, fees and expected completion.
4. Read every approval and transaction request. Reject unexpected spenders or amounts.
5. For a first transfer, use a small amount you can afford to lose and verify receipt on the Arc explorer before sending more.

Banana Gun documents an Arc bridge flow; Maestro’s launch post also confirms bridging. This does not prove every source asset or source chain is supported. A successful bridge transfer and a successful swap are separate operations.

Gas: leave a USDC reserve

USDC pays Arc network fees. Keep enough uncommitted USDC for later approvals, swaps and withdrawals. Do not spend the entire balance on an order. Network gas, bot commission, pool fees and token-specific charges are separate costs.

Arc uses 18 decimals for native USDC accounting while ERC-20 representations use their documented token interface. Some wallets can display an ETH label despite the underlying gas asset being USDC. Use the official network reference to resolve the display; do not bridge ETH just because an unfamiliar wallet label says ETH.

Read the fee and execution guide →

Understand the DEX route before the token price

A DEX executes swaps using contracts and liquidity. A terminal helps find tokens and submit orders. A launchpad can use an initial pricing mechanism before a token moves into a pool. Support for one phase does not prove support for the next.

Bloom’s Arc support matrix names Uniswap V2/V3/V4. Sigma documents Argus, and Maestro documents Aero. These are provider-specific integration records. Check the exact version, contract, quote asset and order eligibility in your selected product.

Verify the token contract

• Obtain the full contract address from the project’s independently checked official channels. Names, logos and ticker symbols can be copied.
• Check that the explorer and wallet are on Arc mainnet. An identical-looking address on another network is not the same asset.
• Inspect ownership controls, supply, holder concentration and any changeable transfer restrictions. A verified source-code badge is not an audit.
• Inspect current liquidity and a sell quote. A high displayed valuation does not mean you can exit at that price.
• Treat contract scanners as one input. A clean result does not prove safety or prevent later changes.

Slippage, price impact and finality

Price impact is the effect of your order on the pool. Slippage tolerance is the permitted movement between the quote and execution. Raising slippage can make a trade executable at a substantially worse price; it does not fix thin liquidity or an unsafe token.

Arc documents sub-second deterministic finality. That describes network settlement, not the time from a click to a bot’s successful fill. RPC delays, route construction and application behaviour remain relevant. Final settlement also means you should not expect a mistaken transfer to be reversible.

MEV and private transactions: separate the claims

Do not assume Ethereum relay support, Solana priority tips or private routing carries over to Arc. Circle’s launch material describes network-wide opt-in privacy as under development. That is not proof that a trading bot currently submits private Arc transactions. This site leaves those fields unverified without product-specific evidence.

Bot versus a manual DEX interface

A safe first-trade procedure

1. Set a loss limit. Decide an amount whose total loss would be acceptable. A first trade is not a test of whether a token will rise.
2. Verify the interface. Open the official product and select Arc mainnet.
3. Check your wallet. Confirm the account, receiving address, recovery method and USDC reserve.
4. Match the token. Paste and compare the full verified contract address.
5. Inspect both directions. Read a buy quote and a sell quote at your intended size.
6. Review the full cost. Check platform fee, network cost, price impact and minimum received.
7. Inspect the permission. For an approval, verify spender and allowance; for a swap, verify recipient and amounts.
8. Submit only if clear. Cancel if the request differs from your intent. This guide does not require you to trade.
9. Verify independently. Check the receipt and balances on the explorer. Do not repeatedly submit merely because the interface looks slow.
10. Close the loop. Review remaining allowances and the gas reserve. Disconnecting a website does not itself revoke token approvals.

Phishing and approval checklist

• Never share private keys or recovery phrases with support.
• Avoid sponsored search-result lookalikes and unsolicited migration links.
• Read allowance amounts and contract recipients, including during bridging.
• An ARC token claim is not required to pay native gas. Circle’s genesis-mint announcement is not a commitment to a public token launch.
• Do not equate a mainnet launch, partnership announcement or referral link with a security endorsement.

Glossary

Explore Arc tools · Compare verified bots · Wallet and bridge checks

Frequently asked questions