Integration Guide for OP Stack Rollup with GlitchD DA Layer
This section describes the requirements and procedures necessary to integrate OP Stack rullups with with GlitchD Data Availability (DA) Layer solution using Holesky testnet on Ethereum as settlement.
Prerequisites and Initial Configuration
To initiate an OP Stack rollup, follow the steps provided in the official documentation. OP Stack documentation covers all procedures necessary for deplying the rollup, however, please note that the following adjustments are necessary for switching the network to Holesky testnett:
Change the Network Chain ID: Modify the chain ID from Sepolia to Holesky.
Modify the Batcher’s Destination L1 Address: Update the batcher’s destination L1 address to separate transactions from the default destination address on the Holesky 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.
As illustrated in the Light Client diagram, the light client performs the following functions:
Stores L2 transaction batch data to the DA Layer.
Saves versioned hashes on L1.
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 Holesky network can be found at the following link:https://holesky.etherscan.io/txs?a=0xff00000000000000000000000000000000042444
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.
Last updated