-
Notifications
You must be signed in to change notification settings - Fork 0
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] <Tess> #51
Comments
Application is waiting for allocator review |
Additional Information RequestedA verifier has reviewed your application and has issued the following message:
The initial issue can be edited in order to solve the request of the verifier. The changes will be reflected in the application and an automatic comment will be posted in order to let the verifiers know the updated application can be reviewed. |
@Chuangshi1 Thank you so much.
|
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/bafy2bzacebmlmm3s34dn3hupytrklspgmljk36v4hjczjxq7bedvwk4nys6ge |
Application is Granted |
Version
1
DataCap Applicant
Cavanito
Project ID
46
Data Owner Name
Space Telescope Science Institute
Data Owner Country/Region
United States
Data Owner Industry
Environment
Website
http://astroquery.readthedocs.io/en/latest/mast/mast.html
Social Media Handle
http://astroquery.readthedocs.io/en/latest/mast/mast.html
Social Media Type
Other
What is your role related to the dataset
Data Preparer
Total amount of DataCap being requested
4PiB
Expected size of single dataset (one copy)
430TiB
Number of replicas to store
9
Weekly allocation of DataCap requested
800TiB
On-chain address for first allocation
f1h5ogydjm23bxqqbrd5bm6isvqz6ei5hnabvkpxa
Data Type of Application
Public, Open Dataset (Research/Non-Profit)
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
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)
No response
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.
No response
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
Sporadic
For how long do you plan to keep this dataset stored on Filecoin
1.5 to 2 years
In which geographies do you plan on making storage deals
North America
How will you be distributing your data to storage providers
HTTP or FTP server, Shipping hard drives
How did you find your storage providers
Partners
If you answered "Others" in the previous question, what is the tool or platform you used
No response
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, Singularity
If you answered "Others/custom tool" in the previous question, enter the details here
No response
Can you confirm that you will follow the Fil+ guideline
Yes
The text was updated successfully, but these errors were encountered: