Deploy Smart Contracts on Arbitrum: Deployment, Verification, and Optimization

We deploy smart contracts on Arbitrum taking into account all the peculiarities of Optimistic Rollup. It's an EVM-compatible L2 where most Ethereum contracts work unchanged, but there are critical nuances: from two-component gas to precompiles absent in Ethereum. Let's examine them in practice.

Mistakes at deployment can be costly: gas overruns, incorrect handling of block.number, verification issues. Our experience — over 5 years in blockchain development and 50+ successfully launched contracts on Ethereum and L2. We guarantee your contract will run stably and securely.

Why does deployment on Arbitrum require a special approach?

Gas model — the first pitfall for newcomers. Arbitrum uses two-component gas: L2 execution gas (analogous to Ethereum gas, cheap) and L1 calldata cost (cost of publishing data on Ethereum). tx.gasprice on Arbitrum is not equal to Ethereum — use the ArbGasInfo precompile for accurate calculation. Average gas savings when working with Arbitrum amount to 90% compared to Ethereum — deploying a simple ERC-20 contract on Ethereum costs $150–300, on Arbitrum — $1–5.

Block numbers — block.number returns the L1 Ethereum block number, not the Arbitrum-native one. To get the Arbitrum block number, call ArbSys(0x64).arbBlockNumber(). Contracts with vesting or TWAP that rely on block.number may behave unexpectedly.

Block timestamp — updates with every Arbitrum block (~250 ms), which is faster than Ethereum. If your contract uses time oracles, adjustments are needed.

Which precompiles do you need to know?

Arbitrum adds specific precompile addresses: 0x64 (ArbSys — get L1 block number, send messages), 0x6b (ArbGasInfo — gas pricing), 0x6c (ArbAggregator — info about current aggregator). Use them in code for accurate information. The official Arbitrum Developer Docs describe these interfaces in detail.

How to deploy using Hardhat and Foundry?

Example Hardhat configuration for Arbitrum One:

// hardhat.config.ts
networks: {
  arbitrum: {
    url: process.env.ARBITRUM_RPC_URL || 'https://arb1.arbitrum.io/rpc',
    accounts: [process.env.PRIVATE_KEY!],
    chainId: 42161,
  },
  arbitrumSepolia: {
    url: 'https://sepolia-rollup.arbitrum.io/rpc',
    accounts: [process.env.PRIVATE_KEY!],
    chainId: 421614,
  },
}

Deployment and verification via Foundry in one command:

forge create --rpc-url $ARBITRUM_RPC_URL \
  --private-key $PRIVATE_KEY \
  --etherscan-api-key $ARBISCAN_API_KEY \
  --verify \
  src/MyContract.sol:MyContract \
  --constructor-args arg1 arg2

Verification on Arbiscan requires a separate API key from arbiscan.io. The mechanism is the same as Etherscan.

Comparison of deployment frameworks

Contract verification on Arbiscan

After deployment, always verify the source code. This increases user trust and is necessary for interaction with some DApps. We include verification in the basic service package.

Contract size limitations and optimization

Contract limit is 24 KB, as on Ethereum. Gas on Arbitrum is cheaper, but L1 calldata costs money. Optimize calldata for frequently called functions with large arguments (e.g., data compression or using structs instead of arrays).

Bridges and token handling

Canonical Arbitrum bridge for ETH and standard ERC-20s. For custom tokens — registration through the Arbitrum token bridge. If your contract manages a bridge or works with bridged tokens, note: WETH on Arbitrum is not the same address as on Ethereum. We verify compatibility.

How does deployment proceed with our team?

1. Compatibility analysis of the contract with Arbitrum (gas, block.number, precompiles).
2. Deployment with verification on Arbiscan (turnkey).
3. Multisig ownership setup via Safe (optional).
4. Proxy deployment (UUPS/Transparent) and deployment scripts.
5. Documentation on deployment and interaction.
6. Test phase on Arbitrum Sepolia.

We evaluate your project for free — contact us for a consultation.

How do we guarantee quality?

Over 5 years of experience in blockchain development, 50+ successful projects on Ethereum and L2, certified Solidity specialists. We use automated checks (Slither, Mythril) and formal verification of key contracts. We guarantee correct operation after deployment.

Common deployment mistakes

• Using block.number for timing without adaptation.
• Ignoring L1 calldata cost in gas estimates.
• Incorrect WETH address when bridging.
• Skipping verification on Arbiscan.
• Failing to check compatibility with custom token bridge.

Estimated timelines

Deployment of a ready contract with verification — a few hours. Full cycle (compatibility audit, multisig setup, deployment scripts) — 1-2 days. Cost is calculated individually for your project.

Order deployment of your contract on Arbitrum — we will do the job with a quality guarantee.

Blockchain Infrastructure Deployment: Nodes, RPC, Indexing

Subgraph fell at 3:47 AM. By morning users saw outdated balances, transactions "hung" in the UI, support received 47 tickets in an hour. Cause: the handler in the subgraph failed on a transaction with a non-standard event log — and the entire index stopped. We have encountered such situations dozens of times. Our experience shows: blockchain infrastructure does not forgive gaps in observability. Guaranteeing uptime without multi-layered monitoring and fault-tolerant architecture is impossible. Over 8 years working with Ethereum, Polygon, and Solana, we have developed an approach that allows predictable deployment of infrastructure of any scale — from a single node to a multichain grid with dozens of subgraphs.

RPC Layer Architecture

Every dApp interaction with the blockchain goes through RPC — the JSON-RPC API provided by a node. Three options:

Managed providers — Alchemy, QuickNode, Infura, Ankr. Minimal operational costs, SLA, built-in monitoring. Limits: rate limits (Alchemy Free: 300 RU/sec), vendor lock, potential downtime during provider incidents. For most projects — the right choice at the start.

Self-owned nodes — full control, no rate limits, no third-party dependence. Cost: archive Ethereum node requires 2.5–3TB SSD, a strong server, and DevOps support. Sync from scratch on Ethereum via Geth/Nethermind — 3–7 days. Justified under high load or latency requirements.

Hybrid — self-owned node as primary, managed provider as fallback. Standard for protocols with high TVL. Proper load balancing can reduce costs by 20–30% compared to pure managed setup. Under high monthly request volume, hybrid saves significantly.

How to Set Up an RPC Layer Without a Single Point of Failure?

At least two providers, DNS round-robin with health check every 5 seconds, automatic fallback when latency >500 ms. In practice, this gives 99.99% availability during any provider failure. For protocols with high TVL, we recommend a custom HA-proxy (nginx or Envoy) in front of two managed providers.

Why Is a Hybrid RPC Scheme More Cost-Effective Than Pure Managed?

At high request volumes, managed providers can be very expensive; a hybrid using a self-owned node as primary and a managed fallback cuts costs significantly without losing SLA.

Ethereum Node Clients

