Can we encrypt multi-dimensional arrays?

[Deepthiappasani]

like I've 2 arrays:
array1 = [[1.1,2.2],[1.5,2.5]]
array2 = [[5.5,6.6],[4.5,6.7]]

can we encrypt these arrays using CKKS scheme?

[ibarrond]

You have to adapt the multi-dimensional arrays to the constraints of FHE (1D arrays of fixed length), and operate accordingly. E.g., represent a 2D matrix as m ciphertexts, one per row of up to n elements, then iterate over each of the ciphertexts and apply the desired operation (add/multiply) while keeping track of the underlying data sizes.

…

On Wed, 21 Jun 2023, 10:18 Deepthi Appasani, ***@***.***> wrote: *Describe the feature* A short description of what you're trying to accomplish. Make sure there are no Demos covering this feature! *Is this feature related to a project/objective? Please describe briefly* Why do you want this feature? This will motivate us to solve it! Ex. I'm preparing my Master Thesis on this topic "..." [...] — Reply to this email directly, view it on GitHub <#204>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADF6Z53IJTLXJ2P5J6RPTX3XMKU4NANCNFSM6AAAAAAZOL2PBA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Deepthiappasani]

Thank you ibarrond for the neat explanation.
As we are mentioning the qi_sizes in CKKS which is similar to mentioning multiplicative depth of a circuit. Does this mean the CKKS scheme is SHE but not FHE?

[ibarrond]

To make it FHE you need bootstrapping. Sadly SEAL does not provide this out of the box, meaning that we are limited to SHE until we merge the bootstrapping of OpenFHE.

…

On Sat, 24 Jun 2023, 05:35 Deepthi Appasani, ***@***.***> wrote: Thank you ibarrond for the neat explanation. As we are mentioning the qi_sizes in CKKS which is similar to mentioning multiplicative depth of a circuit. Does this mean the CKKS scheme is SHE but not FHE? — Reply to this email directly, view it on GitHub <#204 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADF6Z54AAJYCWHSUMLUS7QLXMZN6VANCNFSM6AAAAAAZOL2PBA> . You are receiving this because you commented.Message ID: ***@***.***>