-
Notifications
You must be signed in to change notification settings - Fork 62
[DataCap Application] <Architectural design> - all architectural design Co., Ltd. #2082
Comments
Thanks for your request!
|
Thanks for your request! A Governance Team member will review the information provided and contact you back pretty soon. |
@Designguy1, could you please clarify the public benefit that this dataset will bring? Additionally, it is important to know if you are willing to compensate the storage providers who will be storing this business data on your behalf. |
We re-uploaded the case, here are our design pictures, CAR, etc. We are committed to creating architectural aesthetics and bringing different beautiful experiences to customers https://drive.google.com/drive/folders/1x1EMlhaaNxs_o3jx8pUuR6by6mfWukw2?usp=sharing |
@Sunnyiscoming Sorry, did I miss something?it seems like you haven't been through us |
@Designguy1 I am sorry I do not see the added value to the Filecoin ecosystem here. |
Don't bring out the saying that "the company's data has no value, only public data has value",Last year @dkkapur has expressed its opinion |
Best practice for storing large datasets includes ideally, storing it in 3 or more regions, with 4 or more storage provider operators or owners. |
Look forward your reply. More information wanted.
|
|
While it's understandable that a design company, particularly one involved in decoration and construction, generates a significant amount of data on a daily basis, it is important to clarify who finds this data valuable. As far as I can assess, it appears that you are a business seeking to store your proprietary business data on Filecoin, utilizing the community-granted multiplier to store it at minimal cost. However, this usage does not align with the intended purpose of FIL+. FIL+'s primary objective is to store open and public data, thereby adding value to the entire ecosystem. By promoting open data storage, we aim to encourage wider usage and attract clients who will eventually contribute to the sustainability of our services through payment. Considering this, it is unclear how your data holds value for anyone beyond your own business. I fail to see any evidence or convincing argument supporting its broader significance. Adding to this, this is your first application on FIL+ ever, you need to build trust with the community first: Here are some steps you can take:
By following these steps, you can build trust within the community and demonstrate the worthiness of your data. |
We don't need to discuss the issue of "corporate data has no value, only public data has value".Because there is no need for discussion. @dkkapur Conclusions have been drawn. Therefore, your thoughts will not affect the @raghavrmadya @Sunnyiscoming and the result |
Who will be the SP's with presence outside of China if i may ask? All the mentioned miners are located in China. Can you read the FIL+ rules here please A small snapshot from it: If a client wants to onboard more than 5+PiBs, the recommendation would be to start with a few applications and earn trust from the community. Having a positive reputation and proving to the community first by onboarding a smaller amount of data will help anyone who wants to onboard massive amounts of data much faster and smoother. Stored data should be readily retrievable on the network and this can be regularly verified (though the use of manual or automated verification that includes retrieving data from various miners over the course of the DataCap allocation timeframe). At this time all LDNs may have full retrievability, but it is not required. Each project should specify what portion of the data is retrievable and provide justification. From there notaries can decide during the due diligence phases if the client’s application is justifiable and can agree to sign it or not. There should be no open disputes in the Fil+ ecosystem against the client during the time that the application is open for review With the current tooling and workflow, the recommendation would be to use a different address for every application. However, if you cannot, know that the workaround requires manual attention. We strongly do not recommend this due to delays created and mixed math for subsequent allocation issues. In the short term, we can support this. Please notify Simon Kim and add this to your LDN application if you absolutely have to go down this path and share why. Best practice for storing large datasets includes ideally, storing it in 3 or more regions, with 4 or more storage provider operators or owners, and having at least 5 replicas of the dataset. No more than one replica should be stored with one SP ID, and if the data cannot leave a particular geographic boundary, then it is expected that replication will still happen across different locations (cities, datacenters, etc.). Each storage provider should not exceed 30% of the total datacap that the client was allocated and the storage provider should have published its public IP address. If you cannot follow these practices due to policy or any other issues, you may explain your case in the application and provide to the community what method you can do instead. These are recommendations and not strict rules that every client must follow. Regarding cases of abusing the program’s incentive structure, notaries should not be signing their own applications. For the program to work, each stakeholder will need to play their parts in a truthful manner. Datasets that have been stored previously, may be allowed to be copied over time on chain. This can provide value to the network if it is a new team, a new datacenter, and a new geopolitical region. However, storage providers should not be storing more than 20% of the duplicated data. While same datasets may help the network, this should not be a reason for client’s to onboard the same exact dataset repeatedly, client’s should explicitly justify their reasoning on why the repeated dataset should be onboarded. To help notaries more efficiently complete their due diligence process, clients should justify their reasoning of the amount of DataCap that you are applying for will help notaries with their due diligence process. Clients should explain how their dataset is useful for the network, and visible proof of the size of the data that is being onboarded. |
Thank you, we decided to look for more overseas sp, we will reply you as soon as possible |
Hello @Designguy1 per the new guidelines filecoin-project/notary-governance#922 for Open Dataset applicants, please complete the following Fil+ registration form to identify yourself as the applicant and also please add the contact information of the SP entities you are working with to store copies of the data. This information will be reviewed by Fil+ Governance team to confirm validity toward the Fil+ guideline of a distributed storage plan and then the application will be triggered for notary review. Let us know if you have any questions. |
This application has not seen any responses in the last 10 days. This issue will be marked with Stale label and will be closed in 4 days. Comment if you want to keep this application open. |
Hello @Filplus-govteam we have submitted the form. |
Thank you for sharing SP details @Designguy1 The following SP Entity info was shared: |
The reports look good.The client was cooperative with due diligence. |
checker:manualTrigger |
DataCap and CID Checker Report Summary1Retrieval Statistics
Storage Provider Distribution✔️ Storage provider distribution looks healthy. Deal Data Replication✔️ Data replication looks healthy. Deal Data Shared with other Clients2✔️ No CID sharing has been observed. Full reportClick here to view the CID Checker report. Footnotes |
Not sure why the bot is doing only 1 or 2 checks. But the rate is good anyway. Also tried retrieval by myself, also successful with a decent transmitting rate. The distribution looks ok. No dispute. Will support for this round. |
Request ApprovedYour Datacap Allocation Request has been approved by the Notary Message sent to Filecoin Network
Address
Datacap Allocated
Signer Address
Id
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebg5txu53zkbmogopdjip74m3lgiol3aja6ix7lul7cy7hlqb2ico |
DataCap Allocation requestedRequest number 3Multisig Notary address
Client address
DataCap allocation requested
Id
|
Stats & Info for DataCap AllocationMultisig Notary address
Client address
Rule to calculate the allocation request amount
DataCap allocation requested
Total DataCap granted for client so far
Datacap to be granted to reach the total amount requested by the client (5PiB)
Stats
|
checker:manualTrigger |
DataCap and CID Checker Report Summary1Retrieval Statistics
Storage Provider Distribution✔️ Storage provider distribution looks healthy. Deal Data ReplicationDeal Data Shared with other Clients2Full reportClick here to view the CID Checker report. Footnotes |
CID REPORT The following SP Entity info was shared: Seeing the SPs matching the original list. However, also seeing f02252097 who was not listed and is storing 26%. How is this @Designguy1? Also seeing CID Sharing |
Client self closed this. @raghavrmadya Let's make a note to monitor applications with these SPs, including f02252097 |
Data Owner Name
Guangzhou All Architectural Design Co., Ltd.
What is your role related to the dataset
Dataset Owner
Data Owner Country/Region
China
Data Owner Industry
Resources, Agriculture & Fisheries
Website
http://www.a.cn/
Social Media
Total amount of DataCap being requested
5PiB
Expected size of single dataset (one copy)
500TiB
Number of replicas to store
10
Weekly allocation of DataCap requested
800TiB
On-chain address for first allocation
f1xjdq6fopvir2ikm4vcfrchhkwajxq57xj3kzzky
Data Type of Application
Public, Open Commercial/Enterprise
Custom multisig
Identifier
No response
Share a brief history of your project and organization
Is this project associated with other projects/ecosystem stakeholders?
No
If answered yes, what are the other projects/ecosystem stakeholders
No response
Describe the data being stored onto Filecoin
Where was the data currently stored in this dataset sourced from
My Own Storage Infra
If you answered "Other" in the previous question, enter the details here
No response
How do you plan to prepare the dataset
IPFS, lotus, singularity
If you answered "other/custom tool" in the previous question, enter the details here
No response
Please share a sample of the data
Confirm that this is a public dataset that can be retrieved by anyone on the Network
If you chose not to confirm, what was the reason
No response
What is the expected retrieval frequency for this data
Monthly
For how long do you plan to keep this dataset stored on Filecoin
1.5 to 2 years
In which geographies do you plan on making storage deals
Greater China, Asia other than Greater China, North America, Europe
How will you be distributing your data to storage providers
Cloud storage (i.e. S3), HTTP or FTP server, Shipping hard drives, Lotus built-in data transfer
How do you plan to choose storage providers
Slack, Filmine
If you answered "Others" in the previous question, what is the tool or platform you plan to use
No response
If you already have a list of storage providers to work with, fill out their names and provider IDs below
No response
How do you plan to make deals to your storage providers
Boost client, Lotus client, Singularity
If you answered "Others/custom tool" in the previous question, enter the details here
No response
Can you confirm that you will follow the Fil+ guideline
Yes
The text was updated successfully, but these errors were encountered: