No reduction from ORAM to sublogarithmic-overhead ORAM
Statement
Let be an online ORAM, one that processes each operation before receiving the next (BN16), whose server only stores and returns cells. Let have blocks of bits, bits of client memory and server cells of any size, and let it be secure, even only computationally and even if it errs with probability up to . Then some sequence of operations has expected amortized bandwidth blowup , even when encodes the data arbitrarily — LN18. For , with a constant, the bound is , so no sublogarithmic-overhead ORAM exists. ORAM itself exists unconditionally: the linear scan, which reads and rewrites every cell on each operation, is perfectly secure — folklore. Hence no reduction of any class from ORAM to sublogarithmic-overhead ORAM exists.
Notes
- Every online ORAM makes amortized memory probes per operation, where is the virtual cell size and the physical cell size; the bound is tight up to the factor and extends to non-colluding multiple servers. When and , some offline ORAM makes probes per operation on average, while every online one makes — KL21.
- LN18’s adversary knows which physical accesses belong to which operation. The bound for online ORAM holds without that knowledge — HKKS19.
- The bound is tight: OptORAMa has amortized bandwidth blowup (PRF ⇒ logarithmic-overhead ORAM (OptORAMa)) — AKL+20. It also matches the upper bounds known before OptORAMa when — LN18.
- Offline ORAM with fixed instructions that may encode the data is not covered: a lower bound there, with blocks of client memory at every step, would imply superlinear lower bounds on the size of sorting circuits (Small sorting circuits ⇒ sublogarithmic-overhead offline ORAM with fixed instructions) — BN16. Online ORAM whose reads, but not writes, have overhead follows from small sorting circuits and locally decodable codes with parameters not known to exist, so a lower bound for online read-only ORAM would need a new circuit lower bound or would have to rule out such codes — WW18.
- With server computation the bound does not apply: Onion ORAM has worst-case bandwidth blowup (DCR ⇒ constant-bandwidth ORAM (Onion ORAM)) — DDF+16.