New

ZipPIR: Private Retrieval Without Client-Side Storage

How compressed phases move preparation and update work to the server

7 chapters64 min total
Keywords
ZipPIRPIRLWEPaillierCompressionThroughputUpdatesStateAuthorization
Overview

ZipPIR studies how single-server PIR can hide a selected database index while avoiding a large client-held hint. Its linear LWE decryption phase is evaluated over encrypted key material with Paillier, while offline preparation moves database-dependent work to the server. The series weighs throughput against server state, query traffic, updates, correctness, security assumptions, and authorization boundaries.

Learning outcomes
  • ZipPIR hides the selected database index in single-server PIR, not the client’s connection, authorization, or all metadata.
  • Its compression evaluates the LWE decryption phase over Paillier-encrypted key material, allowing a smaller response.
  • Offline server preparation avoids a large database-dependent client hint, but retains per-client state, refresh work, and query traffic.
  • Reported throughput was above 3 GB/s in tested 1 GB and 2 GB cases; the result is hardware- and parameter-specific.
Keywords
ZipPIRPIRLWEPaillierCompressionThroughputUpdatesStateAuthorization

Chapters

Preview every chapter · Unlock full text, audio, and video from chapter 4

Plans
Ch.1-3 FreeCh.4-7 Premium

FAQ

What problem does ZipPIR solve?

ZipPIR lets a client retrieve one indexed database value from a single server without revealing the selected index, while avoiding a large client-held hint.

How does ZipPIR reduce the response size?

ZipPIR has the server evaluate the linear LWE decryption phase over Paillier-encrypted secret-key material and return that phase instead of the full LWE representation.

What does ZipPIR require the server to do?

The server must retain client-specific preparation, regenerate it when the database changes, and perform online matrix work; the client still sends a substantial query.

How fast is ZipPIR?

In the paper’s 1 GB and 2 GB evaluations, ZipPIR reported 3,020 and 3,531 MB/s throughput, respectively. These results came from specified hardware, implementation, and parameters.

Does ZipPIR replace authorization or PSI?

No. ZipPIR hides a selected index in single-server PIR; it does not replace authorization, conceal all connection metadata, or perform private set intersection.