- Rating
- 2
- Confidence
- 2
- Informativeness
- 3(+1)
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
CipherGenome enables private inference for a 15.1B genomic MoE by retaining attention, routing, and nonlinearities on a trusted client while outsourcing encrypted expert projections. It combines module-LWE encryption, integer tensor-core computation, reusable public hints, and communication compression. Experiments evaluate numerical fidelity, performance, inversion attacks, and routing leakage.
Critical strengths
Well-motivated system design. The expert-level partition and integer tensor-core implementation provide a concrete approach to scaling encrypted inference for public-weight MoE models.
Careful numerical validation. The evaluation separates encryption, quantization, and routing effects, with confidence intervals and known-bad controls supporting the reported fidelity.
Critical weaknesses
Practical efficiency remains unverified under realistic network conditions. All end-to-end measurements use two GPUs on a single node communicating through ZeroMQ TCP loopback (Appendix C). However, the hint configuration transfers 8.94 MB per token—approximately 9.15 GB per 1024-token window—and the 24-layer architecture requires two dependent client–server round trips per layer. These communication demands could substantially change performance across machines. Although the paper explicitly targets datacenter links and acknowledges round-trip costs, it does not establish the bandwidth and latency conditions required for practical benefits.
Questions for authors
Computation–communication trade-off. How is the total inference workload divided between the trusted client and the external servers, including client-side attention, routing, nonlinearities, and encryption/decryption? Beyond parameter counts and linear-layer FLOPs, could the authors provide a runtime breakdown showing whether the computational savings from outsourcing outweigh the additional communication and cryptographic overhead? Under what combinations of client/server compute capacity, network bandwidth, and RTT does outsourcing provide an end-to-end advantage over local execution, including CPU/NVMe offloading?
The assumption of this paper is unrealistic as shown in weakness, so I lean to keep my rating