NateWebb03 / FilTestRepo

A test repository for allocator application automation
1 stars 0 forks source link

Test app 1033 #1033

Open NateWebb03 opened 5 months ago

NateWebb03 commented 5 months ago

Notary Allocator Pathway Name:

FilscanOfficial

Organization:

Filscan.io

Allocator's On-chain addresss:

TBD

Country of Operation:

PRC

Region(s) of operation:

Asia minus GCR,Greater China

Type of allocator: What is your overall diligence process? Automated (programmatic), Market-based, or Manual (human-in-the-loop at some phase). Initial allocations to these pathways will be capped.

Manual

Amount of DataCap Requested for allocator for 12 months:

50 PiB

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.

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. Additionally, I will adhere to all local & regional laws & regulations that may relate to my role as a business partner, organization, notary, or other operating entity. * You can read the Filecoin Code of Conduct here: https://github.com/filecoin-project/community/blob/master/CODE_OF_CONDUCT.md

Acknowledgment: Acknowledge

Cient Diligence Section:

This section pertains to client diligence processes.

Who are your target clients?

Other (specified above)

Describe in as much detail as possible how you will perform due diligence on clients.

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

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

Will you use a 3rd-party "Know your client" (KYC) service?

TBD

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

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

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 • the data owner wants to see on the network, including private/encrypted data • or is open and retrievable • or demonstrates proof of concept or utility of the network, such as efforts to improve onboarding

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?

Other (specified elsewhere)

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.

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.

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.

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

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?

2+

What geographic or regional distribution will you require?

We do not strictly restrict geographic or regional distribution.

How many Storage Provider owner/operators will you require to meet programmatic requirements for distribution?

2+

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.

What tooling will you use to verify client deal-making distribution?

filplus.info and CID Checker Bot

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.

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

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. Additional trust and power need to be earned over time through good-faith execution of their responsibilities and transparency of their actions.

Will you use standardized DataCap allocations to clients?

No, client specific

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.

Will you use programmatic or software based allocations?

No, manually calculated & determined

What tooling will you use to construct messages and send allocations to clients?

filplus.fil.org

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.

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 • due diligence & investigation • bookkeeping • on-chain message construction • client deal-making behavior • tracking overall allocator health • dispute discussion & resolution • community updates & comms

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

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.

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

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.

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.

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.

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.

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.

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.

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

TBD

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.

Our monetization model is based on community governance. Our challenge zone can be a governance council to oversee our monetization model.

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

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.

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

/

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.

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.