Author: Shahryar, Partnerships Lead @ Scroll
Proposal Overview
The Scroll core team proposes the integration of Across to Scroll. In collaboration with the Across core team, the Scroll 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 be enabled:
- Tokens: ETH, WETH, WBTC, USDC & USDT
- Route: Supported Chains <> Scroll
Proposal Motivation & Benefits
This integration will enable Across to tap into the bridge volume from the expanding Scroll ecosystem. This 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 Scroll 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 Scroll ecosystem.
Strengthened Partnerships – The Scroll team is happy to support Across with partnership opportunities to key dApps in our ecosystem.
Background
About Scroll
Scroll is a bytecode-compatible zkEVM L2 built on Ethereum, focused on security, speed, finality, and decentralization. Scroll has experienced significant TVL growth, reaching over $1B in TVL according to L2Beat and $626M in DeFi TVL according to DeFiLlama. Within Scroll there are a range of projects that could be interesting for Across to partner with to create new product experiences or power their protocols.
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 Scroll.
The Scroll core team is excited to work with Across on engineering, 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, Scroll 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 preference for at least one Tier 1 provider of Infura, Alchemy, Quicknode
- Yes; we have Ankr, Chainstack, and Quicknode
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 have dedicated support from our team to ensure 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 Scroll. If the vote passes, the core teams will collaborate to deploy on Scroll. The community will be notified as we make progress.