Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SPEC] Add TEE/SGX support for the signing/keygen functionality #422

Open
Tracked by #16
drewstone opened this issue Oct 18, 2022 · 2 comments
Open
Tracked by #16

[SPEC] Add TEE/SGX support for the signing/keygen functionality #422

drewstone opened this issue Oct 18, 2022 · 2 comments
Assignees
Labels
needs more info ℹ️ Add additional information p3 🔵 Issues should be resolved eventually spec 🆕 Specification details for future implementation

Comments

@drewstone
Copy link
Contributor

Overview

  • We want the keygen to run inside an enclave. The key should be stored in the enclave.
  • We want the signing to run inside an enclave. All sensitive operations happen inside the enclave.
  • We can send the public key generated outside of the enclave for signing set operations.
  • Using AWS / Fortanix libraries.

Research

  • All MPC companies use enclaves for key management / operations (Fireblocks, Lit Protocol, etc.)

Examples

Questions/Issues

@dutterbutter dutterbutter added spec 🆕 Specification details for future implementation p3 🔵 Issues should be resolved eventually needs more info ℹ️ Add additional information labels Oct 24, 2022
@drewstone
Copy link
Contributor Author

@drewstone
Copy link
Contributor Author

@thomivy we should consider structuring this as a grant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs more info ℹ️ Add additional information p3 🔵 Issues should be resolved eventually spec 🆕 Specification details for future implementation
Projects
Status: Not Started 🕧
Development

No branches or pull requests

3 participants