You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[ZK] Research spike: ZK verification on Soroban #35
Decide how SecureFlow will do zero-knowledge verification before building the ZK features
(#36, #37, #38). This is a research/design spike that ends in a written ADR, not production code.
Questions to answer
Can a ZK verifier run on-chain in Soroban within instruction/cost limits? Which proof
systems are feasible (Groth16 / PLONK / STARK / Bulletproofs) given available host functions
(pairing/curve ops)?
If on-chain verification is too costly: off-chain proof generation + on-chain attestation
(an oracle/attester posts a verified result) — what are the trust assumptions?
Proving stack: which toolchain (e.g. circom/snarkjs, halo2, noir) fits a Rust/Soroban project?
Where do proofs get generated — client-side in the browser/wallet, or a service?
Nullifier + commitment scheme shared across the three ZK features
Deliverable
An ADR in docs/adr/ documenting the chosen architecture, trade-offs, and a reference flow
A throwaway proof-of-concept proving one trivial statement end-to-end
Activity
[-]Research spike: ZK verification on Soroban[/-][+][ZK] Research spike: ZK verification on Soroban[/+]rupesh-kumar-sah commentedon Oct 7, 2026
Hi team,
Happy to tackle this. Here is how I plan to implement it:
Implementation approach:
I can deliver a clean, tested PR within 24 hours. Please assign!