We checked the sources for this guide on 24 Sept 2026. Use the linked sources for current availability, terms and network details. See subsequent updates
Moving an Arc application to mainnet changes the funds, contracts, credentials and operational consequences of every transaction. Treat it as a release with explicit configuration and recovery checks.
Freeze an environment manifest
Record the chain ID, RPC providers, explorer, asset contracts, application contracts, deployment commit and administrative addresses. Generate the frontend and backend configuration from the same reviewed manifest. Avoid scattered hard-coded addresses in components, workers and support scripts.
The network reference provides current connection settings. The contract reference separates mainnet and testnet deployments. A familiar token name or matching address prefix is insufficient evidence that the configuration is correct.
Review the Arc-specific assumptions
Read the EVM differences before promoting an Ethereum-compatible integration. Review how the application handles native USDC precision, ERC-20 USDC precision, transfer events, fees and exceptional transaction behavior.
Turn those differences into concrete acceptance checks. A wallet screen should show one USDC balance. A receipt should use actual fee units. An event consumer should observe the documented transfer source. A transaction error should produce an actionable state even when a receipt is not available.
Verify the deployed result
Use the deployment tutorial as a tooling reference, then verify the exact environment of any command or example before running it. Record the resulting contract addresses and inspect bytecode, permissions and constructor configuration through independent reads.
If a generated application came from Arc Studio, export and review its code and dependencies. A working preview is useful evidence of a prototype; mainnet operation requires its own validation.
Exercise recovery before opening access
Run the payment flow with a rejected signature, an RPC timeout after submission and an unavailable indexer. Test duplicate callbacks and a browser refresh during a pending operation. Verify that the system recovers the same business payment instead of submitting another one.
For crosschain flows, save the source result and complete a destination retry. For sponsored flows, test the budget ceiling and permission rejection. Keep one successful and one failed trace for each required operation in the release notes.
Make operations part of the release
Define alerts for submission failures, indexing lag, depleted fee balances and stuck operations. Assign an owner and a response path. Monitor service health through the actual dependencies your application uses, alongside the Arc status page.
Publish support instructions with the app’s network, operator, contract references and the payment information users can safely share. Close the release when the configured app, observed contracts, ledger and recovery procedures describe the same system.
Sources & references
Documents cited in this guide.