feat(security): implement ZK-KYC nullifier registry with on-chain anchoring#71
Conversation
…horing Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This PR implements the ZK-KYC nullifier registry to prevent proof replay attacks.
Key changes:
NullifierRegistrywith TTL logic, an in-memory fallback, and Upstash Redis integrationverifyProofinindex.tsto check nullifiers during verification and throwProofReplayErrorAXIOM.mdwith new ZK-KYC security guaranteesPR created automatically by Jules for task 5211477336914530391 started by @Moeabdelaziz007