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.

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

Test app 1054 #1056

Open
NateWebb03 opened this issue Jan 22, 2024 · 1 comment
Open

Test app 1054 #1056

NateWebb03 opened this issue Jan 22, 2024 · 1 comment

Comments

@NateWebb03
Copy link
Owner

No description provided.

@NateWebb03
Copy link
Owner Author

Notary Allocator Pathway Name:

EF

Organization:

EF

Allocator's On-chain addresss:

f13ujyzruulb6isvjlto2snyj5weptr4shqbh4bvq

Country of Operation:

China

Region(s) of operation:

Africa ,Asia minus GCR,Greater China,Europe,Oceania,Japan,North America,South America

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?

By manually distributing and labeling the data manually, you can differentiate the available data. This approach helps you better manage and organize your data, making it easier to understand and use.
During the data distribution process, labels are used to mark the characteristics or attributes of each data set. These labels can be descriptive words, numbers, or other identifiers, depending on your needs and preferences. For example, you can use tags to indicate the source, type, time frame, geographic location, etc. of the data.

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.

We will ask the customer to provide supporting documents, and may also require the customer to provide proof of business registration, tax registration certificates and other relevant documents.
In order to verify the identity of the customer, we will verify the identity verification documents provided by the customer by comparing them with information from public databases or other reliable sources.
In addition, we will also conduct a background check on the customer to find out his/her past credit history, criminal records, legal disputes, etc. This can be done by checking credit reporting agencies, court records, and other relevant databases.
Finally, we will assess the client's risk level, including factors such as his or her financial condition, business history, and industry background. This will help us determine the potential risk and creditworthiness of the client.

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

Introduce yourself/your organization (with links);
Example use cases and scope;
Geographic location of customers;
Number of DataCap allocation requests;
Filecoin on-chain address;
Copyright notice and legal compliance requirements;
Specific requirements for miners and warehousing services
Nature of business (government, public, private, NGO)

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

Yes, we use KYC as a third party service.
Verify business entity information by going to relevant information websites based on customer information
Search the name of the business on social media platforms (e.g. LinkedIn) to view its page and related information.
In addition, use inquiries ,(e.g. Yelp, Google My Business, etc.) to find information such as a business's address, phone number, and hours of operation.

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

We welcome any customer to apply for our services, whether internal or external, and we aim to provide high quality service and support to all our customers. Whether you are an individual user or a corporate user, we are ready to help you whenever you need it.

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

We will use an advanced monitoring system to monitor DataCap's distribution rate in real time. The system will collect and analyze relevant data and generate detailed reports so that we can understand the actual distribution situation. We will maintain close contact with our customers and collect their feedback and comments on a regular basis. This will help us understand their experience with DataCap and any potential problems or limitations.

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

How will you verify a client's data ownership? Will you use 3rd-party KYB (know your business) service to verify enterprise clients?

For data, we verify the ownership of the data, whether there is a watermark, and query according to the sample provided by the label customer, and strictly verify the data compliance according to the third-party KYB service.

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

We consult with local laws and regulations to ensure that data management activities comply with local laws and regulations, and conduct regular compliance reviews.

What types of data preparation will you support or require?

We support various types of data preparation and data slicing.

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

We can use methods such as random sampling or stratified sampling to select a portion of the sample from the client's data for validation. This will help us ensure that the sample is representative and accurately reflects the characteristics of the entire dataset. We will also conduct a manual review. Professional data analysts will scrutinize the data and compare it with the information provided by the client to ensure consistency and accuracy. We will clearly agree sector size requirements with the client and ensure that both parties are in agreement on this. This will help prevent sector size abuse.

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?

3 physical locations At least 2 separate geopolitical regions Not less than 4 or more SP entities

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?

Each batch of data is distributed over more than 4 sp's with no more than 30% stored on each sp. Public program description on Github

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

Existing datacapstats.io tools and CID check bots

How will clients meet SP distribution requirements?

Explicitly require customers to SP plans and specific distributions in advance on Github Manual selection and distribution of data: customers can use their own tools or systems to manually select the data to be distributed and send it to SPs

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

We don't support VPN, we ask customers to provide the real address of sp and related materials.

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:

Distribution according to existing rules
5% of the first DataCap total, or 50% of the weekly allocation rate, whichever is lower
Second 10% of total DataCap or 100% of weekly allocation rate, whichever is less
Third 20% of total DataCap or 200% of the weekly allocation rate, whichever is less
Fourth 40% of total DataCap or 400% of the weekly allocation rate, whichever is less
Overall cap of 8P for a single client for a single application

