DEV Community

sahilahmad
sahilahmad

Posted on

GhostKey v2.0: Decentralized P2P Hardware Biometric Auth with ZKP Ledger

Traditional authentication architectures rely on central password stores, OAuth relays, and costly SMS OTP vectors. These create central honeypots vulnerable to credential stuffing, database leaks, and account sharing.

GhostKey Protocol is an autonomous, decentralized authentication substrate anchored to physical device Hardware Security Modules (WebAuthn / FIDO2).


🏛️ Core Architecture Pillars

  1. Autonomous Core: Pure, zero-dependency Python cryptographic challenge verifier without framework overhead.
  2. P2P Node Daemon: Socket-based mesh listener relaying verification events across peers without centralized servers.
  3. Zero-Knowledge Commitments: Blinds identity hashes into cryptographic commitments, ensuring zero user identity leak on the public chain.
  4. Tamper-Proof Ledger: SHA-256 hash-chained distributed verification blocks with built-in mathematical integrity audits.

🚀 Quick Start: Run a Local Sovereign Node

You can test and run your own sovereign node locally using our CLI:


bash
# Clone and inspect
git clone [https://github.com/skraj748487-blip/ZeroPass.git](https://github.com/skraj748487-blip/ZeroPass.git)
cd ZeroPass

# Run local autonomous node
python ghostkey_cli.py start-node --port 9000

# Execute peer hardware handshake
python ghostkey_cli.py test-handshake --port 9000

# Audit local ledger integrity
python ghostkey_cli.py audit-ledger
Enter fullscreen mode Exit fullscreen mode

Top comments (1)

Collapse
 
skraj748487blip profile image
sahilahmad •

📦 Source & Technical Whitepaper
​GitHub Repository & v2.0 Release: github.com/skraj748487-blip/ZeroPa...
​Technical Whitepaper: Available in repository root (WHITEPAPER.md).
​Looking for peer review from backend engineers, systems developers, and cryptographers on mesh block synchronization and ZKP commitment entropy!