Integration Grants Application '26: Conflux DevKit

Application Introduction

1. Project Name

Conflux DevKit — an open-source, batteries-included Conflux developer stack delivered as a devcontainer with AI-powered tooling. The public repository is published as devkit-workspace.

2. Problem Statement

Building on Conflux requires simultaneously managing a local node, funded accounts, smart contract toolchains, wallet integration, DEX testing infrastructure, and (increasingly) AI agent workflows. Each component has its own documentation, CLI, and failure modes. A developer evaluating Conflux for the first time typically spends 4–8 hours on infrastructure setup before writing a single line of product code.

This friction is measurably hurting adoption:

  • Hackathon participants lose their first sprint to setup instead of building
  • Web2 developers evaluating Conflux give up before reaching “hello world”
  • AI-assisted development teams cannot point their agents at Conflux without custom integration work

3. Proposed Solution

Conflux DevKit packages the entire local development stack into a single devcontainer — a portable, reproducible environment that starts in under 2 minutes on any devcontainer-capable host (local IDEs, GitHub Codespaces, cloud dev environments). The stack includes:

  • Local Conflux node (eSpace + Core Space) with 10 pre-funded genesis accounts
  • Editor extension with status bar, command palette, and contract tree views
  • MCP server with 30+ typed tools for AI agent integration (any MCP-compatible assistant)
  • Local Uniswap V2-compatible DEX with 15 seeded token pairs at real market prices
  • Three scaffold templates for immediate project bootstrapping

4. Alignment with Conflux Network

Benefit to the Conflux Ecosystem:

  • Reduces time-to-first-transaction for every new Conflux developer
  • Positions Conflux as the most AI-friendly EVM-compatible chain (first MCP-native dev environment)
  • Provides a reference architecture for MCP + blockchain tooling
  • Serves as an integration platform for other community projects (ChainBrawler, CAS, etc.)

Economic benefit:

  • Lower developer onboarding friction → more projects building on Conflux → more on-chain transactions
  • Scaffold templates generate projects that deploy to Conflux by default
  • Local DEX testing leads to mainnet DEX usage as developers graduate from local to testnet to mainnet

5. Competitive Edge

  • Only local Conflux development environment with integrated AI tooling (MCP)
  • Only devcontainer that includes both eSpace and Core Space with cross-space bridge
  • Only scaffold system that generates Conflux-native projects with pre-wired infrastructure
  • Runs on any devcontainer-capable environment — not locked to a single editor
  • Built by a Conflux ambassador with years of practical tooling experience in the ecosystem

6. Project Links

7. Grant Recipient Wallet Address

  • eSpace address: 0x31b9eA2985A8EF36735bC9b81BdB975628820C00

8. Incorporation Status

Not incorporated. This is an independent open-source project maintained by a Conflux ambassador and community contributor.


Technical Introduction

Problem Reference

See Problem Statement above. Existing solutions are fragmented:

  • Hardhat/Foundry alone — handles contract compilation but not node management, wallet setup, AI tooling, or DEX infrastructure
  • Remix — browser-based, no local node, no AI integration, no devcontainer
  • Manual Docker setup — requires significant DevOps knowledge; no one has packaged the full Conflux stack with AI tools into a portable devcontainer before

Purpose of the System

Provide a complete, reproducible, AI-addressable local Conflux development environment that works out of the box inside any devcontainer-capable host.

Scope

  • Local development only (not a hosted service)
  • Devcontainer as primary distribution format (runs on any compatible IDE or cloud host)
  • MCP as the AI integration standard (adopted by GitHub Copilot, Claude, and growing ecosystem)

Objectives and Success Criteria

Objective Success Criterion
Zero-config setup Developer goes from git clone + reopen in container to a running node in < 2 minutes
AI-native tooling 30+ MCP tools covering full development lifecycle
Template system 3+ scaffold templates generating working Conflux projects
Community adoption 50+ active developers using the platform within 6 months
Ecosystem integration 2+ external projects integrated as templates/modules within 12 months

Definitions, Acronyms, and Abbreviations

  • MCP — Model Context Protocol, the tool interface used by AI assistants to call structured developer operations
  • DEX — Decentralized exchange
  • eSpace — Conflux’s EVM-compatible execution environment
  • Core Space — Conflux’s native execution environment
  • SIWE — Sign-In with Ethereum style wallet-authentication flow supported by shared UI components
  • Devcontainer — A containerized development environment format supported by VS Code, Codespaces, and similar hosts

References


Technical Proposal

Functional Overview

Core packages (pnpm monorepo):

Package Purpose
devkit-backend Express API server, process manager for node + services
mcp-server MCP v1 server exposing 30+ typed tools
vscode-extension Editor extension (status bar, commands, tree views)
contracts Solidity contracts + Hardhat toolchain
scaffold-cli CLI for generating new projects from templates
ui-shared Shared React components (wallet connect, SIWE, etc.)
conflux-wallet Fluent Wallet connector package
shared Common utilities and types
template-core Template engine for scaffold system
devkit-base Docker base image with Conflux node + toolchains

DEX stack:

  • Uniswap V2 factory + router + WETH9, deployed to local eSpace
  • 15 seeded token pairs with prices pulled from CoinGecko
  • Full React UI for swap/pool operations

Licensing: Apache 2.0 — fully open source, no proprietary components.

Non-Functional Requirements

  • Usability: One-command setup; no blockchain knowledge required for basic usage
  • Reliability: Persistent chain state across container restarts; deterministic genesis accounts
  • Performance: Container start < 2 minutes; MCP tool response < 500ms
  • Implementation: pnpm monorepo, typed package boundaries, reproducible devcontainer builds, and automated contract artifact generation
  • User interface: Dedicated editor extension views plus a local React DEX UI for swap/pool workflows
  • Security: Typed ABI calls only (no raw calldata injection); input validation at HTTP boundary; OpenZeppelin contract standards; encrypted keystore support

Total Budget

Grant Request: Technical Validation & Promotion

This application prioritizes technical validation, contract audit, and security analysis over general product funding.

Primary grant amount requested: $2,000 for a scoped third-party contract audit and security analysis.

Extended six-month support estimate: Up to $3,360 if documentation hosting, CI/CD support, and community activation costs are included.

The project is currently community-funded through donations and volunteer development time. At this stage, the most valuable support from the Conflux Foundation is:

  1. Technical validation — review and endorsement by the Conflux core engineering team
  2. Security scope — contract audit and security analysis of the local stack, contract interactions, and AI-facing surfaces
  3. Official listing — recognition as a recommended developer tool in Conflux documentation
  4. Promotion — visibility through official Conflux channels (docs, social media, developer events)
  5. Community access — introduction to other Conflux ecosystem projects for integration partnerships

Budget estimate and audit-scope note:

The current codebase has a relatively small Solidity surface, so $2,000 is a reasonable estimate for a scoped review of the custom contract layer and the highest-risk integration paths. It should not be interpreted as a guarantee of a comprehensive full-stack audit covering every contract, backend service, editor integration, and AI-facing surface in depth. This estimate can be revised upward or downward if the final scope changes or if audit partnerships become available through the Conflux grants committee.

Optional financial support (if available):

Item Estimated Cost Purpose
Documentation hosting $10/month Small dedicated VPS for project docs and tutorials
CI/CD infrastructure $50/month Automated testing and Docker image builds
Security review $2,000 (one-time) Professional review of the contract surface, MCP server, and AI-assisted contract interactions
Community event $1,000 First cfxdevkit bounty/mini-hackathon prizes
Total (first 6 months) $3,360

The project will continue development regardless of funding decisions — the goal is to earn ecosystem trust through consistent, high-quality contributions.


Development Roadmap

Phase 1 — Foundation (Completed :white_check_mark:)

Deliverables: Hackathon submission

  • Devcontainer with local Conflux node (eSpace + Core Space)
  • Editor extension with status bar, command palette, contract tree
  • MCP server with 30+ tools
  • Local Uniswap V2 DEX with 15 seeded pairs
  • Three scaffold templates
  • Project website (cfxdevkit.org)
  • Demo video, Electric Capital PR, and social submission assets completed

Phase 2 — Stabilization & Community (Months 1–6)

Milestone 2.1 — Public Launch (Month 1)

  • Devcontainer image published to container registry
  • Editor extension published to marketplace
  • Complete documentation site
  • Funding requested: $0

Milestone 2.2 — Template Ecosystem (Month 3)

  • Scaffold CLI interactive wizard
  • Hardhat plugin for direct devkit integration
  • 20+ projects bootstrapped with templates
  • Funding requested: $0

Milestone 2.3 — Community Building (Month 6)

  • First cfxdevkit bounty or mini-hackathon
  • Community donation infrastructure live
  • Integration plan defined for the first external project (ChainBrawler or CAS)
  • Note: ChainBrawler and CAS would likely apply for separate grant requests once their implementation plans are defined
  • Funding requested: $1,000 (event prizes)

Phase 3 — Ecosystem Growth (Months 6–12)

Milestone 3.1 — Project Integration (Month 9)

  • ChainBrawler or CAS integration pilot running on the DevKit stack
  • Separate grant requests for ChainBrawler and CAS evaluated only after their individual scopes are defined
  • GitHub Action for CI deployment
  • Funding requested: $0

Milestone 3.2 — Maturity (Month 12)

  • 3+ community projects integrated
  • Active contributor base
  • Contract audit and security analysis completed
  • Evaluate tokenization if warranted
  • Funding requested: $2,000 (security review) + $300 (CI hosting)

Team

SP (Solo Developer / Conflux Ambassador)

  • Roles: Architecture, backend, frontend, smart contracts, DevOps, MCP server, editor extension, documentation
  • Relevant experience:
    • 20+ years across systems administration, network/security, DevOps, system integration, and full-stack software delivery
    • Recent focus includes Web2/Web3 architecture refactoring, CI/CD integration, smart contract development, review, and optimization
    • Senior systems integration background spanning enterprise infrastructure, AWS-based data pipelines, automation, monitoring, and production troubleshooting
    • Conflux ambassador who built multiple developer tools under cfxdevkit.org; this project unifies and productizes that work into a single developer stack
  • GitHub: cfxdevkit/devkit-workspace
  • X: @CFXDevkit
  • Discord: spcfxda

Terms of Use

I agree to all of the following terms of use in applying to a Conflux Ecosystem Grant:

  1. I have read and understood the Conflux Grants Ecosystem Overview
  2. I have read about and understood that the Conflux Technical Grants are subject to a No-Sale rule
  3. I agree to provide KYC information to the Conflux Foundation for the sake of overall ecosystem security
  4. I understand that I will be required to follow public grant reporting requirements

Dear Conflux DevKit Team,

Thank you for submitting your application for the DevKit grant. I will review it in detail and follow up with any questions. You can expect to hear back from us on a decision timeline within the coming month.

Thanks again for your interest and for contributing to the Conflux ecosystem.

Best regards,

Máté
Head of Grants | Conflux Network