The EC Protocol

  1. Web 3.0 dApp developer

This refers to a dApp developer who aims to leverage the Ethernity Cloud Protocol to build their own application while ensuring the secure handling of user information and confidential data processing. The developer is responsible for writing the app, incorporating data encryption, utilizing decentralized storage, and ensuring confidential data processing using the Ethernity CLOUD protocol.

  1. Web 3.0 dApp user

The Web3.0 dApp User is an essential participant in the ecosystem, utilizing the dApp to maintain the privacy and security of their sensitive data. They interact with the decentralized application built using the Ethernity Cloud Protocol, ensuring that their information remains confidential and secure.

  1. Ethernity Cloud (EC) Smart Contract

The EC Smart Contract plays a crucial role in the protocol and performs key functions to ensure the smooth operation of the Ethernity Cloud ecosystem.

Task Request Handling and Approval: The dApp User operates through the dApp to submit task requests, and the EC Smart Contract handles the approval process, matching task requirements to suitable EC Nodes for execution. It also provides node and task execution status information.

Advertising Nodes Resource Availability: The EC Smart Contract enables EC Nodes to advertise their resource availability to facilitate efficient task request matching.

Handling Task Request Matching and Approval by EC Nodes: EC Nodes interact with the EC Smart Contract to initiate the matching and approval process, ensuring proper task distribution for execution.

Receiving Proof of Execution Submissions from EC Nodes: EC Nodes submit proof of execution to the EC Smart Contract to confirm the task execution on the blockchain.

  1. Decentralized Storage

The Decentralized Storage, represented currently by the Inter Planetary File System (IPFS), serves as the platform for users to upload dApp encrypted input and metadata. EC Nodes then download this encrypted data for task execution, and subsequently, the EC Node uploads the encrypted result. Users can download, decrypt, and analyze the results securely. IPFS's decentralized and distributed protocol enables faster and more resilient data sharing compared to traditional centralized servers.

  1. Ethernity Cloud Nodes

EC Nodes play a pivotal role in the protocol and carry out the following steps:

Sending Available Node Resources to the Blockchain: EC Nodes use the EC Smart Contract to send information about their available resources to the blockchain. This information is crucial for the task request matching process.

Task Execution Process: EC Nodes initiate the task execution process by downloading the binaries and encrypted data from Decentralized Storage.

Managing Task Processing in Trusted Execution Environment (TEE) Enclaves: EC Nodes send task request metadata and encrypted input data to the Trusted Execution Environment (TEE) enclave for secure processing. They also perform mutual attestation through CAS (Configuration and Attestation Service). Upon completion, encrypted results are uploaded to Decentralized Storage for user access.

  1. Trusted Execution Environment (TEE) Enclaves

The TEE enclaves represent the secure execution environment where all encrypted user tasks are sent for execution. Once the execution is complete, the encrypted results are propagated back to the dApp user, ensuring confidentiality and security. The technologies powering the enclaves are confidential computing technologies like Intel SGX, AMD SEV, ARM TrustZone

  1. Configuration and Attestation Service (CAS)

CAS plays a critical role in the ecosystem by registering binaries running within it. Moreover, CAS provides the required environment configuration to ensure consistent generation of Proof of Execution signatures within the enclaves, enhancing the integrity and security, while allowing the decentralization of the execution process across the whole ecosystem.

Last updated