CONFLUX PAYMASTER SDK - GRANT PROPOSAL

PROJECT OVERVIEW

Name: Conflux Paymaster SDK
Tagline: Gasless Infrastructure for Conflux eSpace

The Conflux Paymaster SDK enables any Conflux eSpace dApp to sponsor gas fees for users through a simple 3-line integration. Built on ERC-4337 Account Abstraction, it removes the biggest barrier to Web3 adoption: requiring users to hold CFX before transacting.


TEAM

Name Role GitHub Discord
Anthony Kimani CTO - Full-stack blockchain developer, built AxPesa on Conflux anthonykimani tonykim8450
Moses Epale COO - Operations, partnerships, go-to-market mosesepale mosesepale#1234

PROBLEM STATEMENT

For developers building on Conflux eSpace, user onboarding is broken:

  1. The CFX Requirement: Every new user must acquire CFX from an exchange or faucet before performing their first transaction, creating 60-80% drop-off at onboarding.

  2. Conceptual Overload: Users are forced to understand “gas,” “gwei,” and “network fees” before experiencing the dApp’s value.

  3. Missed Opportunities: DeFi, NFT, and Gaming dApps lose users who cannot complete transactions due to insufficient CFX balance.

  4. Complexity for Developers: Implementing gas sponsorship from scratch requires deep knowledge of ERC-4337, bundler infrastructure, and secure key management.


SOLUTION

The Conflux Paymaster SDK provides a complete, production-ready abstraction layer:

  • SDK: 3-line integration to enable gasless transactions
  • Smart Contracts: Pre-deployed Verifying Paymaster + Simple Account Factory
  • Backend: Reference signing service with rate limiting
  • Relayer: Built-in transaction submission service

ALIGNMENT WITH CONFLUX NETWORK

The Conflux Paymaster SDK directly supports Conflux Network’s mission of:

Goal How We Help
Developer Adoption Lowers barrier to entry for dApp developers
User Onboarding Removes CFX requirement for end users
Ecosystem Growth Enables use cases impossible without gas sponsorship
Infrastructure Fills critical gap in Conflux eSpace toolchain

COMPETITIVE ADVANTAGE

Feature Conflux Paymaster SDK Other Solutions
Conflux Native :white_check_mark: Purpose-built for eSpace Ethereum-based, adapted
Full-Stack Contracts + Backend + SDK + Relayer Partial solutions
Open Source MIT License Proprietary
TypeScript First-class TS support JavaScript only
AxPesa Use Case Real-world validation Proof-of-concept

DEVELOPER PORTAL

We provide a self-service Developer Portal at https://conflux-paymaster-docs.vercel.app for developers to:

Feature Description
Sign Up / Login Create your developer account
Deposit CFX Fund your paymaster account balance
Get API Keys Obtain your unique API key for SDK integration
Track Usage Monitor transactions, balance, and usage stats

This portal is essential for:

  • Self-service onboarding - Developers can sign up instantly
  • Usage tracking - Paymaster balance and transaction monitoring
  • API key management - Secure SDK authentication

TECHNICAL ARCHITECTURE

┌─────────────────────────────────────────────────────────┐    
│                    dApp (SDK User)                     │    
└──────────────────────┬──────────────────────────────┘    
                       │ paymaster.sendTransaction()    
                       ▼    
┌──────────────────────────────────────────────────────┐    
│            ConfluxPaymaster SDK                       │    
│  ┌─────────────┐  ┌─────────────┐  ┌────────────┐  │    
│  │UserOp Build│  │Sign Service │  │  Relayer   │  │    
│  └─────────────┘  └─────────────┘  └────────────┘  │    
└──────────────────────┬──────────────────────────────┘    
                       │    
          ┌────────────┼────────────┐    
          ▼            ▼            ▼    
┌──────────┐  ┌──────────┐  ┌──────────┐    
│Paymaster │  │ Factory  │  │ Bundler  │    
│Contract  │  │Contract  │  │(Alto)    │    
└────┬─────┘  └────┬─────┘  └────┬─────┘    
     │             │            │    
     └─────────────┼────────────┘    
                   ▼    
