Open jacktree7 opened 5 months ago
Application is waiting for allocator review
Hey @jacktree7 , thanks for applying to Marshall-Fil-Data-Pathway. In addition to the questions in the issue, I would still like you to confirm the following. 1.Have you prepared enough token for sector pledge? 2.Are you a data preparer? What is your previous experience as a data-preparer? List previous applications and client IDs 3.How will the data be prepared? Please include tooling used and technical details 4.If you are not preparing the data, who will prepare the data? (Name and Business) 5.Has this dataset been stored on Filecoin before? If so, why are you choosing to store it again? 6.Best practice for storing large datasets includes ideally, storing it in 3 or more regions, with 4 or more storage provider operators or owners.You should list Miner ID, Business Entity, Location of sps you will cooperate with.
Other than that, can you send an email using the official email address to verify authenticity? marshallbtc1990@gmail.com The content should contain the name of your application.
Hello, I am glad to receive your patient review. Currently the SPs I communicated with are ready to pledge 90% of their coins. I am a data preparer, I have participated in the early slingshot, mainly through the official tools, such as boost, lotus. the data stored so far is the first time for the SPs I work with. The information of SPs being communicated is as follows: f03000070 Honglian Tec China; f03091739 lanxin USA; f03028310 Fly Hk; f03028315 Datastone Guangdong; f03028318 Seven Singapore; f03028326 HKblockchain US; f03028321 Datastone HK.
Hey @jacktree7 , thanks for applying to Marshall-Fil-Data-Pathway. In addition to the questions in the issue, I would still like you to confirm the following. 1.Have you prepared enough token for sector pledge? 2.Are you a data preparer? What is your previous experience as a data-preparer? List previous applications and client IDs 3.How will the data be prepared? Please include tooling used and technical details 4.If you are not preparing the data, who will prepare the data? (Name and Business) 5.Has this dataset been stored on Filecoin before? If so, why are you choosing to store it again? 6.Best practice for storing large datasets includes ideally, storing it in 3 or more regions, with 4 or more storage provider operators or owners.You should list Miner ID, Business Entity, Location of sps you will cooperate with.
@Marshall-btc Verification email sent.
Passport information is also attached to the email, please check,thanks!
I have received a KYC email from this client.
Before the first round begins, I still want to remind you @jacktree7 :
You and SP are to strictly adhere to the rules of Fil+ and Marshall-Fil-Data-Pathway. Please confirm SP's geographic location and name before the start of each allocation round. If there is a change, please comment promptly in that application. Please keep the SP retrievable.
Total DataCap requested
15PiB
Expected weekly DataCap usage rate
1000TiB
DataCap Amount - First Tranche
500TiB
Client address
f1ojdxbixro3pxlozhcra5tzxe5p6df6rzwrmlaja
f1ojdxbixro3pxlozhcra5tzxe5p6df6rzwrmlaja
500TiB
e28dfcf7-0aac-45e4-850a-8e0d38c00843
Application is ready to sign
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacedapupgwh6rbqqcrgumsfguh7mybodrtsx4yldpw2sayqszwfscmc
Address
f1ojdxbixro3pxlozhcra5tzxe5p6df6rzwrmlaja
Datacap Allocated
500TiB
Signer Address
f16b6a4s63opnunpag3llqg77pfl4pyixwb657iza
Id
e28dfcf7-0aac-45e4-850a-8e0d38c00843
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedapupgwh6rbqqcrgumsfguh7mybodrtsx4yldpw2sayqszwfscmc
Application is Granted
Synchronize the latest information in a timely manner: f01315096、f03091739 、f03144037、f03055005、f01106668、f03055018、f03055029、f0870558.
Client used 75% of the allocated DataCap. Consider allocating next tranche.
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 50.00% of Storage Providers have retrieval success rate equal to zero.
⚠️ The average retrieval success rate is 12.01%
✔️ 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.
Hey @jacktree7.I see that you have completed this round of encapsulation and have a few questions for you .
1.Sorry, these two SPs were not updated in time. 3 weeks ago, the original SPs were delayed in the data storage process due to a temporary problem with filecoin pledged coins, so I temporarily found a partner to recommend these two new SPs, and I will continue to update them later. f03148356 Linyun Japan, f03156617 Tongkun Sydney. 2.f03055005, f01106668, f01315096 these SPs, I have contacted and communicated with them, they told me that they are studying the principle of Spark, and recently happened to run into the main network upgrade on August 6, it will be improved later. Please stay tuned.
Ok, I'll support this round, but still want you to contact SPs to improve retrieval success.
Application is in Refill
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacebqnhcsmmrjexguznm2zb7gazg2wmk7otmrf735a35th7l27sb7r4
Address
f1ojdxbixro3pxlozhcra5tzxe5p6df6rzwrmlaja
Datacap Allocated
1PiB
Signer Address
f16b6a4s63opnunpag3llqg77pfl4pyixwb657iza
Id
5f2aaab7-3a21-4d9c-a70d-3c0024e49404
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebqnhcsmmrjexguznm2zb7gazg2wmk7otmrf735a35th7l27sb7r4
Application is Granted
Client used 75% of the allocated DataCap. Consider allocating next tranche.
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 57.14% of Storage Providers have retrieval success rate equal to zero.
⚠️ 100.00% of Storage Providers have retrieval success rate less than 75%.
⚠️ The average retrieval success rate is 13.53%
✔️ 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.
Timely update of information:f01518369、f01889668、f03151449、f03151456、f03179555、f03179570、f03188440、f03190614、f03190616.
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 18.18% of Storage Providers have retrieval success rate equal to zero.
⚠️ 54.55% of Storage Providers have retrieval success rate less than 75%.
✔️ 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.
Hey @jacktree7 ,I see that overall Spark retrieval is good in your latest report, but please explain these 5 node Spark retrieval anomalies.
Thank you for the allocator operator's patient response. I have communicated with these clients, and I’m providing the information below:
The two nodes in the United States experienced network outages due to data center failures starting from October 1. During this period, the clients worked hard to restore the network. The screenshot shows the first penalty record 24 hours after the network went down at 3 AM on October 1. It wasn't until today that the client restored a standard 1G local carrier bandwidth, so normal network operations have just resumed, and the Spark retrieval rate will gradually improve in the future.
For the other three nodes, the clients reported that they are using the DDO mode. Currently, Spark and DDO are not fully compatible. Below is a screenshot of the DDO mode. We will try to minimize the use of the DDO ordering mode in the future.
Please review this information and continue to support 2PiB. Thank you very much!
Looks good, but for Allocator compliance operations purposes, I will be approving this round of Datacap cautiously, with limited intervention on the new batch quota, approving 2PiBs as per the rules, but this time only 1PiB at first.I will resume 2PiB quota approvals after subsequent improvements are seen.
Application is in Refill
Your Datacap Allocation Request has been approved by the Notary
bafy2bzaced7dppspujgfyknpwoowhafces6z7loh7vsizzgjvpbqpwo4irkh6
Address
f1ojdxbixro3pxlozhcra5tzxe5p6df6rzwrmlaja
Datacap Allocated
1PiB
Signer Address
f16b6a4s63opnunpag3llqg77pfl4pyixwb657iza
Id
1aa815d3-3ea2-417e-9d58-651d14028945
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaced7dppspujgfyknpwoowhafces6z7loh7vsizzgjvpbqpwo4irkh6
Application is Granted
Client used 75% of the allocated DataCap. Consider allocating next tranche.
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 11.76% of Storage Providers have retrieval success rate equal to zero.
⚠️ 70.59% of Storage Providers have retrieval success rate less than 75%.
✔️ 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.
@jacktree7 Please explain “The Client declared 6 replicas, while 8 of them already exist.” https://github.com/filecoin-project/Allocator-Governance/issues/216#issuecomment-2486404278
Hi @Marshall-btc 6 copies is the minimum, so some data will have more backups in order to have more secure redundancy for the data. Also, considering that some sp declared sector period is only 180 days, had to find more sp for storage in order to meet my data storage deadline.
Data Owner Name
National Astronomical Observatories, Chinese Academy of Sciences
Data Owner Country/Region
China
Data Owner Industry
Environment
Website
http://dr5.lamost.org/
Social Media Handle
http://dr5.lamost.org/
Social Media Type
Other
What is your role related to the dataset
Data Preparer
Total amount of DataCap being requested
15PiB
Expected size of single dataset (one copy)
3000TiB
Number of replicas to store
6
Weekly allocation of DataCap requested
1000TiB
On-chain address for first allocation
f1ojdxbixro3pxlozhcra5tzxe5p6df6rzwrmlaja
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
Other
If you answered "Other" in the previous question, enter the details here
If you are a data preparer. What is your location (Country/Region)
None
If you are a data preparer, how will the data be prepared? Please include tooling used and technical details?
No response
If you are not preparing the data, who will prepare the data? (Provide name and business)
No response
Has this dataset been stored on the Filecoin network before? If so, please explain and make the case why you would like to store this dataset again to the network. Provide details on preparation and/or SP distribution.
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
2 to 3 years
In which geographies do you plan on making storage deals
Greater China, Asia other than Greater China, Africa, North America, South America, Europe, Australia (continent), Antarctica
How will you be distributing your data to storage providers
HTTP or FTP server, Shipping hard drives
How did you find your storage providers
Slack, Partners
If you answered "Others" in the previous question, what is the tool or platform you used
No response
Please list the provider IDs and location of the storage providers you will be working with.
How do you plan to make deals to your storage providers
Boost client, Lotus client
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