feat(vendors): add iExec confidential computing entry#99
feat(vendors): add iExec confidential computing entry#99edenbd1 wants to merge 5 commits intoethereum:masterfrom
Conversation
Updated descriptions for clarity and consistency throughout the document. Enhanced the language for better readability and understanding of iExec's features and use cases.
rymnc
left a comment
rymnc
left a comment
There was a problem hiding this comment.
thank you for your PR!
https://docs.iex.ec/ refers to deployments on arbitrum, do you have a link to the mainnet deployment so we can check?
vendors/iexec.md
Outdated
|
|
||
| - Reliance on hardware security assumptions (Intel SGX trust model) | ||
| - Centralization considerations around TEE hardware supply | ||
| - Performance constraints for heavy workloads |
There was a problem hiding this comment.
can we have something more concrete here which says what exactly cannot be run on this solution?
There was a problem hiding this comment.
good point, i have updated the section to clarify the limitations
Co-authored-by: Aaryamann Challani <43716372+rymnc@users.noreply.github.com>
Co-authored-by: Aaryamann Challani <43716372+rymnc@users.noreply.github.com>
Clarify performance constraints and memory limits for workloads.
|
thanks for addressing comments @edenbd1
|
|
yes, there have been several audits over time: iExec PoCo Audit – ConsenSys Diligence (2019) iExec v3 Security Audit – ChainSecurity (2019) RLC Multichain Bridge – Halborn (2025) these cover core protocol components such as PoCo and the RLC bridge infrastructure |
|
hi, i think all review comments have been addressed and checks are passing |
2 participants
What are you adding?
Description
Add iExec to the vendors list as a confidential computing provider leveraging TEE for secure off-chain computation.
Checklist