- From: Christopher Patton via GitHub <noreply@w3.org>
- Date: Tue, 20 Jan 2026 20:08:54 +0000
- To: public-patwg@w3.org
> 1. DAP might assume that the verification key is fixed for the lifetime of a task, but it doesn't need to be. I realize that the validation key needs to be agreed, but it could be agreed across an aggregation job instead. Because it isn't specified, that would seem to be possible without changing specifications (though integrating the change in a specification might be an improvement). One subtle thing to keep in mind is that the [verification key needs to be committed to](https://cfrg.github.io/draft-irtf-cfrg-vdaf/draft-irtf-cfrg-vdaf.html#section-9.1-2.2.1) before reports are generated for the task. This helps ensure the attacker (which may include an Aggregator and the Collector) can't bias the key in a way that might reveal information about the measurement. (The analysis for this comes from https://eprint.iacr.org/2023/130.) -- GitHub Notification of comment by cjpatton Please view or discuss this issue at https://github.com/w3c/patwg/issues/76#issuecomment-3774726187 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 20 January 2026 20:08:55 UTC