Test app 1004

[NateWebb03]

No description provided.

[NateWebb03]

Notary Allocator Pathway Name:

Blockchain World FIL+ DC Allocator(BCWFDA)

Organization:

Blockchain World News

Allocator's On-chain addresss:

F1qdko4jg25vo35qmyvcrw4ak4fmuu3f5rif2kc7i

Country of Operation:

Republic of Korea

Region(s) of operation:

Asia minus GCR

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:

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. This applicant has participated from the beginning of the Filecoin network and has a high understanding and contribution to the ecosystem.
2. FIL+ 3rd and 4th notary public due diligence experience helps you better understand workflows and prevent misuse/fraud issues in DC.
3. In the meantime, the number of due diligence on DC applications is the top of all notaries, contributing significantly to the role of the next notary, which can increase governance team and client satisfaction.
4. If you look at a number of due diligence and DC approvals, there are no disputes such as fraudulent abuse, so transparency is high.

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?

Individuals learning about Filecoin,Small-scale developers or data owners,Enterprise Data Clients

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

Client due diligence is largely divided into individuals and organizations. It is not much different from the existing manual due diligence method.

1. Due diligence on individuals and small developers or data owners

• Most individual clients can check their identities through online accounts. They check their identities through GitHub accounts, Linkedin, and SNS (Twitter, Facebook, Instagram, Telegram, etc.).
• Check whether the DC application homepage (https://filplus.storage/apply) is KYC.

Questions for client due diligence
(1) Please introduce me to know you.
(2) Please let me know the SNS, mail, and Slack accounts of the means of contacting you.
(3) If there is an organization you belong to, please introduce it. Please let me know your homepage, type of organization, and your position and role in the organization.
(3) How did you learn about Filecoin Plus (FIL+)? If you're not sure, I'll let you know more during the due diligence.

2. Enterprise data client due diligence

• Check the applicant's KYC status and personal contact information (SNS, mail, Slack).
• Receive the DC application number title in the organization's email to verify that the applicant is affiliated with the organization or organization.
• Check the facts with the institution or organization that applied for DC. For example, check the website, business registration certificate, corporate certificate, and other government-issued group certificates.

Questions for institutional or organizational due diligence
(1) Please explain in detail about the organization you belong to.
(2) How did you learn about Filecoin Plus (FIL+)? If you're not sure, I'll let you know more during the due diligence.
(3) Are you familiar with the workflow and regulations of FileCoin Plus (FIL+)?

Please specify how many questions you'll ask, and provide a brief overview of the questions.

The questions are as follows.
(1) Have you applied for DC before?
(2) Please tell me the type of DC you have received before and the application number.
(3) Please introduce the data you want to store using DC.
(4) Is the data you want to save public data?
(5) Please prove the amount and ownership of the data.
(6) Did you select the SP you want to save? Please tell me about the selected SPs and nodes.
(7) How do you plan to distribute your data?
(8) What kind of methods do you usually use to deliver your data? Online, offline, and other methods
(9) What is the special contract with SP?
(10) Did you have any difficulty handling SP?
(11) If the data stored after the SP transaction is not retrieved, you may be disadvantaged by the next level of DC allocation. Do you understand?
(12) AC Bot tracks DC usage and determines compliance. A lack of scores may disadvantage the next level of DC allocation. Do you understand?
(12)What DataCap do you want to add? Is it an increase in existing data or is it a new type of data?
(13)If you use DC in a fraudulent way (data storage, misuse, fraud, collusion, etc. that is different from what you applied for), are you responsible for the dispute, and are you in favor of eliminating DC?

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

No, FIL+ is enough.

Can any client apply to your pathway, or will you be closed to only your own internal clients? (eg: bizdev or self-referral)

Yes, all of our customers can apply.

How do you plan to track the rate at which DataCap is being distributed to your clients?

Filecoin Plus Dashboard : https://filplus.d.interplanetary.one/clients

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?

Public Open Dataset (Research/Non-Profit),Public Open Commercial/Enterprise,Private 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?

1, DC applicants are asked first for proof of ownership data.
2. Check the source and sample data of the data to determine whether it is owned or not.
3. If necessary, use 3rd-party KYB (Know Your Business) services. Korean clients can use verification services if the applicant is in a foreign country.
e.g.) 3rd-party KYB services
https://ondato.com/business-onboarding/

How will you ensure the data meets local & regional legal requirements?

1. First, ask DC applicants whether they have reviewed whether they meet local and local legal requirements. 2. Check sample data to see if it violates the authority of individuals or other institutions, depending on whether they answered or not. 3 It also checks whether there is illegal, illegal, or harmful data according to social wisdom. Even if it is not illegal data, it also judges whether meaningless data (e.g., CCTV footage) is used.

What types of data preparation will you support or require?

We will support data consolidation or data sharding.

What tools or methodology will you use to sample and verify the data aligns with your pathway?

