Why we can't build perfectly secure multi-party applications (yet)

โš“ General    ๐Ÿ“… 2025-01-06    ๐Ÿ‘ค enrico    ๐Ÿ‘๏ธ 168      

enrico

Warning

This post was published 46 days ago. The information described in this article may have changed.

I just published a post exploring why building secure multi-party applications is impossible today. These applications aim to compute a function over inputs from different parties while keeping those inputs private. We use Multi-party Trade Credit Set-off (MTCS) as an example, showing how technologies like MPC and FHE fall short of perfect security due to a fundamental tradeoff between security and liveness. The current solution involves a delegated security model, but itโ€™s not ideal. Are there any robust patches to this problem, or will we have to wait for indistinguishability obfuscation? Read the article and share your thoughts here

๐Ÿท๏ธ FHE ๐Ÿท๏ธ MPC ๐Ÿท๏ธ iO

atomictag    2025-02-01 ๐Ÿ‘ 1 ๐Ÿ‘Ž

In my view the โ€œinteractiveโ€ nature of most (practical) MPC protocols is always going to be the bottleneck. Hence the appeal of FHE, which, at least in principle, removes that constraint at least to some extent. Perhaps there should be more research, as far I can tell, on practical, concretely efficient NI-MPC protocols, or โ€œlowโ€ interaction ones. Promising directions are Mr NISC and related/derived works (which try to circumvent the IO problem) or perhaps YOSO-like MPC like SCALES. None of the above are practical by any definition today - but I would love to hear your thoughts on these

1