You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The comments describe duration and expiration as defining the life-time of the E3 along with the timestamp at which committee duties expire, presumably after this timestamp committee members are no longer required to respond to decryption requests as they should have disposed of the keys for this E3.
/// @param duration Duration of the E3./// @param expiration Timestamp when committee duties expire.
At the very least, we should make the natspec comments consistent with the use. However, I'd like to propose that we remove the concept of an input deadline from Enclave.sol and rely on implementations of IInputValidator.sol to define their own logic around input timing and implementations of IE3Program.sol to define their own logic for if/when/how ciphertext outputs should be published.
The text was updated successfully, but these errors were encountered:
IE3 currently has a concept of duration and expiration.
The comments describe duration and expiration as defining the life-time of the E3 along with the timestamp at which committee duties expire, presumably after this timestamp committee members are no longer required to respond to decryption requests as they should have disposed of the keys for this E3.
However, in Enclave.sol we treat
expiration
as a deadline by which inputs must be published and require that this timestamp passed before the output can be published.At the very least, we should make the natspec comments consistent with the use. However, I'd like to propose that we remove the concept of an input deadline from Enclave.sol and rely on implementations of
IInputValidator.sol
to define their own logic around input timing and implementations ofIE3Program.sol
to define their own logic for if/when/how ciphertext outputs should be published.The text was updated successfully, but these errors were encountered: