Integration Grants Application '25: Cregis

Application Introduction

  1. Name of Project: Cregis Technology

  2. Problem statement in the existing Conflux ecosystem (customer, application, process, etc) and the proposed solution

Development to support Conflux onto Cregis’ Multichain MPC wallet ecosystem and CFX enablement for crypto payment gateway.

  1. Alignment of the project with the Conflux Network
    Cregis’ wallet infrastructure is particularly interesting to Conflux, mainly due to our exposure to the Chinese markets. Much of which are institutional clients such as OTCs, Trust Companies, Investment Brokerage companies, USDT Card Issuers transacting in stablecoins (USDC/USDT).

a. Benefit to the Conflux Ecosystem: How this product will entice more developers to build on Conflux

b. Economic benefit: How this product will increase assets and transactions on-chain

Cregis’ core business lies in our enterprise-grade MPC wallet infrastructure that is suitable for B2B2C operations, designed for scalability. A unique approach that we have taken is to support privatisation deployment and in some instances, offering source codes to enable our clients to fully customize their wallet to suit the unique use case and regulatory requirements.

As an extension to our core service, Cregis has branched out to the payment space with a plug-and-play crypto payment gateway API, USDT USDT-backed debit card.

Currently we are developing our in-wallet bridging, swap and yield generation which can potentially bring additional value to Hedera.

In terms of user count, we are currently serving over 3500 enterprises with over 100 million sub-addresses generated. Much of the clients are from the Chinese community, since 2023 we have gone international and are seeing exponential growth in markets like Dubai and SEA.

  1. Demonstrate a competitive edge that differentiates it from other projects
    As mentioned in the earlier response, the unique approach that we have taken is to support privatisation deployment and in some instances, offering source codes to enable our clients to fully customize their wallet to suit the unique use case and regulatory requirements.

  2. Links to the projects webpage, DApp, socials and chat groups
    Website: www.cregis.com
    Socials:
    Linkedin: https://www.linkedin.com/company/cregis/posts/?feedView=all
    X: https://x.com/0xCregis

  3. Conflux eSpace grant recipient wallet address
    ERC-20 Wallet Address: 0x7b18ea773785003e53e0a0267bd079d17bbdd9a3

  4. Are you an incorporated startup?
    Yes, under Cregis Technology Limited incorporated in Hong Kong

Technical Introduction

  1. Refer back to Problem statement:
  • Cregis offers a multi-chain MPC wallet for both laptops and mobile devices
  • Multi-chain wallet: Assets from multiple chains at a glance without manual switching between all the supported networks
  • Multiple wallets in one screen: Users always have an overview of all wallets and do not need to switch between accounts
  • Accurate real-time prices on bridges and swaps
  • Payment gateway to increase CFX’s utilities and TVL
  1. Purpose of the system
    The purpose is to increase adoption for the chain and token utilities by enabling in wallet swaps, token bridging and acceptance via payment gatewat

  2. Scope of the system

Cregis is committed to providing Conflux access to its clients and volumes from the Chinese communities and some trad-fi investment firms, stablecoin flows, in the 1 stop shop for bridging, swaps, and yield generation from our in wallet service catalogues.

  1. Objectives and success criteria of the project

Total Budget
Grant Size: What is the total grant amount begin requested?

USDT 50,000

Justification: Break down the activities and costs associated with requested grant amount
The funds will be allocated as per the following:

  • 70% on development
  • 30% on mass marketing to promote our collaboration with Conflux

Development Roadmap
Timeline and milestones
Milestone 1: Present beta version of our MPC wallet with Hedera incorporated: Transaction on Conflux, CFX token support.
Milestone 2: Going live with the above-mentioned features (Transaction on Conflux, CFX token support), enabling our client portfolio to gain access to the Conflux on our wallet infrastructure.
Milestone 3: 250-500 unique Conflux Accounts opened within Cregis ecosystem
Milestone 4: Present beta version of our payment gateway that supports CFX as a form of payment
Milestone 5: Going live the CFX enablement on our payment gateway opening up the option to our existing clients who are mainly in the payments and forex brokerage space in EU, UAE and APAC.
Milestone 6: Pilot merchant using CDX and/or Conflux supported stablecoins as a form of payment for their services

Requested funding per milestone
USDT 25,000 upfront
USDT 25,000 once the milestones are completed

Team
The team will consist of both our co-founders who has an engineering background led the development of Cregis core products, Product Director, who has extensive experience working with exchange, OTC, and Payments, and myself, who has been in the web2 and web3 payment industry for over 10 years.

Shawn Yan (Co-Founder & CEO) - https://www.linkedin.com/in/shawn-qz-yan/
Aaron Zhang (Co-Founder & CTO) - https://www.linkedin.com/in/aaron-zhang-541356366/
Keian Wong (Product Director) - https://www.linkedin.com/in/keianwong/
Eric Cheung (Regional Business Development Director) - https://www.linkedin.com/in/eric-cheung0117/
Janice Tang (Marketing Director) - https://www.linkedin.com/in/janice-tang-625713169/

Github - https://github.com/0xcregis

Terms of Use
Cregis confirms that we agree to the terms of use for applying to a Conflux Ecosystem Grant by including the entirety of the following statement and conditions:

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

Dear Cregis Technology Team,

Thank you for submitting your application for the Cregis Technology integration 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 Cregis Team,

Thank you again for submitting your proposal to integrate Conflux into the Cregis MPC wallet and payment gateway. Before moving this application to our internal vote, we’d like to clarify a few key points to ensure proper due diligence:

  1. Technical & Scope
    • Is your MPC wallet fully self-developed and audited?
    • Will the Conflux integration be publicly available to all users, or limited to enterprise clients?
    • What verifiable deliverables (e.g., test transactions, SDK, or repo updates) will you provide?

  2. Ecosystem Impact
    • How many of your 3,500 enterprise clients are expected to adopt Conflux in practice?
    • What is the estimated adoption or transaction volume within the first 3–6 months?
    • Will your wallet or payment gateway support CFX or Conflux-based stablecoins for real transactions?
    • How will Conflux be promoted or featured within your wallet and client network?

  3. Financials & Milestones
    • Could you explain why 50% of the grant is requested upfront?
    • Can you share a clear breakdown of the 70% development / 30% marketing allocation?
    • What are your maintenance and support plans after integration?

  4. Business & Legal
    • Please confirm your Hong Kong incorporation and regulatory compliance documents.
    • Are there any regulatory limitations that could restrict Conflux integration?
    • Have you received or applied for grants from other chains (e.g., Hedera, BNB, Polygon), and how does Conflux integration differ?

  5. Marketing & Risk
    • What specific marketing deliverables are planned to promote the collaboration?
    • What are the main risks or potential blockers to delivery or adoption?
    • How will you ensure long-term support and updates for Conflux beyond the grant period?

We appreciate your time in addressing these questions so the committee can proceed with a well-informed vote.

Best regards,
Máté
Head of Grants | Conflux Network

[quote=“Mate_Conflux, post:3, topic:22797”]

  1. Technical & Scope
    • Is your MPC wallet fully self-developed and audited?
    yes
    • Will the Conflux integration be publicly available to all users, or limited to enterprise clients?
    yes
    • What verifiable deliverables (e.g., test transactions, SDK, or repo updates) will you provide?
    test transactions, SDK, or repo updates and etc.

  2. Ecosystem Impact
    • How many of your 3,500 enterprise clients are expected to adopt Conflux in practice?
    90% of 3500
    • What is the estimated adoption or transaction volume within the first 3–6 months?
    1mil usd at least
    • Will your wallet or payment gateway support CFX or Conflux-based stablecoins for real transactions?
    yes
    • How will Conflux be promoted or featured within your wallet and client network?
    we will fully expose via all publications and internal systems and send emails to our clients about our collaborations after we receive your vote

  3. Financials & Milestones
    • Could you explain why 50% of the grant is requested upfront?
    we have focused on wallet and payment engine for over 8 years and we have a global distribution of offices in SG, Dubai, HONGKONG, AND Kuala Lumpar. We need USDT 25,000 upfront to integrate with Conflux before we support Conflux and etc. Money are for development of the integration of Conflux and personnel burns and everything.
    • Can you share a clear breakdown of the 70% development / 30% marketing allocation?
    Sure.

70% Development / 30% Marketing Resource Allocation for Cregis.com’s Conflux Integration Bounty​

I. 70% Development Allocation (Core Focus: Technical Integration & Feature Delivery)​

  1. Technical Integration & Protocol Development (35%)​
    Conflux Network Integration​
    Develop Conflux smart contract interfaces for Cregis wallet communication with the Conflux mainnet (10%).
    Enable cross-chain asset transfers for CFX tokens and Cregis-native assets on Conflux (10%).
    Implement automated management modules for Conflux Gas Tokens (e.g., CFX) (10%).
    Security Architecture Upgrade​
    MPC-based private key sharding management for Conflux (5%).

  2. Feature Module Development (25%)​
    Wallet Functionality Expansion​
    Add Conflux chain address generation and asset management interfaces (8%).
    Support batch transaction signing and offline transactions on Conflux (12%).
    Payment Engine Adaptation​
    Integrate Conflux real-time settlement channels (compatible with T+0 clearing requirements) (5%).

  3. Testing & Optimization (10%)​
    Stress-test cross-chain transactions under high-concurrency scenarios (5%).
    Conduct security audits focused on Conflux-specific vulnerabilities (5%).

  4. Documentation & Tooling (5%)​
    Develop Conflux integration guides (SDK/API documentation) (3%).
    Provide automation scripts for Conflux asset configuration (2%).
    II. 30% Marketing Allocation (Core Focus: Ecosystem Collaboration & Market Impact)​

  5. Industry Partnerships & Co-Promotion (15%)​
    Host joint technical workshops/AMAs with Conflux (6%).
    Onboard at least 3 leading Conflux ecosystem projects (e.g., DEXs, NFT platforms) to integrate Cregis (9%).

  6. Content Marketing & PR (10%)​
    Publish a technical whitepaper: “Cregis × Conflux: Enterprise-Grade Cross-Chain Asset Management”(4%).
    Feature case studies in industry media (e.g., Cointelegraph, Decrypt) (3%).
    Produce a Conflux integration demo video (3%).

  7. Community Building & User Growth (5%)​
    Launch a “Best Integration Use Case” contest on Conflux communities (Reddit, Discord) (3%).
    Offer Conflux users exclusive airdrops or gas subsidies (2%).

  8. Data Monitoring & Iteration (5%)​
    Track user activity and transaction volume post-integration (3%).
    Optimize UX based on feedback (2%).
    III. Expected Outcomes​
    Technical: Seamless Cregis-Conflux integration supporting enterprise-grade cross-chain asset management and payments.
    Market: Engage >500 Conflux ecosystem enterprises, securing 10+ flagship client partnerships.
    Brand: Strengthen Cregis’ reputation as a strategic partner in the Conflux ecosystem.
    This allocation balances technical rigor with market-driven impact to ensure both feasibility and commercial viability of the integration project.

• What are your maintenance and support plans after integration?
To ensure the long-term success and stability of the Cregis-Conflux integration, we outline the following comprehensive maintenance and support framework:

  1. Technical Support​
    24/7 Availability​
    Dedicated engineering teams will provide round-the-clock support via ticketing systems, live chat, and email.
    Critical issues (e.g., security breaches, critical bugs) will trigger immediate escalation protocols with a maximum response time of 1 hour.
    Patch Management​
    Regular updates to address bugs, optimize performance, and ensure compatibility with Conflux protocol upgrades.
    Quarterly security patches and hotfixes for critical vulnerabilities.
    Disaster Recovery​
    Automated backups and failover mechanisms to minimize downtime during outages.
    Disaster recovery drills conducted bi-annually to validate system resilience.

  2. Security & Compliance​
    Continuous Security Audits​
    Quarterly penetration testing and vulnerability assessments by third-party firms (e.g., CertiK, SlowMist).
    Real-time monitoring of suspicious activities using AI-driven threat detection tools.
    Regulatory Compliance​
    Updates to align with evolving global regulations (e.g., KYC/AML, FATF guidelines).
    Annual SOC 2 and PCI DSS compliance audits to maintain security certifications.

  3. Operational Maintenance​
    System Health Checks​
    Daily monitoring of wallet nodes, transaction throughput, and API endpoints.
    Weekly reports on system performance metrics (e.g., latency, error rates).
    Feature Enhancements​
    Bi-annual roadmap updates based on user feedback and Conflux ecosystem developments.
    Phased rollouts of new features (e.g., multi-chain support, advanced analytics) prioritized by customer demand.

  4. Community & Ecosystem Engagement​
    Developer Support​
    Public SDK/API documentation and code repositories hosted on GitHub/GitLab.
    Monthly AMAs (Ask Me Anything) and technical workshops for developers.
    User Education​
    Webinars and tutorials on integrating Conflux assets with Cregis wallets.
    A dedicated knowledge base for troubleshooting common issues.

  5. Scalability & Upgrades​
    Infrastructure Scaling​
    Auto-scaling cloud infrastructure (AWS/Azure) to handle increased transaction volumes.
    Load testing simulations to identify and address bottlenecks proactively.
    Future-Proofing​
    Integration with emerging Conflux features (e.g., layer 2 scaling solutions, privacy tools).
    Participation in Conflux governance proposals to shape protocol upgrades.

  6. Service Level Agreements (SLAs)​
    Uptime Guarantee: 99.9% annual uptime, with compensation for breaches.
    Support SLA: Priority tickets resolved within 4 hours, standard tickets within 24 hours.
    Penalty Clauses: Financial penalties for failing to meet agreed-upon response times or resolution deadlines.

  7. Long-Term Partnership Program​
    Joint Roadmap Alignment: Collaborative planning with Conflux to integrate future protocol upgrades (e.g., zkRollups, interoperability tools).
    Incentivized Feedback: Token-based rewards for users who contribute actionable improvement suggestions.
    By combining proactive maintenance, robust security practices, and adaptive support structures, Cregis ensures the Conflux integration remains secure, performant, and aligned with the evolving needs of enterprises and developers in the Web3 ecosystem.

  8. Business & Legal
    • Please confirm your Hong Kong incorporation and regulatory compliance documents.
    confirm. we have obtained SOC2 and ISO27001

