Open
Conversation
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
… SAFE_SERIALIZATION_SIZE_LIMIT (1GB)
This reverts commit 32c2acb.
architect-dev
force-pushed
the
feat/tfhe153
branch
from
8eab58e to
53ae3b9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates the imported tfhe and node-tfhe versions from 0.11.0 to 1.5.3. This is a hard breaking change, all previous versions of cofhesdk will no longer be able to generate encrypted inputs.
The updated tfhe version requires using
safe_serializeandsafe_deserializeto work with the FHE publicKey and CRS. This future proofs the sdk, as the keys include a version indicator which can be parsed by the tfhe package, so we shouldn't need to handle this as a breaking change in the future.