Doubt about Recommended parameter for LogStandardDev::from_log_standard_dev in concrete-core
VARUN-2K opened this issue · 4 comments
What is the problem you want to solve and can not with the current version?
A clear and concise description of what the problem is.
the encryption part of concrete-core has the following code.
secret_key.encrypt_lwe(
&mut ciphertext,
&plaintext,
LogStandardDev::from_log_standard_dev(-18.),
&mut EncryptionRandomGenerator::new(None)
);
What is the recommended parameter range for the LogStandardDev::from_log_standard_dev?
Describe the solution you'd like
Please let me know the answer to the question asked.
Dear @VARUN-2K,
The choice of parameters for the encryption depends on your application. You can find examples of parameter sets in https://github.com/zama-ai/concrete/blob/main/concrete-boolean/src/parameters/mod.rs, that were found for the specific case when ciphertexts only encrypt 1 bit of message.
Please note that our product policy is undergoing changes, so I would advise you to check this library instead: https://github.com/zama-ai/tfhe-rs. You will find simple examples of encryption, computation and decryption in the README. Parameters are then set for you, which makes things simpler.
I hope this helps!
Agnès
Agnès,
Thank you for your message. I request you to clarify my other doubt too.
ZAMA is constantly updating the concrete-core codebase. Are the changes being made in the concrete-core codebase enhancing the security of the library or is it primarily focused on adding new use cases and features for its users?
Hi @VARUN-2K! Indeed we are still working in the concrete-core repository: right now we're focusing there on GPU acceleration mainly, using the Concrete-core test & benchmarking infrastructure to stabilize our implementations. This is why you're noticing frequent contributions there.
Best regards,
Agnès
closing this issue as concrete libraries have been replaced by concrete TFHE compiler since v1.0