Integration Grants Application ‘26: VerifyFlow Conflux eSpace Deploy & Verify Preflight

#1

Application Introduction

Project name

VerifyFlow — Conflux eSpace Deploy & Verify Preflight

Problem statement

Developers deploying Solidity contracts to Conflux eSpace repeatedly hit avoidable failures that waste gas, time, and momentum:

  • Wrong chain ID — MetaMask or Hardhat pointed at the wrong network (eSpace mainnet 1030 vs testnet 71)
  • RPC misconfiguration — unreachable endpoints, elevated latency, or mismatched net_version
  • ConfluxScan verify rejection — compiler settings mismatch, missing fields, or known quirks such as evmVersion: "default" being rejected (documented in conflux-skills #5)
  • Post-deploy discovery — teams only learn verify will fail after broadcasting a deploy transaction

ConfluxScan is an explorer (post-hoc verification). Hardhat and generic Ethereum tooling are not Conflux-aware (chain IDs, ConfluxScan API fields, eSpace-specific verify rules). There is no neutral, open-source preflight layer that validates RPC + verify payload before deploy.

Proposed solution

VerifyFlow is an open-source preflight toolkit for Conflux eSpace:

  1. @verifyflow/core — doctor engine: RPC reachability, chain ID, gas/fee data, ConfluxScan API health, verify-payload lint
  2. REST API — embed checks in CI or custom tooling (/api/doctor, /api/lint-payload)
  3. Web dashboard — visual preflight rail, Monaco JSON editor, Ready/Blocked gate
  4. CLI (M0 completion) + Hardhat plugin + GitHub Action (M1/M2) — standard Solidity workflow integration

Live prototype (M0): https://conflux-e-space-deploy-verify-prefl-gamma.vercel.app/

Hosting plan: Vercel hosts the M0 grant demo and API during prototype review. After grant approval, M2 delivers migration to a standalone official website on a dedicated custom domain — dashboard, docs, and public API endpoints move off the Vercel preview URL to a permanent project home.

Alignment with Conflux Network

Conflux grant goal How VerifyFlow helps
Developer tooling & infrastructure Direct hit on official tooling wishlist — pre-deploy validation for eSpace
More developers building on Conflux Lowers onboarding friction for Ethereum devs redeploying to eSpace
Network liveliness Fewer abandoned deploy attempts; faster successful mainnet launches
Diverse ecosystem More verified contracts → more DeFi, PayFi, and dApp protocols live on eSpace

VerifyFlow targets eSpace (EVM-compatible), the primary path for Ethereum developers porting to Conflux.

Benefit to the Conflux ecosystem

  • Onboarding accelerator — teams catch misconfig before first mainnet deploy
  • Open-source reference — MIT-licensed toolkit, docs, and integration examples other tutorials can link
  • CI-ready — non-zero CLI exit codes and GitHub Action gates for eSpace repos
  • Knowledge capture — encodes ConfluxScan verify quirks (e.g. evmVersion) so new builders don’t rediscover them
  • Complements existing infra — works alongside ConfluxScan, Fluent Wallet, and official RPC docs; does not duplicate them

Target KPIs (90 days post-grant):

  • ≥5 eSpace projects adopt VerifyFlow in CI or README
  • ≥3 tutorial repos reference preflight checks
  • ≥500 dashboard/API preflight runs (opt-in telemetry or documented usage)
  • ≥1 community tutorial or forum post citing VerifyFlow

Economic benefit (on-chain activity)

VerifyFlow does not custody funds or route payments. Its economic impact is indirect but measurable:

Mechanism On-chain effect
Fewer failed deploy cycles More successful contract deployment transactions on eSpace
Faster verify success More verified contracts on mainnet/testnet → higher trust for DeFi/PayFi protocols
CI gates before mainnet Teams ship to eSpace mainnet sooner → more txs from live dApps
Reduced RPC/verify friction Lower abandonment rate for teams evaluating Conflux vs other EVM chains

Proposed numeric targets (6 months):

  • Contribute to ≥50 additional verified contracts on eSpace (via teams using preflight)
  • Support ≥100 successful deploy transactions that passed preflight first
  • Enable ≥5 new eSpace project launches that document VerifyFlow in their deploy workflow

Competitive edge

Existing solution Limitation VerifyFlow difference
ConfluxScan Post-deploy verify only Pre-deploy CI gate + payload lint
Hardhat / Foundry Generic EVM, not Conflux-specific Built for chainId 71/1030 + ConfluxScan quirks
FluxPay Payment checkout SDK Deploy/verify QA — different layer
Conflux Paymaster SDK Gas abstraction Preflight validation — complementary
Quantir DeFi risk intelligence Developer preflight — not protocol risk scoring
nodes.garden (declined) Node hosting SaaS Integrator QA tooling — not infrastructure hosting
CompareNodes / wallet failover RPC benchmarking inside wallets Neutral preflight for deploy + verify workflows

VerifyFlow is the first dedicated open-source preflight for eSpace deploy-and-verify success.

Links

Resource URL
Live demo (dashboard) https://conflux-e-space-deploy-verify-prefl-gamma.vercel.app/
Usage guide https://conflux-e-space-deploy-verify-prefl-gamma.vercel.app/usage
Milestones https://conflux-e-space-deploy-verify-prefl-gamma.vercel.app/milestones
Twitter / X https://x.com/panagot
LinkedIn https://www.linkedin.com/in/panagiotis-pollis-33509831/
Telegram @panagot
eSpace docs https://doc.confluxnetwork.org/docs/espace/DeveloperQuickstart
ConfluxScan API https://doc.confluxnetwork.org/docs/espace/build/infrastructure/confluxscan-api/
conflux-skills #5 https://github.com/conflux-fans/conflux-skills/issues/5

Conflux eSpace grant recipient wallet address

0xE80266B8D76A95BF0233203470C5240E68AD0567

Are you an incorporated startup?

No. Solo independent developer / open-source maintainer.

Technical Introduction

Problem (recap)

eSpace is marketed as EVM-compatible, but production deploys fail on Conflux-specific details: chain IDs (71 / 1030), ConfluxScan verify API field requirements, and documented rejections like evmVersion: "default". Teams waste deploy gas and delay mainnet launches.

Existing solutions & feasibility

Solution Status Gap
ConfluxScan explorer + API Production No pre-deploy validation
Official eSpace docs + RPC list Production Informational only — no automated checks
Hardhat network config Widely used No ConfluxScan verify lint or explorer API probe
conflux-skills #5 Community issue Documents pain; no shipped tooling
VerifyFlow prototype Live on Vercel Proves feasibility — doctor runs end-to-end on testnet

Feasibility: M0 prototype is deployed and functional (~80% complete). Core engine uses ethers v6 against public RPC endpoints; ConfluxScan API probes use documented public endpoints. No secrets or private keys required. Remaining M0 work: CLI packaging and demo assets. M1/M2 (Hardhat plugin, GitHub Action) are standard TypeScript/npm delivery.

Purpose of the system

Provide a single preflight command (verifyflow doctor / API POST /api/doctor) that answers: “Is this eSpace environment ready for deploy and verify?”

Scope

In scope:

  • eSpace testnet (chainId 71) and mainnet (chainId 1030)
  • RPC health, chain ID, gas/fee data, ConfluxScan API reachability
  • ConfluxScan verify JSON lint (compiler, optimizer, evmVersion, source/contract name)
  • CLI, REST API, web dashboard, Hardhat plugin, GitHub Action
  • MIT open-source, 12-month maintenance (M2)

Out of scope:

  • Contract deployment or verification submission (users keep their own keys)
  • Wallet connect, paymaster integration, or payment checkout
  • Core Space (non-EVM) tooling
  • DeFi risk scoring or block explorer features

Objectives & success criteria

Objective Success criterion
Catch RPC/chain misconfig Wrong chainId → BLOCKED with clear message
Catch verify payload errors evmVersion: "default" → FAIL before ConfluxScan submit
CI integration CLI exits non-zero on failure; GitHub Action documented
Developer adoption npm packages published; ≥5 repo integrations in 90 days
Grant completion All M0–M2 deliverables shipped + public completion report

Definitions, acronyms & abbreviations

Term Definition
eSpace Conflux EVM-compatible execution environment
Core Space Conflux native VM space (out of scope)
ConfluxScan Official Conflux block explorer with contract verification API
Preflight Pre-deploy validation run against live infrastructure
Doctor VerifyFlow’s core diagnostic engine (runDoctor)
Verify payload JSON fields submitted to ConfluxScan for contract verification
CFX Conflux native token; grant disbursement currency

References

  1. Conflux eSpace Developer Quickstart — https://doc.confluxnetwork.org/docs/espace/DeveloperQuickstart
  2. Conflux RPC Providers — https://doc.confluxnetwork.org/docs/espace/build/infrastructure/RPC-Provider/
  3. ConfluxScan API documentation — https://doc.confluxnetwork.org/docs/espace/build/infrastructure/confluxscan-api/
  4. conflux-skills issue #5 — https://github.com/conflux-fans/conflux-skills/issues/5
  5. Conflux Integration Grants Overview — CONFLUX INTEGRATION GRANTS OVERVIEW

Technical Proposal

Functional overview

VerifyFlow runs a doctor pipeline against a selected network (testnet | mainnet) and optional verify payload:

User input (network, RPC URL, verify JSON)
↓
@verifyflow/core — runDoctor()

  1. RPC reachability + latency
  2. Chain ID validation (71 / 1030)
  3. Gas / fee data availability
  4. ConfluxScan API health probe
  5. Verify payload lint (if provided)
    ↓
    DoctorReport { ready, summary, checks[] }
    → CLI (exit 0 / 1)
    → REST API (JSON)
    → Dashboard (Preflight Rail UI)

Core checks (implemented in M0):

  • checkRpcReachability — block number, chainId, latency
  • checkGasAndFeeData — gasPrice availability
  • checkExplorerApi — ConfluxScan API reachability
  • lintVerifyPayload — compiler version, evmVersion, optimizer, source/contract name

Core system elements

Component Role
@verifyflow/core Shared doctor engine (TypeScript, ethers v6)
web/api/* Vercel serverless routes
web/ dashboard React UI — preflight rail, Monaco editor, results stream
CLI (verifyflow doctor) Terminal interface, non-zero exit on BLOCKED
@verifyflow/hardhat (M1) hardhat verifyflow:doctor task + pre-deploy hook
verifyflow/action (M2) GitHub Action for PR/deploy workflow gates
Official docs site (M2) Usage guides mirroring CLI + API flows

Legal / licensing

  • License: MIT (permissive open source)
  • No token sale — tooling only; complies with Integration Grant No-Sale rule
  • No custody — VerifyFlow never holds user funds or private keys
  • Third-party APIs — uses public Conflux RPC and ConfluxScan endpoints per their terms
  • Telemetry (M2): opt-in, privacy-preserving aggregate metrics only

Non-functional requirements

Usability

  • Dashboard: single-screen preflight with clear Ready/Blocked gate
  • Tooltips on network, RPC, payload fields
  • CLI: one command (verifyflow doctor) with human-readable check output
  • Docs: copy-paste examples for Hardhat, curl, GitHub Action

Reliability

  • Graceful degradation: explorer API warn (not hard fail) when API is down but RPC is healthy
  • 12s timeout on external probes
  • Static network config for ethers providers (no accidental chain drift)

Performance

  • Full doctor run target: < 5 seconds on default public RPC
  • API routes: Vercel serverless, 1024 MB, 30s max duration
  • Lint-only endpoint: < 100ms (no network calls)

Implementation

  • Monorepo: npm workspaces (core + web)
  • TypeScript throughout
  • M0 hosting: Vercel serverless — core/dist copied to web/core-dist/ at build
  • M2 hosting: migrate dashboard, docs, and API from Vercel preview to a standalone official website (custom domain, dedicated deployment — not a temporary demo URL)
  • Unit tests on verify-payload lint rules

User interface

  • React 19 + Vite + Tailwind CSS v4
  • Preflight rail stepper: RPC → Chain → Gas → Explorer → Verify
  • Monaco JSON editor for verify payload
  • Pages: Dashboard, Usage, Milestones
  • Design: Sora + JetBrains Mono, accessible contrast, mobile-responsive layout

Total Budget

Grant size requested

$3,000 USD (paid in CFX per program terms)

Justification

Solo developer delivery across three milestones. Budget covers open-source package development, CI integration, documentation, Vercel hosting, and 12-month maintenance — no salaries, marketing spend, or token liquidity costs.

Milestone Funding Deliverables
M0 — Prototype & public demo $1,000 Core engine, API, dashboard, Vercel deploy, CLI completion
M1 — Hardhat plugin & verify dry-run $1,000 @verifyflow/hardhat, verify dry-run, example project, docs
M2 — GitHub Action, website & 1-year support $1,000 Action, standalone official website (migrate off Vercel), maintenance plan, grant report
Total $3,000 Full grant scope

Infrastructure costs (Vercel free tier, public RPC) are $0 out-of-pocket. No audit or third-party contractor fees.

Development Roadmap

Timeline overview

Phase Duration Funding Status
M0 — Prototype & public demo Weeks 1–3 $1,000 ~80% complete (live demo shipped)
M1 — Hardhat plugin & verify dry-run Weeks 4–6 $1,000 Planned
M2 — GitHub Action, website & 1-year support Weeks 7–10 $1,000 Planned

Total timeline: ~10 weeks from grant approval

Milestone M0 — Prototype & public demo

Funding: $1,000

Deliverables (shipped):

  • @verifyflow/core doctor engine — RPC, chainId, gas, ConfluxScan API checks
  • ConfluxScan verify-payload linter (evmVersion, compiler, optimizer)
  • Web dashboard with preflight rail + Monaco JSON editor
  • REST API (/api/doctor, /api/lint-payload, /api/networks, /api/health)
  • Public Vercel deployment + README

Deliverables (remaining):

  • CLI verifyflow doctor with non-zero exit on BLOCKED
  • Demo GIF for forum / docs

Verification criteria:

  • Demo runs end-to-end on eSpace testnet without manual RPC setup
  • Known-bad payload (evmVersion=default) surfaces as BLOCKED
  • CLI exits non-zero on failure (CI-ready)

Milestone M1 — Hardhat plugin & verify dry-run

Funding: $1,000

Deliverables:

  • @verifyflow/hardhat published to npm
  • hardhat verifyflow:doctor task + optional pre-deploy hook
  • ConfluxScan verify dry-run (payload validation without submit)
  • Bundled eSpace mainnet/testnet network presets (chainId 1030 / 71)
  • Example Hardhat project + integration docs
  • Migration notes for teams moving from Ethereum tooling

Verification criteria:

  • Plugin installable via npm install @verifyflow/hardhat
  • Sample contract deploy blocked when RPC chainId mismatches
  • Verify dry-run catches evmVersion=default before ConfluxScan submit
  • ≥3 documented integration paths (Hardhat, Foundry notes, CI snippet)

Milestone M2 — GitHub Action, website & 1-year support

Funding: $1,000

Deliverables:

  • verifyflow/action — GitHub Action for PR / deploy workflow gates
  • Standalone official website — migrate dashboard, docs, and API from Vercel preview to a permanent custom-domain site (usage guides, API reference, changelog)
  • Vercel preview URL retired or redirected to the official domain
  • Open repository with CONTRIBUTING, issue templates, release tags
  • 12-month maintenance: ConfluxScan API changes, RPC endpoint updates, security patches
  • Export preflight report as Markdown (dashboard + CLI)
  • Grant completion report with adoption metrics

Verification criteria:

  • Action documented with composite workflow example
  • Standalone official website live on custom domain — CLI + API + dashboard flows; no longer dependent on Vercel preview URL
  • Monthly release cadence documented for 12 months post-delivery
  • Completion report published in forum Awardees category

Team

Panagiotis Pollis — Founder, sole developer

Field Details
Role Architecture, backend (TypeScript), frontend (React), DevOps (Vercel), documentation, grant reporting
Responsibilities Full delivery of M0–M2; 12-month OSS maintenance
Relevant experience Production blockchain tooling: public on-chain monitoring, explorer-backed validation, REST APIs, alert systems, and multi-chain incident workflows
Twitter / X https://x.com/panagot
LinkedIn https://www.linkedin.com/in/panagiotis-pollis-33509831/
Telegram @panagot

Portfolio (live production products):

Project URL Relevance to VerifyFlow
Address Poisoning Detector https://addresspoisoningdetector.com Arbitrum wallet safety — scheduled on-chain scans, lookalike-address detection, multi-channel alerts (email, X, Telegram, webhooks), developer API. Demonstrates shipping production monitoring tooling with public explorer data.
Tracefunds https://tracefunds.app Multi-chain fund-flow tracing and incident reports (Ethereum, Solana, Arbitrum, and more). Fund-flow graphs, verification checklists, exchange abuse packs. Demonstrates complex on-chain analysis pipelines, plain-language UX, and explorer integration at scale.
VerifyFlow (this grant) https://conflux-e-space-deploy-verify-prefl-gamma.vercel.app/ Conflux eSpace deploy & verify preflight — live M0 prototype

Skills: TypeScript, React, REST APIs, CI/CD, Vercel serverless, public blockchain data pipelines, open-source grant delivery.

Source code and additional repositories available to the committee on request.

Terms of Use

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

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

#2

Dear VerifyFlow Team,

Thank you for submitting your application for the VerifyFlow integration grant, and apologies for the slightly delayed response. 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

1 Like
#3

Hi Máté,

Thank you for your message. Happy to answer any questions as you review.

Best regards

#4

I’m also happy to incorporate related enhancements or features if the committee has specific preferences requests.