cybercentry-private-data-verification_skill

This skill enables real-time zero-knowledge proof generation and text integrity verification for private data, delivering verifiable proof_id and proof_url for
  • Python

2.1k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill cybercentry-private-data-verification

  • _meta.json509 B
  • SKILL.md17.6 KB

Overview

This skill provides real-time Zero-Knowledge Proof (ZKP) generation and text integrity validation for privacy-preserving verification at $1.00 per check. It returns a cryptographically secure proof_id and proof_url plus a structured verification report suitable for Web3, identity claims, and secure authentication flows. The service is designed to enable trustless validation without exposing raw data.

How this skill works

Submit a text payload (prefer hashed or non-sensitive values) and the service validates integrity, generates a ZKP, and returns a JSON deliverable containing proof_id, proof_url, zkp_hash, integrity_status, timestamp, and validity_period. Verification typically completes in seconds; you can poll job status via ACP commands and fetch the public proof URL to allow third parties to confirm results without seeing underlying data. Reports include proof strength and cryptographic algorithm metadata for integration into dApps and smart contracts.

When to use it

  • When you need privacy-preserving proof of a login or authentication event
  • To prove NFT ownership or identity claims without exposing wallet data
  • Before submitting an on-chain authorization or contract call that requires attestations
  • When auditing or compliance requires verifiable data-integrity proofs
  • For building anonymous voting or credential verification flows in decentralized apps

Best practices

  • Never submit raw sensitive data; use hashes or public identifiers instead
  • Verify the service wallet address before paying using wallet-verification tools
  • Sanitize and minimize context fields to reduce exposure risk
  • Treat all submitted data as potentially retained; only send what you can tolerate being stored
  • Use the returned zkp_hash or proof_url in on-chain verification instead of raw data

Example use cases

  • Generate a ZKP for a user login event and grant access when integrity_status == VERIFIED
  • Produce a proof URL proving NFT ownership that a dApp can check before unlocking features
  • Create a ZKP hash and submit it to a smart contract verifyProof(bytes32) function
  • Issue anonymous voting receipts where each vote has a ZKP proving eligibility without revealing identity
  • Provide employers verifiable credential proofs for education or certification claims

FAQ

Each verification returns structured JSON with proof_id, proof_url, integrity_status, zkp_hash, claim_type, timestamp, validity_period, and verification_details including proof_strength and algorithm.

Can I submit passwords, keys, or PII?

No. Never submit passwords, private keys, wallet seeds, SSNs, or other sensitive PII. Use hashed values or non-sensitive claims only.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational