• © Goverland Inc. 2026
  • Privacy Policy
  • Terms of Use
CoW DAO GrantsCoW DAO Grantsby0x9B2FB7a8d227cDaA8002f80e8c8A99a19Bb1b969tantodefi.eth

[RETRO ROUND] CCXT Connector for CoW SDK

Voting ended 3 months agoFailed

Grant Title: CCXT Connector for CoW SDK

Author: Tantodefi.eth & Bhavya Gor
Date: October 26, 2025
Category: Developer Tooling
Funding Requested: 15,000 xDAI + 15,000 vested COW tokens
Gnosis Chain Address: [Insert your Gnosis Chain address here, e.g., 0x123...456]
GitHub: Tantodefi | Bhavya Gor
Contact: tantodefi.eth@proton.me | bhavyagor12@gmail.com

About You

We are Tantodefi.eth , experienced developers specializing in blockchain integrations, API development, and trading systems. We've contributed to open-source DeFi projects, including smart contracts and developer resources for platforms like BUIDLGuidl's Scaffold-ETH. Our expertise lies in creating accessible tools for DeFi ecosystems, with a focus on standardized APIs for development.

Project Overview

This proposal seeks funding from CoW DAO's retroactive funding round to develop a CCXT library connector for the CoW SDK, enabling seamless integration of CoW Protocol's intent-based trading into the widely used CCXT library. This will allow algorithmic traders to leverage CoW's MEV-protected executions through a unified API, reducing integration barriers and driving protocol adoption. The project builds on prior SDK efforts, such as the community-built Python SDK1, to enhance developer accessibility and ecosystem growth.

For full details, including feasibility, implementation, and impact metrics, see our Detailed Proposal.

Team

  • Tantodefi.eth (Fullstack Developer): Blockchain engineer with expertise in DeFi integrations and algorithmic trading. Contributed exchange adapters and participated in BUIDLGuidl hackathons. GitHub: tantodefi, X: @tantodefi.
  • Bhavya Gor (Fullstack. Developer): Full-stack developer focused on API wrappers and Web3 testing. Built TypeScript/Python SDKs and DeFi tools at BUIDLGuidl. GitHub: bhavyagor12, X: @bhavya_gor.

Project Details

Motivation and Rationale

The CoW Protocol's intent-based architecture, powered by the CoW SDK2, offers superior executions with MEV protection and gas efficiency. However, algorithmic traders using CCXT—the standard for 100+ exchanges—face integration hurdles. This connector will map CoW SDK functions (e.g., quoting, order management) to CCXT's API, enabling plug-and-play usage for trading bots and strategies.

Key Benefits:

  • Ease of Integration: Add CoW as a CCXT "exchange" with methods like createOrder and fetchOrder.
  • Increased Usage: Enable algo traders to route orders to CoW, boosting TVL and solver activity.
  • Differentiation: Custom quote comparators highlight CoW's advantages (e.g., 1-5% execution savings) over DEXs like Uniswap.
  • Ecosystem Growth: Open-source CCXT contribution3 attracts builders for AI agents and automated trading.

Feasibility

CoW's batch auction model differs from order-book systems, but CCXT supports partial implementations. We assessed:

  • Compatibility: Map async quoting/orders via polling, inspired by DEX connectors (e.g., Uniswap).
  • Async Handling: SDK-based polling with configurable intervals.
  • Rate Limiting: Mirror SDK logic (10-20 quotes/min) to prevent IP blocks.
  • Missing Features: Disable order books/tickers; synthesize symbols from metadata.
  • Enhancements: Add compareQuoteWithOtherExchanges for multi-venue benchmarking.

This ensures 70-80% CCXT coverage, focusing on trading, similar to prior SDK integrations1.

Implementation

We will implement a TypeScript-derived CCXT class using CoW SDK:

  • Core: Quoting (TradingSdk.getQuote), orders (OrderBookApi.postOrder/getOrder/cancel), trades (OrderBookApi.getTrades).
  • Limitations: Polling for updates; RPC for balances; disable market data.
  • Extras: Quote comparator and risk management bot example.

Milestones

The project spans 8 weeks (October 26 - December 21, 2025):

Milestone Description Timeline Deliverable Verification
1: Research and Setup Analyze SDK/CCXT; review DEX connectors; prototype class. Oct 26 - Nov 2 (Week 1) Feasibility doc, prototype. GitHub commit.
2: Core Implementation Build order lifecycle, polling, rate limiting. Nov 3 - Nov 16 (Weeks 2-3) Functional connector, basic tests. 80% test coverage.
3: Advanced Features and Testing Add comparator/bot; tests/docs. Nov 17 - Dec 7 (Weeks 4-6) Beta version, docs. 90%+ test coverage; draft README.
4: Submission and Review Submit PR to CCXT; iterate. Dec 8 - Dec 21 (Weeks 7-8) Merged PR, usage guide. CCXT merge; metrics report.

Budget

Total: 15,000 xDAI + 15,000 vested COW (12-month vesting).

Category Amount (xDAI) Justification
Development 10,000 200 hours @ $50/hr (research, coding).
Testing/Documentation 3,000 60 hours (polling, docs).
Community Engagement 2,000 Feedback, PR reviews, features.
Vested COW Tokens 15,000 Long-term alignment.

Prefer xDAI for liquidity.

Impact and Metrics

  • Quantitative: CCXT downloads (npm/GitHub); CoW tx uplift (unique tags); comparator savings (1-5%). Target: 10-20% algo volume growth in 6 months.
  • Qualitative: Forum feedback; GitHub stars/forks; developer contributions.
  • Verification: Open-source GitHub; on-chain analytics.

This builds on SDK grants1, expanding CoW's algo trading reach.

Additional Notes

We welcome community feedback to refine this proposal. The project leverages insights from the Python SDK grant4 for robust integration practices.

Full Proposal: HackMD

CoW DAO Grant Agreement

By submitting this proposal, we agree to adhere to the terms outlined in the CoW DAO Grant Agreement. We commit to transparency, timely delivery of milestones, and open-source contributions to maximize value for the CoW ecosystem.

We look forward to your feedback!

Footnotes

  1. Detailed Proposal ↩ ↩2 ↩3

  2. CoW SDK GitHub ↩

  3. CCXT Contributing ↩

  4. Community-built Python SDK Grant ↩

Off-Chain Vote

For
3 HERD100%
Against
0 HERD0%
Abstain
0 HERD0%
Quorum:75%
Download mobile app to vote

Discussion

CoW DAO Grants[RETRO ROUND] CCXT Connector for CoW SDK

Timeline

Oct 27, 2025Proposal created
Oct 27, 2025Proposal vote started
Oct 30, 2025Proposal vote ended
Nov 04, 2025Proposal updated