search

filecoin-project / notary-governance

114 stars 58 forks source link

Notary Application: YuanHe Tech (Firefly） #714

Closed fireflyHZ closed 1 year ago

fireflyHZ commented 1 year ago

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 network. Please include relevant GitHub handles, Storage Provider IDs, significant projects or contributions (with links).

At the end of 2016, I saw great value and potential of IPFS protocol from hundreds of blockchain projects and believed it to be the only project that could be implemented in business scenarios since the appearance of blockchain technology. After careful study of the Filecoin white paper, Thereafter, I have kept a very close attention to this project during 2018 and finally decided to work with some partners to create a company specialized in Filecoin project named Firefly. As an organization, Firefly was founded in 2018 with an aim to build a more secured, efficient and liberated Web of 3.0 and the company has quickly become a major player in the Filecoin field. In addtion, our official website is http://fireflyblock.com
As an individual, I have worked as a crypto miner for over 6 years. I’ve been a part of the Filecoin community since 2017 and founded Firefly  in 2018. As an organization, Firefly is a leading service provider committed to comprehensive Filecoin mining solutions in a cost-effective way. 
We have built quite an extensive relationship with the Filecoin community since its initial launch back in 2017, and as a result, have sustained countless contributions to the overall network. 

At the end of 2020, due to Chinese mainland policies restricting the development of digital currency, all of Firefly's Filecoin-related businesses were sold to Yuanhe Technology in Hong Kong, China.

In April 2022, we applied for and successfully became a third-term co-notary public, spending an average of more than 10 hours per week on community Q&A and LDN due diligence.

Stake Exposure

Please cite total token at stake (currently available, locked as collateral, vesting over time) and any substantiating evidence (i.e., addresses on chain with their corresponding FIL amounts).

We have 30000 Fil currently at stake, 200,000 locked as collateral. minerid: f0839084/f0748101

How did you acquire the FIL cited above?

The rewards we earned from the space race before the launch of the Filecoin mainnet and mining rewards for these 3 years

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. 

As a member of Filecoin community, I have dedicated all my working time in promoting the ecological development of Filecoin industry with the company since 2018.Starting from August 2019，Firefly has been pushing a large number of articles about the latest developments in Filecoin on major social platforms weekly including WeChat official account, Twitter, Zhihu,Tiktok ， and has led thousands of people to get into Filecoin storage
Provide block de-rights source code- 
Commit code（urugang）
-https://github.com/filecoin-project/lotus/commit/69bfe7b7a8eeff6888e51cac3f1bfaa2d76c0c43
Consultation and questioning（embedsky、urugang）
- https://github.com/filecoin-project/lotus/issues/931
- https://github.com/filecoin-project/lotus/issues/495
- https://github.com/filecoin-project/lotus/issues/50447
(jackmimil、urugang)
- https://github.com/filecoin-project/lotus/issues/2929
- https://github.com/filecoin-project/lotus/issues/3973
- https://github.com/filecoin-project/lotus/issues/5042

Open-sourced two filecoin-related projects

https://github.com/yuanheTeck-fireflyblock/ff-wallet
https://github.com/yuanheTeck-fireflyblock/block-back-trace

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. 

None.

Organizational Reputation

Please describe the nature of your organization, including the country of registration, size of the organization, and time since inception.

Firefly is a reputable decentralized storage solution provider based in Hangzhou, China. The company was founded in July 2018, then rapidly developed into a leader in the field of IPFS network. Currently, we have about 100 employees, many of whom come from Microsoft, Alibaba, Huawei, Giant Network, AMD, and other well-known enterprises. Our team has been deeply engaged in the field of cloud storage and Internet for more than ten years and has built strategic partnership with major cloud service providers such as Alibaba Cloud and telecom operators globally. 
We will work harder to promote the development of Filecoin ecosystem and lead the upstream and downstream evolution of the distributed storage industry. In addition, Firefly has established a complete sales channel globally, providing thousands of users with the most cost-efficient products and software services. In China, there are more than 100 agents and distributors. Apart from the headquarter in Hangzhou, we have another Operation Centers in different locations, covering all Tier-1 cities and mostTier-2/3 cities in China. Although we are based in China, but we always harbor an international vision. 

At the end of 2020, due to Chinese mainland policies restricting the development of digital currency, all of Firefly's Filecoin-related businesses were sold to Yuanhe Technology in Hong Kong, China.

Please share any relevant details to help substantiate information about your organization (website, named officers, links to social media profiles).

[Please answer here.](https://www.bilibili.com/video/BV1Ky4y187RT?from=search&seid=13745773048619813785
https://twitter.com/fireflyblock1
http://www.fireflyblock.com/
www.fireflypool.com
https://www.bilibili.com/video/BV1nv411r7GX
https://www.chainnews.com/u/095136341312.htm
Tiktok：Firefly萤火虫
Bilibil：Firefly萤火虫区块链)

Please share any relevant external information regarding your organization (e.g. news articles, social media profiles, etc.)

https://news.163.com/20/0403/17/F9A9TMPC00019OH3.html
Cooperate with Chinese colleges and universities to develop FPGA chips and build a perfect Ipfs ecosystem)

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.

