Closed whymichaelgu1 closed 1 year ago
Warehouse surveillance is not suitable for storing as public dataset. The data samples you provided is not enough to prove you have 5 PB data storage needs. Can you explain your data composition and provide sufficient data samples separately? How much original data do you have? How many copies will you store? Can you provide more detailed information about other storage providers participated in this program, such as you can list SPs you have contacted with at present?
@Sunnyiscoming Thank you for your feedback. Those massive surveillance video data is not just for warehouses, financial institutions, but also as raw data for AI machine learning dataset. The data intended to store on the filecoin network is composed of original surveillance video and some AI machine learning video and pic annotation. I have provided more original surveillance video sample in the link:
https://drive.google.com/drive/folders/1dX0CGisAda_jkXwwRdpVzH3mYY0SiyPx?usp=share_link
Those warehouses are all ALOT-enabled warehouses which means there are at least 40 cameras to cover every corner of each facility. And there are a lot ALOT-enabled nonferrous warehouses need to store those data.
The original data is over 5P. We intend to store 4 copies ( maybe 3 in the initial phases), as of right now, I have already contacted:
f01736786 (a China-based node),
Linkspeed (a USA-based SP),
Holon( an Australia-based SP),
and they agreed to provide storage. I will reach out more SPs through the filecoin slack channel to have more SPs.
Let me know if you need more infromation, thanks.
More data samples are needed.
@Sunnyiscoming more sample data has been updated in the link: https://drive.google.com/drive/folders/1dX0CGisAda_jkXwwRdpVzH3mYY0SiyPx?usp=share_link
Reconfirm the original data size. Each video is 50-100M in size.
@Sunnyiscoming the surveillence video came off from NVR, each camera continously records the scene. 50-100m might cover 30 mins to 1 hour of the recording.
@Sunnyiscoming I have been waiting for more than 40 days, is this still in progress?
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!
@cryptowhizzard @Sunnyiscoming @raghavrmadya @Kevin-FF-USA I was a IPFS fan and recommended to the filecoin FIL+ program. Regardless of how the applicaiton goes, one can not help noticing how this program has become. I don't mind @cryptowhizzard ask questions, the tougher the better, I just hope the notary community has the decency and courtesy to ask those questions 40 days earlier, especailly @Sunnyiscoming, I mean, @Sunnyiscoming are you that ineffeicent for all applications, I hope not, I really hope @raghavrmadya @Kevin-FF-USA @cryptowhizzard can do some DD on notaries as well, it has become a joke, a place to trade datacap for profits. I doubt @raghavrmadya @Kevin-FF-USA don't know that, please check those applicaions that approved with light speed and those which left unattended for monthes. Good luck to Filecoin,, but if this system keeps this of corruption, I don't think Filecoin can go anywhere, notary system is not a centralized system, it is a corrupted system, which is quite a shame to the web3.0 world
Due to the large number of datasets, some applications were submerged. Sorry for the delay. You can ask notaries do direct due diligence.
Total DataCap requested
5PiB
Expected weekly DataCap usage rate
150TiB
Client address
f1xppiiufu6rn22zi6d6gq2ivc23updomtl7ainbq
f01858410
f1xppiiufu6rn22zi6d6gq2ivc23updomtl7ainbq
75TiB
34960cfe-6ccb-4df6-880f-a23ca2a60b4c
Hi @whymichaelgu1
I want to get you going and appreciate you want to try Filecoin. Sorry it took so long.
Can you please fill out the KYC so i know who you are? I will try to get you moving on asap.
@cryptowhizzard KYC submitted
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacebqqjs7njf7njejxclnnfbnrtb7yl2scfspc4njxuyk3ilzjteyyc
Address
f1xppiiufu6rn22zi6d6gq2ivc23updomtl7ainbq
Datacap Allocated
75.00TiB
Signer Address
f1krmypm4uoxxf3g7okrwtrahlmpcph3y7rbqqgfa
Id
34960cfe-6ccb-4df6-880f-a23ca2a60b4c
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebqqjs7njf7njejxclnnfbnrtb7yl2scfspc4njxuyk3ilzjteyyc
@Sunnyiscoming can you sign this LDN please, thank you
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacebdkc35k2aymzflgsp534nysuwc4mzpnjccbbse67lsuevyms2ezi
Address
f1xppiiufu6rn22zi6d6gq2ivc23updomtl7ainbq
Datacap Allocated
75.00TiB
Signer Address
f1yjhnsoga2ccnepb7t3p3ov5fzom3syhsuinxexa
Id
34960cfe-6ccb-4df6-880f-a23ca2a60b4c
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebdkc35k2aymzflgsp534nysuwc4mzpnjccbbse67lsuevyms2ezi
f02049625
f1xppiiufu6rn22zi6d6gq2ivc23updomtl7ainbq
150TiB
0acd36ec-fe0b-4593-ab64-2116cda9de2c
f01858410
f1xppiiufu6rn22zi6d6gq2ivc23updomtl7ainbq
100% of weekly dc amount requested
150TiB
75TiB
4.92PiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
1382 | 3 | 75TiB | 33.94 | 18.03TiB |
checker:manualTrigger
⚠️ All retrieval success ratios are below 1%.
✔️ Storage provider distribution looks healthy.
✔️ Data replication looks healthy.
⚠️ CID sharing has been observed. (Top 3)
[^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 report.
can you explain why there are 800GiB sharing reports?
@woshidama323 for testing purpose
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzaceczkmip63d2xjrm72eq54yuioiwt4fdj5llodohv4pxb3umcxpdri
Address
f1xppiiufu6rn22zi6d6gq2ivc23updomtl7ainbq
Datacap Allocated
150.00TiB
Signer Address
f12tk3adljauwnd3hjbigpfxb7b7gdlj63p6afwtq
Id
0acd36ec-fe0b-4593-ab64-2116cda9de2c
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceczkmip63d2xjrm72eq54yuioiwt4fdj5llodohv4pxb3umcxpdri
checker:manualTrigger
⚠️ All retrieval success ratios are below 1%.
✔️ Storage provider distribution looks healthy.
✔️ Data replication looks healthy.
⚠️ CID sharing has been observed. (Top 3)
[^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 report.
Why is the retrieval rate so low?
I asked sp, they did store the unsealed copy, they just did not turn on the retriveal since it takes up bandwidth and they have limited bandwidth, they will turn them on from now on.
Your Datacap Allocation Request has been approved by the Notary
bafy2bzaced2xlsxa3dcn62xsoctop6yfhfzh4xcznqdez5detioellm33sq4q
Address
f1xppiiufu6rn22zi6d6gq2ivc23updomtl7ainbq
Datacap Allocated
150.00TiB
Signer Address
f1xrnysd4gimg64d4l6qi7ulzwwq22c6vfg6lpw3i
Id
0acd36ec-fe0b-4593-ab64-2116cda9de2c
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaced2xlsxa3dcn62xsoctop6yfhfzh4xcznqdez5detioellm33sq4q
checker:manualTrigger
⚠️ All retrieval success ratios are below 1%.
✔️ Storage provider distribution looks healthy.
✔️ Data replication looks healthy.
⚠️ CID sharing has been observed. (Top 3)
[^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 report.
@yaoyuanww
Nothing changed. How long should we wait for your promise?
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
✔️ Storage provider distribution looks healthy.
✔️ Data replication looks healthy.
⚠️ CID sharing has been observed. (Top 3)
[^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.
@Kevin-FF-USA the bot did not trigger the next round, can you take a look, thanks
@kevzak the bot did not trigger the next round, can you take a look, thanks
@yaoyuanww are you using the same address somewhere else? sometimes it causes issues
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
✔️ Data replication looks healthy.
⚠️ CID sharing has been observed. (Top 3)
[^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 no, this address is just for this LDN
f02049625
f1xppiiufu6rn22zi6d6gq2ivc23updomtl7ainbq
300TiB
9370acf4-00f6-4dc1-b637-1c786fabf01f
f02049625
f1xppiiufu6rn22zi6d6gq2ivc23updomtl7ainbq
200% of weekly dc amount requested
300TiB
13642.4YiB
13642.4YiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
3143 | 6 | 150TiB | 35.99 | 0B |
Hi @whymichaelgu1 Thank you for reaching me for your LDN allocation.
How long does this video surveillance will store? Do you think that's necessary?
@Destore2023 It used to be one months since the warehouses do not have the budget or capacity to store them more than that. with Filecoin, those data can be stored much longer and it is absolutely necessary since the financial institutions who do financing on those commodities need longer video surveillnace, the longer the better. For the commodities owner, if the warehouse offers financing service, it is a huge plus. So, in short, it is necessary.
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 71.19% of deals are for data replicated across less than 4 storage providers.
⚠️ CID sharing has been observed. (Top 3)
[^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.
Good morning,
Seems your retrieval is not working correctly. Can you please fix before we move to next allocation.
cat 1148-f01512680-f02230977-47111204-baga6ea4seaqcd4pexulcmdb64b3nfgwz363qbv7k2xhddbccgybhgxboa77esfi.log ERROR: offer error: retrieval query offer errored: failed to fetch piece to retrieve from: getting pieces for cid bafykbzaceatsbvcz5ur5ee7mvks6ctmdm5l5mqfjyuvx4yimw6b6qknsle6wy: getting pieces containing block bafykbzaceatsbvcz5ur5ee7mvks6ctmdm5l5mqfjyuvx4yimw6b6qknsle6wy: failed to lookup index for mh a0e402202720d459ed23d213ecaaa5e14d836757d640a9c52b7e610cb783e829b2593d6c, err: datastore: key not found
Good morning,
Seems your retrieval is not working correctly. Can you please fix before we move to next allocation.
cat 1148-f01512680-f02230977-47111204-baga6ea4seaqcd4pexulcmdb64b3nfgwz363qbv7k2xhddbccgybhgxboa77esfi.log ERROR: offer error: retrieval query offer errored: failed to fetch piece to retrieve from: getting pieces for cid bafykbzaceatsbvcz5ur5ee7mvks6ctmdm5l5mqfjyuvx4yimw6b6qknsle6wy: getting pieces containing block bafykbzaceatsbvcz5ur5ee7mvks6ctmdm5l5mqfjyuvx4yimw6b6qknsle6wy: failed to lookup index for mh a0e402202720d459ed23d213ecaaa5e14d836757d640a9c52b7e610cb783e829b2593d6c, err: datastore: key not found
Hi @whymichaelgu1 Based on the fact that other notaries questioned your retrieval problem, can you improve it? If so, I'm willing to sign.
we did check all the sps and found this error came from f02230977. They do support retrieval, but what they did is that they changed boost code to increase efficiency, in which case it does not allow retrieval to perform while sealing, and this sp probably won't change that back. So we will stop working with the specific miner f0223097. We checked other miners, they supported retrieval unconditionally. attached is one example as of f02231025
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?