The ecosystem has become more fragmented with the proliferation of multiple blockchains (rollups and appchains). Blockchain interoperability is essential to communicating, transferring assets, and connecting across these diverse blockchain networks.Due to fragmented liquidity and interoperability issues, trading assets between different blockchains can be particularly challenging. <a href="https://eips.ethereum.org/EIPS/eip-7683">ERC-7683</a> standard (draft) for cross-chain intents proposed by Uniswap Labs and Across is an interface for a cross-chain trade execution system. This standard aims to simplify cross-chain actions by providing a cohesive framework.Here is a detailed overview of the standard for cross-chain intents and an analysis of how UniswapX brings cross-chain capability in swaps.<h1>ERC-7683: A Unified Standard for Cross-Chain Intents</h1><h2>What is an Intent-based system?</h2>A system that honors the “intention” of the user without worrying about the complexity of the process of execution. <a href="https://docs.across.to/concepts/what-are-cross-chain-intents">Cross-chain intents</a> are when a user wants to act on one blockchain that results in an outcome on another blockchain.Suppose Alice wants to trade her USDC on Ethereum for WETH on an L2. Traditionally, Alice would have to go through multiple steps including using bridges, and different wallets, making it complex and time-consuming.With ERC-7683, Alice doesn’t need to take multiple steps or worry about how it happens. Intents-based systems simply allow users to specify the end state of the chain – and a network of fillers compete to fulfill the user’s outcome as fast and cheaply as possible.&nbsp;<h2>What Problem Does ERC-7683 Solve?</h2>Many intent-based systems rely on their own network of fillers, leading to a single point of failure and centralization risks. As intent-based systems grow, managing separate relayers and fillers for each protocol becomes challenging.The ERC-7683 standard addresses these issues by standardizing cross-chain intents, enabling a universal filler network for more efficient transactions and making it easier for different systems to work together.&nbsp;<h2>Key Components in Cross-chain Trade Execution with ERC7683:</h2>&nbsp;<ol style="list-style-type:upper-latin;"><li>Swapper (user): The one who signs an off-chain message defining the order with <code>CrossChainOrder</code> Struct, which contains all the necessary information about an order for the cross-chain trade.</li></ol>&nbsp;<pre><code class="language-plaintext">struct CrossChainOrder {
 address settlementContract; // Address of the contract to settle the order
 address swapper; // User initiating the swap
 uint256 nonce; // Unique number to prevent duplicate orders
 uint32 originChainId; // ID of the originating blockchain
 uint32 initiateDeadline; // Time by which the order must start
 uint32 fillDeadline; // Time by which the order must complete
 bytes orderData; // Additional data like tokens, amounts, destination chains
}</code></pre>&nbsp;Additionally, <code>ResolvedCrossChainOrder</code> struct provides detailed information about the order, making it easier to compute the necessary inputs and outputs for fulfilling the order. This struct ensures both (swapper and filler) parties know exactly which tokens are exchanged, the amounts, and the blockchains involved.&nbsp;<pre><code class="language-plaintext">struct ResolvedCrossChainOrder {
 address settlementContract;
 address swapper;
 uint256 nonce;
 uint32 originChainId;
 uint32 initiateDeadline;
 uint32 fillDeadline;
 Input[] swapperInputs; // Tokens to be taken from the swapper
 Output[] swapperOutputs; // Tokens to be given to the swapper
 Output[] fillerOutputs; // Tokens to be given to the filler
}
struct Input {
 address token; // ERC20 token address
 uint256 amount; // Token amount
}
struct Output {
 address token; // ERC20 token address (or native token if address is 0)
 uint256 amount; // Token amount
 address recipient; // Address to receive the output
 uint32 chainId; // Destination blockchain ID
}</code></pre>&nbsp;&nbsp;B. &nbsp;Filler (entity that completes the trade): Fillers are entities or smart contracts responsible for initiating trades on the origin chain, &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;executing orders on the destination chain, and settling cross-chain orders.Fillers receive rewards for the service they provide. They have a flexible design allowing customized behavior such as price resolution mechanisms, fulfillment constraints, and settlement procedures.&nbsp;C. Settlement Contract: The <code>ISettlementContract</code> interface defines the basic structure for a settlement contract functions such as <code>initiate</code> and <code>resolve</code>.&nbsp;<pre><code class="language-plaintext">interface ISettlementContract {
 function initiate(CrossChainOrder order, bytes signature, bytes fillerData) external;
 function resolve(CrossChainOrder order, bytes fillerData) external view returns (ResolvedCrossChainOrder);
}</code></pre><h2>How can ERC-7638 be used in other systems for Cross-chain functionality?</h2>By extending<code>IsettlementContract</code>, you can implement the ERC-7638 standard for cross-chain orders specific to any protocol.Let us analyze with an <a href="https://www.erc7683.org/examples">example</a> implementation of how ERC-7683 can work with Permit2 and Across. It defines a settlement contract that handles cross-chain orders on the Across network and uses Permit2 for token transfers. Here is how it works:<ul><li>Alice creates a cross-chain order on the origin chain with essential parameters for the order. She signs the order using Permit2, a mechanism that allows secure token transfers.</li><li>The settlement contract receives Alice's signed order on the origin chain. It checks order details, verifies signatures, and takes the specified amount of ETH from Alice's account.</li><li>On the destination chain, filler resolves the order and prepares the USDC for Alice to fulfill the order.</li><li>Filler calls the <code>fillCrossChainOrder</code> in the SettlementContract to fulfill initiated orders and transfer USDC to Alice.</li></ul>&nbsp;<h2>Benefits of ERC-7683</h2><ul><li>Interoperability: It allows for the seamless interaction between various networks, reducing complexity to bring cross-chain capability in any infrastructure.</li><li>Better User Experience: Simplifies the process for users, making cross-chain transactions more seamless.</li><li>Lower Entry Barriers and Costs: Easier for new fillers to enter the market, expanding the network. Reduced complexity and centralization lower transaction costs.</li><li>Broader Access: Applications benefit from a more extensive filler network, enhancing overall efficiency.</li></ul>&nbsp;<h1>UseCase: UniswapX for Cross-Chain Trades</h1>In July 2023, Uniswap introduced UniswapX for cross-chain functionality, the future of trading assets in crypto. Cross-chain trade is the process of trading tokens or assets between different blockchains. Integrating ERC-7683 into Uniswap's ecosystem can expand its capabilities beyond Ethereum and its L2s, enabling users to perform cross-chain trades.<figure class="image image_resized" style="width:50%;"><img src="https://strapi.buildbear.io/uploads/Uniswap_X_4d2ae26025.png" alt="UniswapX.png" srcset="https://strapi.buildbear.io/uploads/thumbnail_Uniswap_X_4d2ae26025.png 245w,https://strapi.buildbear.io/uploads/small_Uniswap_X_4d2ae26025.png 500w,https://strapi.buildbear.io/uploads/medium_Uniswap_X_4d2ae26025.png 750w,https://strapi.buildbear.io/uploads/large_Uniswap_X_4d2ae26025.png 1000w," sizes="100vw"><figcaption>Image Source: https://blog.uniswap.org/uniswapx-protocol</figcaption></figure>Let's quickly understand how <a href="https://blog.li.fi/uniswapx-a-deep-dive-4b4ea7673dc1">UniswapX operates</a> and how the implementation of ERC-7683 would be.UniswapX is an auction-based protocol for finding the best price for user’s trade across AMMs and other onchain and off-chain liquidity sources. It follows an intent-based approach with new entities called “fillers”, which consist of market makers and MEV searchers, who bid for the trade in a Dutch auction to find the best price.&nbsp;What is Dutch Auction?Dutch auctions start with a high asking price and gradually lower until a bidder accepts it. This concept is how UniswapX fillers compete to give you the best prices. These fillers search their liquidity sources. The one offering the best price wins. If the filler cannot complete the trade, the price drops until the next filler can.UniswapX would be the very first application using the cross-chain intent standard(ERC-7683). Let us see how UniswapX implementation of ERC7683 for cross-chain trade with Alice looks like:<figure class="image image_resized" style="width:50%;"><img src="https://strapi.buildbear.io/uploads/intent_526d4e3012.png" alt="intent_.png" srcset="https://strapi.buildbear.io/uploads/thumbnail_intent_526d4e3012.png 245w,https://strapi.buildbear.io/uploads/small_intent_526d4e3012.png 500w,https://strapi.buildbear.io/uploads/medium_intent_526d4e3012.png 750w,https://strapi.buildbear.io/uploads/large_intent_526d4e3012.png 1000w," sizes="100vw"><figcaption>Image from : https://x.com/Uniswap/status/1812847835693342996/photo/1</figcaption></figure>&nbsp;<ul><li>Alice creates a <code>CrossChainOrder</code> on Uniswap specifying her intention to swap ETH on Ethereum for USDC on another chain, let's say, 1 ETH for 1000 USDC.</li><li>The intent is then sent to the UniswapX Filler network, which checks their liquidity sources(Uniswap Protocol, Sushiswap, etc) for the price.</li><li>For example, Filler A offers 999 USDC for 1 WETH, Filler B offers 998 USDC and Uniswap v3 offers 996 USDC. Filler A wins the bid.</li><li>Alice accepts Filler A, as it offers the best price. And calls the <code>initiate</code> function on the <code>ISettlementContract</code> to begin the trade on Ethereum.</li><li>The filler then executes the trade on the destination chain swapping the tokens.</li><li>The filler calls the <code>resolve</code> function on the settlement contract to finalize the trade. If Filler A couldn’t complete the trade, the auction would continue at the next best price.</li><li>Alice and the filler receive their respective tokens according to the <code>ResolvedCrossChainOrder</code> details.</li></ul><h1>Conclusion</h1>Rollups and L2 have scaled Ethereum but bring fragmentation. This fragmentation will grow as more rollups and app-chains come online. ERC-7683 simplifies cross-chain trading by providing a unified standard. This makes it easier for developers to build and for users to trade across different chains. Platforms like UniswapX can now offer seamless cross-chain trades, improving liquidity, reducing costs, and creating a more efficient ecosystem.&nbsp;<h1 style="margin-left:0px;">About BuildBear:</h1><a href="https://www.buildbear.io/">BuildBear</a>&nbsp;is a platform tailored for DApp development and testing. Developers gain the freedom to construct a personalized Private Testnet sandbox across a variety of blockchain networks. The liberty to mint unlimited Native and ERC20 tokens, coupled with rapid transaction times on BuildBear (under 3 seconds!), enhances the DApp development lifecycle manifold. The platform comes equipped with tools and plugins designed for real-time testing and debugging, ensuring developers can keep tabs on intricate blockchain transactions with unparalleled ease.Connect with us on&nbsp;<a href="https://twitter.com/_BuildBear">Twitter</a>&nbsp;|&nbsp;<a href="https://www.linkedin.com/company/build-bear/">LinkedIn</a>&nbsp;|&nbsp;<a href="https://t.me/Web3_dApp_Developers">Telegram</a>&nbsp;|&nbsp;<a href="https://github.com/BuildBearLabs">GitHub</a>Author: <a href="https://www.linkedin.com/in/sanamummer/">Sana</a>

image (6).png

Blockchain interoperability is essential to communicating, transferring assets, and connecting across these diverse blockchain networks. Here is a detailed overview of the standard for cross-chain intents and an analysis of how UniswapX brings cross-chain capability in swaps.



A Deep Dive into ERC-7683 for Cross-Chain Intent

Let’s get started then, Shall we?

Let’s get started then, Shall we?

Test DApps at Scale.