Skip to content

Naming and notation #1509

@YounesTal1

Description

@YounesTal1

This issue is for unifying and changing notation in the code:

1)To differentiate between the two BFV parameter sets, let's use the names:
-Individual public keys/individual BFV keys to refer the public keys that ciphernodes use to encrypt values to each other (so if i want to send data to ciphernode j, i encrypt using the individual public key of ciphernode j).
-Threshold public key/threshold BFV key to refer to the key that the ciphernodes jointly generate (so this is the key that users use to encrypt their inputs, i.e., this is the public key whose secret key is secret shared between the ciphernodes).

2)For the set of honest parties H, let's use instead the set of Authorized parties A. At the beginning, A contains all the n ciphernodes, then whenever a ciphernode is flagged to be malicious, it is discarded from A.

3)In the code (like in here), let's change the names of the folders dkg and threshold to something else.
For example, we can move the share_computation folder from dkg to threshold, and name the dkg folder Individual_key, and name the threshold folder Threshold_key, to refer to the fact that in the circuits of the Individual_key folder, the parameter set used to encrypt, decrypt, etc, is the one of the Individual keys, and in the circuits of the Threshold_key folder, the parameter set used to encrypt, decrypt, etc, is the one of the Threshold key.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions