Author: Unichain Status : Proposed Related Discussions: https://forum.across.to/t/support-unichain-bridging-routes/2012
Summary:
The Unichain core team proposes the integration of Across to Unichain. In collaboration with the Across core team, the Unichain 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, WBTC and USDC
Route: Supported Chains <> Unichain
Motivation:
Integrating Across aims to tap into the bridge volume from the expanding Unichain 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 Unichain 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 Unichain ecosystem.
Strengthened Partnerships – The Unichain team is happy to support Across with partnership opportunities to key dApps in our ecosystem.
About Unichain:
Unichain is a part of the Optimism Superchain, together with Base, OP Mainnet, Zora, and more.
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 Unichain.
The Unichain 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, Unichain 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
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.
Voting:
For - In support of supporting Unichain bridging routes. Against - Not in support of supporting Unichain bridging routes. If 'For' vote quorum is surpassed, the vote will pass. If the vote passes, the core teams will collaborate to deploy on Unichain. The community will be notified as we make progress.
Off-Chain Vote
Loading…
- Author
brittm.eth
- IPFS#bafkreic
- Voting Systembasic
- Start DateNov 21, 2024
- End DateNov 28, 2024
- Total Votes Cast26.72M ACX
- Total Voters72
Discussion
Timeline
- Nov 21, 2024Proposal created
- Nov 21, 2024Proposal vote started
- Nov 28, 2024Proposal vote ended
- Apr 11, 2025Proposal updated