@@ -8,3 +8,43 @@ The TEN network leverages Intel Software Guard Extensions (SGX) enclaves to crea
88
99## Node Composition
1010
11+ ![ TEN Validator Composition] ( ../../assets/ten-validator-composition.png )
12+
13+ The TEN Validator is composed of the following components:
14+
15+ ## Host and Enclave Architecture
16+
17+ #### Process Separation
18+ - Separate OS processes for Host and Enclave
19+ - Communication via gRPC
20+ - Enclave managed by independent supervisor
21+
22+ #### Security Considerations
23+ - Minimized TCB (Trusted Computing Base)
24+ - Reduced attestation frequency
25+
26+ ### Host Component Responsibilities
27+ - External request handling
28+ - L1/L2 network synchronization
29+ - Secret management and rollup publishing
30+ - Peer node communication
31+ - High-availability management
32+
33+ ### Enclave Components and Responsibilities
34+ - Transaction validation and execution
35+ - Smart contract computation
36+ - Cryptographic operations and key management
37+ - State management and confidential data processing
38+ - Attestation generation and verification
39+ - Secure random number generation
40+ - Batch processing and sequencing
41+
42+ ## Deployment Containerization
43+
44+ There are four deployment containers on a TEN Validator node:
45+ - ** Host** : The host component is responsible for external communications and network operations.
46+ - ** HostDB/Postgres** : Postgres is used to store the validator's host state.
47+ - ** Enclave** : The enclave component is responsible for sensitive computations and data processing (SGX).
48+ - ** EnclaveDB/Edgeless** : Edgeless is used to store the validator's enclave state (SGX).
49+
50+ Running a TEN validator will automatically deploy these containers.
0 commit comments