NOAH (Network for On-chain Authenticated Handshakes) is a state-of-the-art, zero-knowledge proof-based identity protocol for the Avalanche ecosystem. It enables applications (Gaming, DeFi, and Consumer Apps) to verify user compliance (age, jurisdiction, sanctions) without ever touching or storing personal data.

Noah eliminates the redundancy of KYC on-chain. By using Zero-Knowledge Proofs (ZKP), users bind their identity to their wallet address once. This verification is then instantly reusable across every integrated app on Avalanche—from DeFi protocols to Web3 games—while maintaining 100% user privacy.

Here is what you can build with Noah:

Keep your leaderboards fair. Verify that each player is a unique human behind the keyboard, putting an end to multi-accounting and bots.

Age-gate your content or services effortlessly. Prove your user is over 18 without asking them to upload a photo of their ID card to your servers.

Onboard users securely. Meet strict KYC requirements while preserving your users' on-chain privacy.

Noah isn't just a protocol; it's a complete platform with professional presentation tools:

• Professional Pitch Deck: An interactive, slide-based presentation built directly into the UI to communicate Noah's value proposition to stakeholders.
• Visual Data Flow: A high-fidelity animated diagram that visualizes the technical process of transforming sensitive MRZ data into private ZK-Proofs.

The Noah Protocol is structured into into three integrated layers that prioritize user privacy and on-chain security:

Developers integrate the Noah SDK into their decentralized applications (dApps). The SDK provides a seamless UI component that handles user interaction without requiring complex back-end configuration.

All sensitive processing occurs locally on the user's device. The SDK's engine performs OCR to extract document data, which is then passed to the Gnark-WASM Prover. The prover generates a Zero-Knowledge Proof (ZKP) that confirms identity attributes without exposing any Personally Identifiable Information (PII).

The generated ZK Proof is submitted to the CredentialRegistry on the Avalanche network. The registry uses the ZKVerifier to cryptographically validate the proof. Once verified, a unique identity nullifier is permanently bound to the user's wallet address, enabling portable, reusable identity across the ecosystem.

graph TD
    subgraph AppLayer ["1. Application Layer (Noah SDK)"]
        SDK["Noah SDK integration"] --> UI["Seamless UI Components"]
    end

    subgraph VerifLayer ["2. Verification Layer (Local WASM)"]
        OCR["Local OCR Engine"] --> Prover["Gnark-WASM Prover"]
        Prover --> Proof["ZK Proof (No PII)"]
    end

    subgraph ChainLayer ["3. On-chain Layer (Avalanche)"]
        Registry["CredentialRegistry"] --> Verifier["ZKVerifier"]
        Verifier --> Nullifier["Identity Nullifier"]
        Nullifier --- Wallet["User's Wallet Address"]
    end

    AppLayer --> VerifLayer
    VerifLayer --> ChainLayer
    
    style AppLayer fill:#6b21a8,stroke:#a855f7,stroke-width:2px,color:#fff
    style VerifLayer fill:#1e3a8a,stroke:#3b82f6,stroke-width:2px,color:#fff
    style ChainLayer fill:#064e3b,stroke:#10b981,stroke-width:2px,color:#fff

The heart of the protocol. It handles:

• Automated OCR: Extracts MRZ data from passport images locally.
• Gnark-WASM Prover: A high-performance ZK engine that generates proofs in the browser using the BN254 curve.
• Identity Binding: Automatically binds every proof to the user's active wallet address, preventing proof theft.

The on-chain source of truth for identity status:

• Global Nullifiers: Prevents identity duplication using Hash(PassportNumber).
• Identity-Wallet Binding: Links a specific identity to a single wallet address permanently upon first use.
• Revocation: Allows authorized issuers to revoke credentials instantly.

The gateway for DeFi applications:

• Reusable Proofs: Protocols can verify the same client-side proof if the user-binding matches.
• Customizable Requirements: Protocols set their own thresholds for age, allowed jurisdictions, and accreditation status.

Noah uses Selective Disclosure—the protocol only proves the requirement (e.g., "User is over 18"), not the data (the user's birth date).

• No Backend: No central server ever sees or processes the user's passport data.
• Client-Side Proving: Proofs are generated via WASM in a secure environment on the user's device.
• Nullifier Protection: Uses salted hashes to prevent identity tracking across different protocols.

• ZKVerifier: 0xAAafC153AcB233C1dc29Cb4Cb7B0dB9145dF3541
• CredentialRegistry: 0x66778ebA2d9cc857ea39fbb8e2e54238918B221C
• ProtocolAccessControl: 0x54bCF024486e63777FcC426647E4eeEd3b963260

npm install noah-avalanche-sdk

import { NoahSDK } from 'noah-avalanche-sdk';

const sdk = new NoahSDK({ provider: window.ethereum });

// 1. Scan Passport
const mrzData = await sdk.extractPassportData(image);

// 2. Generate Proof (User-bound to wallet)
const proof = await sdk.proveAge(mrzData, 18);

// 3. Verify on Avalanche
await sdk.grantAccess(protocolAddress, proof);

• Foundry: For smart contract development and testing.
• Go: For ZK circuit implementation (Gnark).
• Node.js: For the SDK and Frontend.

# Test Contracts
forge test

# Generate Circuits (Go)
go build ./circuit/...

# Build Frontend
cd frontend && npm run build

Repository: Samuel1-ona/Noah
Status: Live on Avalanche Testnet
Powered by: Gnark, Solidity, and Avalanche.