Support Redstone Bridging Routes

Author(s): Biscaryn, Ecosystem @ Redstone Status: Proposed

Summary:

The Redstone core team proposes the integration of Across to Redstone. In collaboration with the Across core team, the Redstone team has been working to ensure the new chain requirements 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

Route: Supported Chains <> Redstone

Motivation:

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

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

About Redstone:

Redstone is a part of the Optimism Superchain, together with Base, OP Mainnet, Zora, and more. Redstone is a home for autonomous worlds. It's a Plasma-inspired L2 that is designed from the ground up to make on-chain worlds accessible, scalable, and cheap.

Built by the Lattice team, who are also the core devs of the MUD framework used by the likes of CCP Games of EVE Online fame, Primodium, and Small Brain Game, Redstone represents a nascent but exciting space for Ethereum applications beyond finance and financialization.

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

The Redstone 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.

Rationale:

Explain any decisions above that were chosen over an alternative. Why is this the best way to do it? How will the implementation of this proposal advance the protocol?

New Chain Requirements

Per the New Chain Requirements 4, Found in the Across Documentation, Redstone 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 Quicknode and our own RPC

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 Redstone bridging routes.
• Against - Not in support of supporting Redstone routes.

If 'For' vote quorum is surpassed, the vote will pass. If the vote passes, the core teams will collaborate to deploy on Redstone. The community will be notified as we make progress.