Closed huahuabuer closed 10 months ago
Thanks for your request!
Heads up, you’re requesting more than the typical weekly onboarding rate of DataCap!
Thanks for your request! Everything looks good. :ok_hand:
A Governance Team member will review the information provided and contact you back pretty soon.
Total DataCap requested
5PiB
Expected weekly DataCap usage rate
200TiB
Client address
f1qreowipcbjnfjrpjxbyqnskhgxwbady7nx72o6q
f02049625
f1qreowipcbjnfjrpjxbyqnskhgxwbady7nx72o6q
100TiB
1a728b85-aa97-450d-9300-b9d12e2801e5
About KYC&KYB 1:Could you send an email to filplus-app-review@fil.org ? 2:How large is your existing dataset? How much is the data growth per month?
Thanks for your request!
Heads up, you’re requesting more than the typical weekly onboarding rate of DataCap!
@simonkim0515 @galen-mcandrew @raghavrmadya @Kevin-FF-USA Since the company name has changed recently, the organization information in the submitted information has been modified accordingly. Is it necessary to correct the status of the Issue?
@newwebgroup @Sunnyiscoming
Our company's external corporate email address is mipai-media@qq.com, you can check it from our company's official website https://www.todaysuccess.cn/. So we sent a KYC email from this mailbox, please check it.
Due to the nature of the company's business, our existing data volume is about 4-5PB, and about 500-800GB of various media data will be generated every day.
Total DataCap requested
5PiB
Expected weekly DataCap usage rate
200TiB
Client address
f1qreowipcbjnfjrpjxbyqnskhgxwbady7nx72o6q
f02049625
f1qreowipcbjnfjrpjxbyqnskhgxwbady7nx72o6q
100TiB
78cc7a7e-e179-49cc-9241-7592ccd5c503
Dear applicant,
Thank you for applying for datacap. As Filecoin FIL+ notary i am screening your application and conducting due diligence.
Looking at your application i have some questions: As you are brand new on Github and have no history of past applications it seems to me that applying for 5PB of datacap is a lot. One needs comprehensive knowledge of Filecoin, packing of data, distribution of data and all it's requirements coming with it. Are you brand new in the Filecoin space or have you applied for datacap in the past on different Github account names?
Can you show us visible proof of the size of your data and the storage systems you have there?
As last question i would like you to fill out this form to provide us with the necessary information to make a educated decision on your LDN request if we would like to support it.
Thanks!
It`s done in LDN#1278 and #1276 is not started yet. It will be start after #1277 totaly sealed.
Please disclose your next sealing plan, such as SPs and their distribution areas.
@Bitengine-reeta This project has been implemented on #1278 for few months, and so far more than 9 SPs from different regions have participated: f01986236 from US f01986229 from China, hubei f01964215 from Guangzhou f01986262 from China, Yichang f01771695 from HongKong f01732345 from HongKong
Since #1278 has entered the 5th round, and the data of our video platform is growing rapidly, we will start LDN #1276 #1277, and we will look for more SPs from different regions to join.
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacec2hnkk7p2rr4fu6lcpwmkdq3jezijgeldhl66kn2u6ocj43yp7ek
Address
f1qreowipcbjnfjrpjxbyqnskhgxwbady7nx72o6q
Datacap Allocated
100.00TiB
Signer Address
f1jyvhxp4kmwreo22ke4itspraznpudw3uqaink5i
Id
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacec2hnkk7p2rr4fu6lcpwmkdq3jezijgeldhl66kn2u6ocj43yp7ek
Can you tell me and show us how much data you have?
@stcouldlisa Thanks for attention~ As a media parent company, Jincheng Mingyuan's business is mainly for commercial video production and video creation platforms. Most of the data types that need to be stored are high-quality video data: https://www.xinpianchang.com/ https://www.todaysuccess.cn/a/cgal/page_1.html Our data volume has reached 1.5+PiB, and it is expected to store 6 backups to SPs in different regions
Your Datacap Allocation Request has been approved by the Notary
bafy2bzaced532dtmjc5d2e4npkth5ihxljlyub7ezutevo4atxphbvpt3xal4
Address
f1qreowipcbjnfjrpjxbyqnskhgxwbady7nx72o6q
Datacap Allocated
100.00TiB
Signer Address
f1jvvltduw35u6inn5tr4nfualyd42bh3vjtylgci
Id
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaced532dtmjc5d2e4npkth5ihxljlyub7ezutevo4atxphbvpt3xal4
Can you tell me why you are the same user as in #1016
I don't understand why you need a different useraccount on GIT while you both have the same source wallet?
what you mean the same source wallet ? my client address is f1qreowipcbjnfjrpjxbyqnskhgxwbady7nx72o6q.
Both wallets ( This LDN / 1276 and 1016 ) received funding from this the same source address.
Only f1qreowipcbjnfjrpjxbyqnskhgxwbady7nx72o6q belongs to us, other addresses are not owned by us
checker:manualTrigger
⚠️ 1 storage providers sealed too much duplicate data - f01986229: 20.26%
✔️ Data replication looks healthy.
✔️ No CID sharing has been observed.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger
[^3]: To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ...
Click here to view the CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.
Only f1qreowipcbjnfjrpjxbyqnskhgxwbady7nx72o6q belongs to us, other addresses are not owned by us
Again,
You received funding from the same source addres. How come?
So... , you should ask the owner of the source address with your questions, why are you asking me?
f02049625
f1qreowipcbjnfjrpjxbyqnskhgxwbady7nx72o6q
800TiB
1c68f91e-71bd-434e-b6b4-53f9bfd50e7f
f02049625
f1qreowipcbjnfjrpjxbyqnskhgxwbady7nx72o6q
400% of weekly dc amount requested
800TiB
9.094947017729291e+94YiB
9.094947017729291e+94YiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
5483 | 2 | 100TiB | 72.95 | 20.09TiB |
checker:manualTrigger
⚠️ 1 storage providers sealed too much duplicate data - f01986229: 20.26%
✔️ Data replication looks healthy.
✔️ No CID sharing has been observed.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger
[^3]: To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ...
Click here to view the CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.
checker:manualTrigger
⚠️ 1 storage providers sealed too much duplicate data - f01986229: 20.26%
✔️ Data replication looks healthy.
✔️ No CID sharing has been observed.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger
[^3]: To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ...
Click here to view the CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.
checker:manualTrigger
⚠️ 1 storage providers sealed too much duplicate data - f01986229: 20.26%
✔️ Data replication looks healthy.
✔️ No CID sharing has been observed.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger
[^3]: To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ...
Click here to view the CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.
- Storage provider should not be storing duplicate data for more than 20%.
Please take more attention to this part. I'll sign for this round and look forward to seeing the improvement.
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacebsloy7ie2buxs223cxnrlnmdzkpisxgv6cko2j6e5xkvpqqyek2s
Address
f1qreowipcbjnfjrpjxbyqnskhgxwbady7nx72o6q
Datacap Allocated
800.00TiB
Signer Address
f1bp3tzp536edm7dodldceekzbsx7zcy7hdfg6uzq
Id
1c68f91e-71bd-434e-b6b4-53f9bfd50e7f
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebsloy7ie2buxs223cxnrlnmdzkpisxgv6cko2j6e5xkvpqqyek2s
checker:manualTrigger
⚠️ 1 storage providers sealed too much duplicate data - f01986229: 20.26%
✔️ Data replication looks healthy.
✔️ No CID sharing has been observed.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger
[^3]: To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ...
Click here to view the CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.
checker:manualTrigger
checker:manualTrigger
⚠️ 1 storage providers sealed too much duplicate data - f01986229: 20.26%
⚠️ 1 storage providers have unknown IP location - f02229951
✔️ Data replication looks healthy.
✔️ No CID sharing has been observed.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger
[^3]: To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ...
Click here to view the CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.
@kevzak @fabriziogianni7 @simonkim0515 @huseyincansoylu Since #1276, #1277, and #1278 shared the same client address, #1276/#1276 triggered the DC signature at the same time. After #1277 propose, the first signature of #1276 was directly approved, making it impossible to perform the second signature. In addition, in theory, #1278 should also trigger DC signature at the same time, but it doesn't. Please help me to modify the status of #1276/#1278, thank you.
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.
checker:manualTrigger
⚠️ 1 storage providers sealed too much duplicate data - f01986229: 20.26%
✔️ Data replication looks healthy.
✔️ No CID sharing has been observed.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger
[^3]: To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ...
Click here to view the CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.
check
f02049625
f1qreowipcbjnfjrpjxbyqnskhgxwbady7nx72o6q
720TiB
5a1d8077-5f27-40af-aaf4-25b448b648f1
f02049625
f1qreowipcbjnfjrpjxbyqnskhgxwbady7nx72o6q
400% of weekly dc amount requested
720TiB
7.275957614183434e+125YiB
7.275957614183434e+125YiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
24007 | 6 | 800TiB | 38.41 | 686TiB |
checker:manualTrigger
⚠️ 1 storage providers have unknown IP location - f02222321
✔️ Data replication looks healthy.
✔️ No CID sharing has been observed.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
[^2]: Deals from those addresses are combined into this report as they are specified with checker:manualTrigger
[^3]: To manually trigger this report with deals from other related addresses, add a comment with text checker:manualTrigger <other_address_1> <other_address_2> ...
Click here to view the CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.
Large Dataset Notary Application
To apply for DataCap to onboard your dataset to Filecoin, please fill out the following.
Core Information
Please respond to the questions below by replacing the text saying "Please answer here". Include as much detail as you can in your answer.
Project details
Share a brief history of your project and organization.
What is the primary source of funding for this project?
What other projects/ecosystem stakeholders is this project associated with?
Use-case details
Describe the data being stored onto Filecoin
Where was the data in this dataset sourced from?
Can you share a sample of the data? A link to a file, an image, a table, etc., are good ways to do this.
Confirm that this is a public dataset that can be retrieved by anyone on the Network (i.e., no specific permissions or access rights are required to view the data).
What is the expected retrieval frequency for this data?
For how long do you plan to keep this dataset stored on Filecoin?
DataCap allocation plan
In which geographies (countries, regions) do you plan on making storage deals?
How will you be distributing your data to storage providers? Is there an offline data transfer process?
How do you plan on choosing the storage providers with whom you will be making deals? This should include a plan to ensure the data is retrievable in the future both by you and others.
How will you be distributing deals across storage providers?
Do you have the resources/funding to start making deals as soon as you receive DataCap? What support from the community would help you onboard onto Filecoin?