🚀 Praman Weekly Update 🏆 Certification Platform — Live | @khushi1_debug 💼 Careers Platform — Progress | @SamyagyaGoel @TanayJalan ⚙️ Admin Override — Phase 4 | @BiBiShA21 🔐 Auth & SDK | @Divyanshiverma Building in public. 🚀 #BuildInPublic #Web3‌‌

🛠️ More shipped at @PramanNetwork 👨‍💻 @TanayJalan 🛡️ Fixed production CSP issues 🎨 Updated Praman branding 📬 Improved newsletter flow ⚡ Better API configuration PRs #14 #19 #21 Building. Shipping. Improving. 🚀

🚀 Weekly Update @PramanNetwork Shipped this week: ⚙️ Admin Override Engine Bulk + single-admin overrides. 👨‍💻 @BiBiShA21 — PR #33 🔐 SDK & Auth Fixed SDK dependency issues. 👨‍💻 @Divyanshiverma — PR #26 Building in public. 🚀 #BuildInPublic #OpenSource #Web3‌‌

🚀 We’re Hiring | Praman Network Seeking a Founding Growth & Ecosystem Lead. Web3 Growth • Partnerships • Grants • PR • Hiring • Pitching 🎁 Token allocation + grant incentives + founding-team experience + mentorship + LoR. 📩 [email protected] #Web3 #Hiring

Shipped this week at @PramanNetwork 🚀 📝 Developer Blog 🎨 Better UI/UX 💼 Careers Platform (Phases 1–4) 🌌 3D Landing Page 📄 Resume Upload Huge thanks to TanayJalan, @samplazzgames & Bhavishya ❤️ Building in public. PRs below 👇 #BuildInPublic #OpenSource #Web3Trading

That’s the full stack: Device → Local ZK Proof → Gasless Relayer → On-Chain Assertion Developers can integrate this with a few lines of code using the SDK. Want to see the actual flow in your terminal? npm i @praman-network/sdk tslib Docs: docs.praman.network #Web3 #ZK

Step 4: On-Chain Verification The smart contract (on Polygon/Arbitrum) validates the proof. A unique, privacy-preserving identity assertion is recorded. No personal data. No central database. Just mathematical certainty.

Step 3: Gasless Relaying The client sends the ZK-proof to the Praman Relayer. The relayer verifies the API key, sponsors the gas, and submits the transaction. User experience stays Web2-smooth. No wallet confirmation friction. No gas fees.

Step 2: Client-Side Proof Generation SnarkJS runs a Groth16 zero-knowledge circuit directly in the browser (via WASM). It computes a cryptographic proof that the user is who they claim to be, without revealing any biometric data. Only the proof exists. Nothing else.

Step 1: Device Authentication User triggers face or fingerprint scan on their own device. Biometric features are processed instantly inside a secure enclave. Raw images, video, or facial descriptors never leave the phone. Zero leakage by design.

Most “privacy-preserving” auth systems still leak data. They just move the problem somewhere else. PramanAuth doesn’t. Here’s exactly how it works under the hood 👇