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

Support one party owning several key shares #31

Open
fjarri opened this issue May 19, 2023 · 0 comments
Open

Support one party owning several key shares #31

fjarri opened this issue May 19, 2023 · 0 comments
Labels
API Involves backwards-incompatible changes of the public API enhancement New feature or request
Milestone
v1.0.0

Comments

@fjarri
Copy link
Member

fjarri commented May 19, 2023

This, of course, can be emulated by one party maintaining several separate Session objects, but it is inefficient, since then it will have to effectively creates proofs for itself. Also it would be nice to bundle messages from that party into one message to reduce network latency.

We will need some kind of a ShareDistribution object (should it be separate, or a part of KeyShare?) that Session will be able to make use of.
@fjarri fjarri added enhancement New feature or request API Involves backwards-incompatible changes of the public API labels May 19, 2023
@fjarri fjarri changed the title Support one parties owning several key shares Support one party owning several key shares Oct 11, 2023
@fjarri fjarri mentioned this issue Nov 18, 2023
Open
@fjarri fjarri added this to the v1.0.0 milestone Nov 26, 2023
This was referenced Jan 16, 2024
Merged
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
API Involves backwards-incompatible changes of the public API enhancement New feature or request
Projects
None yet
Milestone
v1.0.0
Development

No branches or pull requests
1 participant
@fjarri