Execution clients: Geth (most used), Nethermind (C#, fast sync), Besu (Java, enterprise), Erigon (fastest sync, efficient archive mode ~2TB instead of 3TB).

Consensus clients (post-Merge): Lighthouse (Rust), Prysm (Go), Teku (Java), Nimbus (Nim). Each node after The Merge requires a pair of execution + consensus clients.

For DevOps: eth-docker — Docker Compose configurations for all client combinations. Setting up monitoring via Grafana + Prometheus is mandatory; a standard dashboard is available in each client's repository.

The Graph: Event Indexing

The Graph Protocol — decentralized indexing. A subgraph describes which events from which contracts to index and how to transform them into a GraphQL schema.

Subgraph structure:

• subgraph.yaml — manifest: contract addresses, startBlock, events to handle
• schema.graphql — GraphQL schema of entities
• src/mapping.ts — AssemblyScript event handlers

dataSources:
  - kind: ethereum
    name: UniswapV3Pool
    network: mainnet
    source:
      address: "0x88e6A0c2dDD26FEEb64F039a2c41296FcB3f5640"
      abi: UniswapV3Pool
      startBlock: 12370624
    mapping:
      eventHandlers:
        - event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
          handler: handleSwap

AssemblyScript handlers — not TypeScript. No nullable types, no closures, no many standard APIs. An error in the handler stops the subgraph indexing on that transaction. Important: add try-catch for operations that can fail (e.g., store.get() for an entity that may not exist).

How to Avoid Subgraph Indexing Stops?

Graph Node logs are monitored in real-time; on hasIndexingErrors = true an alert fires and an automatic node restart (via systemd or Kubernetes). Typical downtime on error — 150–300 seconds to recover. Additionally, for production we set up a watchdog that restarts Graph Node if subgraph lag exceeds 50 blocks.

Choosing Between Hosted Service and Decentralized Network

Graph Hosted Service (free, centralized) is deprecated in favor of Subgraph Studio + Graph Network. For production: deploy on Graph Network with GRT curation signal — the subgraph gets indexers proportional to curation.

Alternatives to The Graph: Ponder (TypeScript, self-hosted, easier to debug), Envio (ultra-fast indexer, supports EVM + non-EVM), Subsquid (TypeScript, own network), Moralis Streams (managed, webhook-based). Our experience shows: for high-load projects with unique logic, Ponder or Envio are more effective — they give full control over the process and do not require GRT tokenomics.

Webhooks and Real-Time Notifications

Alchemy Webhooks and QuickNode Streams allow receiving events in real-time via HTTP webhook or WebSocket. For monitoring addresses, new transactions, mints — this is faster than polling RPC.

Tenderly — platform for monitoring and alerts. You can set up an alert for a specific contract event, balance change, function call with certain parameters. Transaction simulation via Tenderly API is invaluable for debugging.

Monitoring and Observability

Minimum monitoring stack for a protocol:

On-chain: OpenZeppelin Defender Sentinel — watches contract events, triggers webhook or Autotask when conditions are met. Forta Network — community-maintained bots detect anomalies (large withdrawals, flash loans, governance attacks).

Infrastructure: Grafana + Prometheus for nodes, Datadog or Grafana Cloud for managed metrics. Alerts on: node is 10+ blocks behind, RPC latency >500ms, subgraph lag >100 blocks.

Uptime: Better Uptime or PagerDuty on RPC endpoint and subgraph health endpoint (The Graph provides _meta { hasIndexingErrors, block { number } }).

Why Is Monitoring Without Tenderly Insufficient?

Tenderly provides transaction simulation and detailed traces — critical for debugging subgraph and smart contract errors. Forta focuses on network anomalies, not your infrastructure. The combination of Tenderly plus a custom Grafana dashboard covers 90% of incident scenarios.

Multichain Infrastructure

A protocol on 5 chains = 5 separate RPC endpoints, 5 subgraphs, 5 monitoring configs. Manageable but requires deployment automation.

For subgraph multi-network deployment: graph deploy --network mainnet, graph deploy --network arbitrum-one etc. with a unified codebase and network-specific addresses in separate config files.

Chainlink CCIP and LayerZero for cross-chain messaging require monitoring of both chains and transactions on intermediate relayers. A reorg on the source chain after a confirmed mint on the target chain is a classic bridge problem. Solution: wait for finality (on Ethereum ~15 minutes after Merge for economic finality) before confirming on the target chain.

Infrastructure Setup Process

1. Audit current stack — determine chains, request volume, latency and availability requirements.
2. Architecture design — select providers, load balancing, redundancy.
3. Subgraph development — manifest → schema → handlers → testing on local Graph Node → deploy to testnet → mainnet.
4. Monitoring configuration — Tenderly alerts, Grafana dashboard, PagerDuty integration.
5. Documentation and runbook — what to do when: subgraph falls behind, RPC downtime, node desync.
6. Handover to operations — team training, access transfer, first month support.

What's Included

• Deployment of managed or self-hosted Ethereum, Polygon, BNB Chain nodes
• RPC layer setup with primary/fallback and load balancing
• Subgraph development and deployment for your protocol
• Monitoring connection (Tenderly, Grafana, alerts)
• Runbook and operations documentation
• Team training (up to 4 hours online)
• 30-day support after delivery

Timeline

All projects are managed in a GitHub/GitLab repository with CI/CD; configuration code stays with you. Order infrastructure deployment — we'll show how to cut costs by 20–30% without losing reliability. Get a consultation — we'll demonstrate how we deployed infrastructure for a protocol with large TVL on Ethereum and Arbitrum. Contact us.