Across is now live on Lens Chain!
Bridge Now
Across Documentation
V3 Developer Docs
V3 Developer Docs
  • 👋Introduction
    • Welcome to Across
    • What is Across?
    • Technical FAQ
    • Migration Guides
      • Migration from V2 to V3
      • Migration to CCTP
        • Migration Guide for Relayers
        • Migration Guide for API Users
      • Migration Guide for Non-EVM and Prefills
        • Breaking Changes for Indexers
        • Breaking Changes for API Users
        • Breaking Changes for Relayers
        • Testnet Environment for Migration
      • Solana Migration Guide
      • BNB Smart Chain Migration Guide
  • 🔗Use Cases
    • Instant Bridging in your Application
      • Bridge Integration Guide
      • Multichain Bridge UI Guide
      • Single Chain Bridge UI Guide
    • Embedded Crosschain Actions
      • Crosschain Actions Integration Guide
        • Using the Generic Multicaller Handler Contract
        • Using a Custom Handler Contract
      • Crosschain Actions UI Guide
    • Settle Crosschain Intents
    • ERC-7683 in Production
  • 🧠Concepts
    • What are Crosschain Intents?
    • Intents Architecture in Across
    • Intent Lifecycle in Across
    • Canonical Asset Maximalism
  • 🛠️Reference
    • API Reference
    • App SDK Reference
    • Contracts
      • Aleph Zero
      • Arbitrum
      • Base
      • Blast
      • Ethereum
      • Linea
      • Ink
      • Lens
      • Lisk
      • Mode
      • Optimism
      • Polygon
      • Redstone
      • Scroll
      • Soneium
      • Unichain
      • World Chain
      • zkSync
      • Zora
    • Selected Contract Functions
    • Supported Chains
    • Fees in the System
    • Actors in the System
    • Security Model and Verification
      • Disputing Root Bundles
      • Validating Root Bundles
    • Tracking Events
  • 🔁Relayers
    • Running a Relayer
    • Relayer Nomination
  • 📚Resources
    • Release Notes
    • Developer Support
    • Bug Bounty
    • Audits
Powered by GitBook
LogoLogo

Products

  • Across Bridge
  • Across+
  • Across Settlement

Socials

  • Discord
  • Twitter
  • Medium
  • Forum

Resources

  • Blog
  • Across Brand Assets
  • Github

Routes

  • Bridge to Unichain
  • Bridge to Arbitrum
  • Bridge to Optimism
  • Bridge to Linea
  • Bridge to Polygon
  • Bridge to Base
  • Bridge to World Chain
  • Bridge to zkSync
On this page
  • Introduction
  • Interoperability by Passing Messages
  • Interoperability with Intents
  • Closing the Loop: Settlement
  • The Future of Interoperability is Intents
  • Across' Intents Architecture
  1. Introduction

What is Across?

PreviousWelcome to AcrossNextTechnical FAQ

Last updated 2 months ago

Across is an interoperability protocol powered by intents. It is the only crosschain intents protocol in production today, enabling the fastest and lowest-cost way to transfer value without security tradeoffs vs. traditional bridges. Before diving into the technical details, its critical to understand why and where existing interoperability solutions fall short and why Across' intents-based architecture is needed.

Introduction

The arrival of rollups and L2s scaled Ethereum but damaged end user UX in every way except price. Developers building on L2s must choose which silo they want to build on. Users must become experts in the interoperability tooling landscape simply to use dapps. This fragmentation will continue as more rollups and app-chains come online.

Across' thesis is that an intents-based design paradigm is the solution to the interoperability challenges developers and users face today.

Interoperability by Passing Messages

Any interoperability discussion starts with the most fundamental challenge of token bridging: how can assets be sent from Chain A to Chain B? The naive answer is to “send a message” between the chains. Years of R&D have been invested in this approach, but it faces a problem: it is to send messages cheaply, quickly and securely. Every message-passing protocol today has unique trust assumptions, can only ever be as fast as the finality of chains it connects and has deep implementation complexity.

What if there was another way?

Interoperability with Intents

Intents introduce a third party, a relayer (alternatively named filler, or solver), that does the job of delivering assets / executing user transactions quickly.

From the user’s perspective, interoperability is solved. Their desired outcome is achieved.

Closing the Loop: Settlement

Intents architecture enables filling user orders extremely quickly, but how do relayers get paid for performing this service? User funds are escrowed in the settlement protocol, and are only released to the relayer once the protocol has verified that the user intent was “fulfilled.”

By using an intents-based architecture, the urgent part (filling user orders) is decoupled from the complex part (message verification). The trade-off is relayers must loan funds for the duration between filling user orders and verification, but the benefits of slow settlement far outweigh this cost.

The Future of Interoperability is Intents

  • Message-passing is nearly impossible to do cheaply, quickly, and securely.

  • Intents-based solutions with relayers can fill users instantly.

  • Slower verification allows for cheap and secure settlement.

Across' Intents Architecture

Across' intent-based architecture can be distilled into a 3-layered system:

  1. Request for Quote Mechanism: Users express their desired outcomes without specifying the technical steps to achieve them.

  2. Network of Competitive Relayers: A decentralized network of 3rd parties compete to fulfill these orders.

  3. Settlement Layer: Escrows user input funds, performs verification, and repays relayers upon successful completion of the intent.

Across intents-based architecture underpins our suite of products for end-users and developers:

  • Across Bridge dApp: An end-user bridge dApp offering the lowest fees and fastest speeds of any crosschain asset bridge.

Welcome to the developer documentation for Across — where we're building the future of interoperability through intents.

An intent is a type of order where a user specifies an outcome instead of an execution path. In practice, intents manifest as a combination of a crosschain limit order and an action to execute, all encoded within a standardized order structure. Relayers compete on cost and speed to fill these orders, which can include onchain actions as well as assets. Relayers deliver , without any messages.

Across Bridge for Developers: Easily integrate Across' instant and low-cost liquidity via our easy to use into any application. Let users easily onboard assets without leaving your app. And even abstract bridging completely, enabling users to directly interact with your app from any chain.

Across Settlement: The only production-ready, modular settlement layer built to facilitate crosschain intents. Powers use cases that require customization beyond the offering, like crosschain token swaps, new request for quote auction designs and more.

👋
very quickly
REST API
Across Bridge Integration
nearly impossible