Check Arbiscan
Use the deployed address to review indexing, transactions, and source-verification status.
Create an ERC-20 token on Arbitrum
Add mint/burn toggles, blacklist controls, and wallet limits while keeping deployment costs lean. Ideal for utility and gaming tokens.
erc-20supply limitsownershipmintableburnablepausableblacklist
Token configuration
Choose the contract controls you need
Review the selected Arbitrum ERC-20 template, owner permissions, supply rules, and optional tax behavior before deployment.
Set up & review
Fill out the token parameters and review the selected template, network, and service fee before deployment.
Deploy & inspect
Deploy on Arbitrum One, then inspect the transaction, contract address, ownership, and tax settings through Slingzero and Arbiscan.
Open post-launch tools
Continue to supported ownership, mint, burn, multisender, Token Page, and liquidity tools after deployment.
Frequently asked questions
Need something bespoke for your Arbitrum launch? Contact us for a tailored plan.
Deployments cost the prevailing ETH network fee plus the template service fee you select. The complete amount is shown before signing.
Yes. Toggle buy/sell taxes during setup and define how proceeds are routed (treasury, liquidity, burn). You can change or disable taxes post-launch.
Yes. After deployment, open Slingzero's Arbitrum DEX liquidity workflow to select the token, enter pool assets, review the price ratio, and approve the separate wallet transactions. Slingzero does not claim to lock LP tokens automatically.
The confirmed deployment transaction and contract address can be opened on Arbiscan. Explorer indexing and source-code verification are controlled by the explorer and may require separate steps.
Yes. A creator wallet can deploy multiple ERC-20 contracts. Eligible Slingzero-created tokens can appear in My Tokens, where supported follow-up actions are available.
Yes. The optional Token Page publishes creator-supplied project information and on-chain identifiers at a shareable URL. Search engines decide whether and when a qualifying public page is indexed.
Arbitrum One deployment
Deploy an ERC-20 token on Arbitrum One
Arbitrum One runs EVM contracts while settling through Ethereum. Slingzero prepares the selected ERC-20 template and your connected wallet deploys it on Arbitrum One. ETH is used for both the configured service fee and network gas, so the wallet must be funded on Arbitrum rather than only on Ethereum mainnet.
Use the official Arbitrum documentation for current chain information, bridging guidance, and technical details about how Arbitrum works.
Before signing
- Confirm the wallet shows Arbitrum One and holds ETH on that network.
- Choose the contract template that matches the controls you actually need.
- Review supply, owner permissions, maximum supply, and any token tax.
- Check the final ETH service fee and estimated gas in the creator.
Keep chain context clear
An Ethereum address can exist on several EVM networks; always share the address together with Arbitrum One.
Treat liquidity separately
Creating the token does not create a DEX pool, lock liquidity, bridge assets, or guarantee discovery.
Arbitrum One release guide
Fund ETH on the L2
Arbitrum One uses ETH for execution fees, but the wallet needs that ETH on Arbitrum. Mainnet funds do not become L2 gas automatically; check the network balance before deployment.
Distinguish deployment from bridging
This creator deploys a new ERC-20 contract directly on Arbitrum One. It does not bridge an existing Ethereum asset or establish an official relationship with an L1 token.
Make the L2 identity explicit
Include “Arbitrum One,” the unshortened contract, and an Arbiscan link in launch materials. That context helps wallets and users distinguish the deployment from similarly named contracts on other chains.