Support Lens Bridging Routes
Title: Support Lens Bridging Routes
Author: Lens
Proposal Overview
The Lens core team proposes integrating Across with Lens. In collaboration with the Across core team, the Lens team has been working to ensure the new chain requirement and technical feasibility (more below in the implementation section) regarding the implementation of the bridge adapters.
At deployment, we propose the following route[s] be enabled:
Token[s]: WETH, USDC
Route: Supported Chains <> Lens
Proposal Motivation & Benefits
Integrating Across aims to tap into the bridge volume from the expanding Lens ecosystem. This move will provide users and developers with efficient, cost-effective token bridging options, leveraging Across’ intent-based infrastructure. The goal is to enhance Across Protocol’s market presence by offering crucial bridging solutions in a promising ecosystem.
Some of the benefits of integrating Across with the Lens ecosystem include:
Market Expansion – This integration enables Across to extend its reach and capture a larger portion of the bridge volume within the L2 space, specifically in the growing Lens ecosystem.
Strengthened Partnerships – The Lens team is happy to support Across with partnership opportunities to key dApps in our ecosystem.
About Lens
Lens is the fastest, lowest-cost Ethereum network powering social and finance.
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 Lens.
The Lens core team is excited to work with Across on engineering, and engage in technical discussions, and audit workstreams to ensure this is a great launch. This collaboration aims to align both teams on the technical nuances and ensure a smooth, efficient implementation process.
An audit was conducted for this deployment.
New Chain Requirements
Per the New Chain Requirements 4, Found in the Across Documentation, Lens meets the following requirements:
Hard Requirements
EVM chain with a canonical token and message bridge to mainnet
- Yes
≥ 2 independent RPC node providers that can reliably support ~150M RPC requests per month from Across, with a preference for at least one Tier 1 provider of Infura, Alchemy, Quicknode
- Yes
Dedicated support channel containing technical members of the new chain with priority support commitment to advise on contract development and debug data quality and/or disagreements between RPC providers
- Yes we will focus on your team to make sure it is a successful deployment.
Next steps
The proposal will be in Request for Comment (RFC) phase. After receiving feedback and if the community agrees, a governance vote (on snapshot) will commence to assess the DAO’s desire to deploy on Lens. If the vote passes, the core teams will collaborate to deploy on Lens. The community will be notified as we make progress.