- From: Erik Taubeneck via GitHub <sysbot+gh@w3.org>
- Date: Tue, 12 Jul 2022 05:27:06 +0000
- To: public-patcg@w3.org
The solution @benjaminsavage references is the one [presented in PRIO](https://crypto.stanford.edu/prio/). It's important to clarify though, this requires a global bound on trigger values (for example we could pick the range [0,2^16) and use 16 bits.) Depending on the cryptographic details of the MPC, we may also be able to limit that just by limiting the secret shared values (and avoid the extra work of a zero-knowledge proof.) To address the main point of your question, @juanli16, the range is in fact revealed to the aggregators (it is a global constant), but individual values are not revealed to the aggregators. And because the range is a known quantity, the distribution from which to draw the DP noise is also known. -- GitHub Notification of comment by eriktaubeneck Please view or discuss this issue at https://github.com/patcg/private-measurement/issues/9#issuecomment-1181330274 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 12 July 2022 05:27:08 UTC