Feature Requests

I would like to request the addition of the Kaspa Mainnet into 0x.

Currently, the maker of a limit order is the always the recipient of the tokens received from the taker. It would be great if it was possible to set a recipient address to override this default behavior. This way, you can get the tokens where you need them to be a block faster and without paying additional gas for the transfer.

I would like to request the addition of support for the Canto blockchain in the 0x Swap and Price API. Canto is a permissionless, general-purpose blockchain running the EVM. It was specifically designed to fulfil the promise of decentralized finance (DeFi) by creating new systems that are accessible, transparent, decentralized, and free. Key Features: Uniswap V2 DEX: Canto has a robust DEX built on the Uniswap V2 protocol, which is widely recognised and trusted in the DeFi community. Solidly for Stable Pairs: For stable pairs, Canto integrates Solidly, providing efficient and reliable trading mechanisms for stable assets. Ambient Pools: The Canto ecosystem also supports ambient pools, further enhancing liquidity and trading efficiency across various asset pairs.

weETHs is routed on 0x protocol however the route is not optimal. There is liquidity on Curve for the token but 0x is not taking it into account. Can you please add that pool aswell? weETHs: 0x917cee801a67f933f2e6b33fc0cd1ed2d5909d88 Curve Pool: 0xb92b054b9cc33685e7f8c3f85177c4b6dc061391

There is some activity taking place and it would be great to support it

Evmos is the EVM of the Cosmos. Its EVM Extensions set it apart from other blockchains, allowing solidity smart contracts to interact cross-chain with any of 100+ IBC-connected chains. One of our ecosystem partners, Revert Finance, has requested 0x support on Evmos as they heavily rely on it for other chains they support. With Evmos' closer alignment to the Cosmos Hub sparking the interest of EVM blue chips & the evmOS ecosystem of chains expanding, most notably to Ripple's sidechain, 0x's APIs may see heavy usage on Evmos with the entire ecosystem able to tap into it.

Ability to request quotes for multiple swaps in a single batch.

Add optional support for receiving swapped tokens on other wallets. Example: Swap A to B, but receive it on another wallet rather than the one sending the tx.

Can we have buyTokenToEthRate and sellTokenToEthRate field in tx-relay price response just like what we have in normal swap price response?

DEX liquidity comes from users providing their assets to liquidity pools on platforms like Uniswap or SushiSwap. https://www.bsetec.com/blockchain-development-company