Slack："FireflyHZ"
Github：fireflyHZ
Email: liuwencheng@fireflyblock.com

Please share any additional relevant information regarding your presence (e.g. news articles, interviews, podcasts, videos, awards, etc.)

https://news.163.com/20/0403/17/F9A9TMPC00019OH3.html
Cooperate with Chinese colleges and universities to develop FPGA chips and build a perfect Ipfs ecosystem)

Allocation Plan refer to the Rubric to see how this impacts your Notary score

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 rate at which you'll allocate DataCap.

We have consulted and learned a lot of the audit plan of the old notary and also updated our own audit plan, which was uploaded to Google Docs.
https://docs.google.com/spreadsheets/d/19XIocGpGNCX6q2KxxmbmB-l98o80KDC5axS2rrlQzyc/edit#gid=0

How do you plan on securing the DataCap to ensure your organization (and its delegated members) are the ones allocating the DataCap?

In general, the higher the DataCap thresholds are, the more restricted the client scrutiny would be. 
For individual clients, online identity will be verified by both account age and account activity perspectives, and this will serve to prove that they are valid users and not bots 
Third-party tools like twitteraudit may also be used to verify online identities. 
For organizational clients, application organizations should be easy to verify through the appearance of their application. 
The developing applications may require further stringent investigation; 
this is to ensure that the application is valid and enclosed with meaningful content, rather than the shell of a malicious client. 
Large public datasets hosted by organizational clients are easy to verify because the data should be unencrypted and accessible to anyone.

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? 

1.Onboarding due diligence First, we will collect KYC & onboarding documents to identify the client. We may also employ a KYC Registry to consolidate all KYC data (may use third-party tooling), depending on the scale of the applications. Typical KYC & onboarding documents are as follows (which may vary across different jurisdictions): the Client’s name, contact details, registration number, registration date, registration certificate, scope of business, members of board and senior management and beneficial ownership structure. 
2. Post-allocation Vetting The post-allocation vetting of Clients will be performed regularly and constantly to avoid the allocated DataCap being abused or misused. The fundamental principle is that the Client is obliged to spend the DataCap exclusively for the approved uses (which will be specified in our allocation decision). To this end, at any time of the Client’s spending the DataCap, we may ask the Client to provide: (i) a consolidated Content Identifier (“CID”) list for verified deals that includes deal CID and miner ID (showing how the allocated DataCap has been used); (ii) description of the data being stored and how the data has been processed; and (iii) instructions on data retrieval. Receiving the foregoing information, we will perform random-sample inspections on the verified deals sent out by the Client on chain by checking the deal CID and retrieve it from the corresponding miners to verify the data authenticity. In addition to the foregoing, other monitoring measures such as public monitoring, auditing (we will elaborate more on Q3 in this section). Since the DataCap will be allocated by stages, we may penalize the Client by delaying or even cancelling the outstanding DataCap if discovering any improper or fraudulent spending the allocated DataCap.

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.

