Closed bq1024 closed 11 months 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.
5PiB
100TiB
f1dxad75jyyqlemexfwbvhbnwundz4sxeu2dza6gi
f02049625
f1dxad75jyyqlemexfwbvhbnwundz4sxeu2dza6gi
50TiB
5b08dc6b-cc9a-4d50-9788-4095dcd74895
There is no previous allocation for this issue.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacedry3swy5ntppw455zruumhbufao2xqevzruvj2tmudbmhsdrucgw
Address
f1dxad75jyyqlemexfwbvhbnwundz4sxeu2dza6gi
Datacap Allocated
50.00TiB
Signer Address
f1yjhnsoga2ccnepb7t3p3ov5fzom3syhsuinxexa
Id
5b08dc6b-cc9a-4d50-9788-4095dcd74895
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedry3swy5ntppw455zruumhbufao2xqevzruvj2tmudbmhsdrucgw
FilSwan/Nebula is long time community participant. Willing to support whole series.
Your Datacap Allocation Request has been approved by the Notary
bafy2bzaceaa7iqsjzhsh7bc6ft6vupczpzpph4ya6e7um4vk2wqj7kvuvk3gi
Address
f1dxad75jyyqlemexfwbvhbnwundz4sxeu2dza6gi
Datacap Allocated
50.00TiB
Signer Address
f1krmypm4uoxxf3g7okrwtrahlmpcph3y7rbqqgfa
Id
5b08dc6b-cc9a-4d50-9788-4095dcd74895
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceaa7iqsjzhsh7bc6ft6vupczpzpph4ya6e7um4vk2wqj7kvuvk3gi
Dear Applicant,
Due to the increased amount of erroneous/wrong Filecoin+ data recently, on behalf of the entire community, we feel compelled to go deeper into datacap requests. Hereby to ensure that the overall value of the Filecoin network and Filecoin+ program increases and is not abused.
Please answer the questions below as comprehensively as possible.
Customer data
Could you demonstrate exactly how and to what extent customer contact occurred? We expect that for the onboarding of customers with the scale of an LDN there would have been at least multiple email and perhaps several chat conversations preceding it. A single email with an agreement does not qualify here.
Did the customer specify the amount of data involved in this relevant correspondence?
Why does the customer in question want to use the Filecoin+ program?
Should this only be soley for acquiring datacap this is of course out of the question. The customer must have a legitimate reason for wanting to use the Filecoin+ program which is intended as a program to store useful and public datasets on the network.
Why is the customer data considered Filecoin+ eligible? (As an intermediate solution Filecoin offers the FIL-E program or the glif.io website for business datasets that do not meet the requirements for a Filecoin+ dataset)
Files and Processing
Could you please demonstrate to us how you envision processing and transporting the customer data in question to any location for preparation? Would you demonstrate to us that the customer, the preparer and the intended storage providers all have adequate bandwidth to process the set with its corresponding size? Would you tell us how the data set preparer takes into account the prevention of duplicates in order to prevent data cap abuse? Hopefully you understand the caution the overall community has for onboarding the wrong data. We understand the increased need for Filecoin+, however, we must not allow the program to be misused. Everything depends on a valuable and useful network, let's do our best to make this happen. Together.
checker:manualTrigger
NebulaBlock
f1dxad75jyyqlemexfwbvhbnwundz4sxeu2dza6gi
1
cryptowhizzard1
kernelogic
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:
⚠️ f01946551 has unknown IP location.
Provider | Location | Total Deals Sealed | Percentage | Unique Data | Duplicate Deals |
---|---|---|---|---|---|
f01225882 | Burnaby, British Columbia, CAAstute Hosting Inc. |
2.78 TiB | 15.59% | 2.78 TiB | 0.00% |
f032824 | Austin, Texas, USAT&T Services, Inc. |
128.00 GiB | 0.70% | 128.00 GiB | 0.00% |
f03624 | Nürnberg, Bavaria, DEDeutsche Telekom AG |
1.44 TiB | 8.06% | 1.44 TiB | 0.00% |
f01907556 | Sharjah, Sharjah, AEEmirates Telecommunications Corporation |
576.00 GiB | 3.15% | 576.00 GiB | 0.00% |
f01443744 | Leipzig, Saxony, DEHetzner Online GmbH |
448.00 GiB | 2.45% | 448.00 GiB | 0.00% |
f08399 | Seattle, Washington, USIsomedia, Inc. |
1.00 TiB | 5.60% | 1.00 TiB | 0.00% |
f0717969 | Los Angeles, California, USKrypt Technologies |
2.53 TiB | 14.19% | 2.53 TiB | 0.00% |
f0187709 | Moscow, Moscow, RUMTS PJSC |
2.88 TiB | 16.11% | 2.88 TiB | 0.00% |
f01163272 | Perm, Perm Krai, RUPJSC Rostelecom |
2.94 TiB | 16.46% | 2.94 TiB | 0.00% |
f010088 | Kirkland, Washington, USWholesail networks LLC |
2.44 TiB | 13.66% | 2.44 TiB | 0.00% |
f01946551 | UnknownUnknown |
736.00 GiB | 4.03% | 736.00 GiB | 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 |
---|---|---|---|
192.00 GiB | 192.00 GiB | 1 | 1.05% |
288.00 GiB | 576.00 GiB | 2 | 3.15% |
256.00 GiB | 768.00 GiB | 3 | 4.20% |
1.09 TiB | 4.38 TiB | 4 | 24.52% |
1.38 TiB | 6.88 TiB | 5 | 38.53% |
608.00 GiB | 3.56 TiB | 6 | 19.96% |
224.00 GiB | 1.53 TiB | 7 | 8.58% |
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.
✔️ No CID sharing has been observed.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
lotus client retrieve --provider f08399 --pieceCid baga6ea4seaqpzmmxzhonpqfsdttx3lrmzpvjz3s7rmlr45veqel36r6of6wncei mAXASIDDFymrK2x7SfC17PQJNVPFmPlke4Im63A+z6v5x8ISx test.file Recv 0 B, Paid 0 FIL, Open (New), 0s Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 3ms Recv 0 B, Paid 0 FIL, DealRejected (RetryLegacy), 263ms Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptanceLegacy), 267ms Recv 0 B, Paid 0 FIL, DealRejected (Rejecting), 497ms Recv 0 B, Paid 0 FIL, BlockstoreFinalized (Rejected), 497ms ERROR: Retrieval Proposal Rejected: deal rejected: miner is not accepting online retrieval deals
@filplusapp - What is your name on the Filecoin Slack? Love to talk to you!
ERROR: Retrieval Proposal Rejected: deal rejected: miner is not accepting online retrieval deals
@bq1024 as the earliest member of Filecoin, i think you are well aware that all miners should be reachable. Please contact the sp above and update when it gets fixed. @cryptowhizzard @herrehesse, i don't understand your role in this application. Is speedium involved somehow?
ERROR: Retrieval Proposal Rejected: deal rejected: miner is not accepting online retrieval deals
@bq1024 as the earliest member of Filecoin, i think you are well aware that all miners should be reachable. Please contact the sp above and update when it gets fixed. @cryptowhizzard @herrehesse, i don't understand your role in this application. Is speedium involved somehow?
No, none whatsoever
f02049625
f1dxad75jyyqlemexfwbvhbnwundz4sxeu2dza6gi
100TiB
a2e144a5-4520-4dbb-af19-70f3c36a3d01
f01858410
f1dxad75jyyqlemexfwbvhbnwundz4sxeu2dza6gi
cryptowhizzard & kernelogic
100% of weekly dc amount requested
100TiB
50TiB
4.95PiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
1152 | 15 | 50TiB | 14.15 | 8TiB |
NebulaBlock
f1dxad75jyyqlemexfwbvhbnwundz4sxeu2dza6gi
1
cryptowhizzard1
kernelogic
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:
⚠️ f01946551 has unknown IP location.
Provider | Location | Total Deals Sealed | Percentage | Unique Data | Duplicate Deals |
---|---|---|---|---|---|
f01225882 | Burnaby, British Columbia, CAAstute Hosting Inc. |
4.91 TiB | 14.04% | 4.91 TiB | 0.00% |
f032824 | Austin, Texas, USAT&T Services, Inc. |
320.00 GiB | 0.89% | 320.00 GiB | 0.00% |
f01390330 | Xi’an, Shaanxi, CNCHINANET-BACKBONE |
1.53 TiB | 4.38% | 1.53 TiB | 0.00% |
f03624 | Nürnberg, Bavaria, DEDeutsche Telekom AG |
3.13 TiB | 8.94% | 3.13 TiB | 0.00% |
f01907556 | Sharjah, Sharjah, AEEmirates Telecommunications Corporation |
1.31 TiB | 3.76% | 1.31 TiB | 0.00% |
f01443744 | Leipzig, Saxony, DEHetzner Online GmbH |
480.00 GiB | 1.34% | 480.00 GiB | 0.00% |
f08399 | Seattle, Washington, USIsomedia, Inc. |
1.63 TiB | 4.65% | 1.63 TiB | 0.00% |
f0717969 | Los Angeles, California, USKrypt Technologies |
4.53 TiB | 12.97% | 4.53 TiB | 0.00% |
f0187709 | Moscow, Moscow, RUMTS PJSC |
5.09 TiB | 14.58% | 5.09 TiB | 0.00% |
f01163272 | Perm, Perm Krai, RUPJSC Rostelecom |
4.91 TiB | 14.04% | 4.91 TiB | 0.00% |
f02012951 | Vilnius, Vilnius, LTTelia Lietuva, AB |
3.06 TiB | 8.77% | 3.06 TiB | 0.00% |
f010088 | Kirkland, Washington, USWholesail networks LLC |
2.69 TiB | 7.69% | 2.69 TiB | 0.00% |
f01946551 | UnknownUnknown |
1.38 TiB | 3.94% | 1.38 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 |
---|---|---|---|
512.00 GiB | 512.00 GiB | 1 | 1.43% |
224.00 GiB | 448.00 GiB | 2 | 1.25% |
256.00 GiB | 768.00 GiB | 3 | 2.15% |
1.66 TiB | 6.63 TiB | 4 | 18.96% |
2.44 TiB | 12.19 TiB | 5 | 34.88% |
1.44 TiB | 8.63 TiB | 6 | 24.69% |
704.00 GiB | 4.81 TiB | 7 | 13.77% |
128.00 GiB | 1.00 TiB | 8 | 2.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.
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.
✔️ No CID sharing has been observed.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
lotus client retrieve --provider f08399 --pieceCid baga6ea4seaqpzmmxzhonpqfsdttx3lrmzpvjz3s7rmlr45veqel36r6of6wncei mAXASIDDFymrK2x7SfC17PQJNVPFmPlke4Im63A+z6v5x8ISx test.file
I contacted the SP and the issue is fixed.
lotus net connect f01946551 f01946551 -> {12D3KooWRj5hM6KtShBNnKHNFbfEghZ4XHgGhAPoRUd5TvyW8Yw5: []} ERROR: failed to parse multiaddr "f01946551": must begin with /
i think Nebula Block can add send deals to more SPs as a supplemental of FilSwan Engine. Maybe allocated 3 copies in some fixed SPs as the primary SPs while others as redundant SPs
client retrieve --provider f08399 --pieceCid baga6ea4seaqpzmmxzhonpqfsdttx3lrmzpvjz3s7rmlr45veqel36r6of6wncei mAXASIDDFymrK2x7SfC17PQJNVPFmPlke4Im63A+z6v5x8ISx test.file Recv 0 B, Paid 0 FIL, Open (New), 18ms Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 45ms Recv 0 B, Paid 0 FIL, DealAccepted (Accepted), 896ms Recv 0 B, Paid 0 FIL, PaymentChannelSkip (Ongoing), 903ms Recv 60 B, Paid 0 FIL, BlocksReceived (Ongoing), 928ms Recv 128 B, Paid 0 FIL, BlocksReceived (Ongoing), 944ms Recv 184 B, Paid 0 FIL, BlocksReceived (Ongoing), 957ms Recv 1.827 KiB, Paid 0 FIL, BlocksReceived (Ongoing), 972ms Recv 1.94 KiB, Paid 0 FIL, BlocksReceived (Ongoing), 986ms Recv 51.95 KiB, Paid 0 FIL, BlocksReceived (Ongoing), 1.034s Recv 1.051 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 1.757s Recv 2.051 MiB, Paid 0 FIL, BlocksReceived (Ongoing), 2.133s
works for me
lotus client retrieve --provider f08399 --pieceCid baga6ea4seaqpzmmxzhonpqfsdttx3lrmzpvjz3s7rmlr45veqel36r6of6wncei mAXASIDDFymrK2x7SfC17PQJNVPFmPlke4Im63A+z6v5x8ISx test.file Recv 0 B, Paid 0 FIL, Open (New), 0s Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptance), 3ms Recv 0 B, Paid 0 FIL, DealRejected (RetryLegacy), 263ms Recv 0 B, Paid 0 FIL, DealProposed (WaitForAcceptanceLegacy), 267ms Recv 0 B, Paid 0 FIL, DealRejected (Rejecting), 497ms Recv 0 B, Paid 0 FIL, BlockstoreFinalized (Rejected), 497ms ERROR: Retrieval Proposal Rejected: deal rejected: miner is not accepting online retrieval deals
@claydrone no offence, but you work for Nebula block. A second opinion would be more neutral, could @cryptowhizzard @herrehesse you guys take a look?
I got a different reply from f08399 now ERROR: Retrieval Proposal Rejected: deal rejected: Deal rejected | Too many retrieval deals received, retry later
Another miner not really working f03624 ERROR: Retrieval Proposal Rejected: deal rejected: miner is not accepting online retrieval deals
Currently retrieving a deal from miner f01443744 and Ill report once done.
I got a different reply from f08399 now ERROR: Retrieval Proposal Rejected: deal rejected: Deal rejected | Too many retrieval deals received, retry later
Another miner not really working f03624 ERROR: Retrieval Proposal Rejected: deal rejected: miner is not accepting online retrieval deals
Currently retrieving a deal from miner f01443744 and Ill report once done.
f08399 and f03624 are able to retrieve now. Filswan cannot guarantee that all deals are retrievable from SP currently, however, if there are any retrieval issues, we will do our best to contact and help SP resolve them.
miner is not accepting online retrieval deals
miner is not accepting online retrieval deals
@bq1024 is the information from Lotus, boost or other 3rd party software?
owo 9:40 AM my new SP is f03624, Please activate it. thank you @ribasushi - PLFD
found this on slack, we can talk to him if needed, but still it is not part of the Filecoin Protocol consensus at the moment
miner is not accepting online retrieval deals
miner is not accepting online retrieval deals
@bq1024 is the information from Lotus, boost or other 3rd party software?
I believe it's from Lotus.
So people shut it down by purpose.
checker:manualTrigger
⚠️ 1 storage providers have unknown IP location - f01946551
✔️ 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 full report.
Please tell us where is the ip address of the provider id f01946551.
Please tell us where is the ip address of the provider id f01946551.
Thanks for asking! Please refer to https://github.com/filecoin-project/filecoin-plus-large-datasets/issues/1530#issuecomment-1458366486
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacecouwm57h7xbes4l3epbraqleugrtzxmqcupbjhzx43e6zxlzf63w
Address
f1dxad75jyyqlemexfwbvhbnwundz4sxeu2dza6gi
Datacap Allocated
100.00TiB
Signer Address
f1yjhnsoga2ccnepb7t3p3ov5fzom3syhsuinxexa
Id
a2e144a5-4520-4dbb-af19-70f3c36a3d01
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacecouwm57h7xbes4l3epbraqleugrtzxmqcupbjhzx43e6zxlzf63w
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzaced7iqiev365yfijaovkxw6ms2emkfjdq3ueobicm3ag55edv4leaw
Address
f1dxad75jyyqlemexfwbvhbnwundz4sxeu2dza6gi
Datacap Allocated
100.00TiB
Signer Address
f1k3ysofkrrmqcot6fkx4wnezpczlltpirmrpsgui
Id
a2e144a5-4520-4dbb-af19-70f3c36a3d01
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaced7iqiev365yfijaovkxw6ms2emkfjdq3ueobicm3ag55edv4leaw
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacedksqgptarzhnpcaz3msysjb5h4rfdehjigcsbnp5bw7jdjy5jvni
Address
f1dxad75jyyqlemexfwbvhbnwundz4sxeu2dza6gi
Datacap Allocated
100.00TiB
Signer Address
f1d4gmpqz3execjj2wvrxuuhvbms5mzh7t7yqrviq
Id
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedksqgptarzhnpcaz3msysjb5h4rfdehjigcsbnp5bw7jdjy5jvni
We have found some problems in the information provided in the Approved Comment. We could not find Id** field in the information provided
Please, take a look at the comment and edit the body of the comment providing all the required information.
We have found some problems in the information provided in the Approved Comment. We could not find Id** field in the information provided
Please, take a look at the comment and edit the body of the comment providing all the required information.
f02049625
f1dxad75jyyqlemexfwbvhbnwundz4sxeu2dza6gi
200TiB
5ed9e26a-a964-40bf-92ea-957f5373495b
f02049625
f1dxad75jyyqlemexfwbvhbnwundz4sxeu2dza6gi
IreneYoung & xinaxu
200% of weekly dc amount requested
200TiB
50TiB
4.95PiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
1525 | 17 | 100TiB | 12 | 0B |
✔️ 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 full report.
✔️ 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 full 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 full report.
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzaceb56j4uxuzvcusrvdm4fyxb5xjsisfn2g4a4nztoihjxryjwhewae
Address
f1dxad75jyyqlemexfwbvhbnwundz4sxeu2dza6gi
Datacap Allocated
200.00TiB
Signer Address
f1e77zuityhvvw6u2t6tb5qlnsegy2s67qs4lbbbq
Id
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceb56j4uxuzvcusrvdm4fyxb5xjsisfn2g4a4nztoihjxryjwhewae
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacec472zk4ojtyc4ex5n5w3oz5g7ykz7roxhacjr6c3ly6spnigg2eg
Address
f1dxad75jyyqlemexfwbvhbnwundz4sxeu2dza6gi
Datacap Allocated
200.00TiB
Signer Address
f1e77zuityhvvw6u2t6tb5qlnsegy2s67qs4lbbbq
Id
5ed9e26a-a964-40bf-92ea-957f5373495b
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacec472zk4ojtyc4ex5n5w3oz5g7ykz7roxhacjr6c3ly6spnigg2eg
Looks like a bug was triggered 😅
f02049625
f1dxad75jyyqlemexfwbvhbnwundz4sxeu2dza6gi
200TiB
59683d1e-45ae-4986-9cd6-5b58bd241e03
f02049625
f1dxad75jyyqlemexfwbvhbnwundz4sxeu2dza6gi
200% of weekly dc amount requested
200TiB
9094.9YiB
-1.09B
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
1863 | 5 | 100TiB | 30.76 | 18.21TiB |
Data Owner Name
Nebula Block
Data Owner Country/Region
Canada
Data Owner Industry
Web3 / Crypto
Website
https://www.nebulablock.com/
Social Media
Total amount of DataCap being requested
5PiB
Weekly allocation of DataCap requested
100TiB
On-chain address for first allocation
f1dxad75jyyqlemexfwbvhbnwundz4sxeu2dza6gi
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
singularity, others/custom tool
If you answered "other/custom tool" in the previous question, enter the details here
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
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, IPFS
How do you plan to choose storage providers
Others
If you answered "Others" in the previous question, what is the tool or platform you plan to use
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
Others/custom tool
If you answered "Others/custom tool" in the previous question, enter the details here
Can you confirm that you will follow the Fil+ guideline
Yes