┌──────────────────────────────────────────┐    
│         Conflux eSpace                   │    
│    EntryPoint → Paymaster → Account     │    
└──────────────────────────────────────────┘    

Core Components

Component Implementation
SDK TypeScript with ethers.js
Contracts Solidity 0.8.24, OpenZeppelin
Backend Express.js + TypeScript
Relayer Node.js with CFX wallet
Account Std EIP-4337 SimpleAccount

DELIVERABLES

Deliverable Specification
@conflux-paymaster/sdk npm/jsr package, MIT license
VerifyingPaymaster.sol Verified on ConfluxScan
SimpleAccountFactory.sol Verified on ConfluxScan
Backend Service Running API with /api/paymaster/sign
Relayer Service Running service for tx submission
Developer Portal Live at conflux-paymaster-docs.vercel.app
Documentation Complete API reference + tutorials
AxPesa Integration Live gasless transactions

BUDGET BREAKDOWN

Total Grant: $50,000

Item Cost Description
Mainnet Deployment $8,000 Deploy contracts to Conflux mainnet, verify on ConfluxScan
SDK Polish $8,500 Tests, documentation, npm/jsr publish
AxPesa Integration $8,000 Real-world integration + validation
Relayer Setup $6,000 Production relayer infrastructure
Developer Relations $6,000 Documentation, tutorials, sample apps
Developer Portal $4,000 Sign up, deposit, API keys, usage dashboard
Monitoring $3,500 Dashboard, alerts, 6 months
Team Pre-given (15%) $7,500 15% upfront to team
Contingency $3,500 Unexpected costs
Total $50,000

TIMELINE (5 Months)

Month Milestone Deliverable
1 Mainnet Deployment Contracts deployed and verified
2 SDK v1.0 npm/jsr published, full docs
3 Relayer Setup Production relayer running
4 AxPesa Integration Live gasless transactions
5 Developer Launch Tutorials, sample dApps, monitoring

FUNDING RELEASE

Milestone Funding Release Condition
Team Pre-given (15%) $7,500 Upon grant approval
Mainnet Deploy $12,000 Mainnet addresses, ConfluxScan verification
SDK + Relayer $15,000 npm published, relayer running
Developer Portal $6,000 Portal live, API keys working
AxPesa Live $9,500 Live transactions

Note: 15% ($7,500) is pre-given to team upon grant approval.


DEPLOYED CONTRACT ADDRESSES

Testnet (Ready)

Contract Address
EntryPoint 0x5FF137D4b0FDCD49DcA30c7CF57E578a026d2789
SimpleAccountFactory 0x3d536eA50c323fFA2bc6b7DF0c1AE253f6144eAE
VerifyingPaymaster 0x0cDE16Cf1fD5Bf2536069Aec8a2eF0832A27577B

Mainnet (To Deploy)

Contract Address (TBD)
EntryPoint 0x5FF137D4b0FDCD49DcA30c7CF57E578a026d2789
SimpleAccountFactory TBD
VerifyingPaymaster TBD

RISK MITIGATION

Risk Mitigation
Backend Signer Key Leak Store in secrets manager (AWS KMS), rotate regularly
Signature Replay SDK includes chainId + paymaster address in signed hash
Denial of Service Rate limiting per user/IP
Gas Griefing Contract includes maxGasPrice and maxVerificationGas limits
Relayer Downtime Monitoring + alerts, fallback to direct bundler

RUNNING LOCALLY

See README.md for full setup instructions.

Quick start:

# Clone and install
git clone https://github.com/conflux-paymaster/conflux-paymaster.git
cd conflux-paymaster
npm install

# Run backend
cd packages/backend
npm run dev

# Run test
cd ../conflux-test
node test/gasless-transfer.ts

LINKS


TERMS

  • [x] I have read and understood the Conflux Grants Ecosystem Overview
  • [x] I understand Conflux Technical Grants are subject to a No-Sale rule
  • [x] I agree to provide KYC information to Conflux Foundation
  • [x] I understand the requirement for public grant reporting

Wallet Address: 0xB5d0fDb5EAcb276CAe267fc899C70Da4746A8A26

Dear @Kim_x ,

Thank you for submitting your application for the Conflux Paymaster SDK 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

