White paper WP-014
Double-Spend Prevention for Zero-Knowledge Proofs
One eligibility proof should not work for ten people.
At a glance
- Paper
- WP-014
- Topic
- Double-Spend Prevention for Zero-Knowledge Proofs
- Format
- PDF + web summary
- Signatures
- ML-DSA-65 post-quantum (NIST FIPS 204)
- Sandbox
- Reproducible at affix-io.com/sandbox
- Company
- AffixIO, Wales, UK
Double-Spend Prevention for Zero-Knowledge Proofs is an AffixIO technical paper. One eligibility proof should not work for ten people.
Zero-knowledge credentials fail operationally when the same proof gets shared or replayed. AffixIO tracks proof consumption digests and binds proofs to session nonces so each eligibility check fires once, without storing identity attributes.
Summary
Zero-knowledge credentials fail operationally when the same proof gets shared or replayed. AffixIO tracks proof consumption digests and binds proofs to session nonces so each eligibility check fires once, without storing identity attributes.
Download the full PDF for technical detail, diagrams, and reproduction steps. Public sandbox: affix-io.com/sandbox.
Related reading
Frequently asked questions
What is a ZK double-spend?
Reusing or sharing a valid proof to claim the same entitlement multiple times or across different users.
Does the spent registry store PII?
No. Only cryptographic digests of consumed proofs are retained.
How does session-nonce binding work?
Each verification session receives a fresh nonce embedded in the proof witness so proofs from old sessions fail validation.