Closed Fatman13 closed 1 year ago
Thanks for your request!
Heads up, you’re requesting more than the typical weekly onboarding rate of DataCap!
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
500TiB
Client address
f3qaipvxrz2gxexc7mcvjsxifmscfiw7c7zfhrmq76j5ee4hcbvg3gbtpea7wgz72kkjcjmwzhm5uo2onxyocq
f02049625
f3qaipvxrz2gxexc7mcvjsxifmscfiw7c7zfhrmq76j5ee4hcbvg3gbtpea7wgz72kkjcjmwzhm5uo2onxyocq
250TiB
f9d46ada-0afc-461b-ae68-873792ae4d1d
Guazi Dynamic
f3qaipvxrz2gxexc7mcvjsxifmscfiw7c7zfhrmq76j5ee4hcbvg3gbtpea7wgz72kkjcjmwzhm5uo2onxyocq
The below table shows the distribution of storage providers that have stored data for this client.
If this is the first time a provider takes verified deal, it will be marked as new
.
For most of the datacap application, below restrictions should apply.
⚠️ 43.76% of total deal sealed by f0522948 are duplicate data.
⚠️ 43.27% of total deal sealed by f0867300 are duplicate data.
⚠️ 40.39% of total deal sealed by f01228008 are duplicate data.
⚠️ 39.84% of total deal sealed by f01228000 are duplicate data.
⚠️ 41.33% of total deal sealed by f01228087 are duplicate data.
⚠️ 41.52% of total deal sealed by f01228105 are duplicate data.
⚠️ 41.43% of total deal sealed by f01228100 are duplicate data.
⚠️ 41.88% of total deal sealed by f01228089 are duplicate data.
⚠️ 70.92% of total deal sealed by f01114587 are duplicate data.
⚠️ 44.97% of total deal sealed by f01228065 are duplicate data.
⚠️ 44.56% of total deal sealed by f01228009 are duplicate data.
⚠️ 40.07% of total deal sealed by f023651 are duplicate data.
⚠️ f023651 has unknown IP location.
⚠️ 38.33% of total deal sealed by f01114589 are duplicate data.
⚠️ f01114589 has unknown IP location.
⚠️ 43.84% of total deal sealed by f01114827 are duplicate data.
⚠️ f020378 has unknown IP location.
Provider | Location | Total Deals Sealed | Percentage | Unique Data | Duplicate Deals |
---|---|---|---|---|---|
f0522948 | Singapore, Singapore, SG | 511.91 TiB | 8.27% | 287.91 TiB | 43.76% |
f0867300 | Tokyo, Tokyo, JP | 507.54 TiB | 8.20% | 287.91 TiB | 43.27% |
f01228008 | Sydney, New South Wales, AU | 487.20 TiB | 7.87% | 290.41 TiB | 40.39% |
f01228000 | Seoul, Seoul, KR | 477.52 TiB | 7.71% | 287.28 TiB | 39.84% |
f01228087 | London, England, GB | 447.49 TiB | 7.23% | 262.52 TiB | 41.33% |
f01228105 | Hong Kong, Central and Western, HK | 441.52 TiB | 7.13% | 258.21 TiB | 41.52% |
f01228100 | San Jose, California, US | 440.79 TiB | 7.12% | 258.18 TiB | 41.43% |
f01228089 | Frankfurt am Main, Hesse, DE | 438.91 TiB | 7.09% | 255.08 TiB | 41.88% |
f01114587 | Tokyo, Tokyo, JP | 266.09 TiB | 4.30% | 77.39 TiB | 70.92% |
f01228065 | Singapore, Singapore, SG | 261.23 TiB | 4.22% | 143.77 TiB | 44.97% |
f01228009 | Hong Kong, Central and Western, HK | 259.33 TiB | 4.19% | 143.77 TiB | 44.56% |
f023651 | Unknown | 251.03 TiB | 4.05% | 150.45 TiB | 40.07% |
f01114589 | Unknown | 233.12 TiB | 3.76% | 143.77 TiB | 38.33% |
f0134516 | Hong Kong, Central and Western, HK | 224.05 TiB | 3.62% | 216.13 TiB | 3.54% |
f0118330 | Hong Kong, Central and Western, HK | 218.26 TiB | 3.52% | 215.76 TiB | 1.15% |
f01353593new |
Hong Kong, Central and Western, HK | 130.05 TiB | 2.10% | 106.98 TiB | 17.74% |
f0522949 | Thessaloníki, Central Macedonia, GR | 105.69 TiB | 1.71% | 96.17 TiB | 9.00% |
f0118317 | Frankfurt am Main, Hesse, DE | 105.58 TiB | 1.70% | 96.11 TiB | 8.97% |
f0401135 | Helsinki, Uusimaa, FI | 103.38 TiB | 1.67% | 96.05 TiB | 7.09% |
f0522364 | Al Ain City, Abu Dhabi, AE | 102.72 TiB | 1.66% | 95.23 TiB | 7.29% |
f01114827 | Tokyo, Tokyo, JP | 100.13 TiB | 1.62% | 56.23 TiB | 43.84% |
f033463new |
Hong Kong, Central and Western, HK | 41.82 TiB | 0.68% | 41.82 TiB | 0.00% |
f01509930 | Guangzhou, Guangdong, CN | 13.32 TiB | 0.22% | 10.82 TiB | 18.76% |
f023467 | Oslo, Oslo, NO | 3.69 TiB | 0.06% | 3.65 TiB | 1.06% |
f01199442 | Heerhugowaard, North Holland, NL | 2.49 TiB | 0.04% | 2.45 TiB | 1.57% |
f0187709 | Moscow, Moscow, RU | 2.46 TiB | 0.04% | 2.46 TiB | 0.00% |
f01402814 | Singapore, Singapore, SG | 2.40 TiB | 0.04% | 2.37 TiB | 1.30% |
f01208862 | Heerhugowaard, North Holland, NL | 2.07 TiB | 0.03% | 2.04 TiB | 1.32% |
f01201327 | Heerhugowaard, North Holland, NL | 1.82 TiB | 0.03% | 1.79 TiB | 1.72% |
f01207045 | Heerhugowaard, North Holland, NL | 1.77 TiB | 0.03% | 1.76 TiB | 0.88% |
f01199430 | Heerhugowaard, North Holland, NL | 1.67 TiB | 0.03% | 1.66 TiB | 0.70% |
f03488 | Seoul, Seoul, KR | 1.23 TiB | 0.02% | 1.23 TiB | 0.00% |
f020378 | Unknown | 1.11 TiB | 0.02% | 1.10 TiB | 0.35% |
f033356 | Seoul, Seoul, KR | 1.06 TiB | 0.02% | 1.06 TiB | 0.00% |
f097777 | Kivertsi, Volyn, UA | 764.00 GiB | 0.01% | 764.00 GiB | 0.00% |
f024184 | Seoul, Seoul, KR | 584.00 GiB | 0.01% | 584.00 GiB | 0.00% |
f0440429 | Seoul, Seoul, KR | 442.00 GiB | 0.01% | 442.00 GiB | 0.00% |
f030379 | Seoul, Seoul, KR | 380.00 GiB | 0.01% | 380.00 GiB | 0.00% |
f010617 | Surrey, British Columbia, CA | 152.00 GiB | 0.00% | 152.00 GiB | 0.00% |
f01157288 | Sydney, New South Wales, AU | 24.00 GiB | 0.00% | 24.00 GiB | 0.00% |
f010088 | Everett, Washington, US | 8.00 GiB | 0.00% | 8.00 GiB | 0.00% |
f01163272 | Perm, Perm Krai, RU | 8.00 GiB | 0.00% | 8.00 GiB | 0.00% |
The below table shows how each many unique data are replicated across storage providers.
✔️ Data replication looks healthy.
Unique Data Size | Total Deals Made | Number of Providers | Deal Percentage |
---|---|---|---|
155.98 TiB | 179.05 TiB | 1 | 2.89% |
1.10 TiB | 2.23 TiB | 2 | 0.04% |
157.34 TiB | 796.75 TiB | 3 | 12.87% |
273.11 TiB | 1.84 PiB | 4 | 30.50% |
146.21 TiB | 1.14 PiB | 5 | 18.79% |
132.01 TiB | 997.17 TiB | 6 | 16.10% |
22.53 TiB | 262.81 TiB | 7 | 4.24% |
55.55 TiB | 828.88 TiB | 8 | 13.38% |
640.00 GiB | 8.13 TiB | 9 | 0.13% |
128.00 GiB | 1.72 TiB | 10 | 0.03% |
4.28 TiB | 63.59 TiB | 11 | 1.03% |
The below table shows how many unique data are shared with other clients. Usually different applications owns different data and should not resolve to the same CID.
⚠️ CID sharing has been observed.
Other Client | Application | Total Deals Affected | Unique CIDs | Verifier |
---|---|---|---|---|
f1ymfz2mqdrkrdpjmrwh4qaqtuknfpsq3lp3r3auq | Venus team | 99.95 TiB | 1,429 | LDN v3 multisig |
f1qlw5qik62kvrzvpa7bsst65uobtt3jmkrh3ajsq | アローズコーポレーション(Arrows Corporation) | 50.00 TiB | 218 | LDN v3 multisig |
f3wgfwtrs5p6jrkwfl2mksqa2ivgbgdjjrhjbefy3 n7qzvotc3y6sazmp5gfyj7um6jlgdvlbiepzawnc6 wxtq |
FileDrive Labs | 30.50 TiB | 368 | LDN v3 multisig |
f1pkrmygbvweykpjcut36lf7ewgqdfhjklbhvepda | Protocol Labs ( project: Slingshot Evergreen ) | 7.54 TiB | 262 | LDN # 293 |
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
Fatman13 is an active developer in the community. The CID Checker results look good and is willing to support it
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzaceb6tn7swvasajcoad67mhp4qg7fhrumhymvw5kgyd4yjov2ewbc6m
Address
f3qaipvxrz2gxexc7mcvjsxifmscfiw7c7zfhrmq76j5ee4hcbvg3gbtpea7wgz72kkjcjmwzhm5uo2onxyocq
Datacap Allocated
250.00TiB
Signer Address
f1e77zuityhvvw6u2t6tb5qlnsegy2s67qs4lbbbq
Id
f9d46ada-0afc-461b-ae68-873792ae4d1d
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceb6tn7swvasajcoad67mhp4qg7fhrumhymvw5kgyd4yjov2ewbc6m
It seems (given my crowded inbox) that in the past 15 minutes @newwebgroup has approved 10+ datacap requests.
I wonder if this blind approval is allowed?
Would like to see per project what due diligence you did to explain the approval @newwebgroup.
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacedelgc7kk7j2rifmqgw27ikag7vssjj4h5yiwzjscyf6lfiuewcqk
Address
f3qaipvxrz2gxexc7mcvjsxifmscfiw7c7zfhrmq76j5ee4hcbvg3gbtpea7wgz72kkjcjmwzhm5uo2onxyocq
Datacap Allocated
250.00TiB
Signer Address
f1yjhnsoga2ccnepb7t3p3ov5fzom3syhsuinxexa
Id
f9d46ada-0afc-461b-ae68-873792ae4d1d
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedelgc7kk7j2rifmqgw27ikag7vssjj4h5yiwzjscyf6lfiuewcqk
f02049625
f3qaipvxrz2gxexc7mcvjsxifmscfiw7c7zfhrmq76j5ee4hcbvg3gbtpea7wgz72kkjcjmwzhm5uo2onxyocq
500TiB
3fe6adf8-dcda-45b0-b498-649ea3e9b410
f01858410
f3qaipvxrz2gxexc7mcvjsxifmscfiw7c7zfhrmq76j5ee4hcbvg3gbtpea7wgz72kkjcjmwzhm5uo2onxyocq
kernelogic & newwebgroup
100% of weekly dc amount requested
500TiB
3.43PiB
1.56PiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
115803 | 23 | 250TiB | 11.62 | 73.83GiB |
Guazi Dynamic
f3qaipvxrz2gxexc7mcvjsxifmscfiw7c7zfhrmq76j5ee4hcbvg3gbtpea7wgz72kkjcjmwzhm5uo2onxyocq
1
kernelogic1
newwebgroup
The below table shows the distribution of storage providers that have stored data for this client.
If this is the first time a provider takes verified deal, it will be marked as new
.
For most of the datacap application, below restrictions should apply.
Since this is the 3rd allocation, the following restrictions have been relaxed:
⚠️ 46.89% of total deal sealed by f01228087 are duplicate data.
⚠️ 43.76% of total deal sealed by f0522948 are duplicate data.
⚠️ 43.27% of total deal sealed by f0867300 are duplicate data.
⚠️ 49.12% of total deal sealed by f01228105 are duplicate data.
⚠️ 49.10% of total deal sealed by f01228100 are duplicate data.
⚠️ 49.63% of total deal sealed by f01228089 are duplicate data.
⚠️ 40.39% of total deal sealed by f01228008 are duplicate data.
⚠️ 39.84% of total deal sealed by f01228000 are duplicate data.
⚠️ 70.92% of total deal sealed by f01114587 are duplicate data.
⚠️ 44.97% of total deal sealed by f01228065 are duplicate data.
⚠️ 44.56% of total deal sealed by f01228009 are duplicate data.
⚠️ 40.07% of total deal sealed by f023651 are duplicate data.
⚠️ f023651 has unknown IP location.
⚠️ 38.33% of total deal sealed by f01114589 are duplicate data.
⚠️ f01114589 has unknown IP location.
⚠️ 43.84% of total deal sealed by f01114827 are duplicate data.
⚠️ f020378 has unknown IP location.
Provider | Location | Total Deals Sealed | Percentage | Unique Data | Duplicate Deals |
---|---|---|---|---|---|
f01228087 | London, England, GBAlibaba (US) Technology Co., Ltd. |
512.45 TiB | 7.97% | 272.18 TiB | 46.89% |
f0522948 | Singapore, Singapore, SGAlibaba (US) Technology Co., Ltd. |
511.91 TiB | 7.96% | 287.91 TiB | 43.76% |
f0867300 | Tokyo, Tokyo, JPAlibaba (US) Technology Co., Ltd. |
507.54 TiB | 7.89% | 287.91 TiB | 43.27% |
f01228105 | Hong Kong, Central and Western, HKAlibaba (US) Technology Co., Ltd. |
507.46 TiB | 7.89% | 258.21 TiB | 49.12% |
f01228100 | San Jose, California, USAlibaba (US) Technology Co., Ltd. |
507.21 TiB | 7.89% | 258.18 TiB | 49.10% |
f01228089 | Frankfurt am Main, Hesse, DEAlibaba (US) Technology Co., Ltd. |
506.40 TiB | 7.87% | 255.08 TiB | 49.63% |
f01228008 | Sydney, New South Wales, AUAlibaba (US) Technology Co., Ltd. |
487.20 TiB | 7.58% | 290.41 TiB | 40.39% |
f01228000 | Seoul, Seoul, KRAlibaba (US) Technology Co., Ltd. |
477.52 TiB | 7.42% | 287.28 TiB | 39.84% |
f01114587 | Tokyo, Tokyo, JPAlibaba (US) Technology Co., Ltd. |
266.09 TiB | 4.14% | 77.39 TiB | 70.92% |
f01228065 | Singapore, Singapore, SGAlibaba (US) Technology Co., Ltd. |
261.23 TiB | 4.06% | 143.77 TiB | 44.97% |
f01228009 | Hong Kong, Central and Western, HKAlibaba (US) Technology Co., Ltd. |
259.33 TiB | 4.03% | 143.77 TiB | 44.56% |
f023651 | UnknownUnknown |
251.03 TiB | 3.90% | 150.45 TiB | 40.07% |
f01114589 | UnknownUnknown |
233.12 TiB | 3.62% | 143.77 TiB | 38.33% |
f0134516 | Hong Kong, Central and Western, HKAlibaba (US) Technology Co., Ltd. |
224.05 TiB | 3.48% | 216.13 TiB | 3.54% |
f0118330 | Hong Kong, Central and Western, HKAlibaba (US) Technology Co., Ltd. |
218.26 TiB | 3.39% | 215.76 TiB | 1.15% |
f01114827 | Tokyo, Tokyo, JPAlibaba (US) Technology Co., Ltd. |
100.13 TiB | 1.56% | 56.23 TiB | 43.84% |
f01509930 | Guangzhou, Guangdong, CNCHINANET Guangdong province network |
13.32 TiB | 0.21% | 10.82 TiB | 18.76% |
f0401135 | Helsinki, Uusimaa, FICSC - Tieteen tietotekniikan keskus Oy |
103.38 TiB | 1.61% | 96.05 TiB | 7.09% |
f01157288 | Sydney, New South Wales, AUDATACOM SYSTEMS (AU) PTY LTD |
24.00 GiB | 0.00% | 24.00 GiB | 0.00% |
f0522364 | Ar Ruways, Abu Dhabi, AEEmirates Telecommunications Corporation |
82.92 TiB | 1.29% | 80.42 TiB | 3.01% |
f0118317 | Frankfurt am Main, Hesse, DEeuNetworks GmbH |
105.58 TiB | 1.64% | 96.11 TiB | 8.97% |
f0522949 | Thessaloníki, Central Macedonia, GRForthnet |
85.89 TiB | 1.34% | 83.39 TiB | 2.91% |
f03488 | Seoul, Seoul, KRLG DACOM Corporation |
1.23 TiB | 0.02% | 1.23 TiB | 0.00% |
f033356 | Seoul, Seoul, KRLG DACOM Corporation |
1.06 TiB | 0.02% | 1.06 TiB | 0.00% |
f024184 | Seoul, Seoul, KRLG DACOM Corporation |
584.00 GiB | 0.01% | 584.00 GiB | 0.00% |
f0440429 | Bucheon-si, Gyeonggi-do, KRLG DACOM Corporation |
442.00 GiB | 0.01% | 442.00 GiB | 0.00% |
f030379 | Gangneung, Gangwon-do, KRLG DACOM Corporation |
380.00 GiB | 0.01% | 380.00 GiB | 0.00% |
f097777 | Kivertsi, Volyn, UALink Telecom Service Ltd |
764.00 GiB | 0.01% | 764.00 GiB | 0.00% |
f0187709 | Moscow, Moscow, RUMTS PJSC |
2.46 TiB | 0.04% | 2.46 TiB | 0.00% |
f023467 | Oslo, Oslo, NONexthop AS |
3.69 TiB | 0.06% | 3.65 TiB | 1.06% |
f01163272 | Lys’va, Perm Krai, RUPJSC Rostelecom |
8.00 GiB | 0.00% | 8.00 GiB | 0.00% |
f01402814 | Singapore, Singapore, SGStarHub Ltd |
2.40 TiB | 0.04% | 2.37 TiB | 1.30% |
f010617 | Surrey, British Columbia, CATELUS Communications Inc. |
152.00 GiB | 0.00% | 152.00 GiB | 0.00% |
f010088 | Everett, Washington, USWholesail networks LLC |
8.00 GiB | 0.00% | 8.00 GiB | 0.00% |
f01199442 | Heerhugowaard, North Holland, NLWijnand Schouten trading as Speedium |
2.49 TiB | 0.04% | 2.45 TiB | 1.57% |
f01208862 | Heerhugowaard, North Holland, NLWijnand Schouten trading as Speedium |
2.07 TiB | 0.03% | 2.04 TiB | 1.32% |
f01201327 | Heerhugowaard, North Holland, NLWijnand Schouten trading as Speedium |
1.82 TiB | 0.03% | 1.79 TiB | 1.72% |
f01207045 | Heerhugowaard, North Holland, NLWijnand Schouten trading as Speedium |
1.77 TiB | 0.03% | 1.76 TiB | 0.88% |
f01199430 | Heerhugowaard, North Holland, NLWijnand Schouten trading as Speedium |
1.67 TiB | 0.03% | 1.66 TiB | 0.70% |
f01353593new |
Hong Kong, Central and Western, HKZenlayer Inc |
130.05 TiB | 2.02% | 106.98 TiB | 17.74% |
f033463new |
Hong Kong, Central and Western, HKZenlayer Inc |
55.43 TiB | 0.86% | 55.43 TiB | 0.00% |
f020378 | UnknownUnknown |
1.11 TiB | 0.02% | 1.10 TiB | 0.35% |
The below table shows how each many unique data are replicated across storage providers.
Since this is the 3rd allocation, the following restrictions have been relaxed:
✔️ Data replication looks healthy.
Unique Data Size | Total Deals Made | Number of Providers | Deal Percentage |
---|---|---|---|
179.05 TiB | 202.13 TiB | 1 | 3.14% |
1.10 TiB | 2.23 TiB | 2 | 0.03% |
157.15 TiB | 796.19 TiB | 3 | 12.38% |
279.25 TiB | 2.12 PiB | 4 | 33.72% |
161.90 TiB | 1.23 PiB | 5 | 19.55% |
110.37 TiB | 839.64 TiB | 6 | 13.06% |
22.53 TiB | 262.81 TiB | 7 | 4.09% |
55.55 TiB | 828.88 TiB | 8 | 12.89% |
640.00 GiB | 8.13 TiB | 9 | 0.13% |
128.00 GiB | 1.72 TiB | 10 | 0.03% |
4.28 TiB | 63.59 TiB | 11 | 0.99% |
The below table shows how many unique data are shared with other clients. Usually different applications owns different data and should not resolve to the same CID.
However, this could be possible if all below clients use same software to prepare for the exact same dataset or they belong to a series of LDN applications for the same dataset.
⚠️ CID sharing has been observed.
Other Client | Application | Total Deals Affected | Unique CIDs | Approvers |
---|---|---|---|---|
f1ymfz2mqdrkrdpjmrwh4qaqtuknfpsq3lp3r3auq | 99.95 TiB | 1,429 | 1 cryptowhizzard2 kernelogic1 stcouldlisa |
|
f1qlw5qik62kvrzvpa7bsst65uobtt3jmkrh3ajsq | アローズコーポレーション(Arrows Corporation) | 50.00 TiB | 218 | 1 Joss-Hua1 kernelogic1 psh0691 |
f3wgfwtrs5p6jrkwfl2mksqa2ivgbgdjjrhjbefy3 n7qzvotc3y6sazmp5gfyj7um6jlgdvlbiepzawnc6 wxtq |
FileDrive Labs | 30.50 TiB | 368 | 1 GaryGJG1 IreneYoung3 Joss-Hua1 liyunzhi-6661 MegTei1 MetaWaveInfo3 newwebgroup2 psh0691 |
f1pkrmygbvweykpjcut36lf7ewgqdfhjklbhvepda | Protocol Labs ( project: Slingshot Evergreen ) | 7.54 TiB | 262 | 4 cryptowhizzard3 fabriziogianni73 flyworker1 jimcray3 MegTei2 s0nik421 swatchliu1 TimWilliams00 |
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
Sorry about high duplication on some nodes. We had some bugs in our deal distribution software which caused duplicates to be sent to nodes. The issue should be fixed for future allocations, however the records will stay.
@Fatman13 At least we can now follow the numbers and check if everything is going allright. Keep the transparency and try the best you can.
Singularity has gotten an update to remove duplicates: https://github.com/tech-greedy/singularity
Good luck with the next batch.
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacec6fccmdumx2tpjxamkmipfdpdujbq5j3v6quymfkf3lzqkzikwsw
Address
f3qaipvxrz2gxexc7mcvjsxifmscfiw7c7zfhrmq76j5ee4hcbvg3gbtpea7wgz72kkjcjmwzhm5uo2onxyocq
Datacap Allocated
500.00TiB
Signer Address
f1yjhnsoga2ccnepb7t3p3ov5fzom3syhsuinxexa
Id
3fe6adf8-dcda-45b0-b498-649ea3e9b410
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacec6fccmdumx2tpjxamkmipfdpdujbq5j3v6quymfkf3lzqkzikwsw
I checked on this app. Retrieval works. Duplicates are as expected as Evergreen / Fildrive to replications.
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacebzn765b2yzo4tgiycy67txnl2okp7owaedercebx4g26exs22dtk
Address
f3qaipvxrz2gxexc7mcvjsxifmscfiw7c7zfhrmq76j5ee4hcbvg3gbtpea7wgz72kkjcjmwzhm5uo2onxyocq
Datacap Allocated
500.00TiB
Signer Address
f1krmypm4uoxxf3g7okrwtrahlmpcph3y7rbqqgfa
Id
3fe6adf8-dcda-45b0-b498-649ea3e9b410
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebzn765b2yzo4tgiycy67txnl2okp7owaedercebx4g26exs22dtk
f02049625
f3qaipvxrz2gxexc7mcvjsxifmscfiw7c7zfhrmq76j5ee4hcbvg3gbtpea7wgz72kkjcjmwzhm5uo2onxyocq
1000.0TiB
a1335dbd-ff9a-4bd3-8a84-d76193c4104f
f01858410
f3qaipvxrz2gxexc7mcvjsxifmscfiw7c7zfhrmq76j5ee4hcbvg3gbtpea7wgz72kkjcjmwzhm5uo2onxyocq
cryptowhizzard & kernelogic
200% of weekly dc amount requested
1000.0TiB
4.17PiB
848.84TiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
136498 | 29 | 500TiB | 9.91 | 124.81TiB |
⚠️ 14 storage providers sealed too much duplicate data - f01228087: 46.89%, f01228105: 49.12%, f01228100: 49.10%, f01228089: 49.63%, f01228008: 40.39%, f01228000: 39.84%, f0522948: 41.02%, f0867300: 39.92%, f01114587: 70.92%, f01228065: 44.97%, f01228009: 44.56%, f023651: 40.07%, f01114827: 43.84%, f01114589: 25.62%
⚠️ 3 storage providers have unknown IP location - f023651, f01114589, f020378
✔️ 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 full report.
Hi @Fatman13
I am still supportive on this one, but can you contact the SP's who are not reachable and have them correct the situation. It's just a small portion, but if it's an easy fix that would be welcome.
The CID sharing with arrows is expected. You are storing ( parts ) of the same dataset. If this is not true please message me.
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacec5f5jgd4m5dnc3ntz7qdoto4n45lbjnaundrq3ux4aqyi44sslsc
Address
f3qaipvxrz2gxexc7mcvjsxifmscfiw7c7zfhrmq76j5ee4hcbvg3gbtpea7wgz72kkjcjmwzhm5uo2onxyocq
Datacap Allocated
1000.00TiB
Signer Address
f1krmypm4uoxxf3g7okrwtrahlmpcph3y7rbqqgfa
Id
a1335dbd-ff9a-4bd3-8a84-d76193c4104f
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacec5f5jgd4m5dnc3ntz7qdoto4n45lbjnaundrq3ux4aqyi44sslsc
but can you contact the SP's who are not reachable and have them correct the situation.
Yes, will do! They just switched to a relatively new team of devOps, will send them docs to register their multiaddress onchain.
I mistaken them for these nodes. I will have the team to dig bit more. These might be SP we worked with long long time ago.
checker:manualTrigger
⚠️ 14 storage providers sealed too much duplicate data - f01228087: 46.89%, f01228105: 49.12%, f01228100: 49.10%, f01228089: 49.63%, f01228008: 40.39%, f01228000: 39.84%, f0522948: 42.77%, f0867300: 42.20%, f01114587: 70.92%, f01228065: 44.97%, f01228009: 44.56%, f023651: 36.23%, f01114589: 30.99%, f01114827: 43.84%
⚠️ 3 storage providers have unknown IP location - f023651, f01114589, f020378
✔️ 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 full report.
hi, @Fatman13 the problem is still not resolved, is there any progress on your side?
Hello, @liyunzhi-666, thank you for asking! As we explained earlier, it was due to bugs in our legacy deal-making software. We will be using new client address once we done with this legacy LDN to minimize confusion.
Your Datacap Allocation Request has been approved by the Notary
bafy2bzaceajrlanmoppre2yw4jmkwe46gnmmfivglep64ahd7rzpktrv4nxqi
Address
f3qaipvxrz2gxexc7mcvjsxifmscfiw7c7zfhrmq76j5ee4hcbvg3gbtpea7wgz72kkjcjmwzhm5uo2onxyocq
Datacap Allocated
1000.00TiB
Signer Address
f1pszcrsciyixyuxxukkvtazcokexbn54amf7gvoq
Id
a1335dbd-ff9a-4bd3-8a84-d76193c4104f
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceajrlanmoppre2yw4jmkwe46gnmmfivglep64ahd7rzpktrv4nxqi
f02049625
f3qaipvxrz2gxexc7mcvjsxifmscfiw7c7zfhrmq76j5ee4hcbvg3gbtpea7wgz72kkjcjmwzhm5uo2onxyocq
1.95PiB
15444189-7201-4801-9184-285dca5b0318
f01858410
f3qaipvxrz2gxexc7mcvjsxifmscfiw7c7zfhrmq76j5ee4hcbvg3gbtpea7wgz72kkjcjmwzhm5uo2onxyocq
liyunzhi-666 & cryptowhizzard
400% of weekly dc amount requested
1.95PiB
4.17PiB
848.84TiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
141502 | 30 | 1000.0TiB | 9.58 | 3.83GiB |
⚠️ 14 storage providers sealed too much duplicate data - f01228087: 46.89%, f01228105: 49.12%, f01228100: 49.10%, f01228089: 49.63%, f01228008: 40.39%, f01228000: 39.84%, f0522948: 42.77%, f0867300: 42.20%, f01114587: 70.92%, f01228065: 44.97%, f01228009: 44.56%, f023651: 36.23%, f01114589: 30.99%, f01114827: 43.84%
⚠️ 3 storage providers have unknown IP location - f023651, f01114589, f020378
✔️ 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 full report.
checker:manualTrigger
⚠️ 14 storage providers sealed too much duplicate data - f01228087: 46.89%, f01228105: 49.12%, f01228100: 49.10%, f01228089: 49.63%, f01228008: 40.39%, f01228000: 39.84%, f0522948: 42.77%, f0867300: 42.20%, f01114587: 70.92%, f01228065: 44.97%, f01228009: 44.56%, f023651: 36.23%, f01114589: 30.99%, f01114827: 43.84%
⚠️ 3 storage providers have unknown IP location - f023651, f01114589, f020378
✔️ 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 full report.
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacecsfvzjzte2z36gy4tff5pr6ylexvcs7mhyz4lbe5jlskoc5jbkpk
Address
f3qaipvxrz2gxexc7mcvjsxifmscfiw7c7zfhrmq76j5ee4hcbvg3gbtpea7wgz72kkjcjmwzhm5uo2onxyocq
Datacap Allocated
1.95PiB
Signer Address
f1bp3tzp536edm7dodldceekzbsx7zcy7hdfg6uzq
Id
15444189-7201-4801-9184-285dca5b0318
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacecsfvzjzte2z36gy4tff5pr6ylexvcs7mhyz4lbe5jlskoc5jbkpk
Discussed with @Fatman13 this program and his future distribution plan. Willing to support this round and hope to see much improvement in the Checker report.
Your Datacap Allocation Request has been approved by the Notary
bafy2bzaced2lzytsfzmcixdzxenpb3vlutjqmmxic663kh7dk4t44i3265vsk
Address
f3qaipvxrz2gxexc7mcvjsxifmscfiw7c7zfhrmq76j5ee4hcbvg3gbtpea7wgz72kkjcjmwzhm5uo2onxyocq
Datacap Allocated
1.95PiB
Signer Address
f1dnb3uz7sylxk6emti3ififcvu3nlufnnsjui6ea
Id
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaced2lzytsfzmcixdzxenpb3vlutjqmmxic663kh7dk4t44i3265vsk
The issue reached the total datacap requested. This should be closed
f02049625
f3qaipvxrz2gxexc7mcvjsxifmscfiw7c7zfhrmq76j5ee4hcbvg3gbtpea7wgz72kkjcjmwzhm5uo2onxyocq
total dc reached
0
1.8160790205001834e+267YiB
-2.19B
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
95388 | 20 | 1.95PiB | 7.03 | 459.90TiB |
Client f0215074 does not follow the datacap usage rules. More info here. This application has been failing the requirements for 7 days. Please take appropiate action to fix the following DataCap usage problems. | Criteria | Treshold | Reason |
---|---|---|---|
Percent of used DataCap stored with top provider | < 75 | The percent of Data from the client that is stored with their top provider is 100%. This should be less than 75% | |
Shared data percent | < 20% | 20.04% of the clients data is shared with other clients. This should be less than 20% |
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?