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.

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

Design a better serialization strategy #6

Open
ChihChengLiang opened this issue Jul 18, 2024 · 0 comments
Open

Design a better serialization strategy #6

ChihChengLiang opened this issue Jul 18, 2024 · 0 comments

Comments

@ChihChengLiang
Copy link

In a client server interaction, we need to pass data like server key shares, FheUint8 outputs, and decryption shares.

We should have some ways to serialize them.

#3 is a quick and dirty way to fix this problem. We derive Serde traits to structs, then use bincode::serialize to serialize it for minimum data size.

Design consideration and challenges:

  • server key shares CommonReferenceSeededNonInteractiveMultiPartyServerKeyShare is 226 MB. We might want to reduce the size of this struct.
  • FheUint8 and decryption shares are inherently Vec. So simple Serde might already be enough.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant