carrotcypher

What does this mean for speed?

Decrypted on the local computer, not the untrusted remote computer as it were.

Cryptographic is all about privacy of data-in-transit and data-at-rest. What you're discussing is peoples lack of understanding of (or appreciation for) threat models, or taking a "countermeasure-first" approach to security/privacy.

To my understanding, FHE is designed for the threat model where you don't trust the machine you're calculating on to know the data you're calculating.

As for the argument that it can spew out garbage results or false data and no one would be the wiser, when the encrypted data is provided by you, it's pretty easy to validate when something isn't correct. 100,000 passes on predictable data outcomes for example.

Basically. FHE would not "leak" anything that anyone could decipher except the owner of the key for the submitted calculation.

If no one answers here, might try on the FHE.org discord, loads of researchers there who probably wrote a paper on exactly that.

Yes, OP is apparently under the assumption that FHE was designed to solve all problems, instead of the problems it was designed to solve.

> FHE gives you NO guarantee about the code that is running on the encrypted data.

You mean in order to validate the data is authentic? Otherwise the code running on the data is irrelevant, as it can't access the data itself (and thus preserves the before-mentioned privacy).

I'd look at dominating the standards used in the market rather than the market itself.