Closed Janicelu1 closed 1 year ago
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
1PiB
Client address
f1ar7iqp6lpljivz7tgufyik2uvsxpb33tfjcttii
f02049625
f1ar7iqp6lpljivz7tgufyik2uvsxpb33tfjcttii
256TiB
829783d5-9743-4abf-bfe6-e4c3508ed759
dear,
Thank you for applying for datacap. As a Filecoin FIL+Notary Public, I am currently screening your application and conducting due diligence.
Looking at your application, I have some questions:
Because you are a novice on Github and do not have a history of past applications. Can you introduce who you are and your company?
You declare that you are a data preparer. What hardware do you have on your end to prepare this dataset? What is your internet connection speed? Have you downloaded the data locally?
In my opinion, there are many datacaps that apply for 5PB. People need to have a comprehensive understanding of Filecoin, data packaging, data distribution, and all the requirements that come with it. Are you a novice in the Filecoin field, or have you previously applied for datacap on different Github account names?
Can you show us some visible evidence of the size of your data and the storage/packaging hardware you have?
As a final question, I would like you to fill out this form in order to provide us with the necessary information to make a wise decision on your LDN request when we are willing to support it.
thank you!
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacedvke36wt7cwhilc7qiu6lr7hx7llweq53atgchgnjkru676f7z2w
Address
f1ar7iqp6lpljivz7tgufyik2uvsxpb33tfjcttii
Datacap Allocated
256.00TiB
Signer Address
f15impf3j2zcaex4lhyxndxswuuhv24vzstuqtxsi
Id
829783d5-9743-4abf-bfe6-e4c3508ed759
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedvke36wt7cwhilc7qiu6lr7hx7llweq53atgchgnjkru676f7z2w
This is an open data application and the client has provided an appropriate allocation plan. The resources available for review in the first round are very limited. For now i would like to go ahead and help this application move forward.
Your Datacap Allocation Request has been approved by the Notary
bafy2bzaceclq7lxpasr7laifuyek62az4yoozgzq43xklpysjhv67224bsbj6
Address
f1ar7iqp6lpljivz7tgufyik2uvsxpb33tfjcttii
Datacap Allocated
256.00TiB
Signer Address
f1irqs2gmctiv3jcdfwuch7oxvf4ixh3k4b2wc24i
Id
829783d5-9743-4abf-bfe6-e4c3508ed759
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceclq7lxpasr7laifuyek62az4yoozgzq43xklpysjhv67224bsbj6
f02049625
f1ar7iqp6lpljivz7tgufyik2uvsxpb33tfjcttii
512TiB
e1fbaabc-5ad6-4026-9fdd-f4446fa5b099
f02049625
f1ar7iqp6lpljivz7tgufyik2uvsxpb33tfjcttii
10% of total dc amount requested
512TiB
256TiB
4.75PiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
null | null | 256TiB | null | 63.53TiB |
Good morning,
It seems none of your SP's are supporting retrieval at this moment.
lotus client retrieve --provider f0136399 mAXCg5AIgVDUPkVKRrZ8q1DCriCl84TwAUBG9SeKJN+evDyoAih0 test.car Recv 0 B, Paid 0 FIL, Open (New), 0s [1682861878842666113|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 5ms [1682861878842666113|0] Recv 0 B, Paid 0 FIL, DealAccepted (Accepted), 340ms [1682861878842666113|0] Recv 0 B, Paid 0 FIL, PaymentChannelSkip (Ongoing), 340ms [1682861878842666113|0]
cat f02147020-f02019788-34808691-baga6ea4seaqf62f3bjorwchcmkwrpcngsm5hypk47dzanhw53p3sqgu6poldopa.log Error: retrieval query for miner f02019788 failed: failed to dial 12D3KooWDpez5oEcqoWLJArH4zxkpUSpYhvdDx2YADzWWTb8wJ8J:
Any reason for this?
Hello @cryptowhizzard The test of retrieval is without any problems. It may differ from country to country due to network. Welcome more notaries who can review and sign for my applliction!
Hello @cryptowhizzard The test of retrieval is without any problems. It may differ from country to country due to network. Welcome more notaries who can review and sign for my applliction!
Ehm.... if you mean that your miner is not accessible from the Netherlands we might have challenge here since that is against the FIL+ rules.
Can you be more specific ?
Btw , the test you did above is the same outcome as here, since there is nothing retrieved on your side either.
@cryptowhizzard There may be some misunderstanding here. What I meant by my earlier words was---the difference in retrieval results may be related to the network in different countries. We do support retrieval in any country. But sp's network is also a factor in the results. We've already communicated with sp to ask them to fix their network.
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
✔️ 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 full report.
Hi @Janicelu1
That is good to hear. Let us know when the retrieval is fixed in order to continue with this LDN
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzaceb3dnyap6qkpca7s4ulhg34phylkvh676gr53yumf23ggv7czfoeq
Address
f1ar7iqp6lpljivz7tgufyik2uvsxpb33tfjcttii
Datacap Allocated
512.00TiB
Signer Address
f1d4yb3wags3mtddzesxoo63jv7dmlec3bq4yteni
Id
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceb3dnyap6qkpca7s4ulhg34phylkvh676gr53yumf23ggv7czfoeq
The client followed the allocation plan as planned, good report is all dimensions. Keep it up!
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacebqkzwtdpnsibht356ut7nui3ab2yz3mzqrymzs6a7irtg2ulzsze
Address
f1ar7iqp6lpljivz7tgufyik2uvsxpb33tfjcttii
Datacap Allocated
512.00TiB
Signer Address
f1bwugfihrmn3iyunzyxst5nttql3dge4khwmurtq
Id
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebqkzwtdpnsibht356ut7nui3ab2yz3mzqrymzs6a7irtg2ulzsze
Client responded to the retrieval issue. We will be checking reports in the next allocation.
@Casey-PG where did the client respond then? I don't see anything in the ticket here?
Good morning,
It seems none of your SP's are supporting retrieval at this moment.
lotus client retrieve --provider f0136399 mAXCg5AIgVDUPkVKRrZ8q1DCriCl84TwAUBG9SeKJN+evDyoAih0 test.car Recv 0 B, Paid 0 FIL, Open (New), 0s [1682861878842666113|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 5ms [1682861878842666113|0] Recv 0 B, Paid 0 FIL, DealAccepted (Accepted), 340ms [1682861878842666113|0] Recv 0 B, Paid 0 FIL, PaymentChannelSkip (Ongoing), 340ms [1682861878842666113|0]
cat f02147020-f02019788-34808691-baga6ea4seaqf62f3bjorwchcmkwrpcngsm5hypk47dzanhw53p3sqgu6poldopa.log Error: retrieval query for miner f02019788 failed: failed to dial 12D3KooWDpez5oEcqoWLJArH4zxkpUSpYhvdDx2YADzWWTb8wJ8J:
- [/ip4/49.213.6.50/tcp/10242] dial tcp4 49.213.6.50:10242: connect: connection refused
Any reason for this?
Dear notaries, SP has fixed the network problem. Retrieval works fine now.
In our opinion, data retrievals don't require and cannot be done by all notaries, because these are limited and affected by the quality of network links and regional policies in each region, which is the main reason why the community needs to select so many notaries in each region. But for the DPs, the selected storage nodes need to be "subjectively" public to any regions for retrieval. We need to be aware of the subtle differences in the nature of these two things, especially for notaries.
We suggest that notaries who are currently unable to or can only partially successfully complete retrievals temporarily should not be anxious and can refer to the CID reports before you make the decision of signing. Don't forget that you do have the right to choose not to sign. The key indicators that are constantly updated are reflected in the CID reports by P.L., which are the main reference materials we use for our signing.
In our opinion, data retrievals don't require and cannot be done by all notaries, because these are limited and affected by the quality of network links and regional policies in each region, which is the main reason why the community needs to select so many notaries in each region. But for the DPs, the selected storage nodes need to be "subjectively" public to any regions for retrieval. We need to be aware of the subtle differences in the nature of these two things, especially for notaries.
We suggest that notaries who are currently unable to or can only partially successfully complete retrievals temporarily should not be anxious and can refer to the CID reports before you make the decision of signing. Don't forget that you do have the right to choose not to sign. The key indicators that are constantly updated are reflected in the CID reports by P.L., which are the main reference materials we use for our signing.
That's the right attitude, notaries need to communicate better with each other to make the community more friendly and supportive. Many misunderstandings are caused by differences in understanding of the rules.
f02049625
f1ar7iqp6lpljivz7tgufyik2uvsxpb33tfjcttii
1PiB
80b3843e-172f-4d84-8050-52d3a04d3c6b
f02049625
f1ar7iqp6lpljivz7tgufyik2uvsxpb33tfjcttii
20% of total dc amount requested
1PiB
465661.3YiB
-5.62B
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
null | null | 512TiB | null | 127.18TiB |
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 56.83% of deals are for data replicated across less than 4 storage providers.
✔️ 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 full report.
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacedrppnudwmk73ivfs4amdf2mdvm65xmq7ro6ruptbprfghy3ijwvw
Address
f1ar7iqp6lpljivz7tgufyik2uvsxpb33tfjcttii
Datacap Allocated
1.00PiB
Signer Address
f1irqs2gmctiv3jcdfwuch7oxvf4ixh3k4b2wc24i
Id
80b3843e-172f-4d84-8050-52d3a04d3c6b
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedrppnudwmk73ivfs4amdf2mdvm65xmq7ro6ruptbprfghy3ijwvw
No duplicate data,healthy report. Please keep the allocation more decentralized in the future.
Your Datacap Allocation Request has been approved by the Notary
bafy2bzaceaszpupt7772a3pl55ny5actodd2l5kpppimowq6ziw6toevzory2
Address
f1ar7iqp6lpljivz7tgufyik2uvsxpb33tfjcttii
Datacap Allocated
1.00PiB
Signer Address
f1vxbqrf7rfum3n6m5u6eb4re6xj7amvsaqnzu64y
Id
80b3843e-172f-4d84-8050-52d3a04d3c6b
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceaszpupt7772a3pl55ny5actodd2l5kpppimowq6ziw6toevzory2
f02049625
f1ar7iqp6lpljivz7tgufyik2uvsxpb33tfjcttii
2PiB
6fb66271-defd-4d23-86ab-b76d4c9efbf4
f02049625
f1ar7iqp6lpljivz7tgufyik2uvsxpb33tfjcttii
40% of total dc amount requested
2PiB
931322574615478927360.0YiB
-1.12B
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
null | null | 1PiB | null | 284.37TiB |
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacecp56dmmcjznfmr5txm2aipuwqseya7fwhljxwhf6vntjnma2fscg
Address
f1ar7iqp6lpljivz7tgufyik2uvsxpb33tfjcttii
Datacap Allocated
2.00PiB
Signer Address
f15impf3j2zcaex4lhyxndxswuuhv24vzstuqtxsi
Id
6fb66271-defd-4d23-86ab-b76d4c9efbf4
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacecp56dmmcjznfmr5txm2aipuwqseya7fwhljxwhf6vntjnma2fscg
Your Datacap Allocation Request has been approved by the Notary
bafy2bzaced2fbxfojepjtvn6gxnd2qquipmy3325mozfjwlgr5ujom3rgfhly
Address
f1ar7iqp6lpljivz7tgufyik2uvsxpb33tfjcttii
Datacap Allocated
2.00PiB
Signer Address
f1ihv7gz3vn3xqvikpt4rwryecgisl7745lodx3yi
Id
6fb66271-defd-4d23-86ab-b76d4c9efbf4
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaced2fbxfojepjtvn6gxnd2qquipmy3325mozfjwlgr5ujom3rgfhly
The client followed the allocation plan as planned, good report is all dimensions. Keep it up!
Good morning, It seems none of your SP's are supporting retrieval at this moment. lotus client retrieve --provider f0136399 mAXCg5AIgVDUPkVKRrZ8q1DCriCl84TwAUBG9SeKJN+evDyoAih0 test.car Recv 0 B, Paid 0 FIL, Open (New), 0s [1682861878842666113|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 5ms [1682861878842666113|0] Recv 0 B, Paid 0 FIL, DealAccepted (Accepted), 340ms [1682861878842666113|0] Recv 0 B, Paid 0 FIL, PaymentChannelSkip (Ongoing), 340ms [1682861878842666113|0] cat f02147020-f02019788-34808691-baga6ea4seaqf62f3bjorwchcmkwrpcngsm5hypk47dzanhw53p3sqgu6poldopa.log Error: retrieval query for miner f02019788 failed: failed to dial 12D3KooWDpez5oEcqoWLJArH4zxkpUSpYhvdDx2YADzWWTb8wJ8J:
- [/ip4/49.213.6.50/tcp/10242] dial tcp4 49.213.6.50:10242: connect: connection refused
Any reason for this?
Dear notaries, SP has fixed the network problem. Retrieval works fine now.
I don't understand. I tested myself and i checked through dag.parts , nothing works?
Can you make baga6ea4seaqajmsp6lw7mjkd6dtpxboq6cklspagxxj7ie5qj476zuajjsjqeby available for download so we can check the data you are storing here?
Btw , nothing of your data is indexed on the network.
lassie fetch -o baga6ea4seaqajmsp6lw7mjkd6dtpxboq6cklspagxxj7ie5qj476zuajjsjqeby.car baga6ea4seaqajmsp6lw7mjkd6dtpxboq6cklspagxxj7ie5qj476zuajjsjqeby Fetching baga6ea4seaqajmsp6lw7mjkd6dtpxboq6cklspagxxj7ie5qj476zuajjsjqeby 2023-05-27T20:39:14.431+0200 FATAL lassie lassie/main.go:57 no candidates
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.
This application has not seen any responses in the last 14 days, so for now it is being closed. Please feel free to contact the Fil+ Gov team to re-open the application if it is still being processed. Thank you!
@cryptowhizzard We've already fix previous problem. You can try it again.
checker:manualTrigger
⚠️ All retrieval success ratios are below 1%.
✔️ Storage provider distribution looks healthy.
✔️ 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 report.
Hi @Janicelu1
The checkbot states -> All retrieval success ratios are below 1%.
Sorry.
f02049625
f1ar7iqp6lpljivz7tgufyik2uvsxpb33tfjcttii
1.25PiB
0688fe64-6a23-4354-a10d-f0e665a632de
f02049625
f1ar7iqp6lpljivz7tgufyik2uvsxpb33tfjcttii
400% weekly > 2PiB, requesting 2PiB
1.25PiB
1.862645149230957e+37YiB
1.862645149230957e+37YiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
87342 | 21 | 2PiB | 9.88 | 518.96TiB |
Under T&T Review. Pause all signing immediately
Most of the SPs in Graphsync retrieval are timeout, I think this may be the reason why the retrieval rate is showing zero. @raghavrmadya what is the current standard for retrieval timeout? I will contact SPs to find out more about this issue.
Good morning, It seems none of your SP's are supporting retrieval at this moment. lotus client retrieve --provider f0136399 mAXCg5AIgVDUPkVKRrZ8q1DCriCl84TwAUBG9SeKJN+evDyoAih0 test.car Recv 0 B, Paid 0 FIL, Open (New), 0s [1682861878842666113|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 5ms [1682861878842666113|0] Recv 0 B, Paid 0 FIL, DealAccepted (Accepted), 340ms [1682861878842666113|0] Recv 0 B, Paid 0 FIL, PaymentChannelSkip (Ongoing), 340ms [1682861878842666113|0] cat f02147020-f02019788-34808691-baga6ea4seaqf62f3bjorwchcmkwrpcngsm5hypk47dzanhw53p3sqgu6poldopa.log Error: retrieval query for miner f02019788 failed: failed to dial 12D3KooWDpez5oEcqoWLJArH4zxkpUSpYhvdDx2YADzWWTb8wJ8J:
- [/ip4/49.213.6.50/tcp/10242] dial tcp4 49.213.6.50:10242: connect: connection refused
Any reason for this?
Dear notaries, SP has fixed the network problem. Retrieval works fine now.
SP tried again and verified it is retrievable. Timeout is due to geographic location and network quality. They're actively modifying. https://github.com/data-preservation-programs/RetrievalBot/blob/main/filplus.md#deployment
checker:manualTrigger
⚠️ All retrieval success ratios are below 1%.
✔️ Storage provider distribution looks healthy.
✔️ 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 report.
Data Owner Name
NCAR
Data Owner Country/Region
United States
Data Owner Industry
Environment
Website
https://ncar.ucar.edu/
Social Media
Total amount of DataCap being requested
5PiB
Weekly allocation of DataCap requested
1PiB
On-chain address for first allocation
f1ar7iqp6lpljivz7tgufyik2uvsxpb33tfjcttii
Data Type of Application
Public, Open Dataset (Research/Non-Profit)
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
AWS Cloud
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
Yearly
For how long do you plan to keep this dataset stored on Filecoin
More than 3 years
In which geographies do you plan on making storage deals
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, Big data exchange
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
I'm looking for suitable sps.
How do you plan to make deals to your storage providers
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