Viction
  • Getting Started
  • General
    • Overview
    • Viction Blockchain
      • PoSV Consensus
      • Comparison
    • Staking
      • Staking Requirements
      • Staking Rewards
      • How to stake on Viction Wallet
    • Network Information
      • Viction Mainnet
      • Viction Testnet
    • Viction RPC API
  • Smart Contract Development
    • Solidity
      • A Simple Smart Contract
      • Solidity by Example
    • Standards & Specification
      • VRC25 Specification
      • VRC725 Specification
    • IDEs and Tools
      • Remix
      • Ethers.js
      • web3.js
      • thirdweb CLI
    • Deployment & Verification
      • Hardhat
      • Foundry
  • DApp Development
    • Integration
      • Exchange/Wallet integration
      • VRC25 Exchange/Wallet integration
      • Viction Staking Governance
      • VIC ZeroGas
      • VRRF
    • Data and analytics
    • Embedded Wallet (MPC)
    • Walkthrough: Build a Dapp on Viction
      • Setup Environment
      • Write the Smart Contract
      • Interacting with the Dapp in a browser
  • Masternode
    • Requirements
    • Run a Full Node
      • Binary
      • Create a Viction Masternode
      • Tmn
      • Docker
    • Apply Your Node
    • Slashing Mechanism
    • Chain Data Snapshots
    • Troubleshooting
  • Viction Wallet
    • User Guide
      • Authentication
      • How to create a new wallet
      • How to restore a wallet?
      • Wallet settings
      • Send & Receive Tokens
      • Add custom token
      • Manage Tokens
      • Send NFT
      • General settings
    • Developer Guide
    • Privacy Policy
    • Term and Services
  • Viction Bridge
    • Spacegate
    • Arken Bridge
    • Hyperlane
  • Viction Data Availability
    • Viction DA RPC API
    • DA Integration Use cases
      • Simple Guide for Integrating OP Stack Rollup with Viction DA Layer
  • How to
    • How to Connect to Viction Blockchain
      • Coin98 Super Wallet
      • Metamask
      • Ledger
    • How to troubleshoot when the node is up but couldn't begin to sync block
    • How to Vote for Viction Saigon Network Upgrade Proposal
    • How to issue a token via VICIssuer
    • How to verify if a contract has been issued via VICIssuer
    • How to deploy the VRC725 contract
    • How to apply ZeroGas for VRC725 contract
    • How to Migrate Dapps from Ethereum
    • How to register Token or NFT logo on Vicscan
    • How to verify a contract on Vicscan
    • How to confirm a project on Vicscan
    • How to check if a token is gas sponsored on Viction
    • How to verify gas sponsored transactions
    • How to create Telegram Mini Apps
    • How to use VictionSafe (Multisig)
  • FAQ
    • APIs
    • General
      • Viction
      • Ecosystem
      • VIC - Economics
      • Contact & Support
    • Masternodes and Voting
      • Masternodes
      • Voter
    • Products
      • VicScan (Explorer)
      • VicMaster
      • VicStats
      • VicIssuer
        • How to Verify & Publish Contract Source Code on VicScan
      • Viction Wallet
      • Viction Data Availability Network
  • Legal
    • Terms of Use
    • Privacy Policy
  • Whitepaper and Research
  • Archive
    • TOMOE
    • How to Deploy a VRC25 Token on Viction
    • How to deploy an ICO smart contract on Viction
    • How to deploy an NFT token
    • An Example of Building a Dapp on Viction
    • Migrate Ethereum Dapp to Viction
    • TomoMasterDAO
      • Introduction
      • Governance model
        • On-Chain vs Off-Chain Voting
        • Board
        • Proposals
        • Voting and Outcome
      • Tokenomics
      • How to utilize and trade tDAO
      • Proposal guidelines for TomoMasterDAO
    • Old Viction Testnet
    • Deploy on Viction
      • CLI Commands
      • Viction Private Testnet Setup
Powered by GitBook
On this page
  • Prerequisites and Initial Configuration
  • Service Configuration for DA Layer Integration
  • Testing the Integration
  1. Viction Data Availability
  2. DA Integration Use cases

Simple Guide for Integrating OP Stack Rollup with Viction DA Layer

This guide explains how to connect OP Stack rollups with the Viction Data Availability (DA) Layer using the testnet on Viction as settlement.

PreviousDA Integration Use casesNextHow to

Last updated 7 months ago

Prerequisites and Initial Configuration

To initiate an OP Stack rollup, follow the steps provided in the . OP Stack documentation covers all procedures necessary for deploying the rollup, however, please note that the following adjustments are necessary for switching the network to Viction testnet:

  • Change the Network Chain ID: Modify the chain ID from Viction testnet

  • Modify the Batcher’s Destination Viction Address: Update the batcher’s destination Viction address to separate transactions from the default destination address on the Viction network.

The above two updates can be made after creating the getting-started.json file.

Service Configuration for DA Layer Integration

Once all OP services are started, proceed with the following steps:

1. Start the Light Client: Initialize the light client service, which will handle storing L2 transaction batch data to the DA Layer.

2. Stop the Batcher Service: Temporarily halt the batcher service to apply the necessary configuration changes.

3. Update the Batcher Configuration: Modify the --l1-eth-rpc parameter in the batcher’s configuration to point to the light client’s RPC URL.

4. Resume the Batcher Service: Resume the batcher service to continue processing transactions.

, the light client performs the following functions:

  • Stores L2 transaction batch data to the DA Layer.

  • Saves versioned hashes on Viction.

  • Returns the versioned hashes to the batcher.

Testing the Integration

A test OP Stack L2 network is available for experimentation:

  • Chain ID: 42444

  • Batcher transactions on the Viction network can be found at the following link:

By comparing the initial transactions with subsequent ones, particularly focusing on the input size, it becomes evident that the input size is significantly smaller in later transactions. This reduction occurs because the transactions contain only the versioned hashes of the data stored on the DA layer.

By adhering to these steps and configurations, the integration of the DA Layer solution with an OP Stack rollup can be successfully accomplished. For any questions or issues, please consult the documentation or contact our team.

L2 RPC Node:

official documentation
As illustrated in the Light Client diagram
http://geth-l2-op-stack-rollup-dev-1161098553.eu-central-1.elb.amazonaws.com:8545/