Closed Leozhang404 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.
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
2PiB
Expected weekly DataCap usage rate
90TiB
Client address
f13zfhkvtf6mewd74jhav6iqcggwsojht73tickga
f01858410
f13zfhkvtf6mewd74jhav6iqcggwsojht73tickga
45TiB
@flyworker, tagging as application mentions FilSwan. Please provide input if you know of the client to help build trust with notaries
@raghavrmadya Thanks for let me know. There are raise of interests using filswan in the community as the datacap distributor. i believe they have some channel or in the community using it. I have the following questions for @Leozhang404
@raghavrmadya Thanks for let me know. There are raise of interests using filswan in the community as the datacap distributor. i believe they have some channel or in the community using it. I have the following questions for @Leozhang404
- Where did you hear about FilSwan?
- Which tool will you use for sending out deals?
- Do you have preference of the region?
Thanks @flyworker for your reply
FilSwan is very famous in China region, there is a 200+ developers wechat group . SPs get the deal daily so we know the project and tools well. Recently the DataDAO hackathon is spreading in lots of wechat groups so we know this platform
We have tried the swan client tool (https://github.com/filswan/go-swan-client) it works well
We don't have preference of geolocations but we may prefer to have more copies in China, since the content have more audience in China
As a voluntary distributed research organization, in the long run, we do not have enough storage space to store our important research and activity data, so we hope to find a suitable long-term storage method. I’m one of the community members of FilSwan and have been following their project progress. As far as I know, FilSwan has a set of mature tools that can help us store our data onto the Filecoin network conviniently. Through the Filswan official website, their personnel and the community, we’ve also learned that they have many providers who could support the storage. Therefore we believe choosing FilSwan is a good way for us.
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacebwdd27vmpsjltagb6qvkmshm7qwavbhjk6scajdz3yq32m3jrog4
Address
f13zfhkvtf6mewd74jhav6iqcggwsojht73tickga
Datacap Allocated
45.00TiB
Signer Address
f13k5zr6ovc2gjmg3lvd43ladbydhovpylcvbflpa
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebwdd27vmpsjltagb6qvkmshm7qwavbhjk6scajdz3yq32m3jrog4
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacecipypq4i3gvsyvpniclkgmgdrjbiq2i2x7rncsilg266dzqixweg
Address
f13zfhkvtf6mewd74jhav6iqcggwsojht73tickga
Datacap Allocated
45.00TiB
Signer Address
f1yjhnsoga2ccnepb7t3p3ov5fzom3syhsuinxexa
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacecipypq4i3gvsyvpniclkgmgdrjbiq2i2x7rncsilg266dzqixweg
@Leozhang404 Hi! Great to see you have gotten approval for DataCap. If you are looking for more storage providers to store these data or have any questions, please visit #bigdata-exchange on Filecoin Slack or reply here.
We have strong demand from a diverse group of SPs, who are actively looking to onboard more data.
f01858410
f13zfhkvtf6mewd74jhav6iqcggwsojht73tickga
90TiB
f01858410
f13zfhkvtf6mewd74jhav6iqcggwsojht73tickga
kernelogic & neogeweb3
100% of weekly dc amount requested
90TiB
45TiB
1.95PiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
undefined | undefined | 45TiB | 12.62 | 9.37TiB |
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacedlfcqyqqj67yixcqhvtk4222vwkbfhxpa26grkufiyfm26wl3f3s
Address
f13zfhkvtf6mewd74jhav6iqcggwsojht73tickga
Datacap Allocated
90.00TiB
Signer Address
f1d4gmpqz3execjj2wvrxuuhvbms5mzh7t7yqrviq
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedlfcqyqqj67yixcqhvtk4222vwkbfhxpa26grkufiyfm26wl3f3s
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacebw2lxjbm2lyuxcfmsi42hjo2orezc3cd2si5w6mvw4qcuh2sqtuc
Address
f13zfhkvtf6mewd74jhav6iqcggwsojht73tickga
Datacap Allocated
90.00TiB
Signer Address
f1krmypm4uoxxf3g7okrwtrahlmpcph3y7rbqqgfa
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebw2lxjbm2lyuxcfmsi42hjo2orezc3cd2si5w6mvw4qcuh2sqtuc
X-Order Lab
f13zfhkvtf6mewd74jhav6iqcggwsojht73tickga
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.
⚠️ f01947280 has sealed 26.93% of total datacap.
Provider | Location | Total Deals Sealed | Percentage | Unique Data | Duplicate Deals |
---|---|---|---|---|---|
f01947280 | Hangzhou, Zhejiang, CN | 16.34 TiB | 26.93% | 16.09 TiB | 1.53% |
f01786736 | Saint-Gabriel, Quebec, CA | 5.00 TiB | 8.24% | 5.00 TiB | 0.00% |
f01896422 | Fremont, California, US | 4.06 TiB | 6.69% | 4.06 TiB | 0.00% |
f01225882 | Burnaby, British Columbia, CA | 4.06 TiB | 6.69% | 4.06 TiB | 0.00% |
f01858429 | Boston, Massachusetts, US | 4.03 TiB | 6.64% | 4.03 TiB | 0.00% |
f01390330 | Xi’an, Shaanxi, CN | 3.69 TiB | 6.08% | 3.69 TiB | 0.00% |
f0240185 | Clifton, New Jersey, US | 3.53 TiB | 5.82% | 3.53 TiB | 0.00% |
f0143858 | Clifton, New Jersey, US | 3.44 TiB | 5.66% | 3.44 TiB | 0.00% |
f01402814 | Singapore, Singapore, SG | 3.00 TiB | 4.94% | 3.00 TiB | 0.00% |
f01886797 | Vancouver, British Columbia, CA | 2.97 TiB | 4.89% | 2.97 TiB | 0.00% |
f01163272 | Perm, Perm Krai, RU | 2.03 TiB | 3.35% | 2.03 TiB | 0.00% |
f010088 | Everett, Washington, US | 1.97 TiB | 3.24% | 1.97 TiB | 0.00% |
f0187709 | Moscow, Moscow, RU | 1.75 TiB | 2.88% | 1.75 TiB | 0.00% |
f01222595 | Moscow, Moscow, RU | 1.66 TiB | 2.73% | 1.66 TiB | 0.00% |
f08399 | Seattle, Washington, US | 1.50 TiB | 2.47% | 1.50 TiB | 0.00% |
f0214334 | Gwangju, Gwangju, KR | 1.00 TiB | 1.65% | 1.00 TiB | 0.00% |
f0717969 | Los Angeles, California, US | 448.00 GiB | 0.72% | 448.00 GiB | 0.00% |
f01683871 | Gwangju, Gwangju, KR | 160.00 GiB | 0.26% | 160.00 GiB | 0.00% |
f01955030new |
Hangzhou, Zhejiang, CN | 32.00 GiB | 0.05% | 32.00 GiB | 0.00% |
f01708981 | Shenzhen, Guangdong, CN | 32.00 GiB | 0.05% | 32.00 GiB | 0.00% |
The below table shows how each many unique data are replicated across storage providers.
⚠️ 30.07% of deals are for data replicated across less than 4 storage providers.
Unique Data Size | Total Deals Made | Number of Providers | Deal Percentage |
---|---|---|---|
18.00 TiB | 18.25 TiB | 1 | 30.07% |
480.00 GiB | 3.28 TiB | 7 | 5.41% |
544.00 GiB | 4.25 TiB | 8 | 7.00% |
512.00 GiB | 4.50 TiB | 9 | 7.42% |
576.00 GiB | 5.63 TiB | 10 | 9.27% |
512.00 GiB | 5.50 TiB | 11 | 9.06% |
672.00 GiB | 7.88 TiB | 12 | 12.98% |
576.00 GiB | 7.31 TiB | 13 | 12.05% |
128.00 GiB | 1.75 TiB | 14 | 2.88% |
160.00 GiB | 2.34 TiB | 15 | 3.86% |
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 |
---|---|---|---|---|
f1o54sve7ede7im4caux3ug7lsyjmbue7ss3zzl6y | FilSwan | 59.25 TiB | 562 | LDN v3 multisig |
f1bstbq5bi72kyovhh7zoo2f6l6uivsjz4ey5dnqq | FilSwan | 27.72 TiB | 298 | LDN v3 multisig |
f1j22hqwh5tijbaztl7a7plzk5q2s4cesd67nyv3a | FilSwan | 7.72 TiB | 62 | LDN v3 multisig |
f3v7x4a2aapgx6o2r477tenoin3u5oadaeqyd7kjd sitykvf4ok7vq2utcyh34lmu5u7oybs25ff6s4dbu dpma |
LeoCheung - Slingshot Restore | 5.53 TiB | 33 | LDN v3 multisig |
f3rwypb3nhyzkslf6eb2qoiaqdwvaedcawxiav4hm hi4cp4w7ptjua42knqoddbl5uabcrtzgq7jajvjro z54a |
dropcool - Slingshot Restore | 1.63 TiB | 33 | LDN v3 multisig |
f14r2jybmccwiu6hze4fu55jyhclktvwacec56hea | FilSwan | 544.00 GiB | 11 | LDN v3 multisig |
f13d6zt424jkp55u7kp67azotkzadtlokwnz2ntxa | FilSwan - Slingshot Restore | 192.00 GiB | 6 | LDN v3 multisig |
f1r3d25hl2y7rqlsu2mgczdethy4qqjmkfdlmibfq | NEXRAD - FilSwan | 96.00 GiB | 3 | LDN v3 multisig |
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
f01858410
f13zfhkvtf6mewd74jhav6iqcggwsojht73tickga
180TiB
1175e6c0-ab1f-4a48-b423-fd3177fbd20b
f01858410
f13zfhkvtf6mewd74jhav6iqcggwsojht73tickga
cryptowhizzard & IreneYoung
200% of weekly dc amount requested
180TiB
135TiB
1.86PiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
3187 | 23 | 90TiB | 16.88 | 22.03TiB |
X-Order Lab
f13zfhkvtf6mewd74jhav6iqcggwsojht73tickga
1
cryptowhizzard1
IreneYoung1
kernelogic1
neogeweb3
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:
⚠️ f01981571 has unknown IP location.
Provider | Location | Total Deals Sealed | Percentage | Unique Data | Duplicate Deals |
---|---|---|---|---|---|
f01225882 | Burnaby, British Columbia, CAAstute Hosting Inc. |
4.06 TiB | 4.35% | 4.06 TiB | 0.00% |
f01947280 | Hangzhou, Zhejiang, CNChina Mobile communications corporation |
16.34 TiB | 17.50% | 16.09 TiB | 1.53% |
f01955030new |
Hangzhou, Zhejiang, CNChina Mobile communications corporation |
32.00 GiB | 0.03% | 32.00 GiB | 0.00% |
f01390330 | Xi’an, Shaanxi, CNCHINANET-BACKBONE |
3.69 TiB | 3.95% | 3.69 TiB | 0.00% |
f01708981 | Shenzhen, Guangdong, CNCHINANET-BACKBONE |
32.00 GiB | 0.03% | 32.00 GiB | 0.00% |
f01858429 | Boston, Massachusetts, USComcast Cable Communications, LLC |
4.03 TiB | 4.32% | 4.03 TiB | 0.00% |
f0240185 | Clifton, New Jersey, USDigitalOcean, LLC |
3.53 TiB | 3.78% | 3.53 TiB | 0.00% |
f0143858 | Clifton, New Jersey, USDigitalOcean, LLC |
3.44 TiB | 3.68% | 3.44 TiB | 0.00% |
f01938223 | Montréal, Quebec, CAeStruxture Data Centers Inc. |
11.25 TiB | 12.05% | 11.25 TiB | 0.00% |
f01786736 | Saint-Gabriel, Quebec, CAeStruxture Data Centers Inc. |
5.00 TiB | 5.35% | 5.00 TiB | 0.00% |
f08399 | Seattle, Washington, USIsomedia, Inc. |
1.50 TiB | 1.61% | 1.50 TiB | 0.00% |
f0214334 | Gwangju, Gwangju, KRKorea Telecom |
1.00 TiB | 1.07% | 1.00 TiB | 0.00% |
f01683871 | Gwangju, Gwangju, KRKorea Telecom |
160.00 GiB | 0.17% | 160.00 GiB | 0.00% |
f0717969 | Los Angeles, California, USKrypt Technologies |
448.00 GiB | 0.47% | 448.00 GiB | 0.00% |
f01222595 | Moscow, Moscow, RUMTS PJSC |
1.66 TiB | 1.77% | 1.66 TiB | 0.00% |
f01402814 | Singapore, Singapore, SGStarHub Ltd |
3.00 TiB | 3.21% | 3.00 TiB | 0.00% |
f01970622 | Hong Kong, Central and Western, HKUCLOUD INFORMATION TECHNOLOGY (HK) LIMITED |
14.19 TiB | 15.19% | 14.19 TiB | 0.00% |
f01981571 | UnknownUnknown |
5.72 TiB | 6.12% | 5.72 TiB | 0.00% |
f01896422 | Fremont, California, USHurricane Electric LLC |
4.06 TiB | 4.35% | 4.06 TiB | 0.00% |
f0187709 | Moscow, Moscow, RUMTS PJSC |
1.75 TiB | 1.87% | 1.75 TiB | 0.00% |
f01163272 | Lys’va, Perm Krai, RUPJSC Rostelecom |
2.03 TiB | 2.18% | 2.03 TiB | 0.00% |
f0705704 | Taipei, Taiwan, TWUCLOUD INFORMATION TECHNOLOGY (HK) LIMITED |
1.53 TiB | 1.64% | 1.53 TiB | 0.00% |
f010088 | Everett, Washington, USWholesail networks LLC |
1.97 TiB | 2.11% | 1.97 TiB | 0.00% |
f01886797 | Vancouver, British Columbia, CAZayo Bandwidth |
2.97 TiB | 3.18% | 2.97 TiB | 0.00% |
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 |
---|---|---|---|
31.19 TiB | 31.44 TiB | 1 | 33.67% |
7.72 TiB | 15.44 TiB | 2 | 16.53% |
480.00 GiB | 3.75 TiB | 8 | 4.02% |
544.00 GiB | 4.78 TiB | 9 | 5.12% |
512.00 GiB | 5.00 TiB | 10 | 5.35% |
576.00 GiB | 6.19 TiB | 11 | 6.63% |
512.00 GiB | 6.00 TiB | 12 | 6.43% |
672.00 GiB | 8.53 TiB | 13 | 9.14% |
576.00 GiB | 7.88 TiB | 14 | 8.43% |
128.00 GiB | 1.88 TiB | 15 | 2.01% |
160.00 GiB | 2.50 TiB | 16 | 2.68% |
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 |
---|---|---|---|---|
f1o54sve7ede7im4caux3ug7lsyjmbue7ss3zzl6y | FilSwan | 74.56 TiB | 601 | 3 cryptowhizzard3 IreneYoung1 jamerduhgamer1 Joss-Hua9 kernelogic2 liyunzhi-6661 xingjitansuo |
f1bstbq5bi72kyovhh7zoo2f6l6uivsjz4ey5dnqq | FilSwan | 41.47 TiB | 670 | 3 cryptowhizzard1 IreneYoung7 kernelogic2 liyunzhi-6661 psh0691 |
f1j22hqwh5tijbaztl7a7plzk5q2s4cesd67nyv3a | FilSwan | 19.63 TiB | 321 | 3 cryptowhizzard4 kernelogic1 liyunzhi-666 |
f3v7x4a2aapgx6o2r477tenoin3u5oadaeqyd7kjd sitykvf4ok7vq2utcyh34lmu5u7oybs25ff6s4dbu dpma |
LeoCheung - Slingshot Restore | 5.56 TiB | 33 | 1 IreneYoung1 Joss-Hua1 liyunzhi-6661 MetaWaveInfo1 neogeweb31 psh0691 |
f3rwypb3nhyzkslf6eb2qoiaqdwvaedcawxiav4hm hi4cp4w7ptjua42knqoddbl5uabcrtzgq7jajvjro z54a |
dropcool - Slingshot Restore | 1.63 TiB | 33 | 2 flyworker1 IreneYoung1 neogeweb3 |
f14r2jybmccwiu6hze4fu55jyhclktvwacec56hea | FilSwan | 544.00 GiB | 11 | 3 cryptowhizzard2 dannyob1 kernelogic2 MegTei2 neogeweb31 Reiers |
f13d6zt424jkp55u7kp67azotkzadtlokwnz2ntxa | FilSwan - Slingshot Restore | 192.00 GiB | 6 | 4 cryptowhizzard1 dannyob2 IreneYoung2 kernelogic2 MegTei1 psh06911 Reiers1 s0nik421 swatchliu |
f1r3d25hl2y7rqlsu2mgczdethy4qqjmkfdlmibfq | NEXRAD - FilSwan | 96.00 GiB | 3 | 1 cryptowhizzard2 IreneYoung1 jamerduhgamer5 kernelogic1 liyunzhi-6661 Reiers1 xingjitansuo |
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
Thanks for your request! :exclamation: We have found some problems in the information provided. We could not find Organization Name field in the information provided We could not find Website \/ Social Media field in the information provided We could not find Total amount of DataCap being requested (between 500 TiB and 5 PiB) field in the information provided We could not find Weekly allocation of DataCap requested (usually between 1-100TiB) field in the information provided We could not find On-chain address for first allocation field in the information provided We could not find Data Type of Application field in the information provided
Please, take a look at the request and edit the body of the issue providing all the required information.
Client f01929808 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 |
---|---|---|---|
Cid Checker score | > 25% | The client has a CID checker score of 19%. This should be greater than 25%. To find out more about CID checker score please look at this issue: https://github.com/filecoin-project/notary-governance/issues/986 | |
Shared data percent | < 20% | 42.59% 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?