-
Notifications
You must be signed in to change notification settings - Fork 0
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
Test 17 #17
Comments
Pathway Name: Pluskit Organization: Wellhealth International Limited. Allocator's On-chain addresss: f1tgnlhtcmhwipfm7thsftxhn5k52velyjlazpvka Country of Operation: HK, GCN Region(s) of operation: Asia minus GCR,Greater China Type of allocator: Manual Amount of DataCap Requested for allocator for 12 months: 200PiB Is your allocator providing a unique, new, or diverse pathway to DataCap? How does this allocator differentiate itself from other applicants, new or existing? 1.We will manually make a plan for the distribution pathway and distinguish the subjects who have applied and those who have not applied, so as to avoid duplication of work as much as possible to improve work efficiency. 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. Acknowledgment: Acknowledge Cient Diligence Section: This section pertains to client diligence processes. Who are your target clients? Individuals learning about Filecoin,Small-scale developers or data owners,Enterprise Data Clients,Other (specified above) Describe in as much detail as possible how you will perform due diligence on clients. We prepare to do as follows:
Please specify how many questions you'll ask, and provide a brief overview of the questions. We plan to ask the following questions: Will you use a 3rd-party "Know your client" (KYC) service? We recognize and will use official tools such as Toggle, uqudo, linkdin, twitter, facebook and medium to verify clients. That includes the certification and operation of the business, the employment history of the individual, and checking updates through website, social media and portal website to determine whether the business is still functioning. Can any client apply to your pathway, or will you be closed to only your own internal clients? (eg: bizdev or self-referral) No. We will open applications to users in all fields. How do you plan to track the rate at which DataCap is being distributed to your clients? We will clarify the client's usage speed in advance and ask the client to remind us when he has completed 50% of datacap allocated. We will check how much the client has used before each datacap request, and maintain at least once a week to verify the client's datacap usage, and provide guidance and help. Data Diligence This section will cover the types of data that you expect to notarize. As a reminder: The Filecoin Plus program defines quality data is all content that meets local regulatory requirements AND 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, transmitting, or accessing of data. Acknowledgement: Acknowledge What type(s) of data would be applicable for your pathway? Public Open Dataset (Research/Non-Profit),Private Commercial/Enterprise,Public Open Commercial/Enterprise,Private Non-Profit/Social Impact 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 verify their ownership by verifying the authenticity of the client's subject and the correspondence between the data and the client. The general process is as follows. How will you ensure the data meets local & regional legal requirements? First of all,we have mastered the basic data related laws due to longtime working as Notary. We will do the following things to ensure the data meets legal requirements. 1.Ask for commitment.We'll ask clients to make commitment to state their data has met the local legal requirements. 2.Make punishment rules. Once the date is found not meet the requirement, we will not accept their application for a certain time and all the unused DataCap will be taken back. We will also disclose it in the community. What types of data preparation will you support or require? We will ask clients to package the data into categories and give a brief description for each package. We support various preparation methods, such as Singularity, Lotus and so on. What tools or methodology will you use to sample and verify the data aligns with your pathway? We'll start by telling clients on Github and Slack that they can't make sector-size subse. We will randomly check the stored data. 2 pieces of data are sampled for each PiB of data to confirm whether the data is abused. Data Distribution This section covers deal-making and data distribution. As a reminder, the Filecoin Plus program currently defines distributed onboarding as multiple physical locations AND multiple storage provider entities to serve client requirements. Recommended Minimum: 3 locations, 4 to 5 storage providers, 5 copies How many replicas will you require to meet programmatic requirements for distribution? 3+ What geographic or regional distribution will you require? Each batch of data requires at least 3 different provinces or countries. We will not require (or exclude) certain geopolitical regions. How many Storage Provider owner/operators will you require to meet programmatic requirements for distribution? 4+ 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 will require each client that each batch of their data to be stored at least 4 SPs, with no more than 30% of the quantity stored on each SP. At the application stage, we'll ask for a public description of the plan on Github and document it by using a form. Before the subsequent application, we will check whether the actual distribution ratio is roughly in line with their plan. What tooling will you use to verify client deal-making distribution? We will use the existing CID checker bot and datacapstats.io to assist us in verification. At the same time, we will use the browsers to make further confirmation. Filfox:https://filfox.info/en/deal Glif:https://explorer.glif.io/ Filscan:https://filscan.io/tipset/dsn/ FilecoinPLUS:https://datacapstats.io/clients Filecoin tools:https://filecoin.tools/ Filedrive:https://filplus.info/ How will clients meet SP distribution requirements? We will ask clients to clarify the SP plan and specific distribution on Github in advance, and use tools such as Bot to check whether the number of SPs meets the requirement of at least 4 SP after storage. As an allocator, do you support clients that engage in deal-making with SPs utilizing a VPN? We do not support VPNs. We will ask clients to provide the address proof of the selected SPs, and at the same time through the software, such as Filecoin Green, Filstats.io, to query the address. In addition, if a client is reported to be using a VPN, we will reject his/HER subsequent applications. DataCap Allocation Strategy In this section, you will explain your client DataCap allocation strategy. Keep in mind the program principle over Limited Trust Over Time. Parties, such as clients, start with a limited amount of trust and power. Will you use standardized DataCap allocations to clients? No, client specific Allocation Tranche Schedule to clients: For general applications, we will allocate their required amount on a certain ratio basis. But no more than our maximum. Will you use programmatic or software based allocations? Yes, standardized and software based What tooling will you use to construct messages and send allocations to clients? Describe the process for granting additional DataCap to previously verified clients. We will use certain criteria for subsequent allocation. The specific process are as follows: 1. We will define the threshold for reapplication, that is, the amount of remaining datacap/the amount of datacap used in the last week < 0.5, and check whether the client's datacap allocated by us does not exceed 20% of our own total datacap. If these two conditions are met, the client can apply again. We will carry out the following investigation. If not, we will not continue to check and allocate. 2. Based on the results of SA bot, https://datacapstats.io/, etc. We will check the actual usage of the datacap obtained before. The application will be rejected if the following circumstances occur. a. At least 3 different provinces or countries do not exist b. Do not stored on at least four SPs c. The datacap storage of single SP storage exceed 30% d. The stored data does not support retrieval e. The stored data retrieved by sampling is not valid data 3. If there is no problem in the above two steps, we will conduct the next allocation according to the standard. Tooling & Bookkeeping This program relies on many software tools in order to function. The Filecoin Foundation and PL have invested in many different elements of this end-to-end process, and will continue to make those tools open-sourced. Our goal is to increase adoption, and we will balance customization with efficiency. This section will cover the various UX/UI tools for your pathway. You should think high-level (GitHub repo architecture) as well as tactical (specific bots and API endoints). Describe in as much detail as possible the tools used for: • client discoverability & applications Will you use open-source tooling from the Fil+ team? Yes. 1.API integration tools https://documenter.getpostman.com/view/131998/Tzsim4NU#98fe18ca-b15a-4753-986f-91882fd87a12 2. Notary allocation inquiry a.https://datacapstats.io/notaries b.https://filplus.info/ 3. Data retrieval ratio https://retrievalbot-dashboard.vercel.app 4.SP Dispersed location query SA Bot 5. Query the SP allocation https://datacapstats.io/clients/X/breakdown 6. Datacap usage records a.https://filecoin.tools/ b.https://datacapstats.io/clients Where will you keep your records for bookkeeping? How will you maintain transparency in your allocation decisions? All allocation decisions will be recorded in form and kept/updated both on Google&Shimo. and locally. The information will be publicly available on Github. What will your DataCap distribution look like? Our DataCap distribution details are detailed in 22-28. Risk Mitigation, Auditing, Compliance This framework ensures the responsible allocation of DataCap by conducting regular audits, enforcing strict compliance checks, and requiring allocators to maintain transparency and engage with the community. This approach safeguards the ecosystem, deters misuse, and upholds the commitment to a fair and accountable storage marketplace. In addition to setting their own rules, each notary allocator will be responsible for managing compliance within their own pathway. You will need to audit your own clients, manage interventions (such as removing DataCap from clients and keeping records), and respond to disputes. Describe your proposed compliance check mechanisms for your own clients.
Describe your process for handling disputes. Highlight response times, transparency, and accountability mechanisms. First of all, we will avoid disputes as much as possible by setting clear standards and following up datacap usage throughout the process.
Detail how you will announce updates to tooling, pathway guidelines, parameters, and process alterations. We will update some information and tools within community norms, but not too often, no more than twice a year. When it comes to updates, we will explain the update point on Github and Slack. In the meantime, we will notify PL and existing clients via Github, Slack and email. How long will you allow the community to provide feedback before implementing changes? Before changing, we will publicly state the proposed update point and estimated effective time on github and slack. 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 use ledger to manage our on-chain wallet addresses and keep the ledger in a place where only we can get it and sign applications with the Ledger. And, we will use ledger to operate on a specific network. Will you deploy smart contracts for program or policy procedures? If so, how will you track and fund them? No, we won't use smart contracts at this stage. Further consideration will be given in the future based on the development situation and the specification of the rules of Filecoin Plus. Monetization While the Filecoin Foundation and PL will continue to make investments into developing the program and open-sourcing tools, we are also striving to expand and encourage high levels of service and professionalism through these new Notary Allocator pathways. These pathways require increasingly complex tooling and auditing platforms, and we understand that Notaries (and the teams and organizations responsible) are making investments into building effective systems. It is reasonable for teams building services in this marketplace to include monetization structures. Our primary guiding principles in this regard are transparency and equity. We require these monetization pathways to be clear, consistent, and auditable. Outline your monetization models for the services you provide as a notary allocator pathway. In the present stage, we think it is the initial stage of profit exploration, so allocator should not set up too many charges. Describe your organization's structure, such as the legal entity and other business & market ventures. The name of organization: Wellhealth International Limited. The legal entity: Bo Shen Location: suite 603,6/f laws comm plaza 788 cheung sha wan road,kowloon,hong kong Registration date: Aug.18.2017 Wellhealth International Limited. is currently actively exploring the Filecoin and support the further development and operation of Pluskit. Where will accounting for fees be maintained? If expense accounting is involved, we will use a special address for unified income and expenditure. Income and expenditure are presented on the chain. We will use offline forms to record and make them available to the public when necessary. This address is not clear at the moment and will be clear before Jan. 20. If you've received DataCap allocation privileges before, please link to prior notary applications. The GitHub URL of our previous notary applications: filecoin-project/notary-governance#448 filecoin-project/notary-governance#694 How are you connected to the Filecoin ecosystem? Describe your (or your organization's) Filecoin relationships, investments, or ownership. As an independent team, we joined Filecoin as developers and started to develop a statistical tool, pluskit.io, to make it easier for the community to query DataCap distribution data more efficiently. Pluskit team was founded in June 2021, and the product was officially launched in October 2021. In December 2021, Pluskit team was invited to participate in the Notary Governance Call to present a project showcase, which won a large number of likes from community members; In January 2022, Pluskit received Next Step Microgrant; In February 2022, Pluskit was included in the Filecoin Community Roadmap. In March 2022, Pluskit was elected as Notary in the 3rd round of Notary Elections. During the tenure, we actively performed the duties as a notary: a. Attended almost every Governance calls. b. Timely process applications. We received four general applications with an average processing time of 1 day and we dealt LDN for more than 60 times. c. Actively participate in community discussions and express our own views, such as E-Fil+, project Beacon, issue of the third round of notary signing etc. d. Join E-Fli+ group and attend the meetings. In addition, in 2021 and 2022 we are notary of Filecoin Plus and deeply involved in the notary work. How are you estimating your client demand and pathway usage? Do you have existing clients and an onboarding funnel? We will initially assess the actual demand of clients according to their industry, business type and data type. As for the client's pathway usage, we will require it to be publicly posted on Github, and further confirm the actual usage of the allocated datacap through query tools (such as https://filecoin.tools/, https://filplus.info/, etc.). Because I've approved a number of applications as a notary, we have some existing public clients. W usually get clients' applications through Email, Github and Slack. |
No description provided.
The text was updated successfully, but these errors were encountered: