# Project T-TEE: From Trusted to Trustless Execution Environments

**URL:** https://collective.flashbots.net/t/project-t-tee-from-trusted-to-trustless-execution-environments/3541
**Category:** Trustless TEEs
**Tags:** security
**Created:** [June 13, 2024, 7:15pm UTC](https://collective.flashbots.net/t/project-t-tee-from-trusted-to-trustless-execution-environments/3541 "2024-06-13T19:15:29Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![h4x3rotab](https://collective.flashbots.net/user_avatar/collective.flashbots.net/h4x3rotab/32/2540_2.png) [@h4x3rotab](https://collective.flashbots.net/u/h4x3rotab)
#### Post date: [September 8, 2024, 10:18pm UTC](https://collective.flashbots.net/t/project-t-tee-from-trusted-to-trustless-execution-environments/3541/5 "2024-09-08T22:18:53Z")

</div>

As suggested by @guayabyte, quoting my idea:

> [@\[2020\] Securing the Boot Process](https://collective.flashbots.net/t/2020-securing-the-boot-process/3827/3):
>
> Recently I’ve been thinking about a decentralized software based root-of-trust. A significant advantage of that is to dodge all the obvious problems caused by the hardware root-of-trust, like root key extraction and the data loss due to hardware availability.

Still working on some details. Would like to share it as soon as possible 😃

---

_[View the full topic](https://collective.flashbots.net/t/project-t-tee-from-trusted-to-trustless-execution-environments/3541)._