Dear @Kim_x ,

Thank you again for the submission. We believe the project addresses a real onboarding problem within the Conflux ecosystem, especially around gas abstraction and first-time user experience for dApps.

Before moving forward, we would like additional clarification on a few key areas:

  1. Security & Abuse Prevention
  • How do you prevent spam, gas draining, or malicious usage of sponsored transactions?
  • Are there plans for an external audit for the smart contracts and backend infrastructure?
  1. Adoption & Ecosystem Demand
  • Beyond AxPesa, are there already discussions with other Conflux ecosystem projects regarding integration?
  • What are the expected dApp integrations and projected gasless transaction volume during the first 6–12 months?
  1. Sustainability
  • Who ultimately covers the gas sponsorship costs?
  • Is there a long-term pricing/revenue model for developers using the infrastructure?
  1. Infrastructure & Reliability
  • What happens in case of relayer or backend downtime?
  • How is API abuse and rate limiting handled within the developer portal?
  1. Funding Structure
    The proposal currently includes a 15% upfront payment. As Conflux grants are generally milestone-based, could the team clarify:
  • why the upfront allocation is required,
  • and whether the structure can be adjusted toward deliverable-based milestone verification?

Looking forward to your response and additional clarification.

Best regards,
Máté

Security & Abuse Prevention

Developers authenticate via API keys issued through our portal no key, no sponsored transaction. Beyond that, malicious UserOps are rejected at the contract level: the paymaster contract cryptographically verifies every signature before releasing gas funds. A forged UserOp with a valid API key but an invalid paymaster signature will still fail on-chain. On the application side, each developer integrates their own checks (e.g., AxPesa verifies USDT balance before submitting a transfer). This layered approach means an attacker would need to compromise both the developer’s backend AND forge the paymaster signing key , which is statistically difficult.

Yes, a formal audit of all smart contracts and key backend components is planned before mainnet launch.

Adoption & Ecosystem Demand

Our strategy is to build with one anchor project first, prove the model, then onboard the rest of the ecosystem. AxPesa is that anchor , they are solving a real $6B/year problem (Kenyans cant hold and save Chinese yuan ). We estimate at least 100,000 gasless transactions in the first 6–12 months from AxPesa alone. We have also identified AntNest Global and other ecosystem projects as early candidates for integration once the reference implementation is live.

Sustainability

The dApp developer covers gas by depositing CFX into the paymaster smart contract upfront. When a user sends a sponsored transaction, the gas cost is deducted from that pool. We add a 3% surcharge on estimated gas — 70% rewards the node that executes the transaction, 10% is burned, and 20% goes to the protocol treasury. This creates an aligned, sustainable loop.

Infrastructure & Reliability

We are building a permissionless node network where anyone can run a relayer by staking CPM tokens (minimum 10,000). Nodes that go offline or submit invalid transactions are slashed. This ensures redundancy — if one node fails, another picks up the next UserOp from the queue. API rate limiting and per-developer usage controls will be added in the next portal iteration.

Funding Structure

The team has been working on this alongside another project(axpesa). We propose a fully milestone-based structure:

Got it. Here’s the refined version with status indicators and your adjusted split:


Funding Structure (Milestone-Based)

The team has been working alongside another project and has already made significant progress. Below is the proposed milestone structure:

# Milestone Deliverables Status %
1 Foundation SDD, whitepaper, homepage + developer portal, all smart contracts written and deployed on testnet, E2E gasless transaction demonstrated ~90% complete — currently finalizing SDD, whitepaper, and remaining contracts 15%
2 Integration AxPesa integrated on testnet, SDK published, developer onboarding docs Not started 25%
3 Traction 100,000 gasless transactions on testnet, 3+ projects building integrations Not started 30%
4 Mainnet Mainnet deployment, audit completed, 20+ projects onboarded, 50,000+ mainnet transactions Not started 30%

The 15% upfront request covers Milestone 1 , work already underway. The remaining 85% is tied to future deliverables. The team has been self-funding development to this point and the upfront allocation allows us to close the remaining gaps (SDD, whitepaper, developer portal) and finalize the smart contracts without interruption.

This ties every payment to measurable, verifiable outputs.