Author(s): Risk Labs Status: Proposed Related Discussions: (optional)
Summary:
Across proposes integrating Across with an additional L1, next to Ethereum. In collaboration with the Across core team, the L1’s 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]: USDC
Route: Supported Chains <> L1.
Motivation:
Integrating Across aims to tap into the bridge volume from the expanding L1’s 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 an additional L1 ecosystem include:
Market Expansion – This integration enables Across to extend its reach and capture a larger portion of the bridge volume within that L1’s space, specifically in its growing ecosystem.
Strengthened Partnerships – The L1’s team is happy to support Across with partnership opportunities to key dApps in our ecosystem.
Specification & Implementation:
If approved, the technical implementation of this proposal will be led by core team members of Across, who will oversee the launch on the L1.
The L1’s 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.
Voting:
If the vote passes, the core teams will collaborate to deploy on the L1. The community will be notified as we make progress.
Off-Chain Vote
Loading…
- Author
brittm.eth
- IPFS#bafkreic
- Voting Systembasic
- Start DateApr 11, 2025
- End DateApr 18, 2025
- Total Votes Cast14.38M ACX
- Total Voters50
Timeline
- Apr 11, 2025Proposal created
- Apr 11, 2025Proposal vote started
- Apr 18, 2025Proposal vote ended
- Apr 18, 2025Proposal updated