The TEE Wiki is a collaborative knowledge base focused on Trusted Execution Environments (TEEs) and their role in decentralized systems, with particular emphasis on applications in Web3. Its primary goals are to:
- Provide accurate, up-to-date documentation on the principles, components, and implementation details of TEEs.
- Educate developers, researchers, and ecosystem participants about TEE capabilities such as remote attestation, confidential compute, and enclave-based architectures.
- Curate relevant examples, projects, and references that demonstrate the practical use of TEEs in privacy-preserving and verifiable systems. This repository is intended to serve as a shared technical resource to help standardize understanding and accelerate responsible adoption of TEE technology.
Contributions are welcome from developers, researchers, and technical writers. You can help by:
- Adding or updating explanations for core TEE concepts (e.g., attestation flows, TCB composition, enclave isolation).
- Documenting real-world projects or protocols that utilize TEEs.
- Improving content clarity, structure, or formatting.
- Contributing visual aids (e.g., architecture diagrams, flowcharts).
- Reviewing or refining existing content for technical accuracy.
To contribute:
- Fork this repository and create a feature branch.
- Make your changes with clear commit messages.
- Submit a pull request describing the intent and scope of your contribution.
- An administrator will review the submission and provide feedback or merge your request.
All contributions should prioritize clarity, accuracy, and technical rigor. Where possible, cite reputable sources or specifications to support claims.
| Role | Responsibilities | Commitment |
|---|---|---|
| Contributor | • Submit content improvements or new sections via pull requests. • Suggest edits, add references, or update examples. |
• Contribute when you see fit. • No regular schedule required. |
| Admin | • Review and merge pull requests. • Ensure consistency of structure and voice. • Curate and reorganize content when needed. |
• Review and update sections bi-monthly. • Check repo health every 2–4 weeks. |
This website is built using Docusaurus, a modern static website generator.
$ yarn
$ yarn start
This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
$ yarn build
This command generates static content into the build directory and can be served using any static contents hosting service.