[Misdicorl]

Can't it already figure that out based on the query? E.g. I'm asking for the value at key `7`. So my query asks for the encrypted value for whatever `7` gets encrypted to. The db/algo already knows I'm asking for `qasfdj`, and that its returning `zsqwer`.

It doesn't matter whether it walks the dataset or not, it gets to know those two values. So may as well build an index on the keys?

[dodobirdlord]

Most FHE schemes introduce some randomness into the request that differs on every request so that the executor can’t make that sort of association. So if you want the value at key ‘7’ you instead send a request like (7, nonce) but encrypted in a way so that different nonces will make the encrypted bytes of the request look totally different.

If the FHE program then bundles the nonce back into the response you get a brand new request/response on every query, even if you’re just querying the same key over and over.