Integration Grants Application '25: ABYA Passport: Cross Borders, Cross Chains, One Identity

Application Introduction

Project Name: ABYA Passport

Problem Statement:
The Conflux ecosystem lacks a decentralized identity (DID) layer tailored for education, credential verification, and learner-owned data. Current identity systems are siloed, centralized, and not interoperable across chains. This limits trust, portability, and access for millions of learners and employers.

Proposed Solution:
ABYA Passport is a multichain decentralized identity system that enables secure, privacy-preserving, and verifiable credentials across Conflux, Ethereum, ICP, Polygon, Solana, etc. It uses W3C DID standards, ZKPs for selective disclosure, and anchors credentials on-chain for tamper-proof verification.

Alignment with Conflux Network:
ABYA Passport will deploy DID registries, credential anchoring, and verification logic on Conflux eSpace. It leverages Conflux’s EVM compatibility, low fees, and scalability to build a learner-owned identity graph and credential wallet SDK for EdTech platforms.

Benefit to the Conflux Ecosystem:

  • Introduces a novel DID use case for education and employment.
  • Attracts developers building on DIDKit, Veramo, and W3C standards.
  • Expands Conflux’s reach into the $404B EdTech and $70B digital identity markets.

Economic Benefit:

  • Anchors credentials and identity metadata on Conflux, increasing on-chain activity.
  • Enables credential issuance and verification APIs for institutions.
  • Drives adoption of Conflux-based identity infrastructure across Africa and Asia.

Competitive Edge:

  • Multichain DID support (did:conflux, did:ethr, did:web, did:key).
  • ZK privacy layer for selective disclosure.
  • AI-powered learning path engine and reputation scoring.
  • Institutional lock-in via credential issuance partnerships.

Links:

Conflux eSpace Grant Recipient Wallet Address: cfx:aarnknj44bbdc3hm1buyeepzb869sw5vc2k6fpj32b
Are you an incorporated startup? Not yet incorporated.

Technical Introduction

Functional Goals:

  • DID creation and registry on Conflux.
  • Credential issuance and anchoring.
  • Cross-chain verification via Universal Resolver.
  • Privacy-preserving proofs using ZKPs.

Problem Reference:
Learners lack portable, verifiable identities. Institutions struggle with fraud and slow verification. ABYA solves this with multichain DIDs and verifiable credentials.

Existing Solutions:

  1. Spruce: Web3 login, limited education use.
  2. Disco.xyz: Social identity, single-chain.
  3. Polygon ID: EVM-only, enterprise-focused.

Feasibility:

  • DIDKit and Veramo support Conflux integration.
  • W3C standards ensure interoperability.
  • ZKPs (BBS+, zk-SNARKs) already tested in prototype.

Purpose:
To build a learner-owned identity system that scales across chains and institutions, anchored on Conflux.

Scope:

  • DID registry
  • Credential issuance
  • Verification dashboard
  • Privacy layer
  • SDK for EdTech platforms

Objectives & Success Criteria:

  • Deploy DID registry and credential anchoring on Conflux.
  • Launch MVP with 1K+ DID creations and 0.5K+ credential issuances.
  • Integrate with 1+ EdTech platforms or universities.

Definitions:

  • DID: Decentralized Identifier
  • VC: Verifiable Credential
  • ZKP: Zero-Knowledge Proof
  • DIDComm: DID communication protocol

References:

  • W3C DID & VC standards
  • DIDKit, Veramo, Universal Resolver
  • Conflux eSpace developer docs

Technical Proposal

Functional Overview:
ABYA Passport is a multichain decentralized identity system that enables:

  • DID creation using W3C standards (did:conflux, did:ethr, did:web, did:key).
  • Verifiable Credential (VC) issuance for educational achievements.
  • Credential anchoring on Conflux and other chains.
  • Privacy-preserving verification using ZKPs.
  • Cross-chain resolution via Universal Resolver.

Core Components:

  • Smart Contracts: DID registry, credential anchoring, and verification logic on Conflux.
  • Frontend: React dashboard for DID management and credential sharing.
  • Privacy Layer: ZKPs (BBS+, zk-SNARKs) for selective disclosure.
  • Multichain Support: Bridges and resolvers for Ethereum, ICP, Polygon, Solana.

Legal/Licensing:

  • Open-source under MIT or Apache 2.0 license.
  • GDPR and Kenya Data Protection Act compliance.
  • Terms of Service and Privacy Policy for credential issuers and users.

Non-Functional Requirements:

  • Usability: Mobile-first UX and Chrome Extension.
  • Reliability: On-chain anchoring ensures tamper-proof verification.
  • Performance: Fast DID resolution and credential sharing.
  • Security: ZKPs, OAuth, and smart contract audits.

Implementation:

  • DIDKit and Veramo for DID creation and resolution.
  • Solidity smart contracts for credential anchoring.
  • React frontend with wallet connectors (MetaMask, Phantom).
  • MongoDB/Postgres for off-chain metadata.

User Interface:

  • Dashboard for learners to manage DIDs and credentials.
  • Credential viewer with QR sharing and verification status.
  • Admin panel for institutions to issue credentials.

Total Budget
Grant Size Requested: $15,000

Justification:

  • DID Registry Smart Contract (Conflux): $3,500
  • Credential Anchoring & ZKP Integration: $3,000
  • Frontend Dashboard (React + Wallets): $2,000
  • Universal Resolver Integration: $1,500
  • Documentation & Open Source Release: $1,000
  • Community Engagement & Marketing: $2,000
  • Project Management & Reporting: $2,000

Development Roadmap:
Batch 1: Foundation (Weeks 1–4)

  • Finalize DID methods and Conflux integration scope.
  • Develop and deploy DID registry smart contract on Conflux.
  • Begin credential anchoring logic.
  • Funding Release: $5,000

Batch 2: Core Features (Weeks 5–8)

  • Build frontend dashboard for DID creation and credential viewer.
  • Integrate ZKPs for privacy-preserving proofs.
  • Implement Universal Resolver for cross-chain verification.
  • Funding Release: $5,000

Batch 3: Testing & Launch (Weeks 9–12)

  • Conduct QA and performance optimization.
  • Prepare documentation and open-source release.
  • Launch community onboarding and marketing campaign.
  • Funding Release: $5,000

Team
Paul McOlaka | CEO

  • Role: Project Lead, Strategy & Governance
  • Responsibilities: Oversees project vision, partnerships, and compliance.
  • Relevant Experience: MSc in Financial Engineering; DeFi Talent Program alumnus; former Fellow at Digital Euro Association; Co-Founder & CEO of ABYA University; Senior Research Officer at Blockchain & Climate Institute; active contributor to UN Internet Governance Forum.
  • Github Repo: https://github.com/paulmcolaka
  • Social Media Handles: https://www.linkedin.com/in/paulmcolaka/ | https://x.com/PaulMcOlaka

Peter Mwau | CTO & Blockchain Developer

David Dext | Community Manager

  • Role: Ecosystem Engagement Lead
  • Responsibilities: Community building, user onboarding, and educational content.
  • Relevant Experience: Proven track record in Web3 community strategy; experience with Socrates and ABYA University; skilled in translating complex blockchain concepts for mainstream adoption.
  • Social Media Handles: https://www.linkedin.com/in/daviddext/ | https://x.com/Daviswriters98

Norman Gitonga | Full Stack Developer / ML Engineer

  • Role: Frontend & Backend Developer
  • Responsibilities: Builds dashboard, integrates DID flows, and manages backend systems.
  • Relevant Experience: 2+ years in full-stack development; expertise in React.js, Django REST, Node.js; experience implementing decentralized identity systems using Solidity.
  • Github Repo: https://github.com/NORMTOSH
  • Social Media Handles: https://www.linkedin.com/in/normangitonga/

Michael Macharia | AI/ML Engineer / Blockchain Developer

Clifford Omollo | AI/ML Engineer / Android Developer

Gordon Otieno | Digital Marketing & SEO Specialist

  • Role: Marketing & Growth Lead
  • Responsibilities: Drives digital presence, SEO, and content strategy.
  • Relevant Experience: Expertise in digital marketing and blockchain content creation; published work on blockchain’s role in governance.
  • Social Media Handles: https://www.linkedin.com/in/gordon-otieno-8bb537317/

Wayua Musyoka | Business Development & Partnerships

  • Role: Partnerships Manager
  • Responsibilities: Secures institutional collaborations and strategic alliances.
  • Relevant Experience: Strong background in stakeholder engagement and sustainable development; skilled in negotiation and strategic planning.
  • Social Media Handles: https://www.linkedin.com/in/wayua-musyoka-848259132/

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 ABYA Passport Team,

Thank you for submitting your application for the ABYA Passport 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

Thanks @Mate_Conflux for the feedback!

Hi ABYA Passport Team,

Apologies for the long delay, and thank you for your patience.

Thank you for your submission and for bringing a decentralized identity and verifiable credential infrastructure to Conflux. We appreciate the focus on education, credential verification, and learner-owned data, as well as the broader vision of expanding Conflux into DID and institutional identity use cases beyond DeFi.

To further strengthen your application and align it with our grant evaluation criteria, could you please provide:

  • Clear ecosystem impact KPIs specific to Conflux (e.g., projected number of DID creations, credential issuances, monthly verification transactions, active wallets onboarded, and the number of institutional integrations expected on Conflux)
  • More detailed technical architecture for the DID registry and credential anchoring flow, especially how did:conflux will be implemented, how credential issuance and revocation are handled, and how cross-chain verification interacts with Conflux as the primary anchor layer
  • Clarification on the ZKP implementation, including which proof systems (BBS+, zk-SNARKs, etc.) will be used in production, how selective disclosure works for institutions and users, and what parts remain off-chain vs on-chain
  • More details on security and compliance, including whether the DID registry and credential contracts will undergo an external audit, how admin permissions and upgradeability are managed, and how GDPR / Kenya Data Protection Act compliance is operationally enforced
  • Clarification on post-grant sustainability and institutional adoption, including your revenue model after grant funding, how universities or EdTech partners are onboarded, and whether there are already signed or active partnership commitments

These additions will help us better evaluate the technical feasibility, long-term sustainability, and ecosystem value of your proposal for Conflux.

Thank you for your efforts and we look forward to your updates!

Best regards,

Máté
Head of Grants