Spike: Investigate TEE Integration and Subnet Architecture Redesign

[Luka-Loncar]

Problem Statement

Current subnet architecture needs to evolve to support Trusted Execution Environment (TEE) integration and improved network communication. We need to evaluate how to transition from the current Oracle/Protocol architecture to a direct subnet + TEE approach that would simplify our stack and improve trust in data quality.

Current Architecture

• Subnet uses Fiber for communication
• Protocol API handles data validation
• Oracle manages Twitter data scraping
• Validators verify work through multiple steps

Areas to Investigate

TEE Integration

• How to implement T-Worker alongside existing components
• Integration points between TEE and subnet code
• Security model for trusted data execution
• Telemetry data handling within enclaves

Architecture Changes

• Transition from Oracle to direct TEE communication
• Validator role modifications
• Minor registration flow updates
• Data verification process changes

Communication Layer

• Evaluate current Fiber implementation
• Assess NatsIO as alternative
• Consider encryption requirements with TEE
• Review message passing patterns

Implementation Considerations

• Python to Go transition strategy
• Component separation between validator and TEE
• Database interaction patterns
• Migration path from current architecture

Questions to Address

• How do we handle the transition period?
• What are the security implications?
• How do we maintain backward compatibility?
• What are the infrastructure requirements?
• How do we handle validator upgrades?

Success Criteria

• Clear understanding of TEE integration points
• Documented communication patterns
• Identified security considerations
• Migration strategy outline
• Initial proof of concept implementation plan

Resources

• Current architecture diagrams
• TEE implementation examples
• Existing Fiber implementation
• Protocol API documentation

Deliverables

• Technical design document
• Architecture diagram updates
• Security considerations document
• Migration strategy proposal
• Timeline estimation
• Resource requirements assessment

Notes

• Reference provided architecture diagrams from @teslashibe - SN42 and SN59
• Consider feedback from previous discussions
• Focus on simplification opportunities
• Consider impact on existing miners and validators