1. Can you introduce yourself? Where can I find you online? (Github, Twitter, Linkedin handle) 
2. What is your use case for the DataCap being requested? 
3. What is the Filecoin address you would like me to allocate the DataCap? 
4. How much DataCap would you like to request? 
For organizational clients: 
5.First of all, the Client’s Filecoin address is required to be disclosed for us to closely monitor after the DataCap allocation.  Moreover, we will keep our eyes open on such Client’s storage orders placed from time to time (especially for verified deals) and relevant storage providers. 
6.As set forth above, the granted DataCap will be available to the Client by stages.  So usually we can withhold the remaining DataCap from being allocated if the Client is found over-allocating its available DataCap to any single entity.
7.We will set up a Client rubrics mechanism that scores the Clients with varying trust.  Among others, the more diversified the Client allocates its granted DataCap, the higher scores the Client will get.  The Client may get bonus score if deploying less than 30% DataCap to any storage provider while it will suffer score deduction for deploying ≥70% Datacap to any storage miner for a period of time.
8.Penalties - if a Client gets a too low score in terms of diversification of storage providers, a warning will be issued and all the other notaries will be notified of the aforementioned “Over-Concentrated Allocation”.  Further punitive actions, such as cancellation of the remaining DataCap, may be taken in response to any Client’s persistent neglection of our warning.
9.Audits - both external and internal audits will be conducted throughout the data deployment process. The community members are encouraged to take part as the external auditor to expose any Client’s over-concentration on Datacap allocation.  
10.What is the name, nature, registration country, time since inception, and named officers of your organization? Please link to relevant websites. 
11. In which region do you intend to use the DataCap? If you intend to use the DataCap in multiple regions, please specify. 
12. How many miners do you plan on allocating a DataCap? If you have a specific miner(s) you would like to allocate a DataCap, please specify.

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? 

It depends on the particular Client whether we are going to conduct our decision in public or private.  Some Clients are reluctant to be too much exposed and may require us to minimize publicity.  We are generally fine either way.

Where do you plan on keeping a publicly accessible record of all your allocation decisions?

Yes, all allocation decisions will be guided by the rubric publicly on Github. So are all communications. 
Since all interactions are intended to occur publically, most of the allocation decisions should be self-explanatory. 
Any challenges raised regarding allocation decisions should be discussed publicly in the Github repo first.

Service Level Agreement

Engagement in Program

Which level (1-5) of service commitment are you willing to dedicate to participating in the Fil+ program? This includes making DataCap allocations (direct and/or Large Datasets), joining working groups, adding comments on discussion/issues, attendance in governance calls, messages in Slack, etc. For a full list of the service levels and time commitments please review the rubric 

L5

Track Record

Past allocation

Have you previously received DataCap to allocate before? If so, please link to any previous applications.

https://github.com/filecoin-project/notary-governance/issues/465

Disclosures

Do you/your organization have any relationship(s) with other existing notaries or their organizations? If yes, please list the names of the Notary individuals or organizations you may be related to.

No.
filecoin-notaries-onboarding-bot[bot] commented 1 year ago

Thanks for your request! Everything looks good. :ok_hand: 

    A Governance Team member will review the information provided and contact you back pretty soon.
filecoin-notaries-onboarding-bot[bot] commented 1 year ago

Thanks for your request! Everything looks good. :ok_hand: 

    A Governance Team member will review the information provided and contact you back pretty soon.
filecoin-notaries-onboarding-bot[bot] commented 1 year ago

Thanks for your request! Everything looks good. :ok_hand: 

    A Governance Team member will review the information provided and contact you back pretty soon.
filecoin-notaries-onboarding-bot[bot] commented 1 year ago

Thanks for your request! Everything looks good. :ok_hand: 

    A Governance Team member will review the information provided and contact you back pretty soon.
fireflyHZ commented 1 year ago

Notary Ledger Verified

Message sent to Filecoin Network

message CID: bafy2bzacea73kgn6bpsjkvceisoswehoff3ipiuhzuatjlwtsaxfxfyelaig2

You can check the status of the message here: https://filfox.info/en/message/bafy2bzacea73kgn6bpsjkvceisoswehoff3ipiuhzuatjlwtsaxfxfyelaig2

Kevin-FF-USA commented 1 year ago

On multisig - closing application. All set