L2 Blockchains
Last updated
Last updated
- Configure and run the Sunrise DA relay
- Build and deploy a Rollkit-based L2
- Set up Sunrise DA for OP Stack
- Deploy an OP Stack L2 with Sunrise
It is recommended to run the full consensus node locally, without relying on an external RPC. This ensures better reliability and control over your L2 deployment.
sunrise-data
, and rollkit
need to be run. The integration provides:
Native data availability through Sunrise
Sovereign rollup capabilities
Customizable execution environment
Simple configuration and deployment
sunrise-data
, optimism
and op-geth
need to be run. Key points:
The local EVM L1 chain is only used to meet OP Stack requirements
The actual data (metadata) is stored in Sunrise
Use Ganache, Hardhat, Anvil or similar for local L1 chain
Sunrise handles the actual data availability
Rollkit + Sunrise Data
4 Core
x86_64
16 GB
1 TB SSD
1 Gbps
Development and testing
OP Stack + Sunrise Data
6 Core
x86_64
32 GB
1 TB SSD
1 Gbps
Production deployment
Additional considerations:
SSD should be enterprise-grade for production
Bandwidth requirements increase with transaction volume
Memory requirements scale with state size
Provides full EVM compatibility while maintaining Sunrise DA benefits
Comprehensive documentation for OP Stack deployment
Integration guides for various components
Setup Sunrise DA Node
Deploy a Sunrise node or connect to the testnet
Configure network parameters
Set up validator if needed
Verify node synchronization
Configure L2 Framework
Install required dependencies
Set up configuration files
Connect to Sunrise DA layer
Configure network parameters
Implement DA Integration
Configure blob submission
Set up proof verification
Implement fee handling
Set up monitoring
Testing and Deployment
Test on testnet
Verify DA proofs
Deploy to production
Monitor performance
Security
Always verify DA proofs
Use secure RPC endpoints
Implement proper error handling
Regular security audits
Performance
Optimize blob sizes
Implement proper caching
Monitor gas costs
Regular performance testing
Reliability
Implement retry mechanisms
Monitor DA proof status
Set up proper logging
Regular backups
DA proofs not verifying
Check RPC connection and proof format
Regular connection testing
High gas costs
Optimize blob size and frequency
Monitor and adjust gas settings
Connection issues
Verify network configuration and firewall settings
Regular network monitoring
Fee Abstraction
: By combining BeaconKit and Rollkit, EVM compatible L2 blockchain is possible to develop.