-
Notifications
You must be signed in to change notification settings - Fork 58
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
v5 Notary Allocator Application: Starlight #1005
Comments
Please update item 3 (wallet address) to: |
Hi, I have submitted the AirTable form too |
Hi @likkhai-nebula, |
Hi @Kevin-FF-USA, Thanks for the notification. We have already completed and submitted the Airtable form. Do let us know of any clarification you have. |
Basic Information1. Notary Allocator Pathway Name: 2. Organization: 3. On Chain Address for Allocator: 4. Country of Operation: 5. Region(s) of operation: 6. Type of Allocator: 7. DataCap requested for allocator for 12 months of activity: 8. Is your allocator providing a unique, new, or diverse pathway to DataCap? How does this allocator differentiate itself from other applicants, new or existing?: Since these enterprise data can be confidential and sensitive in nature, we are taking additional steps to protect these data:
Due to the enterprise nature of our business, we need to be certain that any data that our clients need to store in the network can be fulfilled. Hence our application to be an allocator for more secure allocation of DataCap. 9. As a member in the Filecoin Community, I acknowledge that I must adhere to the Community Code of Conduct, as well other End User License Agreements for accessing various tools and services, such as GitHub and Slack.: Client Diligence10. Who are your target clients?: 11. Describe in as much detail as possible how you will perform due diligence on clients. If you are proposing an automated pathway, what diligence mechanism will you use to determine client eligibility?: We can have a high degree of certainty that data is relevant since:
12. Please specify how many questions you’ll ask, and provide a brief overview of the questions.:
13. Will you use a 3rd-party Know your client (KYC) service?: However, if we feel that our processes are insufficient in future, we may consider engaging third party KYC services from reputable partners like Regtank. 14. Can any client apply to your pathway, or will you be closed to only your own internal clients? (eg: bizdev or self-referral): 15. How do you plan to track the rate at which DataCap is being distributed to your clients?: Data Diligence16. As an operating entity in the Filecoin Community, you are required to follow all local & regional regulations relating to any data, digital and otherwise. This may include PII and data deletion requirements, as well as the storing, transmit: 17. What type(s) of data would be applicable for your pathway?: 18. How will you verify a client’s data ownership? Will you use 3rd-party KYB (know your business) service to verify enterprise clients?:
19. How will you ensure the data meets local & regional legal requirements?: 20. What types of data preparation will you support or require?: 21. What tools or methodology will you use to sample and verify the data aligns with your pathway?: Data Distribution22. How many replicas will you require to meet programmatic requirements for distribution?: 23. What geographic or regional distribution will you require?: 24. How many Storage Provider owner/operators will you require to meet programmatic requirements for distribution?: 25. Do you require equal percentage distribution for your clients to their chosen SPs? Will you require preliminary SP distribution plans from the client before allocating any DataCap?: 26. What tooling will you use to verify client deal-making distribution?: 27. How will clients meet SP distribution requirements?: 28. As an allocator, do you support clients that engage in deal-making with SPs utilizing a VPN?: DataCap Allocation Strategy29. Will you use standardized DataCap allocations to clients?: 30. Allocation Tranche Schedule to clients:: 31. Will you use programmatic or software based allocations?: 32. What tooling will you use to construct messages and send allocations to clients?: 33. Describe the process for granting additional DataCap to previously verified clients.: 34. Describe in as much detail as possible the tools used for: • client discoverability & applications • due diligence & investigation • bookkeeping • on-chain message construction • client deal-making behavior • tracking overall allocator health • disput: Tools and Bookkeeping35. Will you use open-source tooling from the Fil+ team?: 36. Where will you keep your records for bookkeeping? How will you maintain transparency in your allocation decisions?: For the public disclosure requirements, there will be a report about the DataCap distribution periodically as per requested by the Governance team. We will also provide private communication method to help the team reach more relavant information when needed. Risk Mitigation, Auditing, Compliance37. Describe your proposed compliance check mechanisms for your own clients.:
7 . As we take charge of the data encryption and CAR file preparation accompanied by the DataCap allocation, the new DataCap will be allocated only if the existing quantity is consumed , no matter whether they are new clients or not. 38. Describe your process for handling disputes. Highlight response times, transparency, and accountability mechanisms.: However, if disputes do arise, no matter internally or externally, we have a consolidate system log to show the usage details of all the DataCap and also the payment history to prove they are all paying clients, the allocation of DataCap and distribution of clients’ data are all from clients’ real request that is paid by client. If there is a need to provide such evidence to solve the dispute, will be able to provide these logs and evidences upon request from Fil+ Governance Team. 39. Detail how you will announce updates to tooling, pathway guidelines, parameters, and process alterations.: 40. How long will you allow the community to provide feedback before implementing changes?: At the same time, we will monitor and participate in the Fil+ Slack channel to receive and respond to any feedback related to us; We will seriously consider the feedback from these channels and engage in constructive dialogue with the community when weighing and deciding on relevant changes. 41. Regarding security, how will you structure and secure the on-chain notary address? If you will utilize a multisig, how will it be structured? Who will have administrative & signatory rights?: 42. Will you deploy smart contracts for program or policy procedures? If so, how will you track and fund them?: Monetization43. Outline your monetization models for the services you provide as a notary allocator pathway.: After assessing current Web3 storage options, we have select FileCoin is our preferred storage platform. To ensure data security and privacy, Starlight system shall perform data encryption and data preparation before handing over to selected SPs. The following are our monetization structure:
44. Describe your organization's structure, such as the legal entity and other business & market ventures.: 45. Where will accounting for fees be maintained?: Past Experience, Affiliations, Reputation46. If you've received DataCap allocation privileges before, please link to prior notary applications.: 47. How are you connected to the Filecoin ecosystem? Describe your (or your organization's) Filecoin relationships, investments, or ownership.:
48. How are you estimating your client demand and pathway usage? Do you have existing clients and an onboarding funnel?: |
Hi @Kevin-FF-USA , would like to following up on the progress for this. |
Hi @Kevin-FF-USA , our multisig address is f23pcmi23ftg3hv6yknw6teq4wexzzsh2jynccp3y |
@Kevin-FF-USA seems the airtable form is no longer accepting submissions. ID address is f03019671 Ledger address: f1adtbrt6sjwlg6iartalccragv74fadmr6nv6r2a GitHub Repo is https://github.com/nebuladata-starlight/edms |
Datacap Request for AllocatorAddress
Datacap Allocated
|
The request has been signed by a new Root Key HolderMessage sent to Filecoin Network
You can check the status of the message here: https://filfox.info/en/message/bafy2bzacecyctui4b7injrh4zu774xk2ggnjef5aarrm66hvfu4tj5nuwnzmm |
Hi @galen-mcandrew , this does not seem to be our multisig address. Is it one that you have created for us? Appreciate if you can help advice us on how we can access the datacap. Thank you. |
Hi @galen-mcandrew for those of us who were not able to fill up the Airtable on time the first round, may I know when it will be re-opened? Many thanks. |
v5 Notary Allocator Application
To apply to be an allocator, organizations will submit one application for each proposed pathway to DataCap. If you will be designing multiple specific pathways, you will need to submit multiple applications.
Please complete the following steps:
1. Fill out the information below and create a new GitHub Issue
Notary Allocator Pathway Name (This can be your name, or the name of your pathway/program. For example "E-Fil+"):
Starlight (Enterprise Data Management System)
Organization Name:
Nebula Data Pte. Ltd.
On-chain address for Allocator (Provide a NEW unique address. During ratification, you will need to initialize this address on-chain):
f1x2dxgsklcbphzup6k5d7ds3ysitez7plxtbyd6a
Country of Operation (Where your organization is legally based):
Singapore
Region of Operation (What region will you serve?):
Worldwide, SEA region in the initial phase.
Type of Allocator, diligence process: (Automated/programmatic, Market-based, or Manual (human-in-the-loop at some phase):
Most of our DataCap requests are expected to be initiated from the Starlight Enterprise Data Management System. This system allows enterprises to store their corporate data for extended periods of time for archival and compliance purpose.
All onboarded enterprise clients will go through our internal KYB process.
Our clients are charged for all data stored through our platform and DataCap requests are initiated by these enterprise clients through us as their proxy.
DataCap requested for allocator for 12 months of activity (This should be an estimate of overall expected activity. Estimate the total amount of DataCap you will be distributing to clients in 12 months, in TiB or PiB):
5 PiB
2. Access allocator application (download to save answers)
Click link below to access a Google doc version of the allocator application that can be used to save your answers if you are not prepared to fully submit the application in Step 3. https://docs.google.com/document/d/1-Ze8bo7ZlIJe8qX0YSFNPTka4CMprqoNB1D6V7WJJjo/copy
3. Submit allocation application
Clink link below to access full allocator questionnaire and officially submit your answers:
https://airtable.com/appvyE0VHcgpAkt4Z/shrQxaAIsD693e1ns
Note: Sections of your responses WILL BE posted back into the GitHub issue tracking your application.
The final section (Additional Disclosures) will NOT be posted to GitHub, and will be maintained by the Filecoin Foundation.
Application information for notaries not accepted and ratified in this round will be deleted.
The text was updated successfully, but these errors were encountered: