-
Notifications
You must be signed in to change notification settings - Fork 11
Description
Background
As the MPV migration service for the soft-launch is feature-complete now we should begin working on the design for the TEE enabled backup service.
To enable us to align on the implementation plan for the backup service, we need to define the major components of it, how it is intended to operate, what kind of storage it would need, how it can validate and receive on-chain data, how it handles TEE attestations etc.
The goal of this issue is to have a breakdown of the major components of the backup service, and the interface between these components and any external systems.
User Story
As a developer I'd like to have a design document to know what we're building
Acceptance Criteria
We have an initial design document for the TEE enabled backup service highlighting the major components of it, how these components interact and how the system as a whole interacts with external services.
Resources & Additional Notes
No response