Ethring
  • Introduce
    • Overview
    • Core Benefit
    • Protocol Components
  • Core
    • Wallet Adapter
    • Operation Bag System
    • Config Provider
    • Balance Provider
    • Transaction Manager Service
    • Bridge-Dex Module
    • Asset Integration Layer
    • LP/Assets Standards Support
    • Security for Ethring Middleware
    • Deployment Addresses
  • Resourses
    • FAQ
      • What is Ethring?
      • How does Ethring work?
      • What makes Ethring unique?
      • What yield strategies can I use?
      • How does routing work?
      • Does Ethring hold tokens in its smart contracts?
      • Which networks does Ethring support?
      • What protocols does Ethring support?
      • Which providers does Ethring support?
      • What is The Bag?
      • How to deposit liquidity?
      • How to withdraw liquidity?
      • How can I integrate my LP assets and protocol into Ethring?
      • Partnership
    • Glossary
    • Brand Kit
  • Social
    • Ethring
    • Discord
    • X
    • Warpcast
    • Lens
    • Mirror
Powered by GitBook
On this page
  1. Core

Bridge-Dex Module

PreviousTransaction Manager ServiceNextAsset Integration Layer

Last updated 1 month ago

Bridge-Dex is our unified aggregation engine that ensures smooth asset transfer and exchange across the blockchain using third-party bridge and DEX APIs.

Why It Matters

The future of Web3 is chain-abstracted UX — users shouldn’t have to think about what network their assets are on. Bridge-DEX turns this vision into reality by:

  • Aggregating multiple bridges and DEXes under a single interface

  • Automatically calculating the most optimal path for cross-chain actions

  • Supporting complex multi-steps flows (): Swap → Bridge → Stake, executed as a single bundled transaction plan


What are Zaps ?

Zaps (also known as bundled executions) combine multiple DeFi actions into a single operation. In Bridge-DEX, these Zaps are optimized for gas usage and executed via direct smart contract calls for reliable delivery.


Modular & Scalable Design

Under the hood, Bridge-DEX is built on a standardized service model, which includes bridge and dex provider interfaces that follow a common format.

According to this:

  • Adding a new bridge or DEX doesn’t require changes in aggregator logic.

  • Each provider implements a standardized interface (fetching quotes, estimating fees, building transactions).

  • The aggregator dynamically detects available services and evaluates the best route based on configuration and live data.

  • You only need to provide a config object (e.g. API endpoints, service type, feature flags and etc) — the integration process takes hours, not days.

This design makes the system highly maintainable and future-proof, allowing us to adopt new standards like:

  • Chain Abstraction (CA)

  • Interop APIs

  • Native Account Abstraction bridges


To determine the most optimal route between multiple third-party providers (bridges, DEXes), our Bridge-DEX module includes a priority-based route selection algorithm. This ensures that the user always gets the most favorable outcome based on different criteria like fees, return, or gas costs.

  1. Iterates through all available routes.

  2. Calculates total fees in USD for each route.

  3. Compares routes based on selected priority (bestFee, bestReturn, etc.).

  4. Marks the best route for each priority with a boolean flag.

  5. Sorts the list by selected priority to return an ordered array.

  6. Returns:

    • best: Service ID with the best result

    • priority: The selected priority

    • routes: All enriched and sorted routes

    • routeId: Cached route identifier



Feature
Description

Modular Provider Architecture

Easy to add new Bridges/DEXes via config

Chain-Agnostic Routing

No dependency on specific networks

Real-Time Quote API

Supports full transparency & caching

Cross-Chain Operations

Seamless support for chained actions (swap + bridge)

Extensible Standards Support

Built for Chain Abstraction and Interop futures



List of added services:

Service Name
Integration Type
Active

LiFi

Bridge, Dex

Enso

Dex

ODOS

Dex

Zero-x

Dex

Across

Bridge, Dex

DeBridge

Bridge, Dex

Paraswap

Dex

Synapse

Bridge, Dex


The list of the main routes that we use

Get allowance from service

Get approve Tx from service

Get Quote from service

Get Tx from service

Route Selection Logic

How It Works

Highlights

Deployment & Audits

All deployed contract addresses are listed in the section. Each third-party integration includes a link to its audit, ensuring transparency and security.

🔎
⚙️
⚙️
📜
getAllowance
getApproveTx
getQuote
getTx
Deployment Addresses
🧠
💡
🧩
ZAPs