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. Additionally, I will adhere to all local & regional laws & regulations that may relate to my role as a business partner, organization, notary, allocator, or other operating entity
Acknowledge
Type of Allocator and RFA List
Automated - Novel pathway
Allocator Description
We will be optimising primarily based on Proof of Payment, according to "Allocator which awards DataCap to Storage Providers who can prove that they have real deals with paying customers. " This.
On this basis, combined with the actual application, we will verify two aspects of the applicant's information,
first, proof of co-operation between the two parties: this proof can be chat records, co-operation contracts, co-operation agreements and so on can prove that the two sides of the proof of co-operation relationship.
Second, the two sides of the transaction records: this record can be a bank card, Alipay, WeChat, USDT and so on the transfer of records to prove that the two sides of the proof of money transfers.
Contributions to EcosystemProduce educational materials,Data Stewardship: Curate and provide high-quality datasets to be stored on the Filecoin network, enhancing the overall value and utility of the network.
Client promise/attestation,Manual verification,Proof of provenance
Description of client diligence
1、First of all, we will verify the applicant's identity, verification methods include: requesting customers to confirm by mail, provide relevant documents to prove the qualifications of the enterprise, and build trust through the way of telephone callbacks.
2、At present, because we are not through the automated tool route, so for the time being we do not provide automated route verification.
3、We mainly target storage providers, we will require them to provide proof of cooperation with paying customers and proof of payment, in addition, rivtower has developed a product called rivtrust, we are currently studying how to use the product to verify the authenticity of customer data ownership.
4、we will collect at least three aspects of the proof of documents: 1, proof of data owners 2, proof of co-operation in data transactions 3, proof of the flow of data transactions. In order to avoid any privacy leakage, we will give these documents to the governance team in the form of a private email when they need to review them.
Type of data
Private encrypted with on-chain deal pricing,Public, open, and retrievable
Description of Data Diligence
First of all, we would like to start by stating that our channel is currently geared towards service providers of storage, so it is the storage service providers who are in direct contact with us:
1, we will require the storage service providers contacted by the customer to provide data to prove cooperation documents
2、We will first make a statement that the content of the data must comply with local legal requirements, and leave a message prompting disclaimer content
3、We will ask the storage provider to provide a small amount of data files, we will sample the data before the quota allocation to investigate whether the data is compliant, after the quota allocation, we will randomly sample the chain (if the public data we will directly disclose, if the private data we will save the data files to prove)
4、At present, the screening is mainly done manually
5、During the audit process, we can save and provide the following proofs: data co-operation documents, github message records including exemptions, and data sampling results.
Data Preparation
Client-provided
Replicas required, verified by CID checker
4+
Distribution required
Single region of SPs
Number of Storage Providers required
4+
Retrieval Requirements
Data retrievable over other standard. Based on the current problems of spark, we would like to do some optimisation based on spark:
1, first we will test the connectivity of the nodes, public data must be distributed on connectable nodes
2、We will refer to the value of spark, if the value of spark is normal we will consider the node compliant.
3, if the sprak value is not normal, we will conduct manual retrieval test to verify, if the manual retrieval is normal, then the node supports retrieval, we will further review the ratio of retrieval and will test the records publicly
Allocation Tranche Schedule TypeManual or other allocation schedule.
The rules for allocation will be based primarily on weekly applications:
The first allocation will be 25 per cent of the weekly application volume.
The second allocation will be 50 per cent of the weekly number of applications.
The third allocation will be 100% of the weekly applications.
Subsequent allocations will be made on the basis of 100% of the weekly applications, with the amount delegated not exceeding 1 PiB at any one time.
Will you use FIDL tooling, such as allocator.tech and other bots?
Number of clients,Amount of data onboarded, daily & aggregate,Retrievability of data,Speed of allocations (TTD)
Timeline to begin allocating to clients
1 week from RKH approval
Funnel: Expected DataCap usage over 12 months
75-100PiB
Risk mitigation strategies
1、First of all, if we find that the customer has violated the law during the review process, we will immediately stop the issuance of credits.
2、We will ask the customer to follow the principle of early disclosure, and after the issuance of the quota will be carried out within a week of a check, the storage service provider will have a week to make adjustments, more than the time to stop the issuance of the quota
Dispute Resolutions
1、First of all, we will provide evidence in github within a week.
2、We will speak at the first meeting of the notary public after the dispute if we have the opportunity.
Compliance Audit Check
1、Provide sample reports
2、links to dashboards
3、specific data proofs
Compliance Report content presented for audit
Success metric: Proof of Payments from clients,Success metric: onchain report of data onboarded,Success metric: onchain data report,Client Diligence: Client statements, client provided verification,Client Diligence: Legal Review documents,Client Diligence: KYC/KYB report on clients,Data Compliance: Data Samples,Data Compliance: Manual report,Compliance: CID report.
Connections to Filecoin Ecosystem
Big data contributor,Event sponsor,Developer,Code contributor
Allocator Application
Application Number
rec2hOEdgZZoNCtVf
Organization Name
Rivtower
Organization On-chain Identity
f1stjz2inu3og7qm3jgwnshcx37tgjpydyluxgnea
Allocator Pathway Name
Allocator-Rivtower
Github PR Number
66
Region of Operation
Asia minus GCR,Greater China Region,North America
GitHub ID
Rivtower-work
On-chain address
I have a multisig I want to provide now
Type of Allocator
Novel allocator not on RFA
Filecoin Community Agreement
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. Additionally, I will adhere to all local & regional laws & regulations that may relate to my role as a business partner, organization, notary, allocator, or other operating entity Acknowledge
Type of Allocator and RFA List
Automated - Novel pathway
Allocator Description
We will be optimising primarily based on Proof of Payment, according to "Allocator which awards DataCap to Storage Providers who can prove that they have real deals with paying customers. " This. On this basis, combined with the actual application, we will verify two aspects of the applicant's information, first, proof of co-operation between the two parties: this proof can be chat records, co-operation contracts, co-operation agreements and so on can prove that the two sides of the proof of co-operation relationship. Second, the two sides of the transaction records: this record can be a bank card, Alipay, WeChat, USDT and so on the transfer of records to prove that the two sides of the proof of money transfers.
Contributions to EcosystemProduce educational materials,Data Stewardship: Curate and provide high-quality datasets to be stored on the Filecoin network, enhancing the overall value and utility of the network.
Monetization and Fee structure
None.
Target Clients
Commercial/Enterprise,Open/Public,Other,Individuals Storage Providers
Client Diligence Check
Client promise/attestation,Manual verification,Proof of provenance
Description of client diligence
1、First of all, we will verify the applicant's identity, verification methods include: requesting customers to confirm by mail, provide relevant documents to prove the qualifications of the enterprise, and build trust through the way of telephone callbacks. 2、At present, because we are not through the automated tool route, so for the time being we do not provide automated route verification. 3、We mainly target storage providers, we will require them to provide proof of cooperation with paying customers and proof of payment, in addition, rivtower has developed a product called rivtrust, we are currently studying how to use the product to verify the authenticity of customer data ownership. 4、we will collect at least three aspects of the proof of documents: 1, proof of data owners 2, proof of co-operation in data transactions 3, proof of the flow of data transactions. In order to avoid any privacy leakage, we will give these documents to the governance team in the form of a private email when they need to review them.
Type of data
Private encrypted with on-chain deal pricing,Public, open, and retrievable
Description of Data Diligence
First of all, we would like to start by stating that our channel is currently geared towards service providers of storage, so it is the storage service providers who are in direct contact with us: 1, we will require the storage service providers contacted by the customer to provide data to prove cooperation documents 2、We will first make a statement that the content of the data must comply with local legal requirements, and leave a message prompting disclaimer content 3、We will ask the storage provider to provide a small amount of data files, we will sample the data before the quota allocation to investigate whether the data is compliant, after the quota allocation, we will randomly sample the chain (if the public data we will directly disclose, if the private data we will save the data files to prove) 4、At present, the screening is mainly done manually 5、During the audit process, we can save and provide the following proofs: data co-operation documents, github message records including exemptions, and data sampling results.
Data Preparation
Client-provided
Replicas required, verified by CID checker
4+
Distribution required
Single region of SPs
Number of Storage Providers required
4+
Retrieval Requirements
Data retrievable over other standard. Based on the current problems of spark, we would like to do some optimisation based on spark: 1, first we will test the connectivity of the nodes, public data must be distributed on connectable nodes 2、We will refer to the value of spark, if the value of spark is normal we will consider the node compliant. 3, if the sprak value is not normal, we will conduct manual retrieval test to verify, if the manual retrieval is normal, then the node supports retrieval, we will further review the ratio of retrieval and will test the records publicly
Allocation Tranche Schedule TypeManual or other allocation schedule.
The rules for allocation will be based primarily on weekly applications: The first allocation will be 25 per cent of the weekly application volume. The second allocation will be 50 per cent of the weekly number of applications. The third allocation will be 100% of the weekly applications. Subsequent allocations will be made on the basis of 100% of the weekly applications, with the amount delegated not exceeding 1 PiB at any one time.
Will you use FIDL tooling, such as allocator.tech and other bots?
Yes, all available tools
GitHub Bookkeeping Repo Link
https://github.com/Rivtower-work/Allocator-Rivtower
Success metrics
Number of clients,Amount of data onboarded, daily & aggregate,Retrievability of data,Speed of allocations (TTD)
Timeline to begin allocating to clients
1 week from RKH approval
Funnel: Expected DataCap usage over 12 months
75-100PiB
Risk mitigation strategies
1、First of all, if we find that the customer has violated the law during the review process, we will immediately stop the issuance of credits. 2、We will ask the customer to follow the principle of early disclosure, and after the issuance of the quota will be carried out within a week of a check, the storage service provider will have a week to make adjustments, more than the time to stop the issuance of the quota
Dispute Resolutions
1、First of all, we will provide evidence in github within a week. 2、We will speak at the first meeting of the notary public after the dispute if we have the opportunity.
Compliance Audit Check
1、Provide sample reports 2、links to dashboards 3、specific data proofs
Compliance Report content presented for audit
Success metric: Proof of Payments from clients,Success metric: onchain report of data onboarded,Success metric: onchain data report,Client Diligence: Client statements, client provided verification,Client Diligence: Legal Review documents,Client Diligence: KYC/KYB report on clients,Data Compliance: Data Samples,Data Compliance: Manual report,Compliance: CID report.
Connections to Filecoin Ecosystem
Big data contributor,Event sponsor,Developer,Code contributor
Slack ID
Rivtower