Gov-Auth Verify
Digital Proof. Legal Truth.
The problem Gov-Auth Verify solves
Government impersonation scams thrive because citizens cannot instantly verify whether a person claiming to be a government official is genuine and authorized at that moment. Existing trust mechanisms are outdated and unreliable:
• Physical ID cards can be stolen, duplicated, or forged
• Uniforms and badges do not guarantee legitimacy
• Citizens lack an instant, independent verification method
• Manual verification via helplines or offices is slow, impractical, or unavailable
• Officials who are off duty or unauthorized can still misuse their identity
This creates a dangerous trust gap that enables fraud, extortion, and abuse of authority—especially in high-pressure, real-world situations.
Gov-Auth Verify closes this gap by enabling real-time, consent-based identity verification via QR code or official ID, instantly showing clear results such as Verified, Pending, or Denied—along with the official’s current duty status.
By placing verification power directly in the hands of citizens, the system prevents impersonation at the exact moment it matters most.
Challenges I ran into
1. Secure data access: Preventing exposure of sensitive GitHub credentials required implementing a serverless API proxy instead of direct client-side access.
2. Real-time behavior without a backend: Simulating live verification states and status changes without WebSockets or a persistent server required controlled polling with strict timeouts.
3. Unauthorized profile access: Preventing open lookups of official profiles led to the design of a time-limited, consent-based verification window.
4. QR scanning reliability: Handling camera permissions, device compatibility, and smooth QR scanning across browsers was non-trivial.
5. Clear UX under pressure: Designing verification results that are instantly understandable in stressful situations required careful UI and state design.
Technologies used