📂

Public project doc: Storage Metrics DAO

Protocol Overview

We have an initial consortium of N auditor parties A_1,...,A_n. At this stage, the aim of these nodes is to scan the network according to storage deals that are on-chain (each storage deal needs to provide retrieval).

In particular, this means that parties being audited are essentially storage providers. In future versions of the protocol, we’ll open the possibility to any IPFS node to be audited. In order to do so we’ll put in place mechanisms like indices which will allow non-SP parties to be audited according to what they claim to store and keep available for retrieval

Step 1: Initialization

Auditor List is in a Smart Contract. A commitment to the Auditors list is stored onchain.

Parties involved in Step 1:

• Auditors (passive)
• Smart Contract on-chain storing the Auditors list

Step 2: Survey Protocol

Survey protocol starts at epoch1_start and ends at epoch1_deadline

• Each Auditor A_i, for each storage_deal on a CID cid queries the correspondent storage provider SP_j and checks
  • Time to first byte (Metric 1)
  • Average Retrieval Speed (Metric 2)
  • Retrieval Success (Metric 3)
• According to the survey results, each auditor A_i builds a local table of the form
  • T_i = [SP_ID , Metric 1, Metric 2, Metric 3]
• Local table T is committed
  • A_i.Commit = Comm(T_i) [note: here and below, we can either use Comm Sha256 or a more structured VC]