Will you use programmatic or software based allocations?

Yes, standardized and software based

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

filplus.fil.org website I really like with proficiency

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

I love how easy and quick the follow up distribution bot is now!

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

To ensure the reliability and security of the application, use platforms such as the website, GitHub, and Discord to track and manage application processes, as well as custom programmed Excel sheets to handle bookkeeping. 
For users in the Filecoin Boost community, Discord and GitHub, Slack, and other platforms can be used to track and monitor their transactions to ensure compliance and security.
In order to monitor the health of your allocator in real-time, you can use a customized dashboard for tracking and monitoring. This will help you identify and resolve potential issues in a timely manner.
When dealing with disputes, you can utilize platforms such as Discord, Slack, and GitHub to discuss and communicate in order to reach consensus and resolve issues.
Community Updates & Newsletters*,Slack github Discord,Linkdin, Twitter, Facebook, Medium, etc.- Websites, etc.

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

GitHub repository to create a repository to which the files of the dataset will be uploaded You can use Google Spreadsheets to record and manage information about a dataset, such as the dataset's name, description, file size, and so on. You can create different worksheets to track information about different datasets MongoDB is an open source NoSQL database that can store and retrieve large amounts of unstructured data. You can use MongoDB to store metadata and other relevant information about a dataset. IPFS IPFS is a distributed file system that stores files on multiple nodes and provides persistence and availability. You can use IPFS to host your datasets and link them to the Filecoin network. Inspector App Bot etc.

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

GitHub Repository: publicly store summaries, links to documents, etc. of due diligence and customer information in a GitHub repository.
Issue Tracker: Use GitHub's Issue Tracker to log and resolve any issues or disputes related to the dataset.
Private Methods,Email Communications,Engage in private email communications with relevant parties to discuss and share details of due diligence and customer information,Encrypted Files,Store sensitive due diligence and customer information in encrypted files and share the decryption key with relevant parties.

Public information:Store some due diligence and customer information publicly on a public platform so that it can be viewed and audited by members of the community. This information should include basic information about the dataset, its source, terms of use, etc.
Dispute Resolution Mechanism: Establish a clear dispute resolution mechanism so that community members can raise objections or disputes as needed. Provide the necessary information to resolve disputes or conduct audits as requested by the Fil+ governance team.
Transparent communication: Maintain open and transparent communication with community members and respond to their queries and concerns in a timely manner. This can be done through comments on public platforms (e.g. GitHub), issue trackers, or dedicated community forums.

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.

Establish regular communication channels with customers, such as monthly or quarterly meetings, to understand their business operations and data usage. Online chat tools are available for this.
Track DataCap distribution metrics: set up a system to track and manage your customers' DataCap distribution. This can include recording information such as distribution volume, frequency and target audience for each client. This can be done using spreadsheets or specialized data management tools.
Conduct a trust assessment of new customers to ensure they meet your compliance standards. This can include verifying their identity, checking their business background and reputation, etc. You might consider partnering with a third-party organization for reports on customer credit and compliance
Monitor customer data usage with tools such as CID checkers and retrievable bots, which can help detect potential breaches, such as unauthorized data copying or sharing.

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

When a dispute request is received, within 72 hours and document the request. Ensure that all relevant details and evidence are recorded for follow-up.
Conduct an investigation and analysis to understand the background and cause of the dispute. This may involve communicating with relevant parties, collecting evidence and data, and conducting necessary due diligence.
Develop a fair and reasonable decision based on the results of your investigation and analysis. Ensure that your decision is in line with relevant compliance requirements and policies.
Maintain transparency and proactive communication with relevant parties throughout the processing. Explain the basis and process of your decision-making and provide the necessary information and support.
If the dispute involves other notaries or the Fil+ Governance Team, and provide the necessary support and cooperation. Follow the Fil+ Governance Team's guidelines and procedures for resolving disputes.

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

Maintain a public folder under your github account and use the tool's update email notifications publicly.

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

7 days

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?

I would use a hardware wallet (Ledger) to manage it and the signing would be done by the administrator reviewing the client's application.

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

There are no plans to do so at this time.

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.

There are no plans to monetize

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

At EF, we believe the world is a better place when people from different countries and cultures understand each other. Since its founding years ago, EF has helped millions of people see new landscapes, experience new cultures, and gain new insights into the world and themselves.

Where will accounting for fees be maintained?

N/A

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

no

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

filecoin-project/filecoin-plus-large-datasets#2290 filecoin-project/filecoin-plus-large-datasets#2094

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

Existing customers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant