# Rollup
Blockops Rollups is a managed infrastructure service that enables developers to deploy dedicated Layer 2 (L2) blockchains using the Optimism (OP) Stack. Unlike shared public chains where your application competes for blockspace with thousands of others, a Blockops Rollup provides an isolated, high-performance execution environment with predictable gas costs, customizable throughput, and complete control—while inheriting Ethereum's battle-tested security.
Think of Blockops Rollups as your dedicated blockchain infrastructure team. Instead of spending months deploying smart contracts, configuring sequencers, operating provers, and managing fault-proof systems, you can launch a production-ready L2 chain in approximately 15 minutes. Blockops handles all underlying infrastructure, including:
* 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
Whether you're building a DeFi protocol requiring guaranteed throughput, an NFT platform needing predictable minting costs, or an enterprise application requiring dedicated blockspace, Blockops Rollups provides the execution layer you need without the operational overhead.
### The Problem Rollups Solve
Building applications on shared Layer 1 or Layer 2 blockchains introduces significant constraints that limit user experience and business model viability.
**The Traditional Challenges** Before dedicated rollup infrastructure like Blockops, developers faced fundamental hurdles:
| Challenge | Description |
| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Gas Price Volatility** | On shared chains, gas prices spike during network congestion. A simple transaction can cost $50+ during peak periods, making applications economically unusable. |
| **Throughput Bottlenecks** | Your application competes for limited blockspace. When popular NFTs drop or DeFi protocols launch, other applications slow to a crawl or become unusable. |
| **Infrastructure Complexity** | Operating your own rollup requires deploying 40+ L1 smart contracts, running sequencers and provers, maintaining fault-proof systems, and managing upgrades. |
| **Unpredictable Costs** | Variable gas costs make it impossible to predict operational expenses or build sustainable business models. |
| **Limited Customization** | Shared chains enforce universal parameters. You cannot optimize block time, gas limits, or precompiles for your specific use case. |
**How Blockops Rollups Addresses These Challenges** Blockops eliminates these pain points by providing:
* **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
This section walks you through deploying your first rollup on Blockops. By the end, you'll have a fully operational Layer 2 blockchain syncing with Ethereum and serving RPC requests.
**Step 1: Accessing the Rollup Dashboard** Navigate to your Blockops project dashboard. In the left sidebar, locate the Products section and click Rollup to access the Rollup dashboard.
If this is your first time using Rollups, you'll see an empty state dashboard with a prominent "Create Rollup" button and the message "You don't have any rollups yet."
Figure 1: The Rollup dashboard empty state. The "Create Rollup" button initiates deployment.
If you have existing rollups, you'll see them listed in a table with columns for Name, Status, RPC, Date Created, and Actions.
**Step 2: Creating Your Rollup** Click the "Create Rollup" button to launch the deployment wizard. You'll be guided through a four-step configuration process.
**2.1 Chain Identity** First, assign a unique name to your rollup. This identifier serves multiple purposes:
* 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
Enter your desired name in the Chain Name field. The system validates uniqueness in real-time.
Best Practices for Chain Names:
* 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)
**2.2 Select Environment** Choose the network environment that matches your development stage:
| Environment | Purpose | Cost | Deployment Speed | Access |
| ----------- | ---------------------------------------------- | ------------------ | ------------------------ | ---------- |
| **Testnet** | Development, testing, debugging, beta releases | Free ($0.00/month) | Instant | Self-serve |
| **Mainnet** | Production with real economic value | Contact Sales | Requires onboarding call | Gated |
**Testnet Details:**
* 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
**Mainnet Details:**
* 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
*Important:* If you select Mainnet, a "Confirm request" modal appears explaining: "To move forward with deploying your chain, we'll need to discuss your specific requirements. Please schedule a meeting with our team to initiate the deployment request." Click "Request mainnet" to proceed with scheduling.
**2.3 Build Your Stack** Configure the core architectural components of your rollup. Blockops simplifies this by providing a pre-validated, production-ready Optimism (OP) Stack configuration.
**Configuration Details:**
| Component | Selection | Description | Technical Details |
| --------------------- | ------------------- | ----------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- |
| **Framework** | Optimism (OP Stack) | Industry-leading L2 framework with extensive tooling, documentation, and ecosystem support | Bedrock release, Cannon fault proofs, Superchain compatible |
| **Settlement Layer** | Ethereum | Your rollup's state roots and fault proofs are committed to Ethereum L1, inheriting its security | Sepolia for testnet, Mainnet for production |
| **Data Availability** | Ethereum DA | Transaction data is posted to Ethereum using EIP-4844 blobs, ensuring data availability without extra trust assumptions | Blob transactions, 128KB max per block, automatic blob management |
These defaults are optimized for:
* **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
*Note: Advanced users requiring custom configurations (alternative DA layers, custom gas tokens, or modified precompiles) should contact our team for dedicated deployment options.*
**2.4 Review and Deploy** The Summary panel provides a final configuration review before deployment:
**Summary Contents:**
| Item | Description |
| ----------------------------- | ------------------------------------------------------------------- |
| **What's Included** | Framework (OP), Settlement Layer (Ethereum), DA Layer (Ethereum DA) |
| **Monthly Cost** | $0.00 for Testnet (clearly labeled as estimate) |
| **Estimated Deployment Time** | \~15 minutes (typical range: 10-30 minutes) |
Click **Deploy** to initiate the automated provisioning process. The system will:
* 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
**Step 3: Monitor Deployment** Immediately after clicking Deploy, you'll see deployment confirmation:
**During Deployment:**
* 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
**Deployment Complete:**
* Status changes to "Ready" (green badge)
* RPC column remains `--------` (accessible in detail view)
* Your chain is live and accepting transactions
**Step 4: Access Rollup Details and Configure Connections** Click your rollup's name to access the Detail View, which provides comprehensive information and management options. The detail view has two tabs: Overview and Configuration.
**Overview Tab** The Overview tab displays real-time operational metrics for your chain.
**Header Information:**
* **Chain Name:** Your rollup's identifier (e.g., ch-optimism-testnet-rollup-cboux2)
* **Status:** Ready (green badge) indicates full operational status
* **Metrics Panels:**
| Panel | Description | Initial State |
| ---------------- | ------------------------------------------------------ | --------------------------- |
| **Transaction** | Transaction count and volume over selected time period | "Metrics are not available" |
| **Gas Used** | Total gas consumed by transactions | "Metrics are not available" |
| **Block Height** | Current L2 block number | "Metrics are not available" |
*Important:* These panels display "Metrics are not available" immediately after deployment. This is expected behavior. Metrics populate once your chain processes its first transactions. Each panel includes a "Contact us" button for support if metrics fail to appear after transaction activity.
Time Range Selector: Each panel includes a "Last hour" dropdown to adjust the metrics time window (options typically include Last hour, Last 24 hours, Last 7 days, Last 30 days).
**Configuration Tab** The Configuration tab contains all technical details required to integrate with your rollup.
**Indexer Information Section:**
| Field | Example Value | Purpose |
| ---------------- | --------------------------------------------------------------------- | --------------------------------------------------------------------------------- |
| **ChainId** | 863048 | Unique network identifier. Required for wallet configuration and chain detection. |
| **Framework** | OP Stack | Confirms Optimism compatibility for tooling. |
| **Name** | ch-optimism-testnet-rollup-cboux2 | Full chain identifier. |
| **Date** | February 25, 2026 | Deployment timestamp. |
| **Explorer** | `https://ch-optimism-testnet-rollup-cboux2-explorer.blockops.network` | Dedicated block explorer URL. Copy button provided. |
| **RPC** | `https://ch-optimism-testnet-rollup-cboux2.rollup.blockops.network` | JSON-RPC endpoint for all interactions. Copy button provided. |
| **Genesis File** | JSON download | Genesis block configuration for local node synchronization. |
| **Rollup File** | JSON download | Rollup-specific configuration for advanced debugging. |
**Parent Chain Contracts Section:** This section lists all L1 (Ethereum) smart contracts deployed for your rollup. These contracts manage the bridge, settlement, and security of your L2 chain.
**Contract Categories:**
| Category | Contracts | Purpose |
| --------------------- | ---------------------------------------------------------------------------- | --------------------------------------------- |
| **Bridge Contracts** | L1StandardBridge, L1StandardBridgeProxy, L1ERC721Bridge, L1ERC721BridgeProxy | Token and NFT bridging between L1 and L2 |
| **Portal Contracts** | OptimismPortal, OptimismPortalProxy, OptimismPortalInterop | Main entry/exit point for L1↔L2 communication |
| **System Contracts** | SystemConfig, SystemConfigProxy, SuperchainConfig | Chain configuration and Superchain membership |
| **Proof Contracts** | MipsImpl, FaultDisputeGame, DisputeGameFactory | Cannon fault proof system for security |
| **Proxy Admin** | ProxyAdmin, SuperchainProxyAdmin | Upgrade mechanism management |
| **Utility Contracts** | AddressManager, ProtocolVersions, AnchorStateRegistry | Supporting infrastructure |
Each contract entry displays:
* 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
*Known Issue:* The external link button currently routes to a 404 error page. As a workaround, copy the address and manually search on Sepolia Etherscan for testnet contracts.
**Step 5: Connect Your Application** With your rollup Ready, integrate it into your development workflow:
**5.1 Add to MetaMask or Wallet** Use these parameters to add your chain to any EVM-compatible wallet:
| Parameter | Value | Source |
| ---------------------- | ------------------------------------------------ | ------------------------------- |
| **Network Name** | \[Your Chain Name] | Configuration tab |
| **RPC URL** | `https://[chain-name].rollup.blockops.network` | Configuration tab - copy button |
| **Chain ID** | \[Numeric ID, e.g., 863048] | Configuration tab |
| **Currency Symbol** | ETH | Standard for all rollups |
| **Block Explorer URL** | `https://[chain-name]-explorer.blockops.network` | Configuration tab - copy button |
**5.2 Configure Hardhat**
```javascript
// hardhat.config.js
module.exports = {
networks: {
myRollup: {
url: "[https://ch-optimism-testnet-rollup-cboux2.rollup.blockops.network](https://ch-optimism-testnet-rollup-cboux2.rollup.blockops.network)",
chainId: 863048,
accounts: [process.env.PRIVATE_KEY],
},
},
};
```
**5.3 Configure Foundry**
```bash
# .env
RPC_URL=[https://ch-optimism-testnet-rollup-cboux2.rollup.blockops.network](https://ch-optimism-testnet-rollup-cboux2.rollup.blockops.network)
CHAIN_ID=863048
```
**5.4 Configure viem/wagmi**
```javascript
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](https://ch-optimism-testnet-rollup-cboux2.rollup.blockops.network)",
],
},
},
blockExplorers: {
default: {
name: "Blockops Explorer",
url: "[https://ch-optimism-testnet-rollup-cboux2-explorer.blockops.network](https://ch-optimism-testnet-rollup-cboux2-explorer.blockops.network)",
},
},
});
```
**5.5 Verify Activity** Once you send your first transaction:
* 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
As your project grows, you may deploy multiple rollups for different environments or use cases. The Rollup dashboard provides unified management.
**Dashboard Overview** The main Rollup dashboard displays all your rollups with key information:
| Column | Description |
| ---------------- | ------------------------------------------------------------------------------ |
| **Name** | Click to view detailed information |
| **Status** | Ready, Deploying, Error, or Stopped |
| **RPC** | Endpoint availability (shows `--------` in list view, use detail view for URL) |
| **Date Created** | Deployment timestamp |
| **Actions** | Delete button (trash icon) - use with caution |
**Available Actions**
*Delete Rollup* The trash icon in the Actions column permanently deletes your rollup and all associated infrastructure. This action cannot be undone.
*Warning:* Deleting a rollup removes all L2 state, RPC endpoints, and explorer data. L1 contracts remain deployed but become inaccessible. Ensure you have backups of any critical data before deleting.
***
### Best Practices
Following these guidelines ensures optimal rollup performance and reliability.
**Naming Conventions**
* 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
**Deployment Strategy**
| Stage | Environment | Purpose | When to Advance |
| --------------- | ----------- | ------------------------------------------------- | --------------------------------------------------- |
| **Development** | Testnet | Smart contract testing, integration development | Contracts compile and pass unit tests |
| **Staging** | Testnet | End-to-end testing, load testing, security review | All tests pass, audit complete |
| **Production** | Mainnet | Live user traffic, real economic value | Staging validation complete, team consultation done |
**Security Considerations**
* 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
**Cost Management**
* 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
**Issue: Status Stuck on "Deploying"**
* **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
**Issue: "Metrics are not available" Persists**
* **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
**Issue: 404 Error on Contract Links**
* **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
**Issue: RPC Connection Refused**
* **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
**Issue: High Gas Costs on L2**
* **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
If you encounter issues not covered here:
| Resource | Access |
| --------------------- | ----------------------------- |
| **Documentation** | docs.blockops.network |
| **Email Support** | |
| **Community Discord** | Join Blockops Community |
| **Dashboard Chat** | Blue chat icon (bottom right) |
When contacting support, provide:
* Rollup name (exactly as shown in dashboard)
* Current status (Deploying, Ready, Error)
* Specific error messages or screenshots
* Steps already attempted
***
### Glossary
| Term | Definition |
| -------------------------- | ----------------------------------------------------------------- |
| **OP Stack** | Optimism's open-source software stack for building L2 blockchains |
| **Settlement Layer** | L1 blockchain (Ethereum) where rollup state is finalized |
| **Data Availability (DA)** | Guarantee that transaction data is available for verification |
| **Sequencer** | Component that orders and executes L2 transactions |
| **Prover** | System that generates cryptographic proofs of L2 state |
| **Fault Proof** | Mechanism allowing challenges to invalid state transitions |
| **Genesis** | Initial state of the blockchain at block 0 |
| **Chain ID** | Unique numeric identifier for a blockchain network |
| **RPC** | Remote Procedure Call - endpoint for blockchain interactions |
| **Blob (EIP-4844)** | Temporary data storage on Ethereum for L2 data availability |
{% hint style="info" %}
[**Follow us on Twitter**](https://twitter.com/blockopsnetwork) **for more information on upcoming protocols and developments.**
{% endhint %}
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.blockops.network/developer/products/rollup.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.