ACX

Across Protocol (acx) is an interoperability solution powered by intents, designed to connect users with decentralized applications across various blockchain networks. Instead of specifying complex execution steps, users express their desired outcomes, which competitive relayers then fulfill using their own capital. The protocol employs a three-layered architecture: a request for quote (RFQ) mechanism, a network of competitive relayers, and a settlement layer that escrows funds, verifies fulfillment, and repays relayers. This allows for fast, low-cost crosschain transactions, making it a pivotal cryptocurrency bridge.

Across Protocol (acx) addresses the fragmentation and complexity inherent in the multi-chain Ethereum ecosystem, which has seen user experience degrade despite the scaling benefits of L2s like Polygon and Arbitrum. Traditional message-passing bridges often suffer from slow speeds, high costs, and complex security assumptions. Across Protocol solves this by introducing intents-based interoperability, enabling instant and secure asset transfers. It simplifies the user experience by abstracting away the complexities of cross-chain communication, aiming to unify liquidity and dApp access across chains like Optimism and zkSync Era.

Across Protocol distinguishes itself from traditional message-passing bridges through its unique intents-based architecture. Unlike competitors that rely on sending messages directly between chains, Across (acx) utilizes a network of competitive relayers to instantly fulfill user requests. This design decouples the urgent act of filling orders from the slower, more complex verification process, which occurs optimistically via a settlement layer verified by UMA's Optimistic Oracle. This results in empirically proven lowest fees, fastest speeds (average fill time < 1 minute), and enhanced security by shifting risk to third-party relayers, making Across Protocol a superior cross-chain communication solution.

Traditional bridges often employ multi-sig wallets or representative tokens, creating centralized attack surfaces and asset fragmentation. Across Protocol eliminates these risks through: 1) Direct transfer of canonical assets (never wrapped tokens), 2) Relayer-first design where professionals absorb execution risk, and 3) Optimistic verification requiring only one honest actor to dispute fraud. This model maintains Ethereum-equivalent security while enabling faster settlements than message-passing alternatives.

Yes, Across offers two integration tiers: 1) Simple REST API for basic bridging abstraction within existing dApps, and 2) Settlement Layer access for advanced use cases like cross-chain swaps or conditional transactions. Developers implement post-bridge actions through hook functions and can leverage ERC-7683 standardized intents for compatibility with other intents-based systems.

Three mechanisms ensure relayer integrity: 1) Economic incentives where honest behavior yields rewards (up to 100% APY), 2) Bond requirements that are slashed for provable fraud, and 3) UMA's optimistic oracle providing cryptographic verification of all settlements. RelayNodes fund user transfers from their own capital but receive reimbursement only after dispute windows expire, making attacks economically nonviable.

ACX employs novel incentive structures: 1) Reward locking multiplies LP earnings (up to 3x) when rewards remain unclaimed for extended periods, 2) 4-year vesting schedules for team allocations prevent early dumping, and 3) Superfluid collateralization allows combining ACX with bridge LP tokens for compounded yields. These mechanisms promote stakeholder retention while the fixed 1B supply prevents inflationary dilution.

Intents enable: 1) Execution path optimization where relayers compete on speed/cost rather than fixed routes, 2) Chain abstraction allowing single-chain user experiences with multi-chain functionality, and 3) Generalized function support beyond simple transfers (swaps, conditional logic, multi-step operations). This paradigm reduces latency to seconds versus minutes/hours in message-passing bridges while eliminating user-side finality risk.