[DataCap Application] USC Shoah Foundation #53
Comments
|
Thanks for your request! A Governance Team member will review the information provided and contact you back pretty soon. |
|
@starling-admin Here is the new large dataset application issue, per the new LDN process. |
Multisig Notary requestedTotal DataCap requested
Expected weekly DataCap usage rate
|
|
**Multisig created and sent to RKH f01322626 |
DataCap Allocation requestedMultisig Notary address
Client address
DataCap allocation requested
|
Request ApprovedYour Datacap Allocation Request has been approved by the Notary Message sent to Filecoin Network
Address
Datacap Allocated
Signer Address
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacebmb5eshdszn6mike6iohpbstp7yin4evmiaszriuu2ccxlpimjpo |
Request ApprovedYour Datacap Allocation Request has been approved by the Notary Message sent to Filecoin Network
Address
Datacap Allocated
Signer Address
You can check the status of the message here: https://filfox.info/en/message/bafy2bzaceav3tvsfrq57kzh4ldst2uynaf6ukbtpljyvcavsw7dmqtvkcr4yy |
Request ApprovedYour Datacap Allocation Request has been approved by the Notary Message sent to Filecoin Network
Address
Datacap Allocated
Signer Address
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacecqgfrguyxw33sg5saijaj2jtbkcwzxfcmyhslznvzesvx7rtamzc |
|
^ this went as a proposal, looks like a dup. I'm going to remove the ready to sign label here since the allocation was already made. |
|
@dkkapur + the Datacap notaries, We'd like to move our next tranche of our approved data cap allocation to this wallet: f17g7h52bsi53rb263xwne573dusskit4mieqkgry We are actively sealing deals and ready to scale. Thanks! |
|
According to glif, address f3w5fx6wta4ewl2iyf7xcogmzffz2fmrngpzdpduj3xmk3dwjxc6dyq36gdf3rflkkrblh5nci5xymc5hal3qq has 14 TiB remaining. With the initial allocation of 50TiB, that means the next allocation should kick off at ~12 TiB. Checking lotus, seeing 2 pending transactions with only 1 approval, so I want to check in with the team before I make any changes to the client address. |
|
Additionally flagging for notaries: Per your application and the large dataset process, can you provide some more details about your deal distribution plan? |
|
Hi Galen,
We are still testing the deal automation with Bitbot so we are
progressively decentralizing. The plan so far is as follows:
Pilot 81 TiBs sealed with 1 provider (as a test)
Pilot 81 TiBs sealed with 4 providers
Pilot 81 TiBs sealed with 10 providers
With these pilots finished we are then going to work on a plan for 4 PiBs.
The plan there is to distribute to an initial set of 10 providers and then
scale to as many as possible.
The fulcrum will be what type of financing SPs will need to take on to meet
their pledge. We are working with PL on that mechanism.
Happy to answer any questions you have.
Best,
Jonathan
…On Thu, Dec 16, 2021 at 3:49 PM Galen ***@***.***> wrote:
Additionally flagging for notaries:
@starling-admin <https://github.com/starling-admin> according to a quick
audit (https://filplus.d.interplanetary.one/clients/f0700600/breakdown),
while you have worked with 20 storage providers, an extreme majority of
your deal-making has been with a single storage provider (*84%*).
Per your application and the large dataset process, can you provide some
more details about your deal distribution plan?
—
Reply to this email directly, view it on GitHub
<#53 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AP5M66UQ3V735S4HL3GCNXTURJ3HRANCNFSM5FDDUOOA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***
com>
|
DataCap Allocation requestedMultisig Notary address
Client address
DataCap allocation requested
|
Stats for DataCap AllocationMultisig Notary address
Client address
Last two approvers
DataCap allocation requested
Stats
|
DataCap Allocation requestedRequest number 8Multisig Notary address
Client address
DataCap allocation requested
Id
|
large-datacap-requests
bot
added
ready to sign
and removed
granted
validated
ready to sign
verified client
labels
Stats & Info for DataCap AllocationMultisig Notary address
Client address
Rule to calculate the allocation request amount
DataCap allocation requested
Total DataCap granted for client so far
Datacap to be granted to reach the total amount requested by the client (5 PiB)
Stats
|
|
checker:manualTrigger |
DataCap and CID Checker Report Summary1Retrieval Statistics
Storage Provider Distribution✔️ Storage provider distribution looks healthy. Deal Data ReplicationDeal Data Shared with other Clients2
Full reportClick here to view the CID Checker report. Footnotes |
|
PiKNiK, in collaboration with USC Shoah, kindly requested our attention to review and sign the LDN. Their data exhibits exceptional value and holds significance for the ecosystem. To ensure wider acceptance of the CID report, it is recommended to distribute it to one additional global service provider. |
Request ProposedYour Datacap Allocation Request has been proposed by the Notary Message sent to Filecoin Network
Address
Datacap Allocated
Signer Address
Id
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacedwvpuzrvf4eunpl47cwccck3hd5ovouxxylxjgwtv4o45nwejyg4 |
large-datacap-requests
bot
added
verified client
ready to sign
start sign datacap
and removed
ready to sign
verified client
labels
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 of the message here: https://filfox.info/en/message/bafy2bzacecaamvtmuetlnrxxond3mmdhjvn4ivi4rbcjd42wprkq6pt6cc5xc |
|
This application has not seen any responses in the last 10 days. This issue will be marked with Stale label and will be closed in 4 days. Comment if you want to keep this application open. |
|
This application has not seen any responses in the last 14 days, so for now it is being closed. Please feel free to contact the Fil+ Gov team to re-open the application if it is still being processed. Thank you! |
and others
Large Dataset Notary Application
To apply for a DataCap allocation for your dataset, please fill out the following information.
Core Information
Please respond to the questions below in pargraph form, 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 what is in the dataset? A link to a file, an image, a table, etc., are good examples of 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? Will this be a permanent archival or a one-time storage deal?
DataCap allocation plan
In which geographies do you plan on making storage deals?
What is your expected data onboarding rate? How many deals can you make in a day, in a week? How much DataCap do you plan on using per day, per week?
How will you be distributing your data to miners? Is there an offline data transfer process?
How do you plan on choosing the miners 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 data and DataCap across miners storing data?
The text was updated successfully, but these errors were encountered: