Dataswap

Dataswap storage provides a complete solution through dataset auditing, matching, automatic datacap allocation, and storage.

The Dataset module, specifically DatasetMetadata, DatasetProof, and DatasetVerification, plays a crucial role in implementing the Trustless Notary.

• DatasetMetadata

1. Storage Client (SC) submits dataset information such as title, industry category, name, description, data source, owner, creation time, creator, modification history, etc., to the dataset contract.
2. Storage Client (SC) submits Datacap collateral to the Supervisory Contract based on the dataset's storage capacity to obtain access rights to the Datacap.

• DatasetProof

1. The Data Preparer (DP) utilizes data proof tools (designed based on Dataset Consistency Algorithms) to generate dataset proofs, specifically the dataset proof Merkle tree.
2. DP submits the dataset proof to the dataset contract.

• DatasetVerification

1. Data Auditor (DA) uses data proof verification tools (designed based on Dataset Consistency Algorithms) to generate dataset challenge proof verification information.
2. DA submits the dataset challenge proof verification information to the dataset contract.
3. After all DAs vote to the governance contract.the governance contract determines the final approval of the Dataset based on the audit results from all DAs.

In summary, Dataswap storage, through its dataset module components (DatasetMetadata, DatasetProof and DatasetVerification), addresses the specific design requirements of a Trustless Notary as described in the Filecoin ideation article.

The Matching module implements decentralized matchmaking functionality.

• Data Preparer (DP) participate in auctions within the matching contract to store their prepared datasets.
• Data Preparer (DP) need to ensure that their data is transferred (if the transaction is successful, they will send the data) to the winning SP. DP also needs to assist SP in completing the data onboarding process to receive their DP fee.
• SPs pre-stake funds in the supervisory contract to participate in dataset auctions and obtain validated dataset storage transactions.
• Storage Provider (SP) who bid during the matching period commit to completing data onboarding within a specific window after the auction ends. If they fail to do so, they forfeit their collateral.

The storage module implements dataset onboarding management.

• When a Storage Provider (SP) wins the auction, the storage contract automatically approves Datacap for the SC without requiring any additional authorization.
• After the Storage Provider (SP) completes the storage, they submit the Claim ID to the storage contract to ensure the correct onboarding of data. If there are non-compliant data onboarding issues, the storage contract will halt Datacap approval.

you can refer to this link https://docs.google.com/presentation/d/1Lan7hrBrV1XgDa0V-7g6-TQXwfGl3xVNH90otsDZT9A/edit#slide=id.g1f87997393_0_782

And Dataswap met the requirement about this docment ,https://docs.google.com/document/d/1KLR6nZ8ic4ARj3J46XsxSE_b1RpDP_z3JBKL4alHGGw/edit?pli=1