Support Blast Chain Bridge Routes

Author(s): Blast & Across Status: Proposed

Proposal Overview:

The Blast core team proposes the integration of Across to Blast. In collaboration with the Across core team, the Blast 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, WBTC, DAI Route: Supported Chains <> Blast

Motivation:

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

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

About Blast:

Blast has experienced significant TVL growth, reaching over $2.76B in TVL according to L2Beat and $1.3B in dApp TVL according to DeFiLlama. Within Blast there are a range of projects that could be interesting for Across to partner with to create new product experiences or power their protocols.

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

The Blast 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, Blast 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 Infura 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 focus on your team to make sure it is a successful deployment.

Voting:

For - In support of 'Support Blast Chain Bridge Routes' Against - Not in support of 'Support Blast Chain Bridge Routes'

If the vote passes, the core teams will collaborate to deploy on Blast. The community will be notified as we make progress.