# Threshold CGGI Implementation

**URL:** <https://openfhe.discourse.group/t/threshold-cggi-implementation/1637>\
**Category:** Library Questions\
**Tags:** feature-requests, questions, openfhe-help\
**Created:** [October 12, 2024, 4:49pm UTC](https://openfhe.discourse.group/t/threshold-cggi-implementation/1637 "2024-10-12T16:49:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![fhedude](https://avatars.discourse-cdn.com/v4/letter/f/ce73a5/32.png) [@fhedude](https://openfhe.discourse.group/u/fhedude)\
**Post date:** [October 12, 2024, 4:49pm UTC](https://openfhe.discourse.group/t/threshold-cggi-implementation/1637/1 "2024-10-12T16:49:02Z")

</div>

I’ve noticed that there is a feature branch implementing threshold CGGI. I was wondering what threshold scheme it is using and whether there is noise flooding in the distributed decryption? As you know, the noise flooding (or smudging) in CGGI may be too large that it moves into the message and corrupts it, as per [Noah's Ark: Efficient Threshold-FHE Using Noise Flooding](https://eprint.iacr.org/2023/815). How does OpenFHE mitigate this?

Thanks!

---

<div class="post-metadata">

**Author:** ![ypolyakov](https://yyz1.discourse-cdn.com/flex031/user_avatar/openfhe.discourse.group/ypolyakov/32/47_2.png) [@ypolyakov](https://openfhe.discourse.group/u/ypolyakov)\
**Post date:** [October 12, 2024, 9:38pm UTC](https://openfhe.discourse.group/t/threshold-cggi-implementation/1637/2 "2024-10-12T21:38:22Z")

</div>

This is a prototype implementation for a work-in-progress capability. It reserves room for noise (already uses larger parameters), but does not do noise flooding yet (more analysis would need to be done). We are not actively working on this project at the moment. Threshold FHE is fully supported in OpenFHE for BGV/BFV (with proper noise flooding) and is supported for CKKS (but the configuration is trickier there as 128-bit native words are needed).
