Closed Lind111 closed 10 months ago
The notary can now review it . Thank you.
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacedpls2ot6h4ko73d5wrb5kkjmarabvb7szfiinmmjdutgqb5zqipy
Address
f1m7pjzbzrckvgiuqhbps4e6ziakblvc5rtt4wmqq
Datacap Allocated
512.00TiB
Signer Address
f1o3twrcpwjtpcd4q36lpq4qmy2qfbgtyy5h6tsty
Id
4e48f2d2-8aea-4132-a76f-02964508f9f3
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedpls2ot6h4ko73d5wrb5kkjmarabvb7szfiinmmjdutgqb5zqipy
f02049625
f1m7pjzbzrckvgiuqhbps4e6ziakblvc5rtt4wmqq
512TiB
f41d1a12-f454-44c6-afee-e4d230f61803
f02049625
f1m7pjzbzrckvgiuqhbps4e6ziakblvc5rtt4wmqq
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 |
---|---|---|---|---|
10383 | 6 | 512TiB | 29.37 | 131.93TiB |
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 CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.
This looks great.
checker:manualTrigger
Doing due diligence. Requesting notaries not to engage.
✔️ 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 Dashboard. Click here to view the Retrieval report.
@Filplus-govteam The above entity appears to be manipulating the CID checker tool. Many of these minerID's seem to be operated by the same entity, falsely portraying distribution using VPNs. It's a recurring pattern.
Moreover, a new account requesting 15PiB of datacap should raise immediate concerns. I'm puzzled as to why this hasn't been addressed. Such significant allocations should be reserved for well-known and trusted entities.
Several of the submitted minerID's have a history of self-dealing or abusive behaviors on other LDNs and have been previously flagged and shut down.
Furthermore, I'm skeptical about this entity's intention to bring valuable data to the network. Their request for datacap appears to be more about expanding their operations than contributing meaningful storage or data, a pattern we've seen with others.
I strongly advise notaries to refrain from endorsing or engaging with this LDN.
@Filplus-govteam The above entity appears to be manipulating the CID checker tool. Many of these minerID's seem to be operated by the same entity, falsely portraying distribution using VPNs. It's a recurring pattern.
The miners I contacted all come from different regions, and I have repeatedly confirmed with them that there is no problem. I have contacted different miners through Telegram, Slack, BBS, and offline communication. Confirm what the problem is, and I will verify it clearly.
Moreover, a new account requesting 15PiB of datacap should raise immediate concerns. I'm puzzled as to why this hasn't been addressed. Such significant allocations should be reserved for well-known and trusted entities.
At present, our server storage needs are very high, which can save us costs. We also hope that the filecoin network will be more stable.
Several of the submitted minerID's have a history of self-dealing or abusive behaviors on other LDNs and have been previously flagged and shut down.
I am not sure where to see the marked miner by the community PL. If there are any issues with the miner, we will terminate and look for a suitable miner
Furthermore, I'm skeptical about this entity's intention to bring valuable data to the network. Their request for datacap appears to be more about expanding their operations than contributing meaningful storage or data, a pattern we've seen with others.
I believe that real and effective data is valuable. The data we store can provide free teaching, allowing more people to learn
None of your answers hold any significance. I am sorry but by points remain.
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 CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.
Go through past comments on the issue, while reporting according to the CID https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/2094#issuecomment-1685806768 Check that there is no duplication of CID, search for problems, and reasonably allocate regions. The setting conforms to the Fil+ specification and is willing to support this round.
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacedkzebzh5rrnk3etcvpjzvg7jutzfhvs3lm4sz3aapofjai4fbgp2
Address
f1m7pjzbzrckvgiuqhbps4e6ziakblvc5rtt4wmqq
Datacap Allocated
512.00TiB
Signer Address
f1nwjsd2mc6hu4qrwnmd6ukrfkuu4h5fhs7u3exii
Id
f41d1a12-f454-44c6-afee-e4d230f61803
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedkzebzh5rrnk3etcvpjzvg7jutzfhvs3lm4sz3aapofjai4fbgp2
lotus state get-deal 51368400 { "Proposal": { "PieceCID": { "/": "baga6ea4seaqpo3vkovgtbfmxfk2crc7jcztk25fht2unh5nnowkh7nkusj6w2ni" }, "PieceSize": 34359738368, "VerifiedDeal": true, "Client": "f02366250", "Provider": "f02237010", "Label": "bafybeicamu7ct3x27kzkbgnfwsg4nykwnbt4hxxgnmhmkajfdpc7k2up7i", "StartEpoch": 3159987, "EndEpoch": 4686387, "StoragePricePerEpoch": "0", "ProviderCollateral": "9784285954342815", "ClientCollateral": "0" }, "State": { "SectorStartEpoch": 3135531, "LastUpdatedEpoch": -1, "SlashEpoch": -1, "VerifiedClaim": 33679990 } }
lotus client retrieve --miner f02237010 bafybeicamu7ct3x27kzkbgnfwsg4nykwnbt4hxxgnmhmkajfdpc7k2up7i 7010 Recv 0 B, Paid 0 FIL, Open (New), 0s [1689686801615708038|0] Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 2ms [1689686801615708038|0] Recv 0 B, Paid 0 FIL, DealAccepted (Accepted), 350ms [1689686801615708038|0] Recv 0 B, Paid 0 FIL, PaymentChannelSkip (Ongoing), 351ms [1689686801615708038|0] Recv 253.9 KiB, Paid 0 FIL, BlocksReceived (Ongoing), 2.831s [1689686801615708038|260043] Recv 254.1 KiB, Paid 0 FIL, BlocksReceived (Ongoing), 2.832s [1689686801615708038|260202] Recv 1.248 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 21.232s [1689686801615708038|1308778] Recv 2.248 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 38.63s [1689686801615708038|2357354] Recv 2.265 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 38.843s [1689686801615708038|2374650] Recv 2.265 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 38.844s [1689686801615708038|2374758] Recv 3.265 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 1m3.355s [1689686801615708038|3423334] Recv 3.426 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 1m8.199s [1689686801615708038|3592743] Recv 3.426 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 1m8.2s [1689686801615708038|3592851] Recv 4.426 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 1m29.704s [1689686801615708038|4641427] Recv 4.71 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 1m35.02s [1689686801615708038|4939277] Recv 4.711 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 1m35.021s [1689686801615708038|4939636] Recv 5.711 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 1m52.429s [1689686801615708038|5988212] Recv 6.711 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 2m10.073s [1689686801615708038|7036788] Recv 7.711 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 2m29.293s [1689686801615708038|8085364] Recv 8.711 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 2m48.499s [1689686801615708038|9133940] Recv 9.711 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 3m9.269s [1689686801615708038|10182516] Recv 10.71 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 3m25.252s [1689686801615708038|11231092] Recv 11.57 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 3m38.608s [1689686801615708038|12135251] Recv 11.57 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 3m38.609s [1689686801615708038|12135410]
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 CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.
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 CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.
LGTM The CID report looks great. Willing to support this round.
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacectk3cszca6rzyb3xmgzrpdwql6dggengitrzohiwvttnnpke7apc
Address
f1m7pjzbzrckvgiuqhbps4e6ziakblvc5rtt4wmqq
Datacap Allocated
512.00TiB
Signer Address
f1bp3tzp536edm7dodldceekzbsx7zcy7hdfg6uzq
Id
f41d1a12-f454-44c6-afee-e4d230f61803
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacectk3cszca6rzyb3xmgzrpdwql6dggengitrzohiwvttnnpke7apc
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 CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.
SPs provided f02301 organization: topblocks f03223 organization: topblocks f02062851 Mike California f0240185 organization: topblocks f02337010 Peter California f0143858 organization: topblocks
SPs actually storing data: f01877184 | Singapore, Singapore, SGAlibaba (US) Technology Co., Ltd. | 11.69 TiB | 2.35% | 11.69 TiB | 0.00% f02252173 | Tokyo, Tokyo, JPAwesomecloud Limited | 99.75 TiB | 20.06% | 99.75 TiB | 0.00% f01836766 | Shenzhen, Guangdong, CNCHINANET-BACKBONE | 41.34 TiB | 8.31% | 41.34 TiB | 0.00% f02237010 | Los Angeles, California, USCNSERVERS LLC | 101.28 TiB | 20.36% | 101.28 TiB | 0.00% f0143858 | Clifton, New Jersey, USDigitalOcean, LLC | 10.84 TiB | 2.18% | 10.84 TiB | 0.00% f0240185 | Clifton, New Jersey, USDigitalOcean, LLC | 10.44 TiB | 2.10% | 10.44 TiB | 0.00% f02301 | Clifton, New Jersey, USDigitalOcean, LLC | 9.91 TiB | 1.99% | 9.91 TiB | 0.00% f03223 | Clifton, New Jersey, USDigitalOcean, LLC | 9.81 TiB | 1.97% | 9.81 TiB | 0.00% f02237006 | London, England, GBGTHost | 102.31 TiB | 20.57% | 102.31 TiB | 0.00% f02062851 | Los Angeles, California, USNetLab Global | 99.97 TiB | 20.10% | 99.97 TiB | 0.00%
@Lind111 you were asked several times above for a clear list of SPs, entities and locations. You are storing with SPs not mentioned before. 50% of deals are with SPs never mentioned. Closing this until client clears up who they are working with.
@kevzak I updated the SP in question in this from this comment and learned that they hadn't been verified I suspended my work with them, but I didn't get any response after this comment,So I went to look at other LDNs and found that they were available and had been officially approved, plus when the client contacted me they said they had been verified, so that's why I went ahead and did business with them,So I would like to know exactly which miners I can work with now and what I need to do ahead of time before working together in order to get better at it, please let me know, thanks!
The application was triggered signaling it was ok.
You can work with whichever SPs you choose. You just have to be very clear. Please clarify, thank you
The application was triggered signaling it was ok.
You can work with whichever SPs you choose. You just have to be very clear. Please clarify, thank you
SPs contact, contact info, geographic location are all provided as requested, please let me know what other information I need to provide so that I can request it from SPs, thank you! Can this LDN be reopened if there is no problem? Thank you.
No that's the point @Lind111, the SP information was not provided upfront.
Who are these? As far as I can tell, they were not disclosed upfront. f02237006 | London, England, GBGTHost | 102.31 TiB | 20.57% | 102.31 TiB | 0.00% f01877184 | Singapore, Singapore, SGAlibaba (US) Technology Co., Ltd. | 11.69 TiB | 2.35% | 11.69 TiB | 0.00% f02252173 | Tokyo, Tokyo, JPAwesomecloud Limited | 99.75 TiB | 20.06% | 99.75 TiB | 0.00% f01836766 | Shenzhen, Guangdong, CNCHINANET-BACKBONE | 41.34 TiB | 8.31% | 41.34 TiB | 0.00%
Please provide a complete list of SPs SP ID, Entity, Location
No that's the point @Lind111, the SP information was not provided upfront.
Who are these? As far as I can tell, they were not disclosed upfront. f02237006 | London, England, GBGTHost | 102.31 TiB | 20.57% | 102.31 TiB | 0.00% f01877184 | Singapore, Singapore, SGAlibaba (US) Technology Co., Ltd. | 11.69 TiB | 2.35% | 11.69 TiB | 0.00% f02252173 | Tokyo, Tokyo, JPAwesomecloud Limited | 99.75 TiB | 20.06% | 99.75 TiB | 0.00% f01836766 | Shenzhen, Guangdong, CNCHINANET-BACKBONE | 41.34 TiB | 8.31% | 41.34 TiB | 0.00%
Please provide a complete list of SPs SP ID, Entity, Location
Okay, give me a second, I remember them providing that information, I'll look for it, thanks.
@kevzak Hi, the information is as follows, next time I will disclose the information about the SPs I work with in advance, sorry
SP ID | Entity | Location |
---|---|---|
f02337006 | eager | England |
f01877184 | Aron | Singapore |
f02252173 | luna | Tokyo |
f01836766 | Huang | GuangZhou |
f02049625
f1m7pjzbzrckvgiuqhbps4e6ziakblvc5rtt4wmqq
1PiB
9374650f-c41b-402e-87c1-a0445cd79ac3
f02049625
f1m7pjzbzrckvgiuqhbps4e6ziakblvc5rtt4wmqq
200% weekly > 1PiB, requesting 1PiB
1PiB
465661.3YiB
465661.3YiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
22370 | 10 | 512TiB | 24.42 | 306.71TiB |
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 CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.
files can be retrieved. Reports LGTM. Willing to support.
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 CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacedlemgtfyl2u5adwaar76wnfop3ire2gxgxkaozngvh37lvjcpz4g
Address
f1m7pjzbzrckvgiuqhbps4e6ziakblvc5rtt4wmqq
Datacap Allocated
1.00PiB
Signer Address
f1pnmzlxj7cfeo2v6oj5nco46hkg2l46wj7o4xxui
Id
9374650f-c41b-402e-87c1-a0445cd79ac3
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedlemgtfyl2u5adwaar76wnfop3ire2gxgxkaozngvh37lvjcpz4g
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacecqfnxuo5dtrzqi36w7d2fzsqyhpgqifiz3epbiymylrvozvqdf24
Address
f1m7pjzbzrckvgiuqhbps4e6ziakblvc5rtt4wmqq
Datacap Allocated
1.00PiB
Signer Address
f1n5wlrrhoxpkgwij25xrtt7w7g2k3fhbthmdn6ri
Id
9374650f-c41b-402e-87c1-a0445cd79ac3
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacecqfnxuo5dtrzqi36w7d2fzsqyhpgqifiz3epbiymylrvozvqdf24
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 CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.
Update information on the two miners that will be working together
SP Miner IDs:f02093396, f02259777 Contact name:Lingchao Xu Email:lingchao.xu@bitdeer.com Organization Name:STRAITDEER PTE. LTD. Region:Singapore Using VPN?:No Slack handle:xlcbd(ID:U0453ME4D7X)
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 CID Checker report. Click here to view the Retrieval Dashboard. Click here to view the Retrieval report.
f02049625
f1m7pjzbzrckvgiuqhbps4e6ziakblvc5rtt4wmqq
2PiB
4b485b25-e61d-48bc-8e99-181a478a1061
checker:manualTrigger
✔️ Storage provider distribution looks healthy.
⚠️ 30.46% 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 Dashboard. Click here to view the Retrieval report.
Data Owner Name
EF
What is your role related to the dataset
Dataset Owner
Data Owner Country/Region
China
Data Owner Industry
Education & Training
Website
https://www.hzxsef.com/
Social Media
Total amount of DataCap being requested
15PiB
Expected size of single dataset (one copy)
2.2P
Number of replicas to store
7
Weekly allocation of DataCap requested
1PiB
On-chain address for first allocation
f1m7pjzbzrckvgiuqhbps4e6ziakblvc5rtt4wmqq
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
My Own Storage Infra
If you answered "Other" in the previous question, enter the details here
No response
How do you plan to prepare the dataset
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
Monthly
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
Greater China, Asia other than Greater China, North America, Europe
How will you be distributing your data to storage providers
HTTP or FTP server, Shipping hard drives
How do you plan to choose storage providers
Slack
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
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