Thanks @alois-bissuel! This seems like a useful functionality to add. I don't see a privacy cost to this feature request, and it seems like it does indeed boost ergonomics quite a bit.

It seems like the masking functionality you described only enables the querying of some aggregation of keys. I wonder if it is worthwhile to think through alternative query mechanisms that would allow querying a group like:

• Query {01, 10} but do not include {11 , 00}

This would probably entail extending the API to support lists of buckets, potentially with some ergonomic enhancement with masking as you mentioned.

cc @palenica

Thank you Charlie for responding, and thank you Alois for the question.

Agree that a feature like this seems like a win in usability and utility, with no apparent downside in privacy.
We should flesh out the proposal a bit (e.g. I like Charlie's proposal of a list of buckets potentially combined with masking), and reach a consensus that this is a feature worth supporting.

The implementation work seems relatively modest to me. That said, at this point our team's plate is quite full with things like production hardening, adding test coverage and open sourcing. Please allow some time before we're ready to start considering feature requests.