Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Check if anything should be changed in the multiparty logic for EvalAutomorphismKeyGen (to avoid duplicate generation of keys) #644

Open
yspolyakov opened this issue Jan 19, 2024 · 1 comment
Open

Check if anything should be changed in the multiparty logic for EvalAutomorphismKeyGen (to avoid duplicate generation of keys) #644

yspolyakov opened this issue Jan 19, 2024 · 1 comment
Assignees
@dsuponitskiy @yspolyakov
Labels
optimization Improves performance
Milestone
Release 1.4.0

Comments

@yspolyakov
Copy link
Contributor

Check whether any changes are needed due to #545 and #546
@yspolyakov yspolyakov added the optimization Improves performance label Jan 19, 2024
@yspolyakov yspolyakov added this to the Release 1.1.3 milestone Jan 19, 2024
@yspolyakov
Copy link
Contributor Author

yspolyakov commented Jan 19, 2024 •
edited
Loading

InsertEvalAutomorphismKey avoids deduplication at the last stage of inserting the auto keys into the map. So this part is already addressed.

A duplication of keys is possible if the developer uses MultiEvalSumKeyGen or MultiEvalAtIndexKeyGen. The most efficient way would be to use MultiEvalAtIndexKeyGen once with the full list of indices. Maybe we can come up with a simpler way?

@yspolyakov yspolyakov changed the title Check if anything should be change the multiparty logic for EvalAutomorphismKeyGen Check if anything should be changed the multiparty logic for EvalAutomorphismKeyGen (to avoid duplicate generation of keys) Jan 19, 2024
@yspolyakov yspolyakov changed the title Check if anything should be changed the multiparty logic for EvalAutomorphismKeyGen (to avoid duplicate generation of keys) Check if anything should be changed in the multiparty logic for EvalAutomorphismKeyGen (to avoid duplicate generation of keys) Jan 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dsuponitskiy dsuponitskiy

@yspolyakov yspolyakov

Labels
optimization Improves performance
Projects
None yet
Milestone
Release 1.4.0
Development

No branches or pull requests
2 participants
@dsuponitskiy @yspolyakov