The Chainlink 2.0 whitepaper explores ways to “employ TEEs in ways that recognize their potential for compromise” and also recommends a non-Intel technology in open source alternative—Keystone. Keystone is based on RISC-V architecture, which has already made headway in the smart contract space. Working together, ETH Zurich and the University of Bologna have designed the open-source RISC-V PULPino processor as part of the Parallel Ultra-Low Power (PULP) project for low power IoT computing.
Alternatives like Keystone and still others like AMD Secure Technology, present an increasingly diverse range of hardened compute resources. It can be speculated that in the same way multiple oracles are used to ensure data integrity, multiple forms of secure enclave technology could one day be used in parallel to ensure code execution integrity. For example, a Dapp could request their code to be executed on 3 different technologies—SGX, Keystone and AMD Secure Tech across varying nodes. The data could be broken into parts, and when a 0 day exploit is detected on one enclave, the code execution could be switched to a unaffected environments. The detection and aggregation would happen via smart contract.
Feasibility of such a scheme, would need confirmation, though it seems there is some semblance in “sealed glass proofs“, also mentioned in the Chainlink whitepaper. It incorporate similar elements like smart contracts as part of the security model.
Leave a Reply