Published in


4EVERLAND Storage Node Entry Network Design

4EVERLAND Storage Nodes Introduction

The 4EVERLAND data node layer is based on a globally distributed network of collaborative nodes on top of IPFS, which will form a large IPFS swarm cluster-based network. The node program utilises the technical functionality of TEE-based Trusted Authentication, which aims to verify the node’s on-boarding process and program reliability. Nodes throughout the network are required to undertake the following role functions:

  1. Pin some specific IPFS CID data
  2. Verify the program functionality of other nodes in the network
  3. Regular reporting of data storage on nodes
  4. Simultaneous storage of challenge reports to other nodes and mutual verification that the reported data is logical

In summary, the nodes are organised as shown in the diagram:

Which consists of:

  • PoSC of TEE:PoSC:Proof of Storage challenge, is a TEE based implementation of the node verifiable program.
  • Data Storage: refers to IPFS storage, the terms are tied to each other.

Introduction to PoSC

The nodes in the network collaboratively store some characteristic cid data and therefore require a PoSC (Proof of Storage Challenge) mechanism to verify that the nodes have stored this data according to the expected logic. The node will periodically perform data spot checks on the node’s stored data according to some pre-defined logic. Each such spot-check will result in a report that will be broadcast across the network to other nodes, who will verify the legitimacy of the report and store it locally, which will then be used as a basis for rewarding and punishing the node.

Onboarding process for nodes

The entire node entry process is roughly as follows:

  1. The node program generates a public-private key pair in the TEE enclave area.
  2. Generate Quote and create_attestation_report and send to IAS for authentication.
  3. IAS returns the result of the verification report.
  4. check_mr_enclave is compared with the value in the chain after the verification, if it does not match, the program returns directly.
  5. check_mr_enclave check passed and store the public and private keys and other information.
  6. Subscribe to IPFS message notification topics.
  7. Subscribe to the chain cid storage contract, the subsequent need to do some processing of these CID.
  8. listen to messages passed by other nodes, such as synchronization of reports, public key requests, cid synchronization messages, etc.
  9. Process the different messages according to the predefined logic, the message field types are roughly as follows:

Storage Reports

The node listens for contract events in the storage cid chain, triggering corresponding log processing events (e.g., insert, remove cid), and the node generates a storage proof report according to a certain “periodicity”. The storage report is signed with a local key and then broadcast to other nodes across the network. The approximate process is as follows:



4EVERLAND is a Web 3.0 cloud computing platform that integrates storage, computing, and network core capabilities. It aims to help the user to make a smooth leap from Web 2.0 to Web 3.0 and become the infrastructure for millions of Web 3.0 developers and applications.

Join 4EVERLAND community:

Website | Twitter | Telegram | Discord | Reddit | Medium| Email



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store


4EVERLAND is a Web3.0 cloud computing platform with global acceleration, privacy protection, distributed storage, and other technical features.