Gateway Connectors for Decentralized Exchange Trading and Liquidity
Summary
Gateway is middleware that lets Hummingbot interact with blockchain protocols through a standard interface. Its decentralized exchange connectors maintain connections to automated market makers and other protocols, integrate with their JavaScript software development kits, and expose REST endpoints for trading and liquidity provision. The document explains how this shared interface supports connector development across different chains and protocol types.
It also outlines maintenance and governance: the Hummingbot Foundation maintains reference connectors, community developers can work on fixes through bounties, and governance proposals can affect maintenance, removals, or supported networks. New connectors are contributed with code and proposed through the governance process. A table lists supported connectors and their chain, migration status, and connector types. The document notes that an ongoing refactor means some connectors remain in a legacy architecture or have not yet migrated. It describes infrastructure and contribution processes, not trading performance, execution quality, or protocol risks.
Key ideas
- Gateway standardizes how Hummingbot connects to blockchain trading and liquidity protocols.
- Connectors integrate protocol software development kits and expose REST endpoints.
- Reference connector maintenance involves Foundation work and community bounties.
- Governance proposals can shape connector support and the networks Gateway serves.
- An ongoing refactor means connector availability varies between legacy and newer architectures.
Tags
Full text
# What are Gateway DEX Connectors?
## What are Gateway DEX Connectors?
Gateway is API middleware that enables Hummingbot to send and receive data from different blockchain protocols and provides a standard interface for community developers to add connectors for common DeFi protocols.
Gateway connectors establish and maintain connections to automated market maker (AMM) DEXs and other protocols on various blockchain networks, interfaces with their Javascript SDKs, and exposes standard REST API endpoints for trading and liquidity provision-related actions on these DEXs.
See [Gateway](../../gateway/index.md) for more information.
## Gateway DEX Connector Maintenance and Governance
Like other connectors, Gateway DEX connectors require ongoing maintenance: fixing bugs, addressing user issues, and keeping up with updates to both the exchange/blockchain API as well as improvements to the Hummingbot connector standard.
Hummingbot Foundation maintains certain reference connectors as the standard and utilizes a community-based maintenance process. We assign [Bounties](../../bounties/index.md) to community developers to upgrade and fix bugs for each exchange's connectors in the codebase.
The community can propose changes to connector maintenance, bounty allocations, and connector removals through [Hummingbot Governance Proposals (HGP)](../../about/proposals.md). This process also determines which [blockchains and networks](../../gateway/chains.md) that Gateway supports.
See the **Connector Pots** tab in [HBOT Tracker](https://docs.google.com/spreadsheets/d/1UNAumPMnXfsghAAXrfKkPGRH9QlC8k7Cu1FGQVL1t0M/edit?usp=sharing) for the current allocations for each exchange.
## Adding New Gateway DEX Connectors
New Gateway connectors may be contributed by community members via [Hummingbot Governance Proposals (HGP)](../../about/proposals.md), which require a pull request with the connector code to the Hummingbot Gateway Github repo, along with a minimum HBOT balance to create.
If you're interested in contributing a new Gateway DEX connector, see the [DEX Connectors](../../gateway/connectors.md#building-custom-connectors) documentation which provides guidance on implementing the standardized trading types and creating compatible connectors.
## Current Gateway DEX Connectors
!!! note
Gateway is currently undergoing a large multi-release codebase refactoring, approved in proposal [NCP-22](https://snapshot.box/#/s:hbot-ncp.eth/proposal/0x5cc3540ee219787d5c842bc1ccdb11aab46203bb7f0be658b6b40858501a8e4c). During this refactoring process, not all connectors are available in the new version, as they are being gradually migrated from the legacy architecture.
Here are the Gateway connectors currently in the codebase.
| Exchange | Chain Type | Legacy | New | Connector Types | Guide |
|----------|------------|--------|-----|----------------|-------|
| [Jupiter](jupiter.md) | `solana` | | ✓ | `swap` | |
| [Meteora](meteora.md) | `solana` | | ✓ | `clmm` | |
| [Raydium](raydium.md) | `solana` | | ✓ | `clmm`, `amm` | |
| [Balancer](balancer.md) | `ethereum` | ✓ | | `amm` | |
| [Curve](curve.md) | `ethereum` | ✓ | | `amm` | |
| [ETCSwap](etcSwap.md) | `ethereum` | ✓ | | `amm`, `amm_lp` | |
| [Pancakeswap](pancakeswap.md) | `binance-smart-chain` | ✓ | | `amm`, `amm_lp` | |
| [Quickswap](quickswap.md) | `polygon` | ✓ | | `amm` | |
| [Sushiswap](sushiswap.md) | `ethereum` | ✓ | | `amm` | |
| [TraderJoe](traderjoe.md) | `avalanche` | ✓ | | `amm` | |
| [Uniswap](uniswap.md) | `ethereum` | ✓ | | `amm`, `amm_lp` | |Shown in full with attribution under the source's licence. Licence: Apache-2.0
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.