- From: benjaminsavage via GitHub <sysbot+gh@w3.org>
- Date: Tue, 12 Jul 2022 00:41:06 +0000
- To: public-patcg@w3.org
Hi @juanli16 - and thanks for the question! Our current thinking is that the API caller would provide some kind of "zero knowledge proof" along with each trigger event, proving that the trigger value lies within a given range. The actual range would also need to be an API param, as the MPC would need to add noise proportional to that value. This param value would need to align with the zero knowledge proofs provided. I would not imagine adding any local differential privacy. -- GitHub Notification of comment by benjaminsavage Please view or discuss this issue at https://github.com/patcg/private-measurement/issues/9#issuecomment-1181187561 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 00:41:08 UTC