Closed datalove2 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.
Could you send an email to filplus-app-review@fil.org with your official domain in order to confirm your identity? Email name should includes the issue id #2050.
@Sunnyiscoming Hi, The email has been sent on last week. Please kindly check it.
Hello. I have received your email. But I do not see your business license.
Hi @Sunnyiscoming, the business license has been attached. I resent the email. Please take a look. Thank you.
Total DataCap requested
15PiB
Expected weekly DataCap usage rate
1PiB
Client address
f1tp3kxwlvxd3ggjsfcbivr25fzz2edrrrqe5vapy
f02049625
f1tp3kxwlvxd3ggjsfcbivr25fzz2edrrrqe5vapy
512TiB
fdf30adb-8ae7-427a-bfcf-64383048e88d
I will support you for the first round. Keep following
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacecz3k7aaozrkxcsweqbbpoyurc36r5cbuftneo7lm4zl7us5qargi
Address
f1tp3kxwlvxd3ggjsfcbivr25fzz2edrrrqe5vapy
Datacap Allocated
512.00TiB
Signer Address
f1mdk7s2vntzm6hu35yuo6vjubtrpfnb2awhgvrri
Id
fdf30adb-8ae7-427a-bfcf-64383048e88d
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacecz3k7aaozrkxcsweqbbpoyurc36r5cbuftneo7lm4zl7us5qargi
Willing to support in the first round, will pay attention to the data dispersion later.
Your Datacap Allocation Request has been approved by the Notary
bafy2bzaceaclga63k6lkhgtalz7lizicwwkrfosm6slu26gb76pp3osszkqz2
Address
f1tp3kxwlvxd3ggjsfcbivr25fzz2edrrrqe5vapy
Datacap Allocated
512.00TiB
Signer Address
f1pnmzlxj7cfeo2v6oj5nco46hkg2l46wj7o4xxui
Id
fdf30adb-8ae7-427a-bfcf-64383048e88d
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceaclga63k6lkhgtalz7lizicwwkrfosm6slu26gb76pp3osszkqz2
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.
⚠️ All retrieval success ratios are below 1%.
✔️ Storage provider distribution looks healthy.
⚠️ 98.10% of deals are for data replicated across less than 2 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 CID Checker report. Click here to view the Retrieval report.
f02049625
f1tp3kxwlvxd3ggjsfcbivr25fzz2edrrrqe5vapy
512TiB
57e04d8f-6be5-4429-8aae-838981e217d5
f02049625
f1tp3kxwlvxd3ggjsfcbivr25fzz2edrrrqe5vapy
100% weekly > 0.5PiB, requesting 0.5PiB
512TiB
512TiB
14.5PiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
8665 | 6 | 512TiB | 32.54 | 137.87TiB |
⚠️ All retrieval success ratios are below 1%.
✔️ Storage provider distribution looks healthy.
⚠️ 100.00% of deals are for data replicated across less than 3 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 CID Checker report. Click here to view the Retrieval report.
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 92.56% of deals are for data replicated across less than 3 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 CID Checker report. Click here to view the Retrieval report.
Hello community members and notaries, our program has been updated, and we can now see that the bot is displaying the retrieval rate correctly. Additionally, as the bot conducts retrieval tests approximately once per hour, we will observe an increasing retrieval rate over time. We appreciate the support of the notaries to witness the next round of retrieval rate updates.
✔️ Storage provider distribution looks healthy.
⚠️ 70.51% of deals are for data replicated across less than 3 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 CID Checker report. Click here to view the Retrieval report.
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzaceamgtznfeeaeo4c5uvy5tavrx223gz24dcdxl6vzqb5rxsjmnglz6
Address
f1tp3kxwlvxd3ggjsfcbivr25fzz2edrrrqe5vapy
Datacap Allocated
512.00TiB
Signer Address
f1j3u7crhjzwb2cj5mq7vodlt4o66yoyci7lhcauy
Id
57e04d8f-6be5-4429-8aae-838981e217d5
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceamgtznfeeaeo4c5uvy5tavrx223gz24dcdxl6vzqb5rxsjmnglz6
Reached out by the client on Slack. Walked through their plans on how they could improve on CIDChecker warnings.
Will also support this application and suggest you should fix those warnings in the next round
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacebjl7yppvperuqf4lj2hvfrdtqlgjvvqgjnsugpnvrsxunjnvubyw
Address
f1tp3kxwlvxd3ggjsfcbivr25fzz2edrrrqe5vapy
Datacap Allocated
512.00TiB
Signer Address
f12tk3adljauwnd3hjbigpfxb7b7gdlj63p6afwtq
Id
57e04d8f-6be5-4429-8aae-838981e217d5
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebjl7yppvperuqf4lj2hvfrdtqlgjvvqgjnsugpnvrsxunjnvubyw
f02049625
f1tp3kxwlvxd3ggjsfcbivr25fzz2edrrrqe5vapy
1PiB
01e4f9f1-f645-47ad-aad8-f2c582d513c1
f02049625
f1tp3kxwlvxd3ggjsfcbivr25fzz2edrrrqe5vapy
200% weekly > 1PiB, requesting 1PiB
1PiB
465661.3YiB
465661.3YiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
11629 | 8 | 512TiB | 24.28 | 107.43TiB |
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 98.02% 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 CID Checker report. Click here to view the Retrieval report.
SP position distribution is very scattered, But file replicas are not healthy. Need to fix this issue ASAP no CID sharing
The retrieval success rate of nodes is not bad.
Willing to support this round
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzaceair2m22y5j2qjltk4i7x7zcyb3vg73cj3idxhqh5tfjrhmktk2ak
Address
f1tp3kxwlvxd3ggjsfcbivr25fzz2edrrrqe5vapy
Datacap Allocated
1.00PiB
Signer Address
f1e77zuityhvvw6u2t6tb5qlnsegy2s67qs4lbbbq
Id
01e4f9f1-f645-47ad-aad8-f2c582d513c1
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceair2m22y5j2qjltk4i7x7zcyb3vg73cj3idxhqh5tfjrhmktk2ak
Check project status is good, supported
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacebbucorkoj4dp65fni2hkxumy5v2ud65xkz4stvglq3qjhgy5olte
Address
f1tp3kxwlvxd3ggjsfcbivr25fzz2edrrrqe5vapy
Datacap Allocated
1.00PiB
Signer Address
f1tbd632f6w62glfaf7wjpimacbnjiz26poyoes2q
Id
01e4f9f1-f645-47ad-aad8-f2c582d513c1
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebbucorkoj4dp65fni2hkxumy5v2ud65xkz4stvglq3qjhgy5olte
@luobin544 and @newwebgroup have been recommended for the removal of their notary status. Notary @luobin544 showed a lack of due diligence by signing the application without any due diligence, simply relying on the statement "Check project status is good, supported." Notary @newwebgroup attempted to perform due diligence but still promptly signed the application, which is not proper due diligence at all. It's important to note that signing off on a 1PiB trench is a significant decision.
Furthermore, there are concerns regarding the distribution process, as it appears that all distribution is occurring in a single region, or it could potentially be fake distribution using a VPN.
Additionally, this application involves a merged dataset request, which the community has decided is no longer allowed. Despite being aware of this decision, the notaries still proceeded to sign the application. For reference, please see the following link: https://github.com/filecoin-project/notary-governance/issues/832
I intend to initiate a dispute regarding these matters.
@raghavrmadya and @dkkapur
https://github.com/filecoin-project/notary-governance/issues/921#issuecomment-1627975484
This community member did an IP check for us and the results were the same as we explained, we were not using a VPN
I checked T&T dispute tracker and the dispute is marked as resolved. OK to proceed. Neither VPN usage or merged dataset is a reason to cancel the LDN according to guidelines.
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 99.17% 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 CID Checker report. Click here to view the Retrieval report.
Looks like the bot was not able to retrieve the transaction on the lotus node. Please contact governance team. The message cid: bafy2bzacebbucorkoj4dp65fni2hkxumy5v2ud65xkz4stvglq3qjhgy5olte
Please, contact the governance team.
f02049625
f1tp3kxwlvxd3ggjsfcbivr25fzz2edrrrqe5vapy
2PiB
085a5191-24f9-4c35-8d56-0c493f28b546
f02049625
f1tp3kxwlvxd3ggjsfcbivr25fzz2edrrrqe5vapy
400% weekly > 2PiB, requesting 2PiB
2PiB
931322574615478927360.0YiB
931322574615478927360.0YiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
59693 | 15 | 1PiB | 18.07 | 0B |
I am seeing a slight increase on the replications and the client has reached to me privately saying more replications incoming. Going to support this round.
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacedlkgmmonoyu4h4wtzuyotaasdpfnbvdm3u3hje7qqk3peztinbvw
Address
f1tp3kxwlvxd3ggjsfcbivr25fzz2edrrrqe5vapy
Datacap Allocated
2.00PiB
Signer Address
f1yjhnsoga2ccnepb7t3p3ov5fzom3syhsuinxexa
Id
085a5191-24f9-4c35-8d56-0c493f28b546
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedlkgmmonoyu4h4wtzuyotaasdpfnbvdm3u3hje7qqk3peztinbvw
Seeing that several of the allegations for this LDN have lapsed, and that the check bot shows compliant retrieval rates and CID sharing reports, we are willing to support this round of signatures.
Also, I will keep an eye on this LDN's data storage.
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacecqe4z72aoakuriue6xuln7iko22udo2gjzeatkr74nrvqq6szkfq
Address
f1tp3kxwlvxd3ggjsfcbivr25fzz2edrrrqe5vapy
Datacap Allocated
2.00PiB
Signer Address
f1dnb3uz7sylxk6emti3ififcvu3nlufnnsjui6ea
Id
085a5191-24f9-4c35-8d56-0c493f28b546
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacecqe4z72aoakuriue6xuln7iko22udo2gjzeatkr74nrvqq6szkfq
Immediate removal of @mikezli after signing a disputed application.
https://github.com/filecoin-project/notary-governance/issues/921
I checked T&T dispute tracker and the dispute is marked as resolved. OK to proceed. Neither VPN usage or merged dataset is a reason to cancel the LDN according to guidelines.
I guess I must made a mistake mixed up 2050 and 2055 being disputed. The 2050 dispute is not on the tracker yet.
So what makes one issue being disputed? On the tracker or as soon as an issue is opened but not on the tracker? We need a single source of truth.
Thanks to the support of the two notaries @mikezli 、@kernelogic , the allegations against us for this LDN were the merging of datasets and the use of vpn's. At this point RG has publicly stated that the public datasets that have been applied for and completed are allowed to be signed, and also the allegations against the vpn's have been explained, and the allegations at filecoin-project/notary-governance#921 (comments) have been no follow-up questions. Also there were no new allegations from the TT meeting. @herrehesse
@datalove2 this is factually untrue. Notaries are not allowed to sign.
@herrehesse We have provided evidence for all your unjustified accusations against us, and now you are asking other notaries not to allow signatures without new evidence, is this what a qualified notary would do?
Data Owner Name
RongYin
What is your role related to the dataset
Data Preparer
Data Owner Country/Region
China
Data Owner Industry
IT & Technology Services
Website
https://www.qcc.com/firm/3380acbb3101bd58394d1ba4be51e877.html
Social Media
Total amount of DataCap being requested
15PiB
Expected size of single dataset (one copy)
1.5PiB
Number of replicas to store
10
Weekly allocation of DataCap requested
1PiB
On-chain address for first allocation
f1tp3kxwlvxd3ggjsfcbivr25fzz2edrrrqe5vapy
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, graphsplit
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
1.5 to 2 years
In which geographies do you plan on making storage deals
Greater China, Asia other than Greater China, North America, South America, Europe, Australia (continent)
How will you be distributing your data to storage providers
HTTP or FTP server, IPFS, Shipping hard drives, Lotus built-in data transfer
How do you plan to choose storage providers
Slack, Big Data Exchange, Partners
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
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