CVP Proposal: Connext


Connext is a modular interoperability protocol that allows near-instant and cost-effective crosschain transactions with best-in-class security. Through the use of an intent layer built atop the canonical bridges themselves, Connext is able to resolve the security-speed dichotomy often found in crosschain protocols.

Our simple yet powerful interface allows developers to build crosschain applications that can interact with multiple domains (blockchains and/or rollups) simultaneously, resulting in powerful dApps that can securely interact with users, tokens, and other applications on any chain - just like on the web.

Protocol Architecture & Security

Connext utilizes a modular hub-and-spoke architecture, which derives its security from Ethereum L1 and plugs into the battle-tested canonical messaging bridges that underpin the security of each Ethereum-connected domain.

Messages in Connext are added to a Merkle root generated on each spoke domain, which are then optimistically aggregated into a singular root on Ethereum L1. In the event that fraud is attempted, the system automatically falls back to using the canonical messaging bridge for each chain ecosystem.

For example, a message passed between Polygon and Optimism is secured by a proof posted to Ethereum and verified by the Polygon PoS bridge and Optimism roll-up bridge. Similarly, a message passed within the Cosmos ecosystem is verified by IBC.

This mechanism gives developers the best possible trust guarantees for whichever chains they want to build on. For fraud to occur in our Polygon to Optimism example, there would need to be a compromise of Polygon or Optimism’s canonical bridges and Connext’s failsafe mechanisms.

Connext Vision, Objectives, and Value

Connext aims to bring several key benefits to the Metis ecosystem, including:

  • Fast and cost-effective bridging of ETH, USDC, USDT, METIS, and more between major blockchains and L2s
  • Powerful crosschain tooling, allowing developers to build crosschain-native applications and DAOs
  • Support for xERC20 tokens, allowing for fast, zero-slippage crosschain transactions of supported tokens

Key Resources


I particularly love this aspect of Connext Protocol Architecture and Security but i need you to shed more light on this.

  1. In the modular hub-and-spoke architecture employed by Connext, how does the reliance on Ethereum L1 for security enhance the overall robustness of the system, and what measures are in place to ensure the secure and seamless integration of multiple Ethereum-connected domains?

  2. Could you elaborate on the role of the optimistic aggregation of messages into a singular root on Ethereum L1 in Connext’s architecture? Additionally, what mechanisms are implemented to efficiently handle potential fraud attempts and ensure a smooth transition to the canonical messaging bridge in case of security concerns within the various chain ecosystems?

1 Like

Love to see more interoperability solutions coming to Metis, especially a solution that focuses on bridging the gaps between different EVMs - and particularly L2s.

A couple questions:

  1. How is this similar and unique from Layer 0?

  2. Is Connext a one size fits all interoperability solution - meaning once Connext is deployed is there need for collaboration with other solutions, or Connext is all a chain needs for universal interoperability for various functions?

  3. For tokens that are bridged across chains, does there need to be liquidity on that chain it’s arriving to? If so, how is liquidity provided? If not, please explain bridging cross chain works through Connext using xERC-20.

  4. Please provide a clear example of how a dapp could benefit from utilizing Connext cross chain infrastructure.

Thank you for your offer. I want to ask you a few questions;

1-Can you provide more details about Connext’s security measures?

2-Can you give examples of cross-chain applications that developers can create using Connext?

3-How does Connext support xERC20 tokens that enable fast and zero-slippage cross-chain transactions?

4-How does Connext’s hub-and-spoke architecture work to provide security in Ethereum-connected spaces?

5-What are the contributions of 5-Connext to the Metis ecosystem and the overall goals of the project?

6-How are Connext’s canonical messaging bridges for cross-chain transactions designed and secured?

A lot of interoperable builders coming on metis, but could you illustrate with a practical example how a dApp could leverage Connext’s architecture to create a more fluid and secure experience for its users?