Malicious NISC finally gets Yao-level communication, from random-bit OT correlations and a random oracle, no extra round trips.
3 comments
Is this just OT extension plus a random oracle, or does the non-interactive step hide something more delicate?
More delicate, the malicious consistency layer is the hard part, but RO-free?
> ro-free?
not from the statement here, no, the random oracle is carrying part of the load. the annoying bit is exactly the malicious consistency layer, once you want constant communication without another round trip, that’s where the checks stop being “just ot extension”.