-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DataCap Application] <Tuhun Network> - <Arts&Recreation> #17
Comments
Application is waiting for allocator review |
@Caiuslu |
@Filedrive-ops |
@Caiuslu |
Datacap Request TriggerTotal DataCap requested
Expected weekly DataCap usage rate
DataCap Amount - First Tranche
Client address
|
DataCap Allocation requestedMultisig Notary addressClient address
DataCap allocation requested
Id
|
Application is ready to sign |
Request ApprovedYour Datacap Allocation Request has been approved by the Notary Message sent to Filecoin Network
Address
Datacap Allocated
Signer Address
Id
You can check the status here https://filfox.info/en/message/bafy2bzacec3ox7mtnw2mw52dqkx5rnnpexwz7sgwavqdwzek6jncolgqca3vs |
Application is Granted |
checker:manualTrigger |
DataCap and CID Checker Report Summary1Storage Provider Distribution✔️ Storage provider distribution looks healthy. Deal Data Replication✔️ Data replication looks healthy. Deal Data Shared with other Clients2✔️ No CID sharing has been observed. Full reportClick here to view the CID Checker report. Footnotes |
checker:manualTrigger |
DataCap and CID Checker Report Summary1Storage Provider Distribution✔️ Storage provider distribution looks healthy. Deal Data Replication✔️ Data replication looks healthy. Deal Data Shared with other Clients2✔️ No CID sharing has been observed. Full reportClick here to view the CID Checker report. Footnotes |
Client used 75% of the allocated DataCap. Consider allocating next tranche. |
@Filedrive-ops |
checker:manualTrigger |
DataCap and CID Checker Report Summary1Storage Provider Distribution✔️ Storage provider distribution looks healthy. Deal Data Replication✔️ Data replication looks healthy. Deal Data Shared with other Clients2✔️ No CID sharing has been observed. Full reportClick here to view the CID Checker report. Footnotes |
@Caiuslu |
@Filedrive-ops |
@Caiuslu |
Application is in Refill |
Request ApprovedYour Datacap Allocation Request has been approved by the Notary Message sent to Filecoin Network
Address
Datacap Allocated
Signer Address
Id
You can check the status here https://filfox.info/en/message/bafy2bzaceaxft6qjeiy263jawu2zrlloydg3catrzewhgcojlc54syqxnvxh4 |
Application is Granted |
Client used 75% of the allocated DataCap. Consider allocating next tranche. |
checker:manualTrigger |
DataCap and CID Checker Report Summary1Storage Provider Distribution✔️ Storage provider distribution looks healthy. Deal Data Replication✔️ Data replication looks healthy. Deal Data Shared with other Clients2✔️ No CID sharing has been observed. Full reportClick here to view the CID Checker report. Footnotes |
After reevaluating your application and data, I have a few questions and concerns: All four active SPs are using VPN. Could you clarify this? |
@Filedrive-ops |
@Caiuslu |
Could you add a mapping file into your data preparation process to help the community better understand and discover the data stored? |
@Filedrive-ops |
Data Owner Name
Shanghai Tuhun Network Technology Co., Ltd.
Data Owner Country/Region
China
Data Owner Industry
Arts & Recreation
Website
https://588ku.com/
Social Media Handle
https://588ku.com/
Social Media Type
WeChat
What is your role related to the dataset
Dataset Owner
Total amount of DataCap being requested
10PiB
Expected size of single dataset (one copy)
2.5PiB
Number of replicas to store
4
Weekly allocation of DataCap requested
2PiB
On-chain address for first allocation
f3si72ludz4ftzprswnf4aw4b4e5bpmqmaszw6xnkcmv6u3lcogb35vae7rijvuoluxfkpa3g5zdjfp7wif7wq
Data Type of Application
Public, Open Commercial/Enterprise
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
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
If you are a data preparer. What is your location (Country/Region)
China
If you are a data preparer, how will the data be prepared? Please include tooling used and technical details?
If you are not preparing the data, who will prepare the data? (Provide name and business)
Has this dataset been stored on the Filecoin network before? If so, please explain and make the case why you would like to store this dataset again to the network. Provide details on preparation and/or SP distribution.
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
What is the expected retrieval frequency for this data
Yearly
For how long do you plan to keep this dataset stored on Filecoin
1 to 1.5 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
Cloud storage (i.e. S3), HTTP or FTP server, IPFS, Lotus built-in data transfer, Venus built-in data transfer
How did you find your storage providers
Slack, Big Data Exchange, Partners
If you answered "Others" in the previous question, what is the tool or platform you used
Please list the provider IDs and location of the storage providers you will be working with.
How do you plan to make deals to your storage providers
Boost client, Lotus client, Droplet client, Singularity
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
The text was updated successfully, but these errors were encountered: