-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Capture and relay key id for decryption requests #548
Comments
currently, fetching the keyurl endpoint gives the following kind of output. Ex, for pub key (but same for verifier keys):
if we have multiple keys :
do we agree ? @jot2re full output 👇
|
@RomanBredehoft just loop for now. We can make an issue about changing the format but for the next long time there will not be more than a few keys. Even if everything takes off it will not be more than 100 keys so I think it might be a bit of a premature optimization since it is an endpoint that requires changes in many different repo |
But in general I think we need to be really careful whenever we make endpoints. I think we should always review them in a group to make sure formats are optimal for everyone |
yeah ok I see thanks, makes sense |
looking at the code, I believe that the
but it'll most likely be fixed by https://github.com/zama-ai/kms-core/issues/1506 if we decide to instead use the key id from the gateway's toml |
@RomanBredehoft the It would likely also be possible to simply update the functionality of |
Is it not possible to propagate the request id to the caller (eg CLI tool)? Whoever does this, would then configure the fhEVM chain with it, moving this question of bookkeeping to the fhEVM chain. |
|
So far we have been using a single key per ASC on the KMS side and hence kept it as part of the configuration.
However, to support multiple key's per ASC along with appropriate key rotation, we need to support the idea of multiple keys being constructed per ASC.
This involves capturing the key id from the event emitted after key generation on the KMS blockchain and then using it again when requesting the decryption.
This is not high priority right now, but ideally it would be good to work on it during Q4 2024
The text was updated successfully, but these errors were encountered: