Kevin-FF-USA
commented
6 months ago Hi @cryptowhizzard,
Thanks for submitting to become and Allocator! Wanted to confirm this application has been received along with your completed Airtable form.
Closed cryptowhizzard closed 1 month ago
Kevin-FF-USA
commented
6 months ago Hi @cryptowhizzard,
Thanks for submitting to become and Allocator! Wanted to confirm this application has been received along with your completed Airtable form.
ghost
commented
6 months ago 1. Notary Allocator Pathway Name: Dcent - Fil+ - NC
2. Organization: DCENT
3. On Chain Address for Allocator: f1eiw5gn24wpa44azzxhbyj545vzm7jqjdrcdv2fy
4. Country of Operation: The Netherlands
5. Region(s) of operation: Greater China, Asia minus GCR, Africa , Europe, Oceania, Japan, North America, South America, Other
6. Type of Allocator: Manual
7. DataCap requested for allocator for 12 months of activity: 3000 PiB
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?: At Dcent, our mission is to pave the way for seamless and efficient data allocation within the Filecoin network, catering to non-commercial (unpaid) datasets. With this allocator application we will actively try to bridge the gap between experimental block rewards-based storage and commercial solutions.
Our journey with Filecoin Plus began in 2021, and we've been making a difference ever since. Data packing and distribution are our strengths, and our reputation in the community speaks volumes, especially when it comes to handling extensive datasets like NIH (13PiB+).
Here is what we bring to the table as an non-commercial Dataset Allocator: A robust global BGP network, boasting speeds of up to 80Gbps (equivalent to 0.8PiB of daily RAW data). Experience with successfully onboarding a staggering 75 to 100PiB of RAW deals onto the network, while forming partnerships with over 35 Storage Providers globally. With a whopping capacity of 15PiB for raw deal-data storage, we've got the space to accommodate your needs. We have fine-tuned our specialized computation systems and software tools to ensure efficient data preparing and distribution. We foster the ability to download large datasets locally before global distribution. Collaborations with GLIF, DARMA, and Coinlist to assist Storage Providers in securing the collateral they require.
One standout feature that sets us apart is our commitment to open-source our in-house software for data distribution if we get accepted as a Datacap Allocator. Our aim is simple – to benefit the entire FIL+ community and elevate the Filecoin experience for everyone involved.
Additionally, our extensive European 80 Gbit/s IP BGP powered backbone, under AS-207551, positions us as the perfect candidate to fulfill the network's data distribution demands.
In a nutshell, Dcent's unique approach as a DataCap Allocator revolves around making non-commercial dataset storage simple, facilitating the transition to commercial storage, and contributing to the flourishing Filecoin (plus) ecosystem. We are here to offer our expertise and innovative solutions to fortify the Filecoin network.
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.: Acknowledge
10. Who are your target clients?: Individuals learning about Filecoin, Small-scale developers or data owners, Enterprise Data 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?: Minimum of one video call with visuals. KYC through Veriff where we compare the identity document to the person we are speaking with Chamber of commerce check and VAT check ( Mandatory for business transactions in the EU )
12. Please specify how many questions you’ll ask, and provide a brief overview of the questions.: Business Verification Questions: Can you provide your Chamber of Commerce registration details? Do you have a valid VAT (Value Added Tax) number? Can you provide proof of business identity, such as incorporation documents or business licenses? Data Verification Questions: What type of data do you intend to store on Filecoin? How large is your storage capacity? Do you have retrieval of data enabled and does it work? Do you have any specific storage or retrieval requirements? Is your storage compliant with local and international data protection regulations (e.g., GDPR in Europe and NOTD procedures)? Financial and Contractual Questions: What is your budget for data storage? Are you looking for short-term or long-term storage solutions? Can you commit to a minimum storage period? Do you have any specific Service Level Agreements (SLAs) or Key Performance Indicators (KPIs) that you can offer? Security and Compliance Questions: How do you ensure the security and integrity of your data? Use Case and Purpose Questions: What is the primary purpose of storing this data? Do you anticipate frequent access to this data or is it primarily for archival purposes? What is your uplink bandwidth and is it dedicated or shared? Backup and Recovery Questions: What are your expectations for data backup and recovery? Do you have a disaster recovery plan in place? Audit and Reporting Requirements: Are you subject to any audit requirements for your data? Do you need regular reporting on your data storage?
13. Will you use a 3rd-party Know your client (KYC) service?: Yes, Veriff. We worked with them before doing KYC for the LDN participants. We are open for better solutions tbd.
14. Can any client apply to your pathway, or will you be closed to only your own internal clients? (eg: bizdev or self-referral): Any SP can apply
15. How do you plan to track the rate at which DataCap is being distributed to your clients?: We have our own software system built in retool and will monitor this per tranche / application to make sure it is compliant with the conditions we set. We will use the limited thrust principle ( Start with small tranches ). We also monitor the total use of datacap and put daily alerts on it. We already have PHP scripts looking at certain wallets in the network providing alerts who are suitable for this.
16. 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: Acknowledge
17. What type(s) of data would be applicable for your pathway?: Public Open Dataset (Research/Non-Profit), Private Non-Profit/Social Impact
18. How will you verify a client’s data ownership? Will you use 3rd-party KYB (know your business) service to verify enterprise clients?: We will check the license of the dataset involved. If it is an open license we don’t have to check as it is free to distribute. As this pathway is designed to store open datasets there are no additional considerations required.
19. How will you ensure the data meets local & regional legal requirements?: As we are experienced as a former Usenet provider and the legal aspect of storing data on European ground we will provide advice to client’s / SP’s if deemed necessary. We have NOTD ( Notice and takedown ) procedures implemented and have active cooperation with copyright enforcing agencies to stay within the boundaries of current regulation.
20. What types of data preparation will you support or require?: At this moment we support Singularity to do the packing process and we use our own inhouse build software to manage the distribution. Please note that we are open to use / integrate other existing tools like Spade or web3.storage per clients request.
21. What tools or methodology will you use to sample and verify the data aligns with your pathway?: We will do visual semi-automatic random sample checks on the data. We have this system already operational in the current Fil+ enviroment where we automatically download CID's, unpack them and make them available for inspection. We also have a backup pathway with a We-Transfer alike system where clients can upload their data for random inspection. ( See Github LDN repo ).
22. How many replicas will you require to meet programmatic requirements for distribution?: 5+
23. What geographic or regional distribution will you require?: We will comply with 5 or more regions including unique geopolitical/language coverage, each replica at different physical location, no or minimal VPN and different SP owner operators.
24. How many Storage Provider owner/operators will you require to meet programmatic requirements for distribution?: 5+
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?: Yes, we will require preliminary SP distribution plans and equal distribution
26. What tooling will you use to verify client deal-making distribution?: We are using the CID checker bot, but also use the Fil+ API together with our own software tools built in Retool to check what is stored and where. The governance team is familiar with those we believe. If needed we are open to discuss making them open source.
27. How will clients meet SP distribution requirements?: We use Singularity and our own distribution software where sharding is enabled to make sure that distribution is equal. We monitor this according to point 26 with the CID check bot and our own software.
28. As an allocator, do you support clients that engage in deal-making with SPs utilizing a VPN?: No.
29. Will you use standardized DataCap allocations to clients?: Yes, standardized
30. Allocation Tranche Schedule to clients:: • First: 10% • Second: 20% • Third: 35% • Fourth: 35% • Max per client overall: 100%.
The amount of PiB depends on the scale of the commercial data that is stored. We can imagine that the internet archive for example would need more datacap than a simple ICT company for a one time offline backup. See point 29.
31. Will you use programmatic or software based allocations?: Yes, standardized and software based
32. What tooling will you use to construct messages and send allocations to clients?: We will either use something available ( preferred ) or write something ourselves that keeps track of the messages sent etc. Available tools are the CLI of lotus daemon itself to send datacap, but also the Fil+ registry software panel. It is not clear to us if there are still notary’s in the loop together with the allocators. Notary’s will still use something like the Fil+ registry to grant datacap.
33. Describe the process for granting additional DataCap to previously verified clients.: We will use the SA bot to alert when there is less then 25% of datacap available or write similar software in case it is unavailable for use.
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: Describe in as much detail as possible the tools used for: • client discoverability & applications We will create a public Github repository where we will keep track of the clients applications and where clients can submit their applications. • due diligence & investigation We will do this with Github to have it open towards the community. • bookkeeping
We will do this with Github to have this open towards the community. • on-chain message construction
See question 32. We will either use something available ( preferred ) or write something ourselves that keeps track of the messages sent etc. Available tools are the CLI of lotus daemon itself to send datacap, but also the Fil+ software panel. It is not clear to us if there are still notary’s in the loop together with the allocators. Notary’s will still use something like the Fil+ software to grant datacap. • client deal-making behavior
We intend to use both our custom software that we will open source or make accessible on request, together with the current tooling of PL ( The CID checker bot ). We also build a API on the retrieval bot statistics that we will use to make decisions. • tracking overall allocator health We intend to use both our custom software that we will open source or make accessible on request, together with the current tooling of PL ( The CID checker bot ). • dispute discussion & resolution We intend to use a software tool like https://civicrm.org/ CiviCRM is a powerful, web-based CRM software that is particularly popular among non-profits, civic sector organizations, and advocacy groups. Its flexibility makes it suitable for managing various community interactions, including dispute resolution.
Note: This software is a suggestion. If the governance team has alternatives we are open to conside those. • community updates & comms *
We will create a webpage for this that visualizes all tools available and reports on outage of maintenance.
35. Will you use open-source tooling from the Fil+ team?: Yes. We intend to use all resources available. CID checker bot CID retrieval bot. Sa bot. Vercel.app ( Retrieval bot statistics ) Fil+ notary panel datacapstats.io ( and it’s API ). And others if available.
36. Where will you keep your records for bookkeeping? How will you maintain transparency in your allocation decisions?: Github for the public accessible information:
37. Describe your proposed compliance check mechanisms for your own clients.: Client Onboarding Verification: Implement strict verification processes during client onboarding. This includes validating business registration documents, VAT numbers, and any relevant certifications + KYC / KYB. Conduct background checks to ensure clients have a legitimate business presence and no history of fraudulent activities. Data Usage and Storage Policy Agreement: Require clients to sign a policy agreement that outlines acceptable use of DataCap, data storage protocols, and compliance with legal regulations. Clearly define the consequences of policy violations. Automated Monitoring System: Utilize automated tools described above to monitor client data usage and storage patterns. This can help in identifying any unusual activities or deviations from agreed-upon terms. Set up alerts for when clients approach their DataCap limits or exhibit potential non-compliant behavior. Regular Compliance Audits: Schedule regular audits of client data storage practices, ensuring adherence to Filecoin’s standards and your own compliance rules. Include checks for data security, encryption standards, and data integrity. Documentation and Reporting: Keep detailed records of all client interactions, DataCap allocations, and compliance checks on Github for review by the community. Implement a standardized reporting system for clients to submit their data usage and storage reports periodically. Client Training and Resources: Provide educational resources and training sessions to clients about best practices in data storage, security, and compliance within the Filecoin network. ( A client should attend at least 2 ). Encourage open communication for clients to ask questions or report issues. Response Plan for Non-Compliance: Develop a clear response plan for instances of non-compliance. This may include warnings, reduction or removal of DataCap, and in severe cases, termination of services. Ensure that the response plan is transparent and understood by all clients. Feedback and Improvement Mechanism: Create a feedback loop with clients to continuously improve compliance mechanisms based on real-world usage and challenges. Stay updated with Filecoin network updates and global compliance standards to refine your strategies.
How will you track and audit your own DataCap distribution, and the downstream usage by your clients? How much tolerance will you have for new clients? *
DataCap Distribution Tracking System: We will Establish a robust tracking system that records every allocation of DataCap to clients. This system includes client details, amount of DataCap allocated and dates of allocation. Client Usage Monitoring: We will develop or integrate a monitoring tool that tracks how clients are utilizing their allocated DataCap. This includes tracking the volume of data stored where and when. We will set up alerts for unusual patterns or behaviors that might indicate misuse or deviation from agreed terms. Risk Assessment for New Clients: We will implement a risk assessment protocol for new clients. This involves a tiered approach where new clients start with a smaller DataCap allocation and earn more as they demonstrate compliant usage. We will conduct more frequent audits and reviews for new clients until they establish a history of compliant behavior. Regular Audits and Compliance Checks: We will schedule regular audits of both DataCap distribution and client usage. These audits should assess compliance with our policies and Filecoin's regulations. Include both automated checks and manual reviews in the audit process. Zero Tolerance for Illegal Activities: We maintain a zero-tolerance policy for illegal activities. Any client found using DataCap for unlawful purposes should face immediate action. For other types of non-compliance, we consider a graduated response depending on the severity and frequency of the violation. Documentation and Reporting: We keep detailed documentation of all DataCap distributions and the results of usage audits on Github. This will be crucial for internal reviews and responding to any disputes or inquiries. Regularly report these findings internally and, if required, to the Filecoin community or relevant authorities. Client Feedback and Intervention Mechanism: Allow clients to report their usage and provide feedback on their needs and challenges. This can help in adjusting policies for better compliance and client satisfaction. Set up a clear mechanism for intervening when clients are close to exceeding their allocated DataCap or are showing signs of non-compliance. Tolerance Levels for New Clients: We will define clear tolerance levels for new clients, balancing the need for compliance with the opportunity for them to prove their reliability. This could include a probationary period with more frequent checks and lower DataCap allocations. Gradually increase tolerance as clients demonstrate compliance and trustworthiness over time.
38. Describe your process for handling disputes. Highlight response times, transparency, and accountability mechanisms.: To handle disputes effectively within the context of DataCap allocation on the Filecoin network, it is crucial to establish a clear, transparent, and accountable process. We suggest the following: Dispute Intake and Initial Assessment: We set up a dedicated channel (e.g., email, portal on Civicrm) for clients or involved parties to raise disputes. Upon receiving a dispute, conduct an initial assessment to categorize the issue (e.g., DataCap allocation, compliance issues, storage deal conflicts or NOTD). Acknowledge receipt of the dispute within 24 hours to ensure the parties involved know their concerns are being addressed. Transparent Documentation and Tracking: Maintain a log of all disputes, including details of the parties involved, the nature of the dispute, and any initial evidence or claims. Use a case management system in CiviCRM to track the progress of each dispute, ensuring no case is overlooked or delayed. Investigation and Information Gathering: Assign a dedicated team or individual to investigate the dispute. This might involve gathering data logs, contract details, communication records, and any other relevant information. Ensure that the investigation is thorough and unbiased, seeking to understand all aspects of the dispute. Response Time and Communication: Aim to provide an initial response or update within a set timeframe (e.g., 48-72 hours) after the dispute is logged. Keep all parties informed throughout the investigation process, maintaining transparency about the steps being taken. Resolution and Mediation: Once sufficient information is gathered, propose a resolution based on the findings. In cases where a simple resolution is not possible, consider mediation between parties. Ensure that the resolution is fair, aligns with Filecoin’s guidelines, and respects the terms agreed upon by the parties involved. Accountability and Enforcement: Implement the agreed-upon resolution, ensuring that all parties adhere to the decision. Hold parties accountable for any breach of agreement or misconduct identified during the dispute resolution process. Review and Feedback: After resolution, review the handling of the dispute to identify any areas for improvement in the process. Seek feedback from the parties involved to understand their experience of the dispute resolution process and to make necessary adjustments. Reporting and Learning: Document key learnings from each dispute to refine your processes and prevent similar issues in the future. Regularly review dispute trends to identify systemic issues or areas requiring policy changes. Public Reporting and Transparency: Where appropriate, and respecting confidentiality, share summaries of dispute resolutions with the community to enhance transparency and trust. Regularly update your dispute resolution policy and make it publicly available for clients and other stakeholders to review. This process ensures that disputes are handled efficiently, transparently, and fairly, fostering trust among all parties involved in the Filecoin network. It also demonstrates a commitment to maintaining a high standard of service and accountability in our role as a notary allocator.
39. Detail how you will announce updates to tooling, pathway guidelines, parameters, and process alterations.: We intend to do this by email and slack + on a dedicated website where an overview of all systems is provided.
40. How long will you allow the community to provide feedback before implementing changes?: For effective community engagement and feedback implementation in the context of a decentralized environment like the Filecoin network, it's important to strike a balance between openness and practical governance. Here's a structured approach to this process: Setting a Standard Feedback Period: Establish a standard period for community feedback on proposed changes. This period should be long enough to allow ample participation, typically ranging from 2 to 4 weeks, depending on the complexity and impact of the proposed changes. Announcing Changes and Soliciting Feedback: Clearly communicate any proposed changes to the community through multiple channels (Slack / Website / Mail etc). This ensures broad awareness and encourages participation. Provide detailed information about the changes, including the rationale, expected impact, and any potential concerns. Facilitating and Moderating Discussions: Host moderated discussions, Q&A sessions, or webinars where community members can ask questions, seek clarifications, and voice opinions. Ensure that moderation is fair and unbiased, allowing diverse viewpoints to be expressed while maintaining respectful and constructive discourse. Diverse Channels for Feedback Collection: Offer various channels for feedback, including surveys, online forums, direct emails, and possibly even offline meetings, to accommodate different preferences and ensure inclusivity. Active Listening and Engagement: Actively engage with the community during the feedback period. This includes responding to queries, participating in discussions, and acknowledging the receipt of feedback. Weighing and Integrating Feedback: After the feedback period, we review all input carefully. We consider the feasibility, impact, and alignment of the feedback with the overall goals and policies. Weight feedback based on its relevance, the number of times a particular point is raised, and the overall benefit to the community and network. Transparent Decision-Making: Make decisions transparently, explaining how feedback was integrated into the final implementation. In cases where certain feedback cannot be accommodated, provide clear explanations to the community. Implementing and Reviewing Changes: Implement changes in a phased manner, if possible, to monitor effects and make adjustments as needed. Continuously review the impact of changes and remain open to further feedback and iterations. Reporting Back to the Community: After implementation, providing reports back to the community summarizing the feedback received, decisions made, and the rationale behind them. This ensures accountability and maintains trust in the process. By following this approach, we ensure that the community is actively involved in the decision-making process, their feedback is valued and considered, and that changes are implemented in a way that is transparent and aligned with the community's needs and expectations.
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?: We will create a multisig wallet that requires signatures from both Wijnand Schouten and Hidde Hoogland to authorize transactions. This enhances security by ensuring that no single party can unilaterally make changes or transactions. Setting Up Signatory Rights: We will ensure that both (Wijnand Schouten and Hidde Hoogland) have equal signatory rights. This means that both signatures are required for any transaction to take place. Security Protocols: We will implement robust security protocols for the multisig wallet. This includes secure storage of private keys, regular updating of wallet software, and the use of two-factor authentication (2FA) for access. Backup and Recovery Plan: We will create a backup and recovery plan in case of loss of access to the multisig wallet. This involves secure backups of private keys and having a predefined process for restoring access. Audit and Compliance: Regularly audit the wallet for any unusual activities or security threats.
42. Will you deploy smart contracts for program or policy procedures? If so, how will you track and fund them?: No, no yet but we are open to learn something new ;-)
43. Outline your monetization models for the services you provide as a notary allocator pathway.: Monetization is structured in a simple way:
44. Describe your organization's structure, such as the legal entity and other business & market ventures.: DCENT BV is an innovative company in the Netherlands focusing on decentralized green storage solutions. They are specialized in eco-friendly practices, utilizing solar power for their operations. The company features cutting-edge technology, including 3rd Gen AMD CPUs and Nvidia GPUs, and ensures high-speed connectivity. As a legal entity, DCENT BV complies with European and Dutch data regulations, emphasizing data privacy and security. They are a significant European Storage Provider for the Filecoin/IPFS network, contributing to the decentralized web and secure data storage. For more detailed insights into their structure and business ventures, visit their website at www.dcent.nl.
45. Where will accounting for fees be maintained?: We are planning to establish a new company for this service. Since it is a commercial service, we will record all transactions in our accounting. Annual audits and financial statements will be publicly accessible. Individual invoices can be requested by the governance team.
46. If you've received DataCap allocation privileges before, please link to prior notary applications.: https://github.com/filecoin-project/notary-governance/issues/678 https://github.com/filecoin-project/notary-governance/issues/414
47. How are you connected to the Filecoin ecosystem? Describe your (or your organization's) Filecoin relationships, investments, or ownership.: As an individual, I bring over six years of experience in crypto mining and programming to the Filecoin community, being active since the 2020 spacerace. I co-founded Speedium and DCENT with Hidde. DCENT, as a leading European service provider, specializes in high-quality data onboarding to the Filecoin network, working extensively within the ecosystem. We are a major decentralized Filecoin node in Europe, offering global, reliable storage solutions. Our advanced networking capabilities, private IP backbone, and 100Gbit/s throughput place us at the forefront of this emerging technology. We maintain several Service Provider IDs: f01720359, f01771403, f01786387, f02095132, f02033496, and f02366527.
48. How are you estimating your client demand and pathway usage? Do you have existing clients and an onboarding funnel?: We are already providing service to customers. Our estimate is 365 days * 9 PiB of datacap daily that will be requested. We are aware that this estimation is based on the other applicants who might provide similar pathways but if there are none, we expect something like this.
cryptowhizzard
commented
4 months ago Please note I had to change my ledger address as updated above to f14argljqmkt3ig4yhi5hqbm44eezafterkjj56uq
kevzak
commented
4 months ago f2x2djhw54agyes32iyi2colhflb4ekm32iz54tjq
Datacap Allocated
5PiB
filplus-bot
commented
3 months ago bafy2bzacedzai7iszmcih6vxkf46dtiayiys5mtofoe23tmlyxqkfchgsx5cm
Kevin-FF-USA
commented
1 month ago Hi @cryptowizzard
On the next Fil+ Allocator meeting we will be going over each refill application. Wanted to ensure you were tracking the review discussion taking place in https://github.com/filecoin-project/Allocator-Governance/issues/18.
If your schedule allows, recommend coming to the May 28th meeting to answer/discuss the issues raised in the recent distributions. This will allow you to faster address - or, the issue in Allocator Governance for ongoing written discussion.
Warmly, -Kevin https://calendar.google.com/calendar/embed?src=c_k1gkfoom17g0j8c6bam6uf43j0%40group.calendar.google.com&ctz=America%2FLos_Angeles
galen-mcandrew
commented
1 month ago f2x2djhw54agyes32iyi2colhflb4ekm32iz54tjq
Datacap Allocated
10PiB
filplus-bot
commented
1 month ago bafy2bzacecm7fgmnbbqmneejdmm3znnot7qpxmnd3suutkv6i6v55hvqulfye
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