some doubt about cleaning worker list when the enclave manager boots.

[m3ngyang]

https://github.com/hyperledger-labs/trusted-compute-framework/blob/def0bcc9180ccbd64383a8befff3ffd41edd552b/examples/enclave_manager/tcf_enclave_manager/enclave_manager.py#L66-L80

As the above codes described, when the enclave manager boots, it will clean the whole worker list. If there were other enclave workers, their registered information will be cleaned too.

[manojgop]

When enclave manager starts, the SGX enclaves (aka worker) are loaded in memory, new key pair is generated by the enclave and this worker is registered. In case of SGX based worker, new proofData will be obtained from IAS (Intel Attestation Service). See https://entethalliance.github.io/trusted-computing/spec.html#intel-sgx-worker-type-data for proofData. So when enclave manager restarts the enclaves needs to be registered fresh with IAS since each time it creates a new key pair after enclave (aka SGX worker) is loaded in memory