Rollup Deployment

• L1 smart contract deployment and verification
• Sequencer, prover, and node provisioning
• RPC endpoint allocation and load balancing
• Block explorer configuration
• Genesis state and chain configuration
• Automatic scaling and high-availability guarantees

​

The Problem Rollups Solve

• Dedicated Blockspace: Your application never competes for gas. Fixed, predictable costs regardless of external network activity.
• One-Click Deployment: Deploy a complete L2 chain in ~15 minutes. No smart contract deployment, node configuration, or DevOps expertise required.
• Ethereum-Grade Security: All state roots settle to Ethereum L1. Your rollup inherits Ethereum’s security guarantees and censorship resistance.
• Managed Infrastructure: We operate sequencers, provers, and RPC nodes. You focus on building your application.
• Instant Tooling: Dedicated block explorer, JSON-RPC endpoints, and WebSocket connections provisioned automatically.
• Clear Upgrade Path: Start free on testnet. Scale to mainnet with our team’s support when ready for production.

​

Getting Started

• Appears in your Blockops dashboard
• Forms your RPC endpoint URL: https://[chain-name].rollup.blockops.network
• Labels your dedicated block explorer
• Identifies your chain in wallet configurations

• Use lowercase letters, numbers, and hyphens only
• Include your project or organization name (e.g., acme-defi-testnet)
• Add environment indicators for clarity (-testnet, -staging)
• Keep it concise but descriptive (maximum 30 characters recommended)

• Deploys to Ethereum Sepolia (settlement layer)
• No real economic value, safe for experimentation
• Identical architecture to mainnet
• Perfect for smart contract testing and integration validation

• Deploys to Ethereum Mainnet (settlement layer)
• Real economic security and value
• Requires security review and economic parameter configuration
• Clicking Mainnet displays a confirmation modal requesting a meeting with our team

• Security: Ethereum-grade settlement and data availability
• Cost-efficiency: Blob transactions reduce DA costs vs. calldata
• Compatibility: Full EVM equivalence, existing tooling works out-of-the-box
• Future-proofing: Superchain compatibility for interoperability

• Compile and deploy 40+ smart contracts to Ethereum L1 (SystemConfig, OptimismPortal, L1StandardBridge, FaultDisputeGame, and proxy contracts)
• Provision sequencer infrastructure with high-availability configuration
• Configure prover systems for fault proof generation
• Deploy RPC nodes with load balancing
• Initialize block explorer with your chain’s configuration
• Generate genesis state and chain configuration files
• Begin L2 block production once L1 contracts are confirmed

• Click “View rollup list” to monitor progress
• Your rollup appears in the dashboard with “Deploying” status (orange badge)
• RPC column shows -------- (not yet available)
• This process typically takes 10-30 minutes depending on L1 confirmation times

• Status changes to “Ready” (green badge)
• RPC column remains -------- (accessible in detail view)
• Your chain is live and accepting transactions

• Chain Name: Your rollup’s identifier (e.g., ch-optimism-testnet-rollup-cboux2)
• Status: Ready (green badge) indicates full operational status
• Metrics Panels:

• Contract Name (e.g., OptimismPortalImpl)
• Ethereum Address (0x… format, truncated with full address on hover)
• Copy Button (clipboard icon) - copies address to clipboard
• External Link Button (arrow icon) - attempts to open in block explorer

// hardhat.config.js
module.exports = {
  networks: {
    myRollup: {
      url: "https://ch-optimism-testnet-rollup-cboux2.rollup.blockops.network",
      chainId: 863048,
      accounts: [process.env.PRIVATE_KEY],
    },
  },
};

# .env
RPC_URL=https://ch-optimism-testnet-rollup-cboux2.rollup.blockops.network
CHAIN_ID=863048

import { defineChain } from "viem";

const myRollup = defineChain({
  id: 863048,
  name: "My Rollup",
  network: "my-rollup",
  nativeCurrency: { name: "Ether", symbol: "ETH", decimals: 18 },
  rpcUrls: {
    default: {
      http: [
        "https://ch-optimism-testnet-rollup-cboux2.rollup.blockops.network",
      ],
    },
  },
  blockExplorers: {
    default: {
      name: "Blockops Explorer",
      url: "https://ch-optimism-testnet-rollup-cboux2-explorer.blockops.network",
    },
  },
});

• Return to the Overview tab
• Metrics panels will populate with real data
• Use your Block Explorer to view detailed transaction, block, and contract information

​

Managing Your Rollups

​

Best Practices

• Environment indicators: Use -testnet, -staging, -prod suffixes
• Project identification: Include organization or project name
• Versioning: Add version numbers for iterative deployments (-v1, -v2)
• Example: acme-defi-testnet-v1

• Keep RPC URLs confidential: They provide direct access to your chain
• Implement access controls: Use application-layer authentication for sensitive operations
• Monitor L1 contracts: Regularly verify contract states on Etherscan
• Plan upgrade paths: Understand proxy contract upgrade mechanisms before mainnet deployment

• Testnet is free: Use extensively for development and testing
• Mainnet requires planning: Contact sales early for production budgeting
• Monitor resource usage: Track RPC call volume and explorer usage

​

Troubleshooting Common Issues

• Symptoms: Rollup remains in “Deploying” status beyond 45 minutes.
• Possible Causes:
  • L1 network congestion delaying contract deployments
  • Complex genesis configuration requiring additional validation
  • Infrastructure provisioning delays
• Solutions:
  • Wait up to 60 minutes for L1 confirmations
  • Check Sepolia Etherscan for pending transactions from your deployer address
  • Contact support with your rollup name if exceeded 60 minutes

• Symptoms: Overview tab shows “Metrics are not available” after transaction activity.
• Possible Causes:
  • Indexing service lag
  • Metrics pipeline delay
  • No actual transaction activity confirmed
• Solutions:
  • Verify transactions using your block explorer instead of dashboard metrics
  • Wait 5-10 minutes for metrics pipeline to process
  • Click “Contact us” in the metrics panel for support escalation

• Symptoms: Clicking external link on contract addresses shows “Error 404.”
• Status: Known issue under resolution.
• Workaround:
  • Use the copy button (clipboard icon) next to the contract address
  • Navigate manually to Sepolia Etherscan (for testnet)
  • Paste the address in the search bar

• Symptoms: Cannot connect to RPC endpoint from wallet or application.
• Possible Causes:
  • Endpoint still provisioning (status not yet “Ready”)
  • Incorrect Chain ID in configuration
  • Network connectivity issues
• Solutions:
  • Verify rollup status is “Ready” in dashboard
  • Double-check Chain ID matches Configuration tab exactly
  • Test RPC URL directly: curl -X POST [RPC_URL] -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'
  • Verify no firewall or VPN blocking HTTPS connections

• Symptoms: L2 transactions more expensive than expected.
• Note: This is uncommon on dedicated rollups, but possible if:
  • L1 blob fees are unusually high
  • Complex contract interactions consuming significant L2 gas
  • Misconfigured gas estimation in application
• Solutions:
  • Check L1 blob base fee on Sepolia (testnet) or Etherscan (mainnet)
  • Optimize contract code to reduce gas consumption
  • Contact support for gas parameter review

​

Getting Help

• Rollup name (exactly as shown in dashboard)
• Current status (Deploying, Ready, Error)
• Specific error messages or screenshots
• Steps already attempted