Skip to content
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.

Sign up for GitHub

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

Jump to bottom

v5 Notary Allocator Application:filscan.io #1033

Closed
remakeZK opened this issue Dec 29, 2023 · 16 comments
Closed

v5 Notary Allocator Application:filscan.io #1033

remakeZK opened this issue Dec 29, 2023 · 16 comments
Assignees
@Kevin-FF-USA
Labels
granted Notary Application Round 5 - Allocator

Comments

@remakeZK
Copy link

remakeZK commented Dec 29, 2023 •
edited
Loading

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

  1. Notary Allocator Pathway Name: FilscanOfficial
  2. Organization Name: Filscan.io
  3. On-chain address for Allocator (Provide a NEW unique address. During ratification, you will need to initialize this address on-chain): TBD
  4. Country of Operation: PRC
  5. Region of Operation (What region will you serve?): Asia
  6. Type of Allocator, diligence process: (Automated/programmatic, Market-based, or Manual (human-in-the-loop at some phase): Manual
  7. DataCap requested for allocator for 12 months of activity (This should be an estimate of overall expected activity. Estimate the total amount of DataCap you will be distributing to clients in 12 months, in TiB or PiB):50PiB

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.
@Kevin-FF-USA Kevin-FF-USA self-assigned this Dec 31, 2023
@Kevin-FF-USA
Copy link
Collaborator

Hi @remakeZK
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.

@Kevin-FF-USA
Copy link
Collaborator

Hi @remakeZK,
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.

@remakeZK
Copy link
Author

@Kevin-FF-USA Submitted the Airtable form with our detailed Allocator plan

@Kevin-FF-USA
Copy link
Collaborator

Hi @remakeZK,

Thanks for submitting to become and Allocator! Wanted to confirm this application has been received along with your completed Airtable form.

@ghost
Copy link

ghost commented Jan 13, 2024

Basic Information

1. Notary Allocator Pathway Name:
FilscanOfficial

2. Organization:
Filscan.io

3. On Chain Address for Allocator:
TBD

4. Country of Operation:
PRC

5. Region(s) of operation:
Asia minus GCR, Greater China

6. Type of Allocator:
Manual

7. DataCap requested for allocator for 12 months of activity:
50 PiB

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?:
Overview:
Clients can acquire Datacap by staking FIL. They are not required to meet any strict requirements for data storage, just need to submit the general information. The staked funds are used to maintain allocator's service equipment and provide technical support, as well as to establish a challenge zone to regularly audit data storage. A portion of the client's staked funds goes into the public reward pool of the challenge zone. Any participant can initiate a challenge by paying a commission. After the challenge is initiated, miners vote to arbitrate. The challenge winner receives a reward from the pool.

Flow:

  1. The client submits a DC application and provides basic information.
  2. The client stakes a certain amount of FIL to receive the allocated DC.
  3. Miners in the challenge zone submit challenges.
  4. Miners vote to arbitrate the challenges.
  5. If the challenge is successful, the miner receives a penalty reward. The storage client that is verified to be unqualified will stop receiving DC.

Features:
● Open application mechanism to attract more users.
● Public reward pool of the challenge zone increases participation incentives.
● Decentralized arbitration through voting.

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

Client Diligence

10. Who are your target 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?:
We do not have strict requirements for client onboarding, but client needs to stake a certain amount of FIL. Anyone can participate. Clients need to fill in the basic information and upload the form. The contents include:

  1. Client's basic information
  2. Client's involved business
  3. DC demand

12. Please specify how many questions you’ll ask, and provide a brief overview of the questions.:
A. Applicant information

  1. Applicant name + email
  2. Organization name
  3. Github, Slack, Discord, Telegram
  4. Base city and address

B. Data-related information

  1. Application number
  2. Data access (retrieval) frequency
  3. Relationship with the data
  4. Who else has the right to jointly own this data or LDN address private key

13. Will you use a 3rd-party Know your client (KYC) service?:
TBD

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 can apply the pathway

15. How do you plan to track the rate at which DataCap is being distributed to your clients?:
Use tools such as Glif and filplus.info to check whether LDN is distributed as expected every week, and regularly summarize and analyze the results to form a report and synchronize information.

Data Diligence

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?:
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?:
After the applicant submits the identity information collection form, a single verification will be performed based on the applicant's provided proof. We do not impose too many strict restrictions on the identity and data storage conditions of the client.

19. How will you ensure the data meets local & regional legal requirements?:
Every service region has different regulations. We mainly provide services in the Asia-Pacific region. We have many years of experience in this region. We are familiar with local laws and regulations, and we have our own legal team to ensure that our business is legal in the local area. This can help us avoid most problems. Once we discover that a client is maliciously storing illegal data, we can negotiate a solution and delete the data as soon as possible.

20. What types of data preparation will you support or require?:
We can provide rich technical support and guidance to applicants, including but not limited to data slicing, data processing with droplets, etc.

21. What tools or methodology will you use to sample and verify the data aligns with your pathway?:
We can retrieve client data for regular audits. In addition, we have a challenge zone mechanism: a challenge zone is established to regularly audit data storage conditions. A portion of the funds staked by the client enters the public reward pool of the challenge zone. Miners in the challenge zone submit challenges, and miners vote to arbitrate. If the challenge is successful, the miner receives a penalty reward. The storage client that is verified to be unqualified will stop receiving DC or be subject to other penalties.

Data Distribution

22. How many replicas will you require to meet programmatic requirements for distribution?:
2+

23. What geographic or regional distribution will you require?:
We do not strictly restrict geographic or regional distribution.

24. How many Storage Provider owner/operators will you require to meet programmatic requirements for distribution?:
2+

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 do not impose too many strict restrictions on clients, but we require them to provide a plan that includes the requested Datacap and SP allocation.

26. What tooling will you use to verify client deal-making distribution?:
filplus.info and CID Checker Bot

27. How will clients meet SP distribution requirements?:
Regular audits and the challenge zone mechanism work together to prevent malicious behavior and the submission of false storage data.

28. As an allocator, do you support clients that engage in deal-making with SPs utilizing a VPN?:
Based on our previous experience, it is impossible to completely prevent client nodes from using VPNs. We do not explicitly support VPN use for nodes, but we will track the use of VPNs by clients. Excessive use of VPNs will be recorded, flagged, and may even be blacklisted.

DataCap Allocation Strategy

29. Will you use standardized DataCap allocations to clients?:
No, client specific

30. Allocation Tranche Schedule to clients::
Filscan will allocate data to clients in a single tranche, as soon as they have been approved for access. This will ensure that all clients have access to the data they need without delay.

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?:
filplus.fil.org

33. Describe the process for granting additional DataCap to previously verified clients.:
When a client has an additional DC requirement, they need to submit an application. We will manually review and issue additional DC based on their previous usage.

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:
A. Client discoverability & applications：
bigdataexchange.io
filplus.storage
Github
B. Due diligence & investigation
qcc.com
Official Website
Social Media
C. Bookkeeping
TBD
D. On-chain message construction
TBD
E. Client deal-making behavior
filecoin.tools
F. Tracking overall allocator health
 filplus.info
datacapstats.io
G. Dispute discussion & resolution
Github proposal
Slack
Telegram
H. Community updates
Telegram
Slack
Github

Tools and Bookkeeping

35. Will you use open-source tooling from the Fil+ team?:
We are committed to transparency and openness in our community. As such, we are currently not considering using some of Fil+'s open-source tools because we want to ensure that our community rules are accessible to everyone. We are instead using Google spreadsheets to collect information. This allows us to gather feedback from the community and ensure that our rules are fair and equitable.

36. Where will you keep your records for bookkeeping? How will you maintain transparency in your allocation decisions?:
We will keep records of data allocations in an internal form management system. We will also regularly report on allocation decisions to clients and community members who need to know.

Risk Mitigation, Auditing, Compliance

37. Describe your proposed compliance check mechanisms for your own clients.:
Data allocations will be kept in an internal form management system, and unqualified DC users will be regularly screened out based on challenge zone conditions.

38. Describe your process for handling disputes. Highlight response times, transparency, and accountability mechanisms.:
The challenge zone mechanism works as follows:

  1. Data is stored by SPs.
  2. A challenger discovers an anomaly or cheating.
  3. The challenger pays a commission to the challenge zone and initiates a challenge.
  4. Miners vote to arbitrate the challenge.
  5. Based on the arbitration vote results, the challenge is judged as successful or failed.
  6. If the challenge is successful, the abnormal/cheating party's staked funds are deducted.
  7. The challenger receives a penalty.
  8. The data anomaly is closed or stopped from receiving DCs.
  9. If the challenge is unsuccessful, the challenger's commission is deducted.

This process starts when the challenger initiates the challenge and is temporarily limited to being completed and closed within 7 days.

39. Detail how you will announce updates to tooling, pathway guidelines, parameters, and process alterations.:
We have communities on channels such as Telegram, Slack, WeChat, and GitHub. We can use these channels to know our community members and effectively communicate with them whenever we need to share information.

40. How long will you allow the community to provide feedback before implementing changes?:
According to our experience, feedback can be received gradually within one month.

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 will build and protect addresses through Ledger wallet, and only I can manage and sign them. If the manager is changed in the future, this information will also be synchronized with the governance team.

42. Will you deploy smart contracts for program or policy procedures? If so, how will you track and fund them?:
TBD

Monetization

43. Outline your monetization models for the services you provide as a notary allocator pathway.:
Our monetization model is based on community governance. Our challenge zone can be a governance council to oversee our monetization model.

44. Describe your organization's structure, such as the legal entity and other business & market ventures.:
Filscan team is a data provider based in Shanghai, China. We also have a compliance entity in Singapore. Our team members consist of a full technical and marketing management team. For more information, please visit: ● Website: filscan.io ● Twitter: https://twitter.com/FilscanOfficial ● Telegram group: https://t.me/FilscanOfficial ● Github:https://github.com/remakeZK

45. Where will accounting for fees be maintained?:
All clients can participate in auditing the challenge zone mechanism we have established. Staking, burning, and releasing data will be announced on our public platforms Telegram/Slack/Wechat/Github. Filscan itself is also a data service provider, and all Filecoin ecosystem data can be queried on our official website. We have a lot of experience in data management, and the records of our internal system will be regularly announced on the above channels.

Past Experience, Affiliations, Reputation

46. If you've received DataCap allocation privileges before, please link to prior notary applications.:
/

47. How are you connected to the Filecoin ecosystem? Describe your (or your organization's) Filecoin relationships, investments, or ownership.:
We are a Filecoin block explorer team that is deeply connected to the Filecoin ecosystem. We have a strong relationship with the Filecoin team, and we regularly collaborate with them on product development and community engagement.

48. How are you estimating your client demand and pathway usage? Do you have existing clients and an onboarding funnel?:
We are estimating our client demand based on the following factors: A. Market research: We have conducted market research to understand the demand for data storage services, especially for trusted notary allocator pathways in the Filecoin network. B. Leads: We have received a significant number of leads from potential clients. These leads have come from a variety of sources, including our website, social media, and word-of-mouth. Based on these factors, we believe that there is a strong demand for our services. We are confident that we can attract a significant number of clients in the future.

@galen-mcandrew
Copy link
Collaborator

Datacap Request for Allocator

Address

f2c3kxkjidd4zndo3scdio4mlimy553m7i6q3kmea

Datacap Allocated

5PiB

@filplus-bot
Copy link
Collaborator

The request has been signed by a new Root Key Holder

Message sent to Filecoin Network

bafy2bzacebwzfxuq2rlkl7feo7cwycjn4tqqiakxhmxgnbwtjl25fm2xlj2ps

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

@FilscanOfficial
Copy link

FilscanOfficial commented Mar 18, 2024 via email

@galen-mcandrew
Copy link
Collaborator

This address (f1gcminbhjr5fxqcdbtorlcwptmxhj4egks7il6fa) was added to the msig (f2c3kxkjidd4zndo3scdio4mlimy553m7i6q3kmea) for your pathway. I'm not sure what you mean by "invalidated". Are you able to send any messages from that address? If so, you can manually add your new address to the msig, which would be ideal.

The 'new' address you provided is also not initialized on chain (no messages, no FIL), so I am not going to manually add another address that may also be "invalidated".

You should make sure you have a Ledger address that is valid and active, then either add that address to the existing msig that was created (then no further action needed by gov team), or we will need to add it to the msig for you (once you have proven ownership and activation of the 'new' address).

@FilscanOfficial
Copy link

FilscanOfficial commented Mar 20, 2024 via email

@galen-mcandrew
Copy link
Collaborator

Adding f16mbzjnlccbifopyt4fnd6u4iyd6mmojxtxcki7q:
https://www.glif.io/en/tx/bafy2bzacebcaib6kaqjvxzrbppfbtvq6mjyicxjp35rxdiwlr33rsa6xotujm

Removing f1gcminbhjr5fxqcdbtorlcwptmxhj4egks7il6fa: https://www.glif.io/en/tx/bafy2bzacedtl33b4ik7hsf2w4gxnjrhp45eedhqgkzufhdtdzaoupstrca5je

@galen-mcandrew
Copy link
Collaborator

https://filfox.info/en/address/f2c3kxkjidd4zndo3scdio4mlimy553m7i6q3kmea

Shows f1...7q as signer now.

@FilscanOfficial
Copy link

FilscanOfficial commented Mar 25, 2024 via email

@galen-mcandrew
Copy link
Collaborator

Datacap Request for Allocator

Address

f2c3kxkjidd4zndo3scdio4mlimy553m7i6q3kmea

Datacap Allocated

5PiB

@FilscanOfficial FilscanOfficial mentioned this issue Aug 20, 2024
Closed
@FilscanOfficial FilscanOfficial mentioned this issue Sep 25, 2024
Closed
@galen-mcandrew galen-mcandrew mentioned this issue Oct 15, 2024
Open
@galen-mcandrew
Copy link
Collaborator

Datacap Request for Allocator

Address

f2c3kxkjidd4zndo3scdio4mlimy553m7i6q3kmea

Datacap Allocated

5PiB

@filplus-bot
Copy link
Collaborator

The request has been signed by a new Root Key Holder

Message sent to Filecoin Network

bafy2bzaceb36gpwssqquyqvw3l6ttqrgyliajr2zixhmsr2dlr4gh74c55ioy

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

@FilscanOfficial FilscanOfficial mentioned this issue Nov 11, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Kevin-FF-USA Kevin-FF-USA

Labels
granted Notary Application Round 5 - Allocator
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@galen-mcandrew @remakeZK @Kevin-FF-USA @filplus-bot @FilscanOfficial