v5 Notary Allocator Application: dataswap

[Kennynauh]

v5 Notary Allocator Application

To apply to be an allocator, organizations will submit one application for each proposed pathway to DataCap. If you will be designing multiple specific pathways, you will need to submit multiple applications.

Please complete the following steps:

1. Fill out the information below and create a new GitHub Issue

1. Notary Allocator Pathway Name (This can be your name, or the name of your pathway/program. For example "E-Fil+"):dataswap
2. Organization Name:dataswap
3. On-chain address for Allocator (Provide a NEW unique address. During ratification, you will need to initialize this address on-chain): TBD
4. Country of Operation (Where your organization is legally based): China
5. Region of Operation (What region will you serve?): All regions
6. Type of Allocator, diligence process: (Automated/programmatic, Market-based, or Manual (human-in-the-loop at some phase): Automatic
7. DataCap requested for allocator for 12 months of activity (This should be an estimate of overall expected activity. Estimate the total amount of DataCap you will be distributing to clients in 12 months, in TiB or PiB):200 PiB

2. Access allocator application (download to save answers)

Click link below to access a Google doc version of the allocator application that can be used to save your answers if you are not prepared to fully submit the application in Step 3. https://docs.google.com/document/d/1-Ze8bo7ZlIJe8qX0YSFNPTka4CMprqoNB1D6V7WJJjo/copy

3. Submit allocation application

Clink link below to access full allocator questionnaire and officially submit your answers:
https://airtable.com/appvyE0VHcgpAkt4Z/shrQxaAIsD693e1ns

Note: Sections of your responses WILL BE posted back into the GitHub issue tracking your application.
The final section (Additional Disclosures) will NOT be posted to GitHub, and will be maintained by the Filecoin Foundation.
Application information for notaries not accepted and ratified in this round will be deleted.

[ghost]

Basic Information

1. Notary Allocator Pathway Name:
Dataswap

2. Organization:
Dataswap

3. On Chain Address for Allocator:
TBD

4. Country of Operation:
China

5. Region(s) of operation:
Africa , Asia minus GCR, Greater China, Europe, Oceania, Japan, North America, South America, Other

6. Type of Allocator:
Automatic

7. DataCap requested for allocator for 12 months of activity:
200 PiB

8. Is your allocator providing a unique, new, or diverse pathway to DataCap? How does this allocator differentiate itself from other applicants, new or existing?:
Dataswap storage provides a complete solution through dataset auditing, matching, automatic datacap allocation, and storage.
Flow:
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.
3. The Data Preparer (DP) utilizes data proof tools (designed based on Dataset Consistency Algorithms) to generate dataset proofs, specifically the dataset proof Merkle tree.
4. DP submits the dataset proof to the dataset contract.
5. Data Auditor (DA) uses data proof verification tools (designed based on Dataset Consistency Algorithms) to generate dataset challenge proof verification information.
6. DA submits the dataset challenge proof verification information to the dataset contract.
7. 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.
The Matching module implements decentralized matchmaking functionality.
8.Data Preparer (DP) participate in auctions within the matching contract to store their prepared datasets.
9. 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.
10. SPs pre-stake funds in the supervisory contract to participate in dataset auctions and obtain validated dataset storage transactions.
11. 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.
12. When a Storage Provider (SP) wins the auction, the storage contract automatically approves Datacap for the SC without requiring any additional authorization.
13. 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
https://docs.google.com/presentation/d/1Lan7hrBrV1XgDa0V-7g6-TQXwfGl3xVNH90otsDZT9A/edit#slide=id.g1f87997393_0_835
And
https://github.com/dataswap/specs

9. As a member in the Filecoin Community, I acknowledge that I must adhere to the Community Code of Conduct, as well other End User License Agreements for accessing various tools and services, such as GitHub and Slack.:
Acknowledge

Client Diligence

10. Who are your target clients?:
Individuals learning about Filecoin, Small-scale developers or data owners

11. Describe in as much detail as possible how you will perform due diligence on clients. If you are proposing an automated pathway, what diligence mechanism will you use to determine client eligibility?:
1.Customers provide basic information to the blockchain through the dataswap contract.Such as dataset title, industry category, name, description, data source, owner, creation time, creator, modification history, etc.
2.Ensure data authenticity through dataswap Trustless notary.
3.Storage clients stake FIL to contract for obtaining datacap upon joining.
4.Assessing customer eligibility through a reputation system based on evaluating the reputation of storage clients.
You can refer to
https://docs.google.com/presentation/d/1Lan7hrBrV1XgDa0V-7g6-TQXwfGl3xVNH90otsDZT9A/edit#slide=id.g1f87997393_0_835
And
https://github.com/dataswap/specs

12. Please specify how many questions you’ll ask, and provide a brief overview of the questions.:
Dataswap is a trustless notary system where clients obtain datacap allocation rights through contract pledging. It automatically completes proof and verification of client data and storage consistency through contracts and provides rewards for community contributions as well as a mechanism for penalizing malicious behavior. All of this is achieved through the Dataswap contract, which forms a widely verified list of mechanisms for community consensus without the need for authentication.

13. Will you use a 3rd-party Know your client (KYC) service?:
Yes.

14. Can any client apply to your pathway, or will you be closed to only your own internal clients? (eg: bizdev or self-referral):
Any client can apply the pathway

15. How do you plan to track the rate at which DataCap is being distributed to your clients?:
Dataswap provides an open-source API and develops and maintains a public dashboard to display the distribution of DataCap to customers. It offers real-time progress updates on the allocation and utilization of DataCap, obtaining statistics directly from the blockchain. This ensures that our DataCap allocation and distribution processes are highly transparent and can be audited by any relevant party. You can refer to explorer (https://github.com/dataswap/explorer) http://www.dataswap.info/

Data Diligence

16. As an operating entity in the Filecoin Community, you are required to follow all local & regional regulations relating to any data, digital and otherwise. This may include PII and data deletion requirements, as well as the storing, transmit:
Acknowledge

17. What type(s) of data would be applicable for your pathway?:
Public Open Dataset (Research/Non-Profit), Public Open Commercial/Enterprise

18. How will you verify a client’s data ownership? Will you use 3rd-party KYB (know your business) service to verify enterprise clients?:
Yes. For public datasets, we will require customers to provide source information. For enterprise data, the applicant should provide proof of data ownership.

19. How will you ensure the data meets local & regional legal requirements?:
We require customers to pledge that the data stored on the Filecoin network is public, compliant, and accessible to everyone. Customers, upon application, commit to ensuring that the data complies with local and regional legal requirements. We have a comprehensive legal team with expertise in data protection and privacy laws relevant to each operational region. We conduct a thorough assessment of data protection laws in the cooperating client's region to understand specific requirements and any updates.

20. What types of data preparation will you support or require?:

1. The following tools will be provided: singularity, go-car, go-metadata. 2. Yes, the tool will support

21. What tools or methodology will you use to sample and verify the data aligns with your pathway?:
Dataset Consistency Algorithm (https://github.com/dataswap/specs/blob/main/algorithms/README.md)

Data Distribution

22. How many replicas will you require to meet programmatic requirements for distribution?:
5+

23. What geographic or regional distribution will you require?:
Dataswap fully complies with fil+ rules and requirements,Support THREE OR MORE regions including unique geopolitical/language coverage, each replica at different physical location, no VPN, different SP owner operators,On the basis of meeting fil+'s current rules, customers can customize more requirements

24. How many Storage Provider owner/operators will you require to meet programmatic requirements for distribution?:
5+

25. Do you require equal percentage distribution for your clients to their chosen SPs? Will you require preliminary SP distribution plans from the client before allocating any DataCap?:
Through the Dataswap contract, clients are required to submit detailed dataset allocation requirements when submitting datasets to the contract. These dataset allocation requirements will be transparently recorded in the contract and will constrain the allocation to comply with the Fil+ mechanism. At the same time, clients are allowed to customize their requirements based on this mechanism. Subsequent DataCap allocations to SPs are automatically carried out according to the contract mechanism, taking into account the dataset allocation requirements and SP's allocation collateral.

26. What tooling will you use to verify client deal-making distribution?:
Dataswap, as trustless notary system, inherently ensures the consistency of raw data and Filecoin storage data. It naturally prevents duplicate storage of data within the Dataswap system. Additionally, it provides the Dataswap explorer open-source tool for real-time monitoring of Dataswap contract information. Dataswap relies on DP proofs from clients and SP collateral commitments to ensure CID validity. Anyone can perform CID proof and verification using open-source Dataswap CLI tools, supplemented by other community open-source tools such as datacapstats.io CID checker for assistance.

27. How will clients meet SP distribution requirements?:
Yes, implemented through dataswap contract, using the data consistency challenge proof mechanism to ensure the consistency and correctness of data storage Pls refer to https://github.com/dataswap/specs/tree/main/algorithms

28. As an allocator, do you support clients that engage in deal-making with SPs utilizing a VPN?:
not support

DataCap Allocation Strategy

29. Will you use standardized DataCap allocations to clients?:
Yes, standardized

30. Allocation Tranche Schedule to clients::
Initial Allocation: 5% of the requested DataCap total or 50% of the weekly allocation rate, whichever is smaller.
Second Allocation: 10% of the requested DataCap total or 100% of the weekly allocation rate, whichever is smaller.
Third Allocation: 20% of the requested DataCap total or 200% of the weekly allocation rate, whichever is smaller.
Fourth Allocation: 40% of the requested DataCap total or 400% of the weekly allocation rate, whichever is smaller.
...
The maximum allocation does not exceed 2 PiB.
Distribution rules are set by the dataswap fil+ governance contract

31. Will you use programmatic or software based allocations?:
Yes, standardized and software based

32. What tooling will you use to construct messages and send allocations to clients?:
Issued automatically by the Dataswap contract.

33. Describe the process for granting additional DataCap to previously verified clients.:
Dataswap Contract， Clients need to go through the process again according to Dataswap contract requirements.

34. Describe in as much detail as possible the tools used for: • client discoverability & applications • due diligence & investigation • bookkeeping • on-chain message construction • client deal-making behavior • tracking overall allocator health • disput:
 client discoverability & applications
Dataswap tools，and dataswap blockchain explorer
http://www.dataswap.info/
• due diligence & investigation
Da role of Dataswap contract,
https://github.com/dataswap/specs/tree/main/algorithms
• bookkeeping
explorer (https://github.com/dataswap/explorer)
http://www.dataswap.info/
• on-chain message construction
explorer (https://github.com/dataswap/explorer)
http://www.dataswap.info/
• client deal-making behavior
explorer (https://github.com/dataswap/explorer)
http://www.dataswap.info/

• tracking overall allocator health
explorer (https://github.com/dataswap/explorer)
http://www.dataswap.info/

• dispute discussion & resolution
explorer (https://github.com/dataswap/explorer)
http://www.dataswap.info/
And dataswap tools，dataswap smart contract

• community updates & comms *
Github，slack

Tools and Bookkeeping

35. Will you use open-source tooling from the Fil+ team?:
Yes,datacapstats.io filplus.storage filecoin.tools

36. Where will you keep your records for bookkeeping? How will you maintain transparency in your allocation decisions?:
The records are stored on-chain(dataswap contract) by the contract, ensuring public transparency.

Risk Mitigation, Auditing, Compliance

37. Describe your proposed compliance check mechanisms for your own clients.:
Based on the dataset consistency algorithm, it is possible to prove the consistency between the original dataset and the dataset stored on Filecoin
The distribution and tracking of Datacap are handled by the dataswap contract without the need for manual intervention.
You can refer to
https://github.com/dataswap/specs/tree/main/algorithms

38. Describe your process for handling disputes. Highlight response times, transparency, and accountability mechanisms.:
When disputes arise, utilize the dispute resolution process of dataswap.:
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.
4.When a valid dispute arises, the disputed party will be penalized, and the Data Auditor (DA) will receive a reward.
You can refer to https://docs.google.com/presentation/d/1Lan7hrBrV1XgDa0V-7g6-TQXwfGl3xVNH90otsDZT9A/edit#slide=id.g1f87997393_0_835
or
https://github.com/dataswap/specs

39. Detail how you will announce updates to tooling, pathway guidelines, parameters, and process alterations.:
Updates are released through GitHub, Slack, and other public channels.

40. How long will you allow the community to provide feedback before implementing changes?:
The submission of a proposal for significant updates is made through FIP, and the completion of community governance voting.
And Typically, we allow a minimum of 10 working days for everyone to vote and make decisions.

41. Regarding security, how will you structure and secure the on-chain notary address? If you will utilize a multisig, how will it be structured? Who will have administrative & signatory rights?:
The on-chain notary address is the dataswap contract address, and the contract possesses signatory rights, while the governance team has administrative authority.

42. Will you deploy smart contracts for program or policy procedures? If so, how will you track and fund them?:
The dataswap smart contracts are developed by us，there are our code link. https://github.com/dataswap https://github.com/unipackage

Monetization

43. Outline your monetization models for the services you provide as a notary allocator pathway.:
Dataswap is based on staking and algorithmic validation，Dataswap provides a comprehensive process through smart contracts, encompassing dataset auditing, dataset matching, and automated allocation of DataCap，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

44. Describe your organization's structure, such as the legal entity and other business & market ventures.:
Dataswap team(https://github.com/dataswap)

45. Where will accounting for fees be maintained?:
on-chain（dataswap contract）

Past Experience, Affiliations, Reputation

46. If you've received DataCap allocation privileges before, please link to prior notary applications.:
No

47. How are you connected to the Filecoin ecosystem? Describe your (or your organization's) Filecoin relationships, investments, or ownership.:
Team members are actively engaged in Filecoin, making significant contributions to the network over the long term. Currently, we are autonomously developing the ecosystem project dataswap. The system aims to address Trustless Notary, contributing to the healthy growth of Filecoin's network power. https://github.com/dataswap

48. How are you estimating your client demand and pathway usage? Do you have existing clients and an onboarding funnel?:
Dataswap provides a comprehensive process through smart contracts, encompassing dataset auditing, dataset matching, and automated allocation of DataCap. Users can check the status through the Dataswap explorer and interact with Dataswap contracts using Dataswap tools.

[kevzak]

Datacap Request for Allocator

Address

f03018562

Datacap Allocated

5PiB

[galen-mcandrew]

@Kennynauh We are working to get DataCap to the provided f4 address, but in the meantime can you please set up a new repo inside your GitHub organization? You provided a link to your org, but not to the specific repo that you want to use for bookkeeping. https://github.com/dataswap

[Kennynauh]

Thank you for the update. I've set up a new repository within our GitHub organization for bookkeeping purposes. You can find it here:

https://github.com/dataswap/datacapallocators

[filplus-bot]

The request has been signed by a new Root Key Holder

Message sent to Filecoin Network

bafy2bzacecmtpgkgdg3imf5iglyjvh6zkucrgly6jjzvpajmnrus4ktd4hqy4

You can check the status of the message here: https://filfox.info/en/message/bafy2bzacecmtpgkgdg3imf5iglyjvh6zkucrgly6jjzvpajmnrus4ktd4hqy4