How skepx/nillion-sync works
Project Type & Purpose
• This is a secure communication/integration project where an initiator (Sync) and a responder (User) interact via a secure, decentralized, encrypted network.
• The project illustrates handling sensitive data through decentralized secure computation and local decryption on a User’s device (delivery node).
File Structure
• The project contains two main scripts: compute.py and offchain.py. These are likely to be the core modules handling the computation (integration with Nillion network) and off-chain processing respectively.
Core Components
a. Sync (Initiator):
• Represented as a component or service (possibly tied to compute.py) that starts the secure communication, triggers notifications, and interacts with Nillion.
b. User (Responder):
• This component creates a SyncID and attaches sensitive data. It should be depicted as a separate entity initiating the secure data generation.
c. Delivery Node (User’s Local Device):
• Depicted as the endpoint where local decryption occurs using the Sync mobile app. Clearly mark it as the “decryption endpoint.”
d. Nillion Decentralized Network:
• As the secure, decentralized, encrypted storage and computation engine, this component should be central. It handles data encryption, secure storage, and secret matching.
e. External Messaging Applications:
Depicting the Relationships and Data Flow
• The Sync component (via compute.py) triggers notifications or processing requests which are directed towards the Nillion network.
Architectural Patterns & Technologies
• Decentralization and local decryption principles for ensuring that sensitive data is processed securely.
• That there is a separation of concerns: one part handles initiation and secure computation (compute.py) while the other (offchain.py) might manage interactions that are not directly on-chain.
• Optionally, include notes about the role of Nillion’s infrastructure in facilitating trustless, encrypted communication.