Swap Venue Requirements

​

Background

• DEXes often want Skip Go API to add support for their DEX as a swapping venue because the API powers cross-chain swaps + transfers in all the major cosmos and ethereum wallets (MM, Keplr, IBC Wallet, Metamask Snap) and cross-chain DEX aggregation to many popular defi aggregator and dapp frontends (e.g. Stargaze). As a result, being added to the Skip Go API instantly offers distribution across the interchain for your DEX
• The Skip Go API’s swapping system is currently built in CosmWasm and can support swapping assets on Cosmos SDK modules (ex: Osmosis Poolmanager) and other CosmWasm contracts (ex: Astroport DEX) that can be queried and executed by Skip Go API’s CosmWasm contracts. The API support’s swapping EVM dexes. (Uniswap v2/v3, Aerodrome, Velodrome).

​

Chain Requirements

1. The chain must already be supported by the Skip Go API
   1. Use the /info/chains endpoint to query a list of actively supported chains: /v2/info/chains
   2. If your chain is not already supported, follow the instructions in Chain Support Requirements to request support
   3. This is a pre-requisite
2. CosmWasm Support
3. IBC support
4. ibc-hooks Support (Check out our blog post about ibc-hooks)

​

Module / Contract Requirements

​

General

1. The module / contract must be able to be called by the Skip Go API’s CosmWasm contracts. For Cosmos SDK modules, this will require the module queries described below to be whitelisted and queryable by CosmWasm contracts (see Osmosis for an example).

​

Execution Messages

1. Supports a “Swap Exact In” method where a user specifies an input asset and path to swap, and the module / contract swaps the given user asset to the user’s desired output asset and sends it to the user (see Osmosis for a module example, or Astroport for a contract example).
   1. Inputs into the swap:
      1. An asset (Native cosmos coin or CW20 token, incl. denom and amount)
      2. A path (can be a single pool, or multiple pools if designed like a router)
   2. Outputs of the swap:
      1. An asset
2. NICE TO HAVE (Optional): Supports a “Swap Exact Out” method where a user specifies a desired output asset, a path to swap through to achieve that asset, and a maximum amount of an input asset to swap, and the module / contracts swaps in the exact input asset needed to acquire the specified output asset and sends it to the user (see Osmosis for a module example).

​

Query Messages

3. Exposes a “Swap Exact In Simulation” method where a user can put the inputs that would be used in the “Swap Exact In” execution method, and gets a response from the query that specifies the asset they would receive if executing the method (see Osmosis for a module example, or Astroport for a contract example).
4. Exposes a “Swap Exact Out Simulation” method where a user can input the asset desired and a given pool / path, and the query returns the asset required to swap in to receive the output asset desired (see Osmosis for a module example, or Astroport for a contract example).

​

Getting Skip to Add Support for Your DEX

• Swap volume
• Liquidity
• Quality and clarity of technical documentation

​

Required Submission Info

​

General Information

• Team Name
• Contact Name
• Contact Telegram
• Team Website
• Swapping Venue Name (if different from team name)
• Swapping Venue Website
• Swapping Venue Documentation

​

Additional DEX Information

• What kind of venue is it?
  e.g., AMM, CLOB, staking protocol
• If an AMM, what pricing curves are supported?
  • Include documentation
  • Describe any non-standard logic
• How are fees calculated?
  • Pool fees, maker/taker fees, etc.
  • Include documentation and note any non-standard mechanisms
• Which tokens typically offer better pricing on this venue?
• Which tokens or token pairs are the most popular