docs(frontend-python): improving the doc

closes https://github.com/zama-ai/concrete-internal/issues/#840
This commit is contained in:
Benoit Chevallier-Mames
2024-09-24 17:23:24 +02:00
committed by Quentin Bourgerie
parent 85f72a6b06
commit ddb7bbeaf4
2 changed files with 3 additions and 3 deletions

View File

@@ -98,7 +98,7 @@ serialized_evaluation_keys: bytes = client.evaluation_keys.serialize()
11. **Send the evaluation keys to the server**.
{% hint style="info" %}
Serialized evaluation keys are very large. Consider caching them on the server instead of sending them with each request.
Serialized evaluation keys are very large, even if they are [compressed](https://docs.zama.ai/concrete/compilation/compression) and can be reused several times: consider caching them on the server
{% endhint %}
### Encrypting inputs (client-side)

View File

@@ -1,7 +1,7 @@
# Manage Keys
This document explains how to manage keys when using **Concrete**, introducing the key management API for generating, reusing, and securely handling keys.
**Concrete** generates keys implicitly when needed. While this is convenient for development, it's not ideal for the production environment. The explicit key management API is available for you to easily generate and reuse keys as needed.
**Concrete** generates keys lazily when needed. While this is convenient for development, it's not ideal for the production environment. The explicit key management API is available for you to easily generate and reuse keys as needed.
## Definition
@@ -39,7 +39,7 @@ circuit.keys.generate(seed=420)
```
{% hint style="warning" %}
Do not specify the seed manually in a production environment!
Do not specify the seed manually in a production environment! This is not secure and should only be done for debugging purposes.
{% endhint %}
## Serialization