Closed zhang14725804 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.
What does this mean? Please be specific
What does this mean? Please be specific
Mainland China or Hong Kong or Singapore or United States
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.
Can you explain your data composition? And to provide more data samples related with data you will store to prove that you have 5 PB already. How many copies will you store? What's the relationship between you and the organization? Can you provide more detailed information about other storage providers participated in this program, such as you can list SPs you have contacted with at present?
Any update here?
Hi @Sunnyiscoming , As an industry-leading blockchain data service platform, KingData's data composition comprises of the data generated daily from processing large web3 projects, on-chain blockchain data and also data analysis of them . We plan to store 4-5 copies of the data to ensure that it can be safely stored. We have not contacted any storage providers at this time.
I am applying on behalf of an organization and I have sent a verification email:
Can you provide more data samples related with data you will store to prove that you have 5 PB already?
@Sunnyiscoming Hello, our platform generates a lot of data every day. These data are valuable and can be further analyzed to generate new value. I have added some sample data: https://drive.google.com/drive/folders /1Lmpb_sZ9dUZta4EUfAqVBdIYopSyxF2C?usp=sharing. Thank you, hope to make progress
Total DataCap requested
5PiB
Expected weekly DataCap usage rate
400TiB
Client address
f1nmccvqvv6bsxkqoa6s5nizif2t5g34kqxcyeyhq
f02049625
f1nmccvqvv6bsxkqoa6s5nizif2t5g34kqxcyeyhq
200TiB
509358cc-f7e0-47f8-8419-2064ead05b08
First Signature Support.
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacecbegebbxfnnzfu5rrrkrzeqlbhhvyhh2bomz5ehwmo3qeka2tf7u
Address
f1nmccvqvv6bsxkqoa6s5nizif2t5g34kqxcyeyhq
Datacap Allocated
200.00TiB
Signer Address
f1yayfsv6whu3rheviucvventj3y6t542xfpb47ei
Id
509358cc-f7e0-47f8-8419-2064ead05b08
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacecbegebbxfnnzfu5rrrkrzeqlbhhvyhh2bomz5ehwmo3qeka2tf7u
Your Datacap Allocation Request has been approved by the Notary
bafy2bzacedkuqdkastj5asxjkvmxbvdztu3r4uga6lkvzmobzj47wuuk5lylm
Address
f1nmccvqvv6bsxkqoa6s5nizif2t5g34kqxcyeyhq
Datacap Allocated
200.00TiB
Signer Address
f1q6bpjlqia6iemqbrdaxr2uehrhpvoju3qh4lpga
Id
509358cc-f7e0-47f8-8419-2064ead05b08
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedkuqdkastj5asxjkvmxbvdztu3r4uga6lkvzmobzj47wuuk5lylm
This is the first time to sign. I will follow up on it later. If there are any problems, I will contact the owner to solve them
@zhang14725804 Hi! Great to see you have gotten approval for DataCap. If you are looking for 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.
f02049625
f1nmccvqvv6bsxkqoa6s5nizif2t5g34kqxcyeyhq
400TiB
d4906a87-789b-45b0-8455-1aa191d7fa25
f01858410
f1nmccvqvv6bsxkqoa6s5nizif2t5g34kqxcyeyhq
llifezou & not found
100% of weekly dc amount requested
400TiB
200TiB
4.80PiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
0 | 0 | 200TiB | 0 | 29.56TiB |
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacedztj6ife6isouo2xus54ufqkp5v4ayf34snqpn7nyapevpoor5hc
Address
f1nmccvqvv6bsxkqoa6s5nizif2t5g34kqxcyeyhq
Datacap Allocated
400.00TiB
Signer Address
f1j4n74chme7whbz3yls4a7ixqewb6dijypqg2a3a
Id
d4906a87-789b-45b0-8455-1aa191d7fa25
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedztj6ife6isouo2xus54ufqkp5v4ayf34snqpn7nyapevpoor5hc
Your Datacap Allocation Request has been approved by the Notary
bafy2bzaced77pyhjkbfxxhqykkiyvd7op563ak224o4noordhdc4ey2ogswiq
Address
f1nmccvqvv6bsxkqoa6s5nizif2t5g34kqxcyeyhq
Datacap Allocated
400.00TiB
Signer Address
f1a2lia2cwwekeubwo4nppt4v4vebxs2frozarz3q
Id
d4906a87-789b-45b0-8455-1aa191d7fa25
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaced77pyhjkbfxxhqykkiyvd7op563ak224o4noordhdc4ey2ogswiq
f02049625
f1nmccvqvv6bsxkqoa6s5nizif2t5g34kqxcyeyhq
800TiB
cc28af7a-cbb8-4db3-8de2-ef5f07f391e2
f01858410
f1nmccvqvv6bsxkqoa6s5nizif2t5g34kqxcyeyhq
xingjitansuo & ipfscn
200% of weekly dc amount requested
800TiB
600TiB
4.41PiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
0 | 0 | 400TiB | 0 | 88.28TiB |
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacebzdlavsf73bz4yel6eteydyclrmkcq6wyzjxeoqjdyavvgm2edlg
Address
f1nmccvqvv6bsxkqoa6s5nizif2t5g34kqxcyeyhq
Datacap Allocated
800.00TiB
Signer Address
f1yjhnsoga2ccnepb7t3p3ov5fzom3syhsuinxexa
Id
cc28af7a-cbb8-4db3-8de2-ef5f07f391e2
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebzdlavsf73bz4yel6eteydyclrmkcq6wyzjxeoqjdyavvgm2edlg
Your Datacap Allocation Request has been approved by the Notary
bafy2bzaceafzt36bnucwluik7oa7lnx7xnj6urrlaap3qtp7ghukowctcynkc
Address
f1nmccvqvv6bsxkqoa6s5nizif2t5g34kqxcyeyhq
Datacap Allocated
800.00TiB
Signer Address
f1q6bpjlqia6iemqbrdaxr2uehrhpvoju3qh4lpga
Id
cc28af7a-cbb8-4db3-8de2-ef5f07f391e2
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceafzt36bnucwluik7oa7lnx7xnj6urrlaap3qtp7ghukowctcynkc
kingdata
f1nmccvqvv6bsxkqoa6s5nizif2t5g34kqxcyeyhq
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.
✔️ Storage provider distribution looks healthy.
Provider | Location | Total Deals Sealed | Percentage | Unique Data | Duplicate Deals |
---|---|---|---|---|---|
f01852664 | Singapore, Singapore, SG | 192.59 TiB | 20.77% | 192.53 TiB | 0.03% |
f01852677 | Morrisville, North Carolina, US | 188.31 TiB | 20.31% | 188.25 TiB | 0.03% |
f01852023 | Busan, Busan, KR | 184.75 TiB | 19.92% | 184.69 TiB | 0.03% |
f01852325 | Hong Kong, Central and Western, HK | 184.50 TiB | 19.90% | 184.44 TiB | 0.03% |
f01851482 | Busan, Busan, KR | 177.19 TiB | 19.11% | 177.13 TiB | 0.04% |
The below table shows how each many unique data are replicated across storage providers.
⚠️ 25.63% of deals are for data replicated across less than 4 storage providers.
Unique Data Size | Total Deals Made | Number of Providers | Deal Percentage |
---|---|---|---|
30.22 TiB | 30.22 TiB | 1 | 3.26% |
47.78 TiB | 95.56 TiB | 2 | 10.30% |
37.31 TiB | 111.94 TiB | 3 | 12.07% |
20.06 TiB | 80.25 TiB | 4 | 8.65% |
121.81 TiB | 609.38 TiB | 5 | 65.71% |
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.
✔️ No CID sharing has been observed.
[^1]: To manually trigger this report, add a comment with text checker:manualTrigger
f02049625
f1nmccvqvv6bsxkqoa6s5nizif2t5g34kqxcyeyhq
1.56PiB
194af468-66a6-40e1-b063-ce90bb6e4b2c
f01858410
f1nmccvqvv6bsxkqoa6s5nizif2t5g34kqxcyeyhq
llifezou & kernelogic
400% of weekly dc amount requested
1.56PiB
1.36PiB
3.63PiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
38621 | 5 | 800TiB | 20.76 | 175.75TiB |
kingdata
f1nmccvqvv6bsxkqoa6s5nizif2t5g34kqxcyeyhq
1
ipfscn1
kernelogic1
NDLABS-OFFICE2
Tom-OriginStorage1
xingjitansuo
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.
✔️ Storage provider distribution looks healthy.
Provider | Location | Total Deals Sealed | Percentage | Unique Data | Duplicate Deals |
---|---|---|---|---|---|
f01852325 | Hong Kong, Central and Western, HKBIH-Global Internet Harbor |
239.63 TiB | 19.89% | 239.53 TiB | 0.04% |
f01852023 | Busan, Busan, KRKorea Telecom |
243.25 TiB | 20.19% | 243.19 TiB | 0.03% |
f01851482 | Busan, Busan, KRKorea Telecom |
231.16 TiB | 19.19% | 231.09 TiB | 0.03% |
f01852664 | Singapore, Singapore, SGStarHub Ltd |
250.38 TiB | 20.78% | 250.28 TiB | 0.04% |
f01852677 | Morrisville, North Carolina, USTierPoint, LLC |
240.47 TiB | 19.96% | 240.38 TiB | 0.04% |
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 |
---|---|---|---|
576.00 GiB | 576.00 GiB | 1 | 0.05% |
4.16 TiB | 8.31 TiB | 2 | 0.69% |
22.56 TiB | 67.69 TiB | 3 | 5.62% |
59.75 TiB | 239.00 TiB | 4 | 19.84% |
177.78 TiB | 889.31 TiB | 5 | 73.81% |
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
checker:manualTrigger
kingdata
f1nmccvqvv6bsxkqoa6s5nizif2t5g34kqxcyeyhq
1
ipfscn1
kernelogic1
NDLABS-OFFICE2
Tom-OriginStorage1
xingjitansuo
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.
✔️ Storage provider distribution looks healthy.
Provider | Location | Total Deals Sealed | Percentage | Unique Data | Duplicate Deals |
---|---|---|---|---|---|
f01852325 | Hong Kong, Central and Western, HKBIH-Global Internet Harbor |
264.50 TiB | 20.10% | 264.41 TiB | 0.04% |
f01851482 | Busan, Busan, KRKorea Telecom |
263.13 TiB | 19.99% | 263.03 TiB | 0.04% |
f01852023 | Busan, Busan, KRKorea Telecom |
262.31 TiB | 19.93% | 262.22 TiB | 0.04% |
f01852664 | Singapore, Singapore, SGStarHub Ltd |
263.63 TiB | 20.03% | 263.53 TiB | 0.04% |
f01852677 | Morrisville, North Carolina, USTierPoint, LLC |
262.63 TiB | 19.95% | 262.53 TiB | 0.04% |
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 |
---|---|---|---|
192.00 GiB | 576.00 GiB | 3 | 0.04% |
7.97 TiB | 31.88 TiB | 4 | 2.42% |
256.66 TiB | 1.25 PiB | 5 | 97.54% |
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
Cid Checker's results look good. The SP locations are relatively distributed, and there is no Cid sharing
Your Datacap Allocation Request has been proposed by the Notary
bafy2bzacedx3ievfernam43y5yhjtmv4do3pr5jw2d7dks42547qphgfsfn7u
Address
f1nmccvqvv6bsxkqoa6s5nizif2t5g34kqxcyeyhq
Datacap Allocated
1.56PiB
Signer Address
f1e77zuityhvvw6u2t6tb5qlnsegy2s67qs4lbbbq
Id
194af468-66a6-40e1-b063-ce90bb6e4b2c
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedx3ievfernam43y5yhjtmv4do3pr5jw2d7dks42547qphgfsfn7u
@zhang14725804 Multiple approved applications by the notary are potentially fraudulent, hence increased screening on applications signed by this notary.
In my view, storing "Analytics data from multiple blockchains" adds some value to the network. Useful data.
Also, the CID report looks clean.
My question to the applicant is:
You requested 5PiB of datacap for storing analytics data. Just to put this in perspective, the entirety of wikipedia with 55 million pages of information is 22GiB compressed.
Can you explain to me why you need the volume and hereby provide evidence of file size?
checker:manualTrigger
kingdata
f1nmccvqvv6bsxkqoa6s5nizif2t5g34kqxcyeyhq
1
ipfscn1
kernelogic1
NDLABS-OFFICE1
newwebgroup2
Tom-OriginStorage1
xingjitansuo
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.
✔️ Storage provider distribution looks healthy.
Provider | Location | Total Deals Sealed | Percentage | Unique Data | Duplicate Deals |
---|---|---|---|---|---|
f01852325 | Hong Kong, Central and Western, HKBIH-Global Internet Harbor |
264.50 TiB | 20.10% | 264.41 TiB | 0.04% |
f01851482 | Busan, Busan, KRKorea Telecom |
263.13 TiB | 19.99% | 263.03 TiB | 0.04% |
f01852023 | Busan, Busan, KRKorea Telecom |
262.31 TiB | 19.93% | 262.22 TiB | 0.04% |
f01852664 | Singapore, Singapore, SGStarHub Ltd |
263.63 TiB | 20.03% | 263.53 TiB | 0.04% |
f01852677 | Morrisville, North Carolina, USTierPoint, LLC |
262.63 TiB | 19.95% | 262.53 TiB | 0.04% |
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 |
---|---|---|---|
192.00 GiB | 576.00 GiB | 3 | 0.04% |
7.97 TiB | 31.88 TiB | 4 | 2.42% |
256.66 TiB | 1.25 PiB | 5 | 97.54% |
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
Your Datacap Allocation Request has been approved by the Notary
bafy2bzaceabrmkntvvobrjkwdesvua3zzmt2vqc457jyzzexifnmnghibs6bg
Address
f1nmccvqvv6bsxkqoa6s5nizif2t5g34kqxcyeyhq
Datacap Allocated
1.56PiB
Signer Address
f1q6bpjlqia6iemqbrdaxr2uehrhpvoju3qh4lpga
Id
194af468-66a6-40e1-b063-ce90bb6e4b2c
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceabrmkntvvobrjkwdesvua3zzmt2vqc457jyzzexifnmnghibs6bg
Cid Checker's results look good. The SP locations are relatively distributed, and there is no Cid sharing
@Tom-OriginStorage I would strongly recommend you not to sign looking at the above questions. First due diligence, then approve of next batch. This is NOT proper notary behaviour.
Also, we are checking the distribution, miner ID's are all the same so this is most likely the same entity.
@zhang14725804 can you explain to my why these 5 ownerID's are all successive of each other? Are they the same company? Are they controlled by the same business?
Hello,
I noticed all these providers are not available for retrieval.
Provider | Deals | Ping |
---|---|---|
f01852325 | 8464 | context canceled |
f01852664 | 8436 | context canceled |
f01851482 | 8420 | context canceled |
f01852677 | 8404 | context canceled |
f01852023 | 8394 | context canceled |
For example Deal ID 21036388 results in:
retrieve: offer error: retrieval query offer errored: failed to fetch piece to retrieve from: getting pieces for cid QmTipAaCt3RLQmgpT57XMjvkiiJB2145gVtfvRp2NhgsE2: getting pieces containing block QmTipAaCt3RLQmgpT57XMjvkiiJB2145gVtfvRp2NhgsE2: failed to lookup index for mh 12204ff7e79c4d52a3e818a4049a58161787a1ff1a3e720a570aee9bffcd6369de73, err: datastore: key not found
Deal ID 20973407: retrieve: offer error: retrieval query offer errored: failed to fetch piece to retrieve from: getting pieces for cid QmaTZnESKn24McxBvUoWBEscihKdJ6QYN2aNhP2zzmoCPp: getting pieces containing block QmaTZnESKn24McxBvUoWBEscihKdJ6QYN2aNhP2zzmoCPp: failed to lookup index for mh 1220b411bc567a97137d1658f6f77cb7661ffaff43027ee1fb670dd9af51265e5907, err: datastore: key not found
DealID 20887352: retrieve: offer error: retrieval query offer errored: failed to fetch piece to retrieve from: getting pieces for cid Qma9GkMQP4gKJXP14cnkSFzuVLEjcjFvhqkunzX1JXDxFh: getting pieces containing block Qma9GkMQP4gKJXP14cnkSFzuVLEjcjFvhqkunzX1JXDxFh: failed to lookup index for mh 1220af6205c3fbc9e4d62fdd9691ff381777f69f8284bad33f151f36c826f8dff570, err: datastore: key not found
To be eligible for Fil+ datacap the data needs to be retrievable and the SP's need to be available. Please have a talk with your SP's and get this sorted out. You might want to have them switch to boost here to get the deals stored correctly and have retrieval proper.
@Tom-OriginStorage
We have a sign here from you without you checking that the data is retrievable. @newwebgroup the same. That is unfortunate. Please have a talk with this client to have the data retrievable before he continues with this LDN and starts on further using the datacap. This needs to be sorted.
f02049625
f1nmccvqvv6bsxkqoa6s5nizif2t5g34kqxcyeyhq
2.07PiB
fe9e21af-a7da-4bb9-97e8-09f6f627ac94
f01858410
f1nmccvqvv6bsxkqoa6s5nizif2t5g34kqxcyeyhq
llifezou & newwebgroup
800% of weekly dc amount requested
2.07PiB
1.36PiB
3.63PiB
Number of deals | Number of storage providers | Previous DC Allocated | Top provider | Remaining DC |
---|---|---|---|---|
42365 | 5 | 1.56PiB | 20.00 | 76.59TiB |
kingdata
f1nmccvqvv6bsxkqoa6s5nizif2t5g34kqxcyeyhq
1
ipfscn1
kernelogic1
NDLABS-OFFICE1
newwebgroup3
Tom-OriginStorage1
xingjitansuo
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.
✔️ Storage provider distribution looks healthy.
Provider | Location | Total Deals Sealed | Percentage | Unique Data | Duplicate Deals |
---|---|---|---|---|---|
f01852325 | Hong Kong, Central and Western, HKBIH-Global Internet Harbor |
264.50 TiB | 20.10% | 264.41 TiB | 0.04% |
f01851482 | Busan, Busan, KRKorea Telecom |
263.13 TiB | 19.99% | 263.03 TiB | 0.04% |
f01852023 | Busan, Busan, KRKorea Telecom |
262.31 TiB | 19.93% | 262.22 TiB | 0.04% |
f01852664 | Singapore, Singapore, SGStarHub Ltd |
263.63 TiB | 20.03% | 263.53 TiB | 0.04% |
f01852677 | Morrisville, North Carolina, USTierPoint, LLC |
262.63 TiB | 19.95% | 262.53 TiB | 0.04% |
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 |
---|---|---|---|
192.00 GiB | 576.00 GiB | 3 | 0.04% |
7.97 TiB | 31.88 TiB | 4 | 2.42% |
256.66 TiB | 1.25 PiB | 5 | 97.54% |
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
@Tom-OriginStorage I have messaged you with questions in multiple applications. If you keep blindly signing and do not respond I will be forced to address this behaviour with a dispute.
Please answer my and @cryptowhizzard's questions.
@herrehesse The packaging of this LDN completely conforms to the official rules. For the retrieval problem, I have been contacting them for inspection, Recently, I saw you leave a message under a lot of normal LDN asking questions, and some robots did not see you pay attention to those that did not comply with the rules. What is your purpose? And why can your account apply for so many LDN data? Does it really meet the specifications? Why are some applications closed? Why can your LDN be approved in such a short time? Far below the average time of LDN application
I have a few questions?
who are you? what organization do you belong to? who do you work for and why should I answer your question?
@Tom-OriginStorage love to answer al your questions. But I asked first. Please respond accordingly.
My information is public and can be found in the notary community. You don't tell me who you are? How can I answer your question?
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?