Open Ehume opened 6 months ago
Kevin-FF-USA
commented
5 months ago Hi @Ehume Wanted to let you know this application has been received. Once you complete and submit the include Airtable (form) information - the public answers will be posted in a thread below soon. If you have any questions - please let me know.
Kevin-FF-USA
commented
5 months ago Hi @Ehume,
Thanks for submitting to become and Allocator! Wanted to confirm this application has been received along with your completed Airtable form.
ghost
commented
5 months ago 1. Notary Allocator Pathway Name: Ehume
2. Organization: YugaTech
3. On Chain Address for Allocator: f1gjfz3qnbqjcdal6geo5vemmdqvseaia2l6kwj7i
4. Country of Operation: China
5. Region(s) of operation: Africa , Asia minus GCR, Greater China, Europe, Oceania, Japan, North America, South America, Other
6. Type of Allocator: Automatic
7. DataCap requested for allocator for 12 months of activity: 120PiB
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?: We created a smart contract for our allocator pathway, the Datacap Faucet, where allows clients to request datacap. Clients can easily get a small amount of datacap by simply entering their wallet address! Receiving datacap by using allocator --- Datacap Faucet set up based on a smart contract can provide a secure and convenient distributed storage experience for clients. a. Convenience Clients only need to submit their wallet address, select the amount they want to get, and pay a little amount of Fil as a service cost to successfully get datacap. b. Safe Utilize the security features of smart contracts to make all processes open and transparent. c. Innovation We were the first in Filecoin community to propose the creation of an automated datacap allocator pathway with optional pickup levels, and we are constantly developing new functions to support the growth of Filecoin!
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?: We perform a comprehensive due diligence process on our clients. We will prepare some questions to put on the client's application first. This is to collect basic information about the clients. Then we will verify the clients' identity information to ensure the authenticity of the client. After doing relevant background checks on the client, we will communicate with him about his storage needs and determine the size of datacap we can approve of them. All of our surveys will be done in complying with the laws and regulations of the client's location.
12. Please specify how many questions you’ll ask, and provide a brief overview of the questions.: I will prepare some questions to put on the client's application:
https://1drv.ms/w/s!Avlb5VQ8jLIugSYNxKDFplT4mL0y
Detail is in this link.
13. Will you use a 3rd-party Know your client (KYC) service?: We'll use a third party KYC service. We use local KYC ways based on the location of clients and use reputable third-party services to ensure client qualifications in order to fully and legally verify the client's identity, for example, Jumio https://www.jumio.com/products/authentication/ & Veriff https://www.veriff.com/
14. Can any client apply to your pathway, or will you be closed to only your own internal clients? (eg: bizdev or self-referral): Yes, any client can come to apply. We hope that our support for granting datacap to our clients will allow them to better experience the distributed storage functions offered by Filecoin.
15. How do you plan to track the rate at which DataCap is being distributed to your clients?: Our faucet calls the data on the chain via lotus, and provides real-time data analysis of clients' datacap to come up with the changes in the amount of datacap that the clients received.
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
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 collect information about our clients and use third-party services to verify their identity, such as Jumio https://www.jumio.com/products/authentication/ & Veriff https://www.veriff.com/ . We then confirm the source of the data with the client. Regarding public datasets, we will ask our clients to provide the proof of storing data and provide related information such as data size, data source, etc. and verify it. Regarding private datasets, we will ask our clients to provide proof of data attribution and provide relevant information such as data size and verify it.
19. How will you ensure the data meets local & regional legal requirements?: We collect the legal regulations of the client's country and consult with the legal team in a timely way to check and make a specific plan for the client's data type to ensure that data is under the local regulations.
20. What types of data preparation will you support or require?: We offer data preparation services and are willing to support and help our clients to transfer data to sp if they are not able to prepare the data themselves.
21. What tools or methodology will you use to sample and verify the data aligns with your pathway?: We will ask our clients to provide detailed information about the data and do a manual check to select the data that does not match our demands. We also use programs to check samples of client's data in terms of data format, data source and so on, to make sure that the client's data matches the their description and meets the rules we have set for our allocator. To prevent sector padding, we'll use our own automated program to download random samples of our clients' deal message, and automatically judge the size of the downloaded file as a way of preventing sector padding.
22. How many replicas will you require to meet programmatic requirements for distribution?: 5+
23. What geographic or regional distribution will you require?: We support our clients in storing data in as many locations as possible, at least in 4 regions, and ask them to store each copy in a different physical location. We prefer our clients to try not to work with SPs that use VPNs and want different SPs to use different 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?: We prefer that clients can allocate as evenly as possible to sp. Yes, we require a detailed distribution plan from the client. Before allocating datacap to a client, we send the client a form for collecting information. Then we ask the client to fill in the relevant information and provide kyb information of the SP. After confirming that the client has made a plan, we will consider allocating datacap. Link of template: https://1drv.ms/w/s!Avlb5VQ8jLIugTLEg1DnMox8zkKa?e=Cc39l2
26. What tooling will you use to verify client deal-making distribution?: We will check our clients' distribution from time to time after the first allocation. We utilize datacapstats.io or CID checker to generate reports to measure subsequent allocations to clients. If a problem is found with a client's distribution, we will let the client know to make adjustments.
27. How will clients meet SP distribution requirements?: We have programs that can automatically help our clients send data to SPs. Before transacting with an SP, we ask our clients to review the SP's information and upload it to our platform. After the SPs are approved by our system, our program manually or automatically allocates data to these reputable SPs according to the client's plan.
28. As an allocator, do you support clients that engage in deal-making with SPs utilizing a VPN?: We support our clients to make deals with SPs who're using VPN, even if we prefer clients choose SPs without VPN. We will require a KYB for SP using VPN, after confirming their actual identity, we will transfer the data to those SPs.
29. Will you use standardized DataCap allocations to clients?: Yes, standardized
30. Allocation Tranche Schedule to clients:: • First: lesser of 10% of total DataCap requested or 100% of weekly allocation rate • Second: lesser of 20% of total DataCap requested or 200% of weekly allocation rate • Third: lesser of 40% of total DataCap requested or 400% of weekly allocation rate • Fourth: lesser of 80% of total DataCap request or 800% of weekly allocation rate • Max per client overall: 5PiB
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?: For large amount application, we'll sign in https://filplus.fil.org/#/ and use ledger to allocate datacap. If clients wants to apply for a few amount of datacap, we'll use Datacap Faucet we developed. Automatically allocate datacap to the client after he submits his own wallet address and fee.
33. Describe the process for granting additional DataCap to previously verified clients.: Our process for granting additional datacap is also going to follow a standard process. We will demand that clients provide their new requests and check their past datacap usage through datacapstats.io tooling and/or the CID checker bot. If all data is good, then we will use the SA bot or our Faucet for the following allocation.
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; https://www.ehume.com • due diligence & investigation: Jumio https://www.jumio.com/products/authentication/ ; Veriff https://www.veriff.com/ • bookkeeping: Github; https://www.ehume.com • on-chain message construction: https://www.ehume.com; Ledger; https://filplus.fil.org/#/ • client deal-making behavior: https://DataCapstats.io tooling; AC Bot; CID Checker • tracking overall allocator health: Filfox; https://www.ehume.com • dispute discussion & resolution: Slack; Email • community updates & comms *: https://www.ehume.com; slack; Github
35. Will you use open-source tooling from the Fil+ team?: Yes. We will use open-source tooling such as https://DataCapstats.io, AC Bot, CID Checker and our own developed Datacap Faucet.
36. Where will you keep your records for bookkeeping? How will you maintain transparency in your allocation decisions?: Real-time updates to our allocation records are publicly stored on github and automatically updated on our website for public review. Clients' private information is recorded in our own database. We welcome community to review our allocations, and in a dispute we will provide some information privately after communicating with the client, especially to the Fil+ governance team for review.
37. Describe your proposed compliance check mechanisms for your own clients.: We'll use a database or a sheet to record each distribution. The record would include the client's name, amount of DataCap distributed, date of distribution, and other relevant details. Then we'll monitor how clients use the DataCap. Tools like CID Checker or Retrievability Bot can be utilized to check the actual process clients are storing data in and to ensure data is retrievable. Regular meetings will be scheduled with clients to discuss their DataCap usage and to address any issues or concerns. This also helps us to build trust and maintain a good relationship with clients. Also, it can help us to collect and analyze the latest data about the clients, such as their industry, size, location, etc.
38. Describe your process for handling disputes. Highlight response times, transparency, and accountability mechanisms.: First, we will response to internal dispute within 3 days, to external dispute within 5 days. We'll investigate all the disputes thoroughly, including review any relevant documentation, speak with the parties involved, and use any necessary tools or resources to understand the situation. Throughout the process, we'll keep informed about investigation. We'll give regular updates to relevant. Then we'll use github and email to public the resolution of dispute.
39. Detail how you will announce updates to tooling, pathway guidelines, parameters, and process alterations.: We'll document all updates first by ourselves. Then we'll announce the updates through some channels, such as slack, github and our website. Also, we'll inform our client and guide them to adapt the updates.
40. How long will you allow the community to provide feedback before implementing changes?: We welcome communities give feedback on the updates in a month via Slack: Ehume , so that we can make timely corrections to the updates. We'll create clear and transparent feedback processes to receive feedback. Then we will weigh the feedback by considering the volume, quality, and diversity of feedback, as well as the impact of potential changes on the community. Aim to make changes that are beneficial to Filecoin.
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'll use a secure on-chain notary address and we utilize a multisig to add an additional layer of security to the address. We grant signatory rights to trusted management team. We also implement monitor and encryption to the address, and aim to make privacy measures cores to allocator operation.
42. Will you deploy smart contracts for program or policy procedures? If so, how will you track and fund them?: Yes, we will deploy smart contracts - Datacap Faucet. https://1drv.ms/i/s!Avlb5VQ8jLIugTHdyNMaYqZ1X2mT?e=n9XOsT We will provide part of the funding for the development cost of the smart contract, and the maintenance cost of subsequent contract will be supported by the client's service fee for funding. The code of our smart contract will be uploaded to our github repository for management and for community members to view and use.
43. Outline your monetization models for the services you provide as a notary allocator pathway.: If the client uses our Datacap Faucet to request datacap, it only costs 1TiB/1Fil service fee and real-time gas fee. If the client does not have the ability to package the data, then we charge a fee to help the client with data preparation, which is 15U/TiB. In addition, we also charge our clients for the express fee and labor service fee for helping our clients send data to SPs, which depends on the amount of data of our clients.
44. Describe your organization's structure, such as the legal entity and other business & market ventures.: Yuga Club is a DAO organization initiated and co-founded by a group of enthusiastic members from the Filecoin community in 2021. Till now we have about 30 employees in Shanghai office. Among us are experienced community OGs, clients from the traditional IT industry, and startup gurus from the FIL ecosystem. Moreover, there are also many DPs and notaries who have joined successively. We've been dedicated to building and optimizing industry-leading order encapsulation components for three years, enabling rapid processing and encapsulation of real data, and continuously empowering storage providers and data content providers.
45. Where will accounting for fees be maintained?: We will look for a professional audit team to be responsible for accounting for fees. Transaction records are first made, recording every transaction generated in allocator and publicly posted on github. Next, all transactions will be audited on an annual basis, and generate audit reports. We will provide reports when the governance team needs to review them, and provide transparency and ease of audit for all monetization processes to ensure that all financial information is accurate and complies with laws and regulations.
46. If you've received DataCap allocation privileges before, please link to prior notary applications.: I've not received DataCap allocation privileges before, but I've run for Round 4 Notary in 2022. https://github.com/Filecoin-project/notary-governance/issues/731
47. How are you connected to the Filecoin ecosystem? Describe your (or your organization's) Filecoin relationships, investments, or ownership.: FIL+ project has a significant role in the path of evolution from public chain to storage public chain, we fervently hope that more participants can join it faster, use it easier, and promote it quicker. Ehume.com platform is the first SAAS-like service we have launched for Fil+. We hope to help filter higher quality compliant storage providers through Yuga's advanced tools to help Filecoin network run more stably and securely in the future. Moreover, we've created a smart contract for Allocator to help make Fil+ more accessible to more clients. Moving forward, Yuga Club will continue to integrate more and better tools to contribute to the community and prosper the ecology growth. Ehume.com: https://user-images.githubusercontent.com/107671030/202396189-6019fffe-5b5e-4847-9ea5-c2f04d4e0540.png https://user-images.githubusercontent.com/107671030/202396204-b59c529d-79f9-447e-8949-f9cfdaaaa89d.png DataCap Faucet: https://1drv.ms/i/s!Avlb5VQ8jLIugTHdyNMaYqZ1X2mT?e=n9XOsT
48. How are you estimating your client demand and pathway usage? Do you have existing clients and an onboarding funnel?: Since the creation of the site, Ehume.com has accumulated millions of clicks. We had been in touch with a large amount of community participants and notaries who wanted to work together to build up Filecoin ecosystem. We will actively contact potential clients among the current users of the website and develop more clien through online or on-site visits. And by counting the amount of expected client demand, the technology is updated in a timely way to support the client's experience. Clients can also reach out to us for assistance through our website, Ehume.com. We hope to invite clients to participate in the filcoin community through the convenience of the tools we have created, and would like to bring more clients the initial datacap experience through the low threshold character of the datacap faucet. Furthermore, through our rich experience in blockchain participation and experience in building Filecoin, we are willing to motivate our clients to participate and develop more clients to promote the ecological construction of Filecoin.
galen-mcandrew
commented
3 months ago f02871322
Datacap Allocated
5PiB
galen-mcandrew
commented
3 months ago @Ehume The provided address is not initialized on-chain and therefore cannot receive DataCap from RKH. You need to receive some FIL and send a message so that the address has a created-time https://filfox.info/en/address/f1gjfz3qnbqjcdal6geo5vemmdqvseaia2l6kwj7i
Ehume
commented
3 months ago @galen-mcandrew Hello Galen, we've initialized this f1 address f1gjfz3qnbqjcdal6geo5vemmdqvseaia2l6kwj7i. Cause we have a smart contracts with f4 address for our pathway, can you please help change this f1 address into f4 address f410fvwp5dwsfcicqhmpspdoloo43xzvzpyelhqelg2y? So that we can use f4 address to receive DataCap. Thank you!
filplus-bot
commented
3 months ago bafy2bzacedtn6qkh7s5d67p6dzkbxzephlyyhd2yeaxrkwcrhixrrh35pgfi2
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.