Extract a large number of random sample data

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?

4+

What geographic or regional distribution will you require?

4 actual geographic locations required, no specific designated or excluded locations.

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?

Yes. Check the client's SP deployment plan before allocating DC (SP check tool : filfox.info , fileplus dashboard)

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

https://datacapstats.io/, CID checker bot, AC bot

How will clients meet SP distribution requirements?

It doesn't matter whether it's online (such as using the data center) or offline.

As an allocator, do you support clients that engage in deal-making with SPs utilizing a VPN?

Leverage VPN detection sites (https://www.criminalip.io, https://www.ip2proxy.com/)

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?

Yes, standardized

Allocation Tranche Schedule to clients:

• First allocation: lesser of 5% of total DataCap requested or 50% of weekly allocation rate
• Second allocation: lesser of 10% of total DataCap requested or 100% of weekly allocation rate
• Third allocation: lesser of 20% of total DataCap request or 200% of weekly allocation rate
• Fourth allocation: lesser of 40% of total DataCap requested or 400% of weekly allocation rate
• Max per client overall: lesser of 80% of total DataCap request or 800% of weekly allocation rate

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?

Use the existing notary registry tool (https://filplus.fil.org/ #/).

Describe the process for granting additional DataCap to previously verified clients.

I’ll use the Subsequent Allocation(SA) bot.

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

https://filplus.fil.org/#/
https://filfox.info
https://filfox.info/en/deal
https://datacapstats.io/clients
https://compliance.datacoapstats.io
https://retrievalbot-dashboard.vercel.app
https://www.togggle.io/
https://filecoin.tools/
https://pluskit.io/home
https://filrep.io/
https://console.filswan.com/dashboard
https://filplus.starboard.ventures/
https://verify.glif.io/

Google Spreadsheet
Slack
filplus-check-app(checker Bot)
Aggregation and Compliance bot(AC Bot)
VPN Detection Tools

Will you use open-source tooling from the Fil+ team?

Github repo, Google Spreadsheet

Where will you keep your records for bookkeeping? How will you maintain transparency in your allocation decisions?

1. Record for bookkeep
   Github
   Google Spreadsheet
   E-mail

2. Allocation Decision Transparency
   The allocation decision will be made public as much as possible, and the content will be maintained in the comments on the GitHub application.

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.

1. After the due diligence is completed, DC allocation is signed, and the DC status is checked using the applicant's address to see if normal DC allocation has been made.
2. After confirming that the applicant has received DC, it is checked whether the initial data is distributed (whether to use DC) the next day. If DC is not used, check every 2-3 days.
3. One week after the first DC use data distribution, the SP distribution status is checked using the filplus dashboard (https://datacapstats.io/clients) . At this time, if it is abnormal, the client is notified and the reason is confirmed.
4. If a reasonable reason is given for an abnormal distribution (e.g., online distribution time is required for each region), it should be reconfirmed after a week or two.
5. When distribution is made, the Github application basically checks the filplus-check-app (Checker Bot) and the AC Bot to leave a record.
6. If problems such as misuse or fraud of DC use occur, it is handled by dispute settlement procedures.

Describe your process for handling disputes. Highlight response times, transparency, and accountability mechanisms.

https://docs.google.com/document/d/1fDjlw9ljLTPZImBesQMCWTHfb9UlSunPVOXrq3shnX4/edit?usp=sharing

Detail how you will announce updates to tooling, pathway guidelines, parameters, and process alterations.

Tactical tools, route instructions, and processes remain unchanged. However, it will be used when FIL+ governance guidelines are changed or tactical tools are updated. If there is any change, we will post it on Slack's file-plus channel and notify it in advance so that there is no inconvenience in applying for and allocating DC.

How long will you allow the community to provide feedback before implementing changes?

We will provide a two-week feedback period for implementing the changes, and we will provide a two-week feedback period by modifying or improving it.

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?

The on-chain notary address is stored in Ledger Nano-x. Signing rights are with the allocator applicant himself.

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

We haven't reviewed the deployment of the smart contract yet.

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.

We haven't reviewed smart contracts, so we don't have a revenue-generating model yet.

Describe your organization's structure, such as the legal entity and other business & market ventures.

We are not reviewing corporations, other businesses, and market ventures.

Where will accounting for fees be maintained?

There is also no accounting audit because there is no revenue model.

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

filecoin-project/notary-governance#648

How are you connected to the Filecoin ecosystem? Describe your (or your organization's) Filecoin relationships, investments, or ownership.

Blockchain World News : news media(Researcher), FCC Lab : Filecoin Storage Provider(Director)

How are you estimating your client demand and pathway usage? Do you have existing clients and an onboarding funnel?

It is already well known to filecoin officials in China and Asia, including Korea, so it is easily accessible to new customers. If you have previous LDN assignment experience, it will not be difficult to use this DC assignment path.