dApps often require users to undergo identity verification (KYC) to comply with regulations. However, this process forces users to link their wallet addresses with their real-world identities, posing a serious privacy risk.

ZKProofport directly addresses this issue. It provides a privacy infrastructure that enables users to generate a zero-knowledge proof (ZK Proof) in their browser to attest that “I am the owner of an account that has completed Coinbase KYC.”

With this system, dApps receive only a cryptographically verifiable “verified / not verified” result without ever knowing the user’s actual wallet address.

• Safer for Users:
  • Complete Anonymity: Users can participate in airdrops or DeFi protocols without revealing their wallet addresses, protecting them from on-chain tracking or targeted attacks.
  • Data Sovereignty: All proof generation happens entirely within the user’s browser. No sensitive personal data ever leaves the user’s device.
• Easier for dApps:
  • Effortless Compliance: Developers can integrate complex ZK verification through our SDK with just a few lines of code.
  • Effective Sybil Resistance: By verifying that a user has completed a rigorous KYC process, dApps receive a strong "proof of humanity" signal. This is crucial for fair airdrops, governance, and preventing bot activity, all without compromising user privacy.
  • Reduced Liability: dApps no longer need to store or manage sensitive information like wallet addresses, reducing legal and technical risks.

The core challenge is ensuring the complete cryptographic integrity of the ZK circuit.

Simply verifying a user’s signature (ecrecover) is not sufficient. To prevent malicious actors from submitting tampered data with valid signatures, the circuit itself must recompute the transaction digest from the raw private inputs (calldata).

This requires implementing the full Keccak-256 hash function logic within the Noir circuit as arithmetic operations one of the most complex and computationally intensive tasks in ZK circuit design.

We are currently implementing and optimizing this core logic to guarantee privacy for users while providing dApps with truly trustless verification.

https://github.com/zkproofport

https://zkproofport.com

ZKProofport lets you prove you're KYC-verified without ever revealing your wallet address.

Our unique value proposition is to make on-chain privacy practical and accessible. We stand out as "privacy middleware" through simplicity and trust.

1. Browser-Native & Fast: All proofs are generated locally in the user's browser in seconds. No separate app installation is required.
2. Zero Address Linking: We act as a "privacy middleware." The dApp never learns the user's wallet address; it only receives the cryptographic proof and a simple 'true/false' verification result.
3. Leverages Existing Trust: We don’t create a new identity system from scratch. Instead, we enable users to privately leverage existing trust networks, like Coinbase's on-chain KYC attestation (EAS), which is a key primitive on Base.

Best of all, our SDK abstracts away all ZK complexity, allowing developers to integrate this powerful privacy feature with just a few lines of code:

// How a dApp verifies a user (Example Code)
import { openZkKycPopup, verifyZkKycProof } from "@zkproofport/sdk";

async function handleVerification() {
  try {
    // 1. Open the portal and get the ZK proof
    const proofData = await openZkKycPopup();

    // 2. Verify the proof (off-chain or on-chain)
    const result = await verifyZkKycProof(proofData);

    if (result.success) {
      alert("Success: User KYC is verified!");
    }
  } catch (error) {
    // User closed the popup or verification failed
    console.error("Verification was canceled or failed.");
  }
}

Our alpha build, demonstrated by this SDK and our live demo dApp, validates that any dApp on Base can immediately implement reliable, privacy-preserving KYC.

Our initial target customers are teams within the Base ecosystem attempting to launch KYC-gated airdrops, with a primary focus on DeFi protocols.

These teams are our wedge into the market. They face the most acute dilemma: complying with regulations and filtering out bots (Sybil resistance), all while preserving user privacy. They are the early adopters most desperate for a privacy-preserving compliance and anti-Sybil solution.

Existing KYC solutions require dApps to collect wallet addresses, linking users’ entire on-chain history to their real identities a serious privacy issue.

Through our discussions with Base ecosystem developers, we’ve confirmed strong interest in solutions that eliminate the need to handle user data while still ensuring compliance.

• zkPassport (https://zkpassport.id/)
• World ID (https://world.org/world-id)

Our closest competitors are zkPassport and World ID. Our key differentiator is that we offer a 10x simpler adoption story by leveraging existing trust instead of building a new identity system.

1. Leveraging Existing Trust vs. Creating New Identity:

   Unlike World ID, which builds a new biometric identity system (iris scanning), ZKProofport leverages existing trust (Coinbase KYC), enabling faster adoption by dApps.

2. Browser-Based vs. Hardware-Dependent:

   While zkPassport focuses on mobile NFC/e-passport integration, our solution is 100% browser-based, accessible across desktop and mobile environments.

3. dApp-Centric Security:

   Our long-term roadmap includes a “dApp whitelist model”, allowing only verified dApps to request proofs adding an additional layer of protection against phishing or malicious proof requests.