Closed joshua-ne closed 1 year ago
@Kevin-FF-USA Hi, just want to make sure this application is not missed and is good for evaluation(since I notice you have self-assigned all other applications but missed this one)
Thanks for the tag @junyaoren - Confirming receipt and will be scoring this week and next. Will ping back to this issue if we need anything additional, but application is received!
@galen-mcandrew @Kevin-FF-USA Thanks for your efforts on scoring our application! In response to your questions, we would like to add some follow-ups and supplementations. We hope you can take a look, re-evaluate our application and hopefully update our score. Thank you.
Contribution after 2020 ● We built collaboration with Nanyang goverment. (2020.7) https://mp.weixin.qq.com/s/YrNz8Wl5ZY63Ei_9-CAJ_g ● We accepted the inspection of Quanzhou Digital Office and signed a strategic cooperation document. (2020.8) https://mp.weixin.qq.com/s/2rO3uI_1ykneeitU1iKQNQ ● We were invited to participate in the China Yayun Big Data Industry Investment Promotion Conference. (2020.9) https://mp.weixin.qq.com/s/rIGnZ8--WAq58X-Tse_nbA ● We participated in the first International Blockchain Industry Expo to showcase the Filecoin ecosystem to the audience. (2020.10) https://mp.weixin.qq.com/s/oAIkxOMiYJmtlunaARBzHw ● We participated in the Web3.0 China Summit and took the stage to share the development of the Filecoin ecosystem. (2020.11) https://baijiahao.baidu.com/s?id=1683512426114952502 ● Won the honor of "2020 Most Valuable Mining Institution in the Industry". (2021.1) https://zhuanlan.zhihu.com/p/347341529 ● We accept an exclusive interview about how Filecoin can help the construction of New Infrastructure Project. (2021.12) https://www.ys137.com/jinrong/21307831.html ● Video: How Filecoin, IPFS achieve credible storage. (2021.10) https://www.youtube.com/watch?v=4na0yD2-SQw ● We actively participated in the Filecoin testnets (SpaceRaces) and we were in the 1st tier group on the ranking list. At the end of testnet, we carried about 50PiB of storage power to Filecoin mainnet. ● During Filecoin testnet and mainnet, we have made tons of trials and optimizations on Filecoin sealing architecture (such as separating precommit1/2 from commit/2, saving commit/1 output for later use so that cache can be released early, distributive management of sector numbers, etc.). And we have shared most of our optimizations in the community. ● We have held 6 offline meetings (from Dec, 2021 to Feb, 2022) to train new and less-experienced storage providers so that they could quickly onboard on Filecoin mining. ● Since the end of Filecoin testnets, we have established extensive collaboration with Qiniu to optimize the distributive storage system for Filecoin sectors, including fast retrieval of PoSt data, smarter sector transferring logic, etc. Now Qiniu's filesystem, Kodo system, is supporting the storage of more than 8 EiB of Filecoin storage power.
Audit/Dispute Details From our DataCap allocation strategy, I believe you already have an idea about our thinking and efforts to fulfill the notary work. Based on our understanding of the Filecoin ecosystem, we have designed a highly original and perfect system to ensure that all matters are completed openly, fairly and justly. In terms of audit/dispute resolution, we have also set up a rigorous system and process, and the whole process follows the principles and standards described in the Allocation Strategy. It will also rely on the applicant information collected during the Client Due Diligence process and the record information retained by the Bookkeeping Plan. At the same time, our team has also established a "Notary Performance Working Group" composed of 4 people, and I will lead the team to complete the relevant work as the leader of the group. I will show the details below.
Audit/Dispute In our management of DataCap, Audits fall into two categories: our audits of applicants' qualifications and their applications for DataCap, and audits from the Filecoin community to our assignments. Disputes are also divided into two categories: the handling of applicants' objections to our scores and DataCap assignments, and the handling of disputes in which applicants submit their objections to us to the community. We will elaborate them one by one:
Our audit of applicant qualifications and their application for DataCap -Our audits of clients will be conducted in strict accordance with our rules (see Allocation Strategy below); -If the applicant makes a reasonable suggestion to improve our rules, we will adopt the suggestion and publish and adopt the new DataCap management method in time after this DataCap allocation; -We will focus on reviewing the applicant's interests; -For the address provided by the applicant that has been used for DataCap management, we will use the script to collect the past deal information from the chain and analyze whether there is a centralized transaction with a single SP entity; -If we find that a applicant has improperly used DataCap, we will report it to Notary's governing body, seek the assistance of the governing body to make a correct judgment, discuss whether to cancel its DataCap, and alert other Notaries to the applicant; -We will also analyze the applicant's DataCap usage cycle and discuss with them regularly to help them develop a more scientific and reasonable DataCap usage plan. Audit of community objections to our distribution -When this objection arises, we will apply to the Notary Governance Body for an audit; -We will request the Notary Governance Body to appoint an auditor to direct our audit; -Our audit application form contains the following contents: the objector, the description of the objection, the description of the infringement of interests, the statement of the objector, the evidence information of the objector and our evidence information; -When necessary, we will initiate an open online arbitration meeting so that the community can understand the real process and outcome of the incident. Handling of applicant objections to our ratings and DataCap allocation -We will display the contact details of the Notary governance body on the page of the DataCap allocation rules to ensure that the applicant has the right to request arbitration; -We will demonstrate the process of dispute resolution. Once the applicant raises an objection, we will first negotiate with the applicant. If the applicant is strongly dissatisfied with the result, the dispute will be submitted to Notary Governance for arbitration; -Except for a small number of data that must be kept private, the whole communication of dispute settlement is presented in the form of issues on Github to ensure that the whole process is open and transparent; -We will use the data collected and retained by the Client Due Diligence and Bookkeeping Plan described below in the dispute resolution process.
Allocation Strategy (This part of the content remains unchanged)
Client Due Diligence How will you vet the clients that are applying for DataCap? What questions will you ask to ensure your trust is placed well and that clients can properly handle the DataCap you intend to allocate to them? We collect the following information to determine eligibility:
What processes will you employ when granting additional DataCap to a client that has previously been verified? This includes confirming that the client is not improperly using the DataCap they were previously granted, i.e., making deals with a single SP entity. We will set up a dedicated database to record all the storage deals initiated from the application address, and regularly analyze and summarize the collected data to ensure that the applicant uses DataCap fairly and impartially. Verified applicants are also required to provide us with the following information:
We will compare the information submitted by the applicant with the verified data deal on the chain to evaluate whether to continue to grant the applicant DataCap and the amount granted.
Bookkeeping Plan Do you plan on conducting all your allocation decisions in public (e.g. Github repo), private (e.g. over email, Telegram, etc), or both? Of course, we will retain all the information and accept the relevant audit. All DataCap-managed information is managed hierarchically.
Where do you plan on keeping a publicly accessible record of all your allocation decisions? Github, Google Sheet. Github, as an open and trusted platform, will be the main platform for us to perform Notary's work, as well as the main platform for information display. You can query the application and approval process of all DataCaps, as well as the handling process of objections and disputes. We will also publish our DataCap allocations on a regular basis. Google Sheet will serve as a tabular tool for recording relevant information and will be made public on Github.
Notary Performance Working Group Team Leader: Junyao Ren Team members: Jerry Wu, Alfred Zhou, Molly Wang Responsibilities: Junyao Ren -To be responsible for the formulation of management measures; -Responsible for the distribution and management of the work of the entire team; -Take charge of the Notary private key and perform the DataCap allocation; -Responsible for final decisions on applicant audits, DataCap allocations. Jerry Wu -Responsible for tracking changes in the format of information on the chain that validates data transactions; -When the main network upgrade and other factors lead to changes in the format of relevant rules and information on the chain, the changes should be synchronized to the team members in time to improve the monitoring system. Alfred Zhou -Responsible for maintaining the applicant's DataCap application portal (Github, website, etc.); -Responsible for publishing and updating our DataCap application system and application results; -Responsible for collecting the DataCap application form, audit request form and other information submitted by the applicant. Molly Wang -Responsible for the establishment of an on-chain information detection system; -responsible for establishing a database and importing the monitored information into the database in real time; -Be responsible for establishing a prediction mechanism to initiate an early warning when the applicant's behavior of using DataCap is suspected to be deviated; -Be responsible for writing the scripts required for the above work.
While I spend only 3 to 5 hours per week on Notary management, the entire team will spend more than 15 hours per week on DataCap management.
Hi @junyaoren based on this Notary election cycle's final scoring, you/your organization has qualified to be a Fil+ Notary! You will be receiving your final scored rubric soon, along with the total allocation of Datacap based on rubric scoring.
In order to confirm your participation as a Notary in the Fil+ ecosystem, please respond to the following:
Please confirm that the region of operation for client applications you will focus on is Greater China.
Please confirm each of the following items below (you can do this by quoting each of the following bullets and adding a line under each section agreeing that you'll abide by these operational principles).
• Upfront Disclosures: Prior to being confirmed as a Notary, Notaries are expected to disclose all relevant addresses which they control, have a financial stake in, or are strongly connected to by other means. For the disclosure, the Notary should state the relevant addresses and the nature of the relationship .
• Promoting Client Best Practices: Notaries agree to educate approved clients about the best practices for using their DataCap (e.g. how to request additional services from miners, storing data redundantly across many miners, etc). Some reference information can be found here.
• Commitment to efficiently serving the Network: Notaries agree to serve as fiduciaries of the Network, striving to work towards bringing useful data onto Filecoin and improving the experience for clients to do so. Notaries should generally be able to respond to Client applications and updates within 3 days, and should be comfortable communicating with Clients and Notaries if an application needs to be redirected.
• No Self Dealing: To prevent conflicts of interest, Notaries should not allocate DataCap to Clients over which they control the private keys, or to a Client who intends to specifically spend the allocated DataCap with an address affiliated with the Notary. When in doubt, Notaries should bias towards transparency (i.e. public disclosure) or to getting a different Notary to handle the individual request.
• Operating in Good Faith: Notaries hold a position of trust in the network, and as such it is expected that they operate keeping the Principles of this mechanism in mind. While each form of abuse cannot be exhaustively defined, Notaries are expected to bias towards caution and act in a way that promotes transparency. Notaries should expect to potentially receive requests or questions for allocation decisions (within reason) - and should make decisions with this in mind.
• Community Governance Participation: It is expected that you will participate in the program 3-5 hours a week. Along with data allocation, participation in Github issues and Slack conversations, Notaries are to make an effort to regularly attend the scheduled Governance calls. As these calls are a forum to shape this process, it is important to ensure Notaries are present to provide their context, with discussions and input.
Please list any addresses you are affiliated with, and state the nature of the relationship. Please refer to the first bullet point in (2) for the definition of "affiliated", and bias towards transparency when in doubt.
Please affirm that you will abide by the allocation / client due diligence plan you laid out above.
(If ready) Please confirm the address that should receive DataCap. This is the address which you will use to sign messages on-chain to verify clients (through using a Ledger and the Fil+ Registry App). If you have an active (non-zero) DataCap grant from a previous election cycle, please provide a different address here. • If you do not have a ledger already, we recommend ordering directly from the Manufacturer for the Nano S or Nano X (link: https://shop.ledger.com/pages/ledger-nano-x)
Please confirm that the region of operation for client applications you will focus on is Greater China. - Confirmed
Please confirm each of the following items below (you can do this by quoting each of the following bullets and adding a line under each section agreeing that you'll abide by these operational principles).
• Upfront Disclosures: Prior to being confirmed as a Notary, Notaries are expected to disclose all relevant addresses which they control, have a financial stake in, or are strongly connected to by other means. For the disclosure, the Notary should state the relevant addresses and the nature of the relationship . - Confirmed
• Promoting Client Best Practices: Notaries agree to educate approved clients about the best practices for using their DataCap (e.g. how to request additional services from miners, storing data redundantly across many miners, etc). Some reference information can be found here. - Confirmed
• Commitment to efficiently serving the Network: Notaries agree to serve as fiduciaries of the Network, striving to work towards bringing useful data onto Filecoin and improving the experience for clients to do so. Notaries should generally be able to respond to Client applications and updates within 3 days, and should be comfortable communicating with Clients and Notaries if an application needs to be redirected. - Confirmed
• No Self Dealing: To prevent conflicts of interest, Notaries should not allocate DataCap to Clients over which they control the private keys, or to a Client who intends to specifically spend the allocated DataCap with an address affiliated with the Notary. When in doubt, Notaries should bias towards transparency (i.e. public disclosure) or to getting a different Notary to handle the individual request. - Confirmed
• Operating in Good Faith: Notaries hold a position of trust in the network, and as such it is expected that they operate keeping the Principles of this mechanism in mind. While each form of abuse cannot be exhaustively defined, Notaries are expected to bias towards caution and act in a way that promotes transparency. Notaries should expect to potentially receive requests or questions for allocation decisions (within reason) - and should make decisions with this in mind. - Confirmed
• Community Governance Participation: It is expected that you will participate in the program 3-5 hours a week. Along with data allocation, participation in Github issues and Slack conversations, Notaries are to make an effort to regularly attend the scheduled Governance calls. As these calls are a forum to shape this process, it is important to ensure Notaries are present to provide their context, with discussions and input. - Confirmed
Please list any addresses you are affiliated with, and state the nature of the relationship. Please refer to the first bullet point in (2) for the definition of "affiliated", and bias towards transparency when in doubt. - Owned addreesses: f0133509, f01111111, f020331, f019074, f010056, f0107916, f01111110, f021525, f01111112
Please affirm that you will abide by the allocation / client due diligence plan you laid out above. - We will abide by the allocation / client due diligence plan we laid out above
(If ready) Please confirm the address that should receive DataCap. This is the address which you will use to sign messages on-chain to verify clients (through using a Ledger and the Fil+ Registry App). If you have an active (non-zero) DataCap grant from a previous election cycle, please provide a different address here. • If you do not have a ledger already, we recommend ordering directly from the Manufacturer for the Nano S or Nano X (link: https://shop.ledger.com/pages/ledger-nano-x) - f1y5rllqjmhqj6ppz64ixl42pqe7hua3nzjbd5bpy
@junyaoren
Please fill out this form to move forwards with the ratification process: https://airtable.com/shrs55Lzbm1wJTIRw
@galen-mcandrew We have submitted the form.
@junyaoren Please confirm your ledger address using the verification tool in the Fil+ Registry app.
Here is a troubleshooting guide.
Thanks!
Hi Galen,
The nano X we ordered came all the way from Paris to Shenzhen but was held by customs clearance authorities. DHL had to return the parcel to Ledger. This might be a new policy from the Chinese customer. So I wonder if there are or will there be any workarounds for such an issue?
Thanks, Junyao
On Sat, May 21, 2022 at 3:12 AM Galen @.***> wrote:
@junyaoren https://github.com/junyaoren Please confirm your ledger address using the verification tool in the Fil+ Registry app https://plus.fil.org/.
Here https://docs.google.com/document/d/1VCksV4_roLSTmaPqZJ8u643rykC0A7Z53YBDUoIY1xc/edit?usp=sharing is a troubleshooting guide.
Thanks!
— Reply to this email directly, view it on GitHub https://github.com/filecoin-project/notary-governance/issues/445#issuecomment-1133229268, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACZUDJBN2SF66DCXBTDDVSLVK7P2ZANCNFSM5PZ7ET2Q . You are receiving this because you were mentioned.Message ID: @.***>
Thanks for your request! :exclamation: We have found some problems in the information provided. We could not find the Datacap requested in the information provided
Please, take a look at the request and edit the body of the issue providing all the required information.
@junyaoren Sorry to hear about the hurdle getting your ledger! At this time, our registry app uses that physical device for signing in and approving messages. We hope to build more supports in the future, but those are not yet in scope.
To my knowledge, there is not a way to 'import' another existing address (for example, one created using Lotus) onto a Ledger device. So, if you do not have your Ledger yet, then I think we should wait to award the DataCap to another address, since we would then have to adjust everything and remove that DataCap to transfer to a new notary ledger address.
In the meantime, you can still help us investigate and audit clients, such as large datasets. You can also join our governance calls and engage in the different community discussions!
@junyaoren Any update on getting a ledger device and setting up a wallet address that way?
Hi Galen, thanks for asking! My colleague in Singapore has received the ledger device, and I am trying to guide him to set up an address. Will get back to you as soon as he gets back to me.
On Wed, Jul 27, 2022 at 6:12 AM Galen @.***> wrote:
@junyaoren https://github.com/junyaoren Any update on getting a ledger device and setting up a wallet address that way?
— Reply to this email directly, view it on GitHub https://github.com/filecoin-project/notary-governance/issues/445#issuecomment-1196032907, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACZUDJBLTDVWCKAV2IID723VWBPFRANCNFSM5PZ7ET2Q . You are receiving this because you were mentioned.Message ID: @.***>
Hey @junyaoren,
Just wanted to bump on this again, did your colleague in Singapore manage to set up a wallet address with your ledger?
Hey, thanks for asking. We apologize for having so much trouble getting the ledger. Our colleague in Singapore could not figure out how to set up an address with the ledger.
The good news is that one of my other colleagues has been able to take the ledger back to China after visiting Singapore for the FIL- Singapore meetings, though he is currently in quarantine because he unfortunately got COVID-19 during the meeting. So I think we are really close to getting the ledger and setting up an address, as soon as the quarantine time is over. I'll let you know immediately when I do so. Thank you very much for your support!
Best, Junyao
On Fri, Oct 7, 2022 at 7:21 AM panges2 @.***> wrote:
Hey @junyaoren https://github.com/junyaoren,
Just wanted to bump on this again, did your colleague in Singapore manage to set up a wallet address with your ledger?
— Reply to this email directly, view it on GitHub https://github.com/filecoin-project/notary-governance/issues/445#issuecomment-1270835802, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACZUDJE5HHZGJXZQTZVI7O3WB5NJLANCNFSM5PZ7ET2Q . You are receiving this because you were mentioned.Message ID: @.***>
Hey, we have finally got our ledger and set up a new notary address on it: f1xzff5xup63o5sygr2swp4zvcajg54lotliimdty. I have updated the address on the GitHub issue as well. Could you help us proceed with the following steps? Many thanks! @panges2 @Kevin-FF-USA
Notary Application
To apply to be a Fil+ Notary, please review the Notary Overview here and then fill out the following form.
Core Information
Please respond to the questions below in paragraph form, replacing the text saying "Please answer here". Include as much detail as you can in your answer!
Long Term Network Alignment
Time Commitment
Describe the nature and duration of your affiliation with the Filecoin project. Please include relevant Github handles, miner ids, significant projects, or contributions (with links).
Stake Exposure
Please cite the total token at stake (currently available, locked as collateral, vesting over time) and any substantiating evidence.
Industry Reputation
In-protocol Reputation
Please describe (in detail) your activity and tenure as a member of the Filecoin community. Please note (with links where possible) any contributions made to implementations of Filecoin, the spec, documentation, or to substantially help the Filecoin ecosystem grow.
In-protocol Security
Please describe your contributions to the security of Filecoin and the duration over which you've made contributions. Please also include any links or references that can substantiate your contributions.
Organizational Reputation
Please describe the nature of your organization, including the country of registration, size of the organization, and time since inception.
Please share any relevant details to help substantiate information about your organization (website, named officers, links to social media profiles).
Please share any relevant external information regarding your organization (e.g. news articles, social media profiles, etc.)
Individual Reputation
Please share links to at least 2 of your (personal) social media profiles (or accounts that you are able to use) and the approximate size of your audience (i.e., followers, subscribers) for each one.
Diversity and Decentralization
Use Case Diversity
(Optional) Any additional information you'd like to share about the use case(s) you plan to support?
Allocation Plan
Concreteness of Allocation Plan
Allocation Strategy
How do you plan on allocating the DataCap requested above? Please describe your allocation strategy with as much specificity as you can. This includes the target amount per client and the rate at which you'll allocate DataCap.
How do you plan on securing the DataCap to ensure your organization (and its delegated members) are the ones allocating the DataCap?
Client Due Diligence
How will you vet the clients that are applying for DataCap? What questions will you ask to ensure your trust is placed well and that clients can properly handle the DataCap you intend to allocate to them?
What processes will you employ when granting additional DataCap to a client that has previously been verified? This includes confirming that the client is not improperly using the DataCap they were previously granted, i.e., making deals with a single SP entity.
Bookkeeping Plan
Do you plan on conducting all your allocation decisions in public (e.g. Github repo), private (e.g. over email, Telegram, etc), or both?
Where do you plan on keeping a publicly accessible record of all your allocation decisions?
Service Level Agreement
Engagement in Program
How much time per week, on average, are you willing to dedicate to participating in the Fil+ program? This includes making DataCap allocations (direct and/or Large Datasets), comments on discussion/issues, attendance in governance calls, messages in Slack, etc.
Track Record
Past allocation
Have you previously received DataCap to allocate before? If so, please link to any previous applications.
Cumulatively, how much DataCap have you previously successfully allocated?