Excited to share two new threshold encryption schemes.
More details here:
1. Silent Threshold Encryption (CRYPTO 2024 - ): The first scheme to completely avoid interactive setup without using iO/WE.hackmd.io/@guruvamsi-pol…
ia.cr/2024/263
More details here:
1. Silent Threshold Encryption (CRYPTO 2024 - ): The first scheme to completely avoid interactive setup without using iO/WE.hackmd.io/@guruvamsi-pol…
ia.cr/2024/263
Parties sample their public-key pair *independently* but need a KZG CRS. To encrypt, you just need to download the committee's public keys + threshold can be chosen at the time of encryption. Also gives us timelock encryption with a silent setup.
Concretely efficient!
Concretely efficient!
2. Batched Threshold Encryption (USENIX Security 2024 - ): A “batch” of ciphertexts can be decrypted using communication that is *independent* of the batch size.ia.cr/2024/669
Typically, a committee of n parties requires O(nB) communication to decrypt B ciphertexts. One message per party, per ciphertext. In contrast, we only need O(n) communication. Useful for encrypted mempools, where an entire block needs to be decrypted quickly.
Joint work with @Arka_r_c , @SanjamGarg , Dimitris Kolonelos, @julientpiet , and @MingyuanWang0
• • •
Missing some Tweet in this thread? You can try to
force a refresh
