zk-proofs

Design zero-knowledge proof verification workflows for Stellar smart contracts.

3|1|Updated May 12, 2026
One-click install
npx skills add https://github.com/LumenWipe/lumenwipe --skill zk-proofs-lumenwipe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: zk-proofs
Source: https://github.com/LumenWipe/lumenwipe/tree/main/.claude/skills/zk-proofs
Command: npx skills add https://github.com/LumenWipe/lumenwipe --skill zk-proofs-lumenwipe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers design and implement zero-knowledge proof workflows on Stellar while avoiding unsupported cryptographic primitives, curve mismatches, replay vulnerabilities, and unclear trust assumptions.

Core Features & Use Cases

  • On-Chain Verification: Implement Groth16 verification over BLS12-381 using Soroban host functions available from Protocol 22 onward.
  • Proving Toolchain Guidance: Connect Circom, Noir, or RISC Zero workflows to Stellar, distinguishing native verification from off-chain attestation patterns.
  • Privacy Architecture: Design privacy pools, confidential applications, Merkle-tree commitments, verifier gateways, policy layers, and replay protection.
  • Capability Validation: Check CAP status, target network protocol versions, and soroban-sdk support before depending on BLS12-381, BN254, or Poseidon functionality.

Quick Start

Use the zk-proofs skill to design a Stellar privacy application that verifies Circom Groth16 proofs over BLS12-381, binds public inputs to the intended action, prevents replay, and accounts for current network capabilities.

Frequently Asked Questions about zk-proofs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify zero-knowledge proofs in Stellar Soroban smart contracts?▼

Zero-knowledge proofs can be verified in Soroban smart contracts using Grooth16 verification over BLS12-381 via host functions available from Protocol 22 onward, binding public inputs to intended actions while preventing replay attacks and checking CAP status for capability validation.

Can I use Circom or Noir to generate ZK proofs for Stellar?▼

Circom, Noir, and RISC Zero workflows can connect to Stellar for proof generation, requiring distinction between native on-chain verification and off-chain attestation patterns to ensure proper protocol and SDK support integration.

What's the best way to design privacy pools on Stellar using Merkle commitments?▼

Designing privacy pools on Stellar requires Merkle-tree commitments, verifier gateways, policy layers, and replay protection implemented within Soroban smart contracts to create confidential applications with validated trust assumptions.

Does Soroban support BLS12-381 and BN254 cryptographic curves for ZK verification?▼

Soroban supports BLS12-381 for Groth16 verification from Protocol 22 onward, while BN254 requires capability validation checking CAP status, target network protocol versions, and soroban-sdk support before implementation.

Why do my ZK proof verifications fail with curve mismatches on Stellar?▼

Curve mismatches occur when using unsupported cryptographic primitives or mismatched BLS12-381 and BN254 parameters, requiring validation of protocol and SDK support, curve compatibility, and trusted-setup hygiene before implementation.

How do I prevent replay attacks when verifying zero-knowledge proofs on Stellar?▼

Preventing replay attacks requires binding public inputs to intended actions, implementing replay protection mechanisms in Soroban verifier contracts, and validating proof statement semantics for privacy-preserving applications.