• Are there any regulatory limitations that could restrict Conflux integration?
nope

• Have you received or applied for grants from other chains (e.g., Hedera, BNB, Polygon), and how does Conflux integration differ?
not yet. Conflux is our top priorities.

  1. Marketing & Risk
    • What specific marketing deliverables are planned to promote the collaboration?

To maximize visibility and engagement for the Cregis-Conflux integration, we have designed a multi-channel marketing strategy with measurable deliverables. Below is a breakdown of planned initiatives, timelines, and KPIs:

  1. Launch Campaign (Weeks 1–4)​
    Press Release​
    Distribute a joint press release to top-tier crypto/media outlets (e.g., CoinDesk, Cointelegraph, Decrypt) highlighting the integration’s benefits for enterprises.
    Target: 50+ media pickups, 10,000+ impressions.
    Social Media Teasers​
    Launch a countdown campaign on X (Twitter), LinkedIn, and Telegram, featuring key integration features (e.g., MPC security, T+0 settlements).
    Metrics: 50,000+ impressions, 2,000+ engagements (likes/shares/comments).
    Email Newsletter​
    Send a dedicated announcement to Cregis’s enterprise client list (3,500+ businesses) and Conflux ecosystem partners.
    Goal: 20% open rate, 5% CTA click-throughs (e.g., webinar signup).
  2. Content Marketing (Months 1–3)​
    Technical Whitepaper​
    Publish a detailed guide: “Cregis × Conflux: Securing Enterprise Cross-Chain Transactions”(targeted at developers and CFOs).
    Distribution: Host on Cregis.com, Conflux’s blog, and Medium; submit to Conflux’s documentation portal.
    Case Studies​
    Develop 2–3 mini-case studies showcasing early adopters (e.g., ZBX Exchange, BoundlessPay) leveraging the integration.
    Usage: Featured on Cregis’s website and shared via LinkedIn Pulse.
    Blog Posts​
    Publish a series of 6 blog posts:
    3 technical deep-dives (e.g., MPC key management on Conflux).
    3 business-focused articles (e.g., “How Cregis Streamlines Compliance for Web3 Enterprises”).
    Target: 10,000+ combined page views.
  3. Community Activation (Ongoing)​
    Conflux Ecosystem Collaborations​
    Co-host weekly AMA sessions on Conflux’s Discord server, featuring Cregis engineers and Conflux experts.
    Frequency: Bi-weekly for 3 months.
    Metrics: 500+ participants, 200+ Q&A interactions.
    Referral Program​
    Launch a “Refer-a-Friend” program for Conflux users: Earn CFX tokens for onboarding enterprises to Cregis.
    Incentive: 100 CFX per successful referral (capped at 500 participants).
    Conflux Community Challenges​
    Sponsor a hackathon on Conflux’s Gitcoin platform: “Build the Best Cregis-Conflux Integration Use Case.”
    Prize Pool: 1,000 CFX + Cregis-branded swag.
  4. Event Participation (Months 2–4)​
    Webinar Series​
    Host 3 joint webinars with Conflux:
    “Building Trust: MPC Security for Institutional Investors”.
    “From Testnet to Mainnet: Scaling Cross-Chain Payments.”
    Target Audience: 500+ enterprise decision-makers.
    Conflux Global Events​
    Exhibit at Conflux’s flagship conferences (e.g., Conflux Summit) with a dedicated booth showcasing the integration.
    Goal: 300+ booth visitors, 50+ leads generated.
  5. Ecosystem Partnerships (Months 1–6)​
    Strategic Alliances​
    Collaborate with 3–5 leading Conflux projects (e.g., DEXs, NFT marketplaces) to offer bundled integrations.
    Example: Joint promotion with a Conflux DeFi protocol offering discounted gas fees for Cregis users.
    Conflux Validator Program​
    Become a certified Conflux validator partner to promote joint solutions for enterprise validators.
    Benefit: Co-branded marketing materials and joint press releases.
  6. Performance Tracking & Reporting​
    Monthly Reports:
    Track KPIs such as website traffic, social media engagement, webinar attendance, and lead conversions.
    Tools: Google Analytics, LinkedIn Insights, and Conflux’s ecosystem analytics dashboard.
    ROI Analysis:
    Measure the number of enterprise integrations closed post-launch and attribute them to the collaboration.

• What are the main risks or potential blockers to delivery or adoption?
Nope. as long as the bounty is fully allocated.

• How will you ensure long-term support and updates for Conflux beyond the grant period?
Cregis is committed to fostering a sustainable, long-term partnership with Conflux and its ecosystem. Beyond the grant period, we will maintain and enhance the integration through the following strategies:

  1. Dedicated Engineering and Support Teams​
    Full-Time Resource Allocation: Assign dedicated engineers and support staff to monitor, maintain, and update the Conflux integration continuously.
    24/7 Operations: Leverage Cregis’s global operations hub (with teams in Kuala Lumpur, Hong Kong, Dubai, and Singapore) to provide round-the-clock support and rapid incident response.
  2. Revenue-Sharing and Incentivized Partnerships​
    Token Incentives: Implement a revenue-sharing model for Conflux validators/partners who drive enterprise adoption of the integration.
    Co-Marketing Agreements: Collaborate with Conflux to co-fund joint initiatives (e.g., hackathons, developer grants) to sustain ecosystem growth.
  3. Community-Driven Development​
    Open Governance: Participate in Conflux’s governance forums to align the integration with protocol upgrades (e.g., zkRollups, layer 2 scaling).
    Developer Advocacy: Maintain an open-source repository for integration tools (e.g., SDKs, APIs) on platforms like GitHub, encouraging community contributions and feedback.
  4. Regular Updates and Security Audits​
    Quarterly Updates: Roll out feature enhancements based on user feedback and Conflux’s evolving roadmap (e.g., support for new token standards, improved gas efficiency).
    Bi-Annual Security Audits: Conduct penetration tests and smart contract audits with third-party firms (e.g., CertiK, SlowMist) to address emerging threats.
  5. Scalability and Infrastructure Investment​
    Cloud-Agnostic Architecture: Ensure the integration supports hybrid cloud environments (AWS, Azure, etc.) to handle increased transaction volumes without downtime.
    Load Testing: Simulate high-concurrency scenarios monthly to identify and mitigate performance bottlenecks proactively.
  6. Strategic Ecosystem Alignment​
    Conflux Validator Program: Actively participate as a certified Conflux validator to deepen technical collaboration and ensure alignment with protocol priorities.
    Cross-Chain Synergies: Explore integrations with other Conflux-compatible chains (e.g., Celo, BNB Chain) to expand the solution’s utility.
  7. Financial Sustainability​
    Tiered Pricing Model: Offer premium support tiers (e.g., enterprise-grade SLAs, custom integrations) to generate recurring revenue.
    Value-Added Services: Upsell complementary products like Cregis Payment Engine or TronGas Proxy to Conflux users.
  8. Long-Term Commitment to Innovation​
    Research & Development Fund: Allocate a portion of revenue from the integration to fund R&D for next-generation Conflux use cases (e.g., privacy-preserving transactions, DAO tooling).
    Industry Collaboration: Partner with other Conflux ecosystem players (e.g., DEXs, lending platforms) to co-develop innovative financial products.
    Example Milestones Beyond the Grant Period​
    Year 1: Achieve 100+ enterprise integrations on Conflux, with 50% annual renewal rate.
    Year 2: Expand to support layer 2 solutions (e.g., Conflux zkBridge) and launch a dedicated Conflux-focused developer accelerator program.
    Year 3: Achieve 1M+ wallet addresses on Conflux via Cregis, with annual security audits and protocol upgrades.
    By combining technical rigor, community engagement, and strategic alignment with Conflux’s roadmap, Cregis ensures the integration remains secure, feature-rich, and aligned with the needs of enterprises and developers in the Web3 ecosystem.