Repository navigation
feat(zk): add zero-knowledge range proof service for private settlements - #1022
Merged
Abdulazeem-code merged 2 commits intoOct 24, 2026
Conversation
|
@eeshasalaudeen734-creator is attempting to deploy a commit to the Abdulazeem's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
@eeshasalaudeen734-creator Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
eeshasalaudeen734-creator
force-pushed
the
fix/935-zk-proof-service
branch
from
October 22, 2026 05:44
990b2f6 to
8ccc587
Compare
Strips the payload this branch picked up (deleted api.js, truncated payment-dashboard/vite.config.js, unhooked package.json). No functional change to the branch's own work.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds the backend zero-knowledge proof service requested in #935. The service generates Groth16 range proofs proving that a settlement amount is strictly greater than zero and below the configured maximum, while only revealing a Poseidon commitment and the public limit.
Related Issue
Closes #935
Changes
stellar-payment-platform/src/services/zkProofService.jswith:0 < amount < maxLimitstellar-payment-platform/zk/rangeProof.circomand the compiled Groth16 artifacts.stellar-payment-platform/tests/zkProofService.test.jscovering generation, valid proof acceptance, tampered proof rejection, tampered commitment rejection, malformed encodings and verification latency.snarkjsandffjavascriptdependencies.stellar-payment-platform/zk/README.md.Verification
Result: 10/10 tests passing. Steady-state verification measured below the 50ms acceptance target (median ~20ms locally).
Checklist
Closes #935Notes
The checked-in proving key was generated from a local test setup. It is not suitable for protecting production funds; the README documents how to regenerate the artifacts and why a production trusted setup and audited circuit are required.