Open Bitengine-reeta opened 8 months ago
Hi @Bitengine-reeta Wanted to let you know this application has been received. After you complete and submit the Airtable form with your detailed Allocator plan - the public answers will be posted in a thread below. If you have any questions - please let me know.
1. Notary Allocator Pathway Name: Bitengine Reeta FIL+
2. Organization: Bit Engine Pte Ltd.
3. On Chain Address for Allocator: f15x23zuhctuqz77tvkzthow3xkpvn3q4kjgxpgya
4. Country of Operation: Singapore
5. Region(s) of operation: Asia minus GCR
6. Type of Allocator: Manual
7. DataCap requested for allocator for 12 months of activity: 100PiB
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?: Yes, we will provide a special channel for less experienced SP to obtain a small amount of Datacap for Miner sealing. The quota size is no more than 200T, and this special channel will be realized through Github Application with special label. In order to distinguish it from the applicants of other distributors, we will add allocator field information in the application information to indicate the name of the distributor.
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, Other (specified above)
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?: The basic principles of our clients review are as follows:
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?: No, we will review the client by manual KYC.
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 client
15. How do you plan to track the rate at which DataCap is being distributed to your clients?: We will regularly check the DC balance at each client address and its consumption rate.
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), Public Open Commercial/Enterprise, Private Commercial/Enterprise, Private Non-Profit/Social Impact, Other (specified elsewhere)
18. How will you verify a client’s data ownership? Will you use 3rd-party KYB (know your business) service to verify enterprise clients?: For public data, we will verify the public permission statement of the data. For private data, we require the client to provide relevant authorization documents or certificates.
19. How will you ensure the data meets local & regional legal requirements?: We will try our best to avoid data types with legal risks. For specific data, we will ask the client to provide sufficient proof of use and storage to ensure that the client has the right to use and store data.
20. What types of data preparation will you support or require?: We will encourage the use of open source data preparation tools and services.
21. What tools or methodology will you use to sample and verify the data aligns with your pathway?: We will encourage the use of open source data preparation tools and services.
22. How many replicas will you require to meet programmatic requirements for distribution?: 5+
23. What geographic or regional distribution will you require?: Each Datacap application project must come from at least four different countries or regions and two different continents.
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?:
26. What tooling will you use to verify client deal-making distribution?: Mainly based on datacapstats.iotooling and/or the CID checker bot. In addition, we will also summarize the Miner information disclosed by customers, and manually command to judge Miner IP, and then query the location of IP.
27. How will clients meet SP distribution requirements?: The client will decide how to distribute the data, and we don't limit it.
28. As an allocator, do you support clients that engage in deal-making with SPs utilizing a VPN?: When clients apply for Datacap and during the continuous packaging process, we will ask clients to disclose all the information of Miner involved, including whether to use VPN or not. If clients use VPN, they need to explain why they use VPN, and we will record the original location of the miner. When judging the data distribution, we will judge according to the original position of all miner.
29. Will you use standardized DataCap allocations to clients?: No, client specific
30. Allocation Tranche Schedule to clients::
31. Will you use programmatic or software based allocations?: No, manually calculated & determined
32. What tooling will you use to construct messages and send allocations to clients?: the existing notary registry tooling at https://filplus.fil.org/#/
33. Describe the process for granting additional DataCap to previously verified clients.: First allocation: lesser of 5% of total DataCap requested or 50% of weekly allocation rate Second allocation: lesser of 10% of total DataCap requested or 100% of weekly allocation rate Third allocation: lesser of 20% of total DataCap request or 200% of weekly allocation rate Fourth allocation: lesser of 40% of total DataCap requested or 400% of weekly allocation rate Fifth allocation onwards: lesser of 60% of total DataCap request or 600% of weekly allocation rate I will try to use the Open-Source Tooling Such as the Subequal Allocation (SA) BOT, but I will reserve the right of manual intervention, mainly because automation tools are prone to bugs.
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: • client discoverability & applications Github Repo: Used to collect client requests, it is an open and transparent process audit platform, and clients can publicly disclose some information here. • due diligence & investigation Manual: check the authenticity of information disclosed by clients, the legality of data, the rationality of data volume and evidence. • bookkeeping Google spreadsheet: Organize and manage client information, transaction information and SPs information in a unified way. • on-chain message construction https://filplus.fil.org/#/ • client deal-making behavior filfox.io and other explorer • tracking overall allocator health CID checker bot / retrievalbot-dashboard • dispute discussion & resolution slack channel/ github • community updates & comms slack channel/ github
35. Will you use open-source tooling from the Fil+ team?: Yes, GitHub repo - Collect client's application and handle the whole process. Google spreadsheet - Collect KYC information of client Gmail-receive KYC mail from client MysqlDB-Create a relational table and store all the information. Grafana-Monitor and display Datacap consumption, store deal, Miner distribution and other information.
36. Where will you keep your records for bookkeeping? How will you maintain transparency in your allocation decisions?: In GitHub Repo, what the client submits and discloses is the part that can be made public, which includes the name of the client, the information summary of the applicant, the summary of the project, the size of the Datacap application, the weekly allocation quota and so on. In addition, Github needs to continuously disclose SPs related information: minerID\IP\Location\SP Name.
In the process of due diligence, if it is necessary to investigate the client subject, or the supporting documents and business licenses of the SP subject, we will use email. Internal audit, this part of the information will not be made public.
37. Describe your proposed compliance check mechanisms for your own clients.: Compliance inspection will be carried out regularly, with a frequency of about once every 10 days. We will use tools such as CID Checker/Retrievability Bot comprehensively, and we will also manually download the data and decompress the audit. The main purpose is to ensure that the actual stored data is consistent with the disclosure. The inspection items mainly include the following points:
38. Describe your process for handling disputes. Highlight response times, transparency, and accountability mechanisms.: When there is a dispute in the implementation process, I will first find out the specific details of the dispute in detail, judge the responsibility according to the basic rules of FIL+, and then take corresponding measures. We will respond to the dispute as soon as possible, and this time will be kept within one week. We will be completely open to the process, basis and conclusion of judgment, and listen carefully to the opinions of other community workers. Penalties for liability will be imposed from the aspects of client qualification and Datacap quota, and those with serious circumstances will be directly disqualified and the distribution of remaining data caps will be cancelled.
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?: The duration of community feedback depends on many factors, including the nature and urgency of change, the complexity of community structure and the potential impact on stakeholders. If changes are urgent, such as addressing security vulnerabilities, a shorter feedback window may be necessary to expedite the implementation. Major changes or those with significant implications may require a longer feedback period to ensure thorough input from the community.
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?: Create an on-chain address using leger hardware wallet.
42. Will you deploy smart contracts for program or policy procedures? If so, how will you track and fund them?: Not yet.
43. Outline your monetization models for the services you provide as a notary allocator pathway.: We currently do not use a monetization strategy to achieve the purpose of restraint
44. Describe your organization's structure, such as the legal entity and other business & market ventures.:
45. Where will accounting for fees be maintained?: Singapore
46. If you've received DataCap allocation privileges before, please link to prior notary applications.: https://github.com/filecoin-project/notary-governance/issues/692
47. How are you connected to the Filecoin ecosystem? Describe your (or your organization's) Filecoin relationships, investments, or ownership.: Bit Engine has been paying attention to web3 and joined the blockchain industry for more than ten years. Tomi Wen, the founder of the company, is also a pioneer in the blockchain industry. The company began to study IPFS technology in 2016 and began to participate in the construction and technical research of Filecoin nodes in 2019. Miner, currently operating, such as f081977 f081978 f081979 f081986 f081995 f0408629 f01741924 f01771695 f01753006 f01782338 f090665 f02208888 Tomi Wen founded Bit Engine Singapore's predecessor ""Beijing Digital Engine Technology Co., Ltd."" in Beijing in 2009, and obtained tens of millions of financing from top venture capital companies in China, and focused on deepening the market of web3 and blockchain. In 2016, the DBX public chain was created, and the ecological application on the public chain used IPFS as the underlying storage technology. https://github.com/dbxone/dbxchain In 2019, the company began to develop Web3 services with IPFS and Filecoin as the underlying storage technologies, and set up a professional technical team to help the development of IPFS and Filecoin ecological technologies. They helped to develop a decentralized video platform Voodfy based on Filecoin, which made outstanding contributions to the development of the underlying technologies of the project. https://github.com/Voodfy Tomi, the founder of the company, moved to Singapore in 2021 and founded BitEngine Pte Ltd. Since then, all the business of the company has been operated in Singapore. At the same time, we hope to expand our business in Singapore and have a brighter future in the field of distributed storage.
48. How are you estimating your client demand and pathway usage? Do you have existing clients and an onboarding funnel?: We will judge whether the client has a reasonable data storage requirement according to the application information submitted by the client and the client information collected during the KYC process, and we will track its usage with tools such as CID checker. There are already a number of interested clients in our current business cooperation, and we will release the recruitment information of client through X, Youtube, slack and other channels.
f2p2yz6iv33uiz6snsbgheuvwa4cjclcpi46fpbkq
Datacap Allocated
5PiB
bafy2bzaceavyjtz7aw2qcbril46mldr4kobjtgr3highaxvgwavfxye46l7iw
@kevzak @galen-mcandrew Need change my On Chain Address for Allocator to : f1km6utrorrtqh572e3ybfu7jq2gfktkgfghscr6i
and the New Multi-Address is : f2jh575hxrtfjl7uvu5ymfzrpfyq45fnhvhlajjdi
f2p2yz6iv33uiz6snsbgheuvwa4cjclcpi46fpbkq
Datacap Allocated
5PiB
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
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.