Homomorphic encryption

So David, the first question that I have here is from Cameron, who is in San Jose, California.

And what Cameron is asking is, Which high-value use case is best suited for a first FHE deployment?

So I'd point to two different options.

One is encrypted search.

You have data that, especially things like vector databases, are quite efficient for FHE.

If you have vector data that you like to search over, do a vector embedding search for things that are nearby.

That's a great use case, and it applies to a lot of data sets where you want a query to be private and the response to be private, and someone else holds the database.

More generally, encrypted search over databases is a good one.

In mass, while never having to go through any fugazi direction because the users have chosen to sell it, right? I can also choose to buy it, um, pre- pre- pre-clear, like pre-screened, right? I could buy, I could use...

I could say if I plumb ZK or FHE on my side, now I don't need, even need to take your data in the clear.

I can just do it all programmatically and prove that it's there or through FHE.

That doesn't work in all cases, but where the options are there, they can match up, right? We don't have any of that even option to do any of that matching now.

Yeah.

Yeah.

FHE.

That was wild.

Yeah.

Yeah.

And so this is what ZK and there's new cryptographic technologies, like also FHE, you know, a lot of very interesting things you can do with that as well.

I know people, I, I, there are FHE is not a drop in that can be used everywhere, but there are very specific uses of, of that.

that really improved the UI UX of anonymous applications massively, that we're also using in DarkFi.

Let's get Mr. Quibs in here because, you know...

It's so annoying, right? No, no, no, no.

We can get rid of that now.

That's why I was talking about FHE, because now your wallet can sync on the mobile phone instantly and anonymously.