You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 21, 2022. It is now read-only.
If a node ends up using less privacy than the upper bound provided to it, this lower usage is stored in the release. But nodes introduced by expansions are typically dropped from the release. So if a mechanism invocation inside of a partitional map actually uses less privacy than its upper bound, the record of the reduced usage is not retained in the release- only its downstream union.
Assuming components always respect the upper bound they are given, this bug can only inflate reported privacy usage.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If a node ends up using less privacy than the upper bound provided to it, this lower usage is stored in the release. But nodes introduced by expansions are typically dropped from the release. So if a mechanism invocation inside of a partitional map actually uses less privacy than its upper bound, the record of the reduced usage is not retained in the release- only its downstream union.
Assuming components always respect the upper bound they are given, this bug can only inflate reported privacy usage.
The text was updated successfully, but these errors were encountered: