Hi,
My codes reference tfhe crate only for fhe operations on ciphertext, which are deterministic. But the static validation tool which checks for randomness would fail on me because tfhe crate as a whole has dependencies on csprng. Is there any way, such as features, to only import the deterministic part of tfhe?
Its not very clear what your problem is and why your “static validation tool” fails
There are ways that you can make the randomness deterministic, however it’s not advertised as without randomness FHE is not secure
My codes will run in a smart contract which requires deterministic behavior. I think crate tfhe has a dependency on getrandom which the static validation tool does not like and therefore the smart contract cannot be deployed to the chain. So what options do we have on the tfhe crate to avoid that?
Oh so you mean that you have a static analysis tool that looks at all the dependencies and rejects if there is any thing related to randomness ?
There is no way to remove the csprng dependency there is only a wayto make the randomness deterministic at runtime
Is it possible to split tfhe crate into two crates, one doing encryption which needs csprng (getrandom), and other doing fhe ops which may not need that?