Point of Contact
Yunus Tasliel - Lisk, Head of Business Development
Alexis Low - Lisk, Asia Business Development Lead
Proposal Details
Proposal Overview
The Lisk core team proposes the integration of Across to Lisk. The focus is establishing an efficient Across <> Lisk bridge adapter to ensure seamless interoperability to the network.
In collaboration with the Across core team, the Lisk team has been working to ensure the new chain requirements and technical feasibility (more below in the implementation section) regarding the integration. No technical hurdles prevent a successful deployment outside of the standard auditing processes.
At deployment, we propose the following route[s] be enabled at deployment time:
Token[s]: LSK, ETH, USDC, USDT
Route: Supported Chains <> Lisk
Proposal Motivation & Benefits
This integration will provide several benefits for both Across and Lisk.
Key Benefits for the Lisk Ecosystem:
- Smoother and faster bridging experience
- Minimized fees on cross-chain swaps for Lisk users
- More secure bridging leveraging Across’ intents-based architecture
Key Benefits for Across:
- First-mover advantage for Lisk routes
- Capture growing volumes in the promising Lisk ecosystem
- Extend its reach and access Lisk users in emerging markets
Background
About Lisk
Founded in 2016 as a Layer 1 blockchain, Lisk was one of the pioneering projects to advocate for horizontal blockchain scaling.
Lisk has recently made a significant shift to become an Ethereum Layer 2 platform, utilizing the OP Stack and Gelato’s Rollup-as-a-Service to connect with the Optimism Superchain. The testnet was rolled out in the first quarter of 2024, with plans for the developer mainnet and public mainnet to be deployed in the second and third quarters of 2024, respectively.
The overarching goal of Lisk is to offer Web3 builders an appealing ecosystem to realize their products focused on real-world use cases in emerging markets. In anticipation of the launch, Lisk has strengthened its ties within emerging markets by securing government contracts and forging strategic partnerships with reputable organizations. These partnerships aim to provide foundational developer platforms, mentorship, and initial funding grants to support Web3 startups. Numerous exciting product integrations are also expected over the next 12 months.
Implementation
Timeline
The following key dates are targeted for this deployment.
Topic | Dates |
---|---|
Forum Post | 6 May 2024 |
Governance Vote | 13 May 2024 |
Target Deployment | June 2024 |
Technical Implementation
If approved, the technical implementation of this proposal will be led by core team members of Across, who will oversee the launch on Lisk. The Lisk engineering team will provide dedicated engineering resources available to actively support and collaborate with the Across team on engineering, technical discussions and reviews. This collaboration aims to align both teams on the technical nuances and ensure a smooth, efficient implementation process.
New Chain Requirements
Per the New Chain Requirements found in the Across Documentation, Lisk meets the following requirements:
Criteria | Description | Status |
---|---|---|
EVM Chain & Bridges | EVM chain with a canonical token and message bridge to mainnet | |
RPC Node Providers | ≥ 2 independent RPC node providers | |
Support Channel | Dedicated support channel with technical members and priority support for contract development and debug | |
Token Grant for Across DAO | Bonus: Token grant for Across DAO to distribute to users for transfers to new chain |
Security Considerations
- As part of the Superchain, Lisk is a “canonical” OP stack implementation which does not require smart contract development as Across’ existing OP contracts can be reused
- This maximizes security while minimizing surface area for human error and potential vulnerabilities.
- Also important to note is that Lisk is an official member of the Superchain and works closely with the Optimism Governance Council.
Sources
Next steps
The proposal will be in the Request for Comment (RFC) phase for at least 7 days. After receiving feedback and if the community agrees, a governance vote (on snapshot) will commence to assess the DAO’s desire to deploy on Lisk. If the vote passes, the core team[s] will collaborate to deploy on the target chain. There will be transparent communication throughout this process!