--- title: FuzzyPSI-hamming emoji: 🔐 colorFrom: indigo colorTo: blue sdk: docker app_port: 7860 pinned: false license: mit --- # FuzzyPSI-hamming: Deployment-Oriented FPSI Demo This Hugging Face Space presents **FuzzyPSI-hamming** as a reviewer-facing, deployment-oriented demo for privacy-preserving fuzzy private set intersection over Hamming distance. ## What this Space demonstrates - **Image-driven query workflow** for a public demo frontend - **Binary-code matching** derived from the Hamming-FPSI pipeline - **E-LSH candidate generation + exact verification story** exposed in a product-style interface - **Protocol metrics panels** showing threshold, communication, latency, and Gao-feasibility information - **Dual backend modes**: - **Simulation mode** for robust public interaction - **Optional full protocol mode** when native FPSI binaries are configured ## Reviewer-facing positioning This Space is designed to show the engineering effort beyond the paper artifact: 1. turning the protocol into an interactive web application; 2. bridging uploaded images to binary-code matching; 3. exposing system metrics and deployment status in a usable UI; 4. organizing the project as an isolated Hugging Face deployment target. The current public release is **image-first**. The code layout also includes a path for short-video analysis, but the first deployment focuses on making the image path reliable. ## Demo data policy The public demo uses a **fixed LFW-derived gallery** so reviewers can test the system in a stable and reproducible way. The deployment project is intentionally isolated from the main research artifact repository. ## Repository structure ```text . ├── app.py ├── Dockerfile ├── requirements.txt ├── src/ │ ├── config.py │ ├── protocol/ │ ├── pipeline/ │ ├── data/ │ └── ui/ └── assets/ ├── gallery/ ├── examples/ └── videos/ ``` ## Notes - The protocol core is adapted into this Space as a separate deployment project. - Public demo mode prioritizes reliability and reviewer usability. - Full native protocol execution is exposed only when the deployment environment is provisioned for it.