Support Ink Chain Bridging Routes

Author(s): Ink Chain Status: Proposed Related Discussions: https://forum.across.to/t/support-ink-chain-bridging-routes/2022/2

Summary:

The Ink core team proposes the integration of Across to Ink. In collaboration with the Across core team, the Ink 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]: ETH, WETH, USDT, DAI and USDC

Route: Supported Chains <> Ink

Motivation:

Integrating Across aims to tap into the bridge volume from the expanding Ink 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 Ink 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 Ink ecosystem.

Strengthened Partnerships – The Ink team is happy to support Across with partnership opportunities to key dApps in our ecosystem.

About Ink:

Ink is a part of the Optimism Superchain, together with Base, OP Mainnet, Zora, and more.

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 Ink.

The Ink 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, Ink 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 Ink Chain bridging routes. Against - Not in support of supporting Ink Chain bridging routes. If 'For' vote quorum is surpassed, the vote will pass. If the vote passes, the core teams will collaborate to deploy on Ink Chain. The community will be notified as we make progress.