Skip to content

Allow bypassing TEDecryptionShare validation in constructor #296

Description

@PropzSaladaz

Description

  • In some cases, when a decryption share is definitely known to be valid (has been validated previously), we should not pay the validation cost again. We should only deserialize it

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions