• Currently, DKG supports n-of-m parameters. Notice that n, or the security threshold, has nothing to do with the actual ceremony - The threshold only comes into play in the "phase 2" of Ferveo, which is where we generate "a threshold" of decryption shares, and combine them to decrypt.
• When under relaxed ceremony constraints, instead of "m" shares we allow for [m, validators.len()] shares to be created in a ceremony. Meaning that the number of validators (and shares created) could be different than the minimum number of shares required by the PVSS. So we only need m shares to have a successful ceremony
• In this new regime, the old shares_num is effectively replaced by validators.len(), and from now on shares_num denotes the minimum number of shares (or validators) that the DKG ceremony accommodates
• This change will require updates to PVSS dealing and PVSS aggregation & verification

CC: @cygnusv