Hi @bigdata-memory , I think you're right about this example! Since the enclave measurement is determined by its initial code and data before instantiation, the payload which is loaded into Teaclave after instantiation cannot affect the measurement. At least for MesaPy and WASM executor, the payload was uploaded by the users and then loaded after enclave instantiation. However I **guess** the story may be different for the [`Builtin` executor](https://github.com/apache/incubator-teaclave/blob/master/executor/src/builtin.rs), because if you want to add a function, you may need to change the executor itself directly first before an enclave is generated.
-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-teaclave/issues/525#issuecomment-887110907
