> For the complete documentation index, see [llms.txt](https://docs.slerf.tools/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.slerf.tools/bsc-en/multi-chain-config/arc-chain-guide.md). # Arc Chain Guide ### πŸš€ About Arc **Arc** is an **EVM-compatible Layer 1** designed by Circle for stablecoin finance. It combines a Tendermint-based **Malachite BFT** consensus layer with a permissioned Proof-of-Authority validator set and Reth execution, delivering deterministic finality in under one second. Gas is paid in **USDC**, not ETH, and there is no ARC gas token. **SlerfTools offers full support for Arc Chain**, enabling you to manage assets on the network with high efficiency and minimal cost. {% hint style="info" %} **πŸ“– Setup Guide** The settings below configure Arc Mainnet. Shared tutorials may show BSC screenshots; use the same click flow only for an enabled equivalent tool, read BNB/ETH gas examples as this network's **USDC**, and recheck the network, contracts, fields, and live fees. {% endhint %} *** ### πŸ’Ÿ Arc Mainnet Parameters
ParameterValueDescription
Network NameArcMainnet wallet configuration
RPC URLhttps://rpc.mainnet.arc.ioOfficial Mainnet RPC
Chain ID5042 (0x13b2)Mainnet identifier; Testnet is 5042002
Gas TokenUSDCNative gas balance uses 18 decimals
Block ExplorerArc ExplorerVerify transactions, contracts, and balances
Observed Block Time~0.5 secondsRecent Mainnet sample; actual intervals vary
ConsensusMalachite BFT + permissioned PoAPermissioned PoS remains a roadmap item
ExecutionReth / EVM (Osaka baseline)Review Arc-specific EVM differences before deployment
Address Format0x... (EVM-compatible)Standard Ethereum-style addresses
Official Portalportal.arc.ioSend, Swap, and related cross-chain workflows
DocsArc DocumentationNetwork, gas, contracts, and development guidance
🎯 **Arc Advantage:** USDC-denominated gas and deterministic sub-second finality provide an EVM environment designed for payments, FX, capital markets, and other stablecoin financial applications. *** ### βš™οΈ Step 1: Network Setup (RPC) If Arc does not appear in your wallet's network list, add it manually: {% hint style="info" %} **Arc Mainnet Parameters:** * **Network Name:** `Arc` * **RPC URL:** `https://rpc.mainnet.arc.io` * **Chain ID:** `5042` * **Currency Symbol:** `USDC` * **Block Explorer:** `https://explorer.arc.io` {% endhint %} **How to Add It:** See the [Wallet Configuration Guide](/bsc-en/general-guide/metamask-wallet-tutorial.md) or [official Connect to Arc documentation](https://docs.arc.io/arc/references/connect-to-arc). Verify the Chain ID, RPC domain, explorer, and Arc USDC balance before signing. Some wallets do not yet display custom gas tokens correctly and may label the balance or fee as β€œETH.” The underlying Arc gas token is still **USDC**. Do not fund Arc with ETH for gas, and never provide a private key or seed phrase to a site or support account. *** ### πŸ›  Step 2: Core Functionality Guide Open the [SlerfTools Arc portal](https://slerf.tools/en-us/arc) and select the required tool. These routes load with Arc configured; connected-wallet and onchain execution still require live verification. {% hint style="info" %} **General Usage Instructions (Read First)** Shared tutorials may use BSC screenshots. For an enabled Arc tool: * **Follow the Flow:** Use the corresponding tutorial and the controls shown on the live page. * **Replace Gas Examples:** Read BNB/ETH gas examples as **USDC**; never reuse another chain's fee or contract address. * **Check the Network:** Keep the wallet on **Arc Mainnet (Chain ID 5042)** and review recipients, amounts, fees, and the wallet request before approval. {% endhint %} #### πŸͺ™ Token Launch [**Create Standard Token**](https://slerf.tools/en-us/token-creator/arc) **(Standard ERC-20)** * Enter the token name, symbol, supply, and precision. Check Arc and the live fees before submitting; verify any result on Arc Explorer. * πŸ‘‰ View [Standard Token Tutorial](/bsc-en/token-management/token-creator.md) [**Create Vanity Token**](https://slerf.tools/en-us/token-vanity-creator/arc) * Choose an available contract-address pattern and recheck the network and generation options before starting. * πŸ‘‰ View [Vanity Token Tutorial](/bsc-en/token-management/token-vanity-creator.md) #### πŸ‘› Wallet Management [**Batch Generate Wallets**](https://slerf.tools/en-us/wallet-creator/arc) * Generate EVM-compatible wallet addresses. Store exported private keys offline and never send them to support or a bot. * πŸ‘‰ View [Generation Tutorial](/bsc-en/wallet-management/wallet-creator.md) [**Generate Vanity Wallet**](https://slerf.tools/en-us/vanity-wallet-generator/arc) * Generate a 0x wallet address with an available character pattern. This is different from a vanity token contract address. * πŸ‘‰ View [Vanity Wallet Tutorial](/bsc-en/wallet-management/vanity-wallet-generator.md) #### πŸ“¦ Multi-Sender (Airdrops) [**Batch Transfer**](https://slerf.tools/en-us/multi-sender/arc) * Check token contracts, recipients, totals, and gas when distributing USDC or ERC-20 assets. Test a small operation first. * πŸ‘‰ View [Batch Transfer Tutorial](/bsc-en/multisender/multi-sender-one-to-many.md) [**Asset Collection**](https://slerf.tools/en-us/multi-collector/arc) **(Consolidation)** * Check source accounts, destination, token contracts, permissions, and each source account's gas balance before consolidation. * πŸ‘‰ View [Collection Tutorial](/bsc-en/multisender/token-batch-collection.md) **Liquidity and Trading Boundary:** Arc Portal provides Send, Swap, and related cross-chain workflows, but that does not confirm Arc-specific SlerfTools DEX, router, liquidity, or trading-tool support. Deploying an ERC-20 does not automatically create liquidity. *** ### ⛽️ Gas Fees & Optimization (Using USDC) **1. Fee Profile** * **Gas Token:** Native **USDC** on Arc, not ETH or ARC. * **Fee Mechanism:** EIP-1559-compatible pricing with smoothing to reduce short-term volatility. Use the wallet estimate and final receipt; no fixed fee is promised. * **Tool Service Fee:** Keep a SlerfTools service quote, if any, separate from network gas. Do not reuse BSC examples. **2. How to Fund Gas** * **Official Entry:** Use the current cross-chain funding or Send flow in [Arc Portal](https://portal.arc.io). Verify the source chain, destination, USDC, recipient, and fees, then start small. * **Testnet Only:** [Circle Faucet](https://faucet.circle.com) provides test assets, not Mainnet gas. Mainnet cross-chain funding timing and fees follow the live Portal status. **3. USDC Precision and Wallet Display** * Native transfers, gas, and `msg.value` use **18 decimals**; the USDC ERC-20 interface uses **6 decimals**. * Both interfaces share one USDC balance. They are not separate tokens, and there is no wrapped USDC to locate. * A wallet may display β€œETH” when it lacks custom-gas-token support; verify Arc, the explorer, and the actual USDC balance instead. *** ### πŸ“Š Common Resources (Dev Resources) * **Official Site:** [Arc](https://www.arc.io/) * **Official Docs:** [Arc Documentation](https://docs.arc.io/) * **Network Setup:** [Connect to Arc](https://docs.arc.io/arc/references/connect-to-arc) * **Mainnet Explorer:** [Arc Explorer](https://explorer.arc.io) * **Portal / Cross-Chain:** [Arc Portal](https://portal.arc.io) * **Gas and Fees:** [Gas and Fees](https://docs.arc.io/arc/references/gas-and-fees) * **Contract Registry:** [Official Contract Addresses](https://docs.arc.io/arc/references/contract-addresses) * **EVM Differences:** [EVM Differences](https://docs.arc.io/arc/references/evm-differences) ⚠️ **Security Alert:** The official Arc Mainnet USDC address is `0x3600000000000000000000000000000000000000`. Verify every other stablecoin, DEX router, factory, and pool through the official registry and Arc Explorer. Never copy contracts from another chain. An ordinary ERC-20 is not endorsed by Circle or Arc. πŸ‘‰ View more [**On-Chain Resources**](/bsc-en/help/on-chain-resources.md) *** ### ❓ Arc Exclusive FAQ
Is the Mainnet Chain ID 5042 or 5042002? **Mainnet is 5042 (`0x13b2`); Testnet is 5042002.** Their RPCs, explorers, assets, and transaction histories are separate. Testnet uses `https://rpc.testnet.arc.io` and [explorer.testnet.arc.io](https://explorer.testnet.arc.io).
My wallet shows ETH. What actually pays Arc gas? Arc gas is paid in **USDC**. A wallet without custom-gas-token support may show β€œETH,” but fees still debit the underlying USDC balance. Verify Chain ID `5042`, Arc Explorer, and the receipt; Ethereum Mainnet ETH cannot directly pay Arc gas.
Does deploying a token make it an official Circle or Arc asset? **No.** An ordinary ERC-20 is an independent contract, not a Circle, Arc, or USDC certification, partnership, listing, or endorsement. It does not automatically receive liquidity, and official branding must not be used misleadingly.
If blocks take about 0.5 seconds, why should I still check the transaction? Arc provides deterministic finality in under one second, so a committed block does not require multiple confirmation rounds. A web page, wallet, RPC, or indexer may still display it later. If a page times out after returning a transaction hash, check Arc Explorer before retrying.
Ready to start? πŸ‘‰ Complete [wallet setup](/bsc-en/general-guide/metamask-wallet-tutorial.md), open the [**SlerfTools Arc portal**](https://slerf.tools/en-us/arc), and verify Mainnet `5042` with USDC for gas. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.slerf.tools/bsc-en/multi-chain-config/arc-chain-guide.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.