Paper 2026/2214

Communication Preserving SFE from Obfuscation

Omkant Pandey, Stony Brook University
Christopher Smith, Stony Brook University
Yuhao Tang, Stony Brook University
Abstract

The communication complexity of computing a function in the two party setting can be much smaller than requiring one of the parties to send its input. We revisit how this communication complexity must change if the function must be computed securely. Hubáček and Wichs show that any protocol for computing a function securely must communicate at least as many bits as the length of the function's output. However, all positive results in this direction require much more communication than optimal. In particular, the state of the art for general protocols requires a $\textit{multiplicative}$ overhead polynomial in the security parameter, achieving only ''rate 0'' asymptotically. We show that, assuming the existence of input-succinct indistinguishability obfuscation for Turing machines, it is possible to achieve constant rate for this task. This compiler works even when the original protocol communicates single bits in each round, which is the main obstacle in prior works, and necessitates the use of obfuscation. The compiler can be based on standard non-succinct indistinguishability obfuscation for circuits (instead of Turing machines) in the common random string or random oracle models.

Metadata
Available format(s)
PDF
Category
Foundations
Publication info
A major revision of an IACR publication in TCC 2026
Keywords
obfuscationmulti-party computationMPCtwo-party computation2PCcommunication complexity
Contact author(s)
omkant @ cs stonybrook edu
csasmith @ cs stonybrook edu
yuhtang @ cs stonybrook edu
History
2026-09-27: approved
2026-09-25: received
See all versions
Short URL
https://ia.cr/2026/2214
License
Creative Commons Attribution
CC BY

BibTeX

@misc{cryptoeprint:2026/2214,
      author = {Omkant Pandey and Christopher Smith and Yuhao Tang},
      title = {Communication Preserving {SFE} from Obfuscation},
      howpublished = {Cryptology {ePrint} Archive, Paper 2026/2214},
      year = {2026},
      url = {https://eprint.iacr.org/2026/2214}
}
Note: In order to protect the privacy of readers, eprint.iacr.org does not use cookies or embedded third party content.