For DEXs/Aggregators/Solvers

​

Eligibility for Integration

​

As a solver

Solvers need to have the same user experience as DEXs and have similar flow to already integrated DEXs

​

As a DEX or DEX aggregator

• Architectural Limitations

Currently, we do not support integrations for limit orders, order books, RFQ, or intent execution due to limitations in our backend and smart contract architecture. There is no timeline for adding support for these features.

• Existing Aggregator Integrations

If your project is already integrated with other aggregators we support (e.g., 1inch, 0x, Paraswap, DODO, OpenOcean), we are unlikely to integrate as your liquidity source is already a part of our routing.

​

DEX Integration Requirements

​

UniswapV2 forks

We can efficiently integrate UniswapV2 and V3 forks within a short period of time. However, to proceed, the following information must be provided for each chain on which your DEX operates:

{
    name: 'Honeyswap',
    chainId: 100,
    webUrl: 'https://app.honeyswap.org/',
    tokenlistUrl: 'https://tokens.honeyswap.org/',
    routerAddress: '0x1C232F01118CB8B424793ae03F870aa7D0ac7f77',
    factoryAddress: '0xA818b4F111Ccac7AA31D0BCc0806d64F2E0737D7',
    initCodeHash: '0x3f88503e8580ab941773b59034fb4b2a63e86dbc031b3633a925533ad3ed2b93',
    baseTokens: [
      {
        address: '0x71850b7e9ee3f13ab46d67167341e4bdc905eef9',
        symbol: 'HNY',
        decimals: 18,,
      },
      ...
    ],
  },

Your logo: At least 300x300px and with a white or transparent background.

​

Non-UniswapV2 Forks

If your DEX is not a UniswapV2 clone, an API connection is required. Provide documentation and ensure the following technical standards:

• The ability to handle at least 1 request per second.

• You have legible error messages.

• Your avg. API response time is < 1 second

Furthermore:

• Maintain a support channel and stay responsive throughout the integration process and beyond.

• Stable API without breaking changes, with at least 3 weeks’ notice for updates