Cloud X Lab v5 Notary Allocator Application

[CloudX-Lab]

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 (This can be your name, or the name of your pathway/program. For example "E-Fil+"):CloudX Lab
2. Organization Name:YunXiang Technology
3. On-chain address for Allocator (Provide a NEW unique address. During ratification, you will need to initialize this address on-chain): f1mkrrydd5xdjgtpnlsljkmdy5w3tphzz3orb32di
4. Country of Operation (Where your organization is legally based): CGR
5. Region of Operation (What region will you serve?): HongKong
6. Type of Allocator, diligence process: (Automated/programmatic, Market-based, or Manual (human-in-the-loop at some phase): Automated
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):10Pib

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]

Hi @CloudX-Lab
Thanks. Wanted to send you a friendly note confirming receipt of this application.

Should you have any issues or questions in the process - please tag me in here and I'll be happy to help.

-Kevin

[ghost]

Providing the information shared in Application for Public Review/Comment.

Basic Info

1. Notary Allocator Pathway Name
This can be your name, or the name of your pathway/program. For example "E-Fil+"
• CloudX Lab

2. Organization
• YunXiang Technology

3. On-chain address for Allocator
Provide a NEW unique address. During ratification, you will need to initialize this address on-chain.
• f1mkrrydd5xdjgtpnlsljkmdy5w3tphzz3orb32di

4. Country of Operation
• CGR


5. Region of Operation
• Greater China

6. 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.
• Automatic

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.
▪ 10 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?
Please explain the unique aspects of your proposed pathway.
• Intelligent allocation algorithm: Using advanced algorithms to allocate data. Intelligent allocation can be made based on different indicators and conditions, such as priority, applicant domain, etc. Compared to traditional random or manual allocation methods, intelligent allocation algorithms can more effectively match data with applicants, improving the accuracy and efficiency of allocation.
• Data monitoring: The allocator has real-time data monitoring function, which can track and record the data resources used by each applicant. DataCap can keep abreast of the applicant's application progress and make corresponding adjustments and optimizations as needed.
• Feedback mechanism: Through intelligent feedback mechanism, feedback opinions and suggestions from applicants can be collected, and allocation algorithms can be continuously optimized and improved based on these feedback.
• Our allocator provides DataCap with a unique, new, or diverse approach that can distinguish it from other applicants. Can improve the accuracy and efficiency of data allocation, optimize data processing processes.

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. 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
• Acknowledge

[ghost]

Client Diligence

10. Who are your target clients?
• Individuals learning about Filecoin
• Small-scale developers or data owners
• Enterprise Data Clients
• Other (specified above)
• Individuals learning about Filecoin

11. Describe in as much detail as possible how you will perform due diligence on clients.
• Generally speaking, the higher the DataCap, the stricter the customer review. If it is an individual customer, identity must be verified through account age and account activity to prove that the customer is a valid user, and all customers must go through strict procedures to qualify in the early stages.
• Basic requirements
• Complies with the laws and regulations of the applicant's location, and has no record of illegal or non compliant behavior
• All measures comply with the Filecoin community standards and will not directly or indirectly harm the Filecoin network
• Detailed information includes but is not limited to:
•. Enterprise Information
• Organizational documents: including registration/establishment/information proof
• Government issued company identification number
• Approval signatory information
• Evidence that the authorized signatory has the authority to act on behalf of the applicant (including proof from the company's board of directors or secretary, letters signed by the applicant's chief financial officer, or written consent to the company's operating contract (if necessary)).
• ID card or other government issued photo with signature facial close-up photo next to passport
• Beneficial owners
• If there are more than 25% of shareholders, provide a representative form, a business agreement, or similar proof of ownership documents;
• Legal name, date of birth, address, SSN, ITIN, passport number, issuing country, foreign ID card number or nationality, and other government issued documents certifying residence and country of origin.

12. Please specify how many questions you’ll ask, and provide a brief overview of the questions.
If you have a form, template, or other existing resource, provide the link.
• Introduce yourself/your organization (with links) - English organization name, registration/establishment/information proof, official website; For individuals, provide a copy of their ID card, position in which company, or other supporting documents to prove their identity.
Why save data in the Filecoin system using examples and scope?
The geographical location of the customer;
DataCap allocation request amount; Can you explain the growth rate of future weekly data if the total requested dataCap is greater than the current held quantity?
Filecoin on chain address;
Copyright statement and legal compliance requirements;
Specific requirements for miners and warehousing services
Commercial nature (government, public, private, non-governmental organizations)
Is it profitable?
Do you agree to publicly disclose trading information after the application is approved?

13. Will you use a 3rd-party "Know your client" (KYC) service?
Provide as much detail about the service, what questions and regions they cover, and how the data will be integrated with your pathway.
• Yes

1. Evaluate based on its reputation, service scope, and customer support.
2. It is necessary to determine the type of data to be collected through the KYC service. These data include but are not limited to personal identification information (such as name, date of birth, address), identification documents (such as passport, ID card), phone number, email address, enterprise information, etc.
3. Supported issues and regions: Different KYC service providers may have different coverage areas in terms of issues and regions. We need to confirm whether the KYC service provider can meet the needs of the region and industry.
4. Data security and compliance: As KYC involves sensitive customer data, ensure that third-party KYC service providers have appropriate security measures, such as data encryption, access control, and compliance authentication.
5. Testing and monitoring: Before integrating KYC services into the process, conduct testing to ensure everything is working properly and monitor the performance of KYC services.

14. Can any client apply to your pathway, or will you be closed to only your own internal clients? (eg: bizdev or self-referral)
For example, a 'white label' service where you apply directly on behalf of your clients.
• Any client can apply our pathway.

15. How do you plan to track the rate at which DataCap is being distributed to your clients?
•The data score will have a minimum value, and clients below this value will be banned. The higher the score, the more DataCap quotas can be allocated. After pre evaluating the above conditions, we will select storage customers that meet the criteria and continue to track, optimize, and adjust the process. Subsequent tracking and feedback will mainly refer to the following elements: The degree of dispersion and fairness of DataCap allocation; The success rate of data storage for each client; Transparency of allocation; Data diligence.

[ghost]

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, transmitting, or accessing of data. 
• acknowledge

17. What type(s) of data would be applicable for your pathway?
• Public Open Dataset

18. How will you verify a client’s data ownership? Will you use 3rd-party KYB (know your business) service to verify enterprise clients?
Provide as much detail as possible about how you will confirm the provenance of claimed data, such as the type of KYB service.
• Understand the source of data: inquire about the original source of customer data and whether there is a legal license or right to use this data.
• View relevant documents or contracts: Please ask customers to provide relevant documents or contracts to prove their legal rights to the data. For example, license agreements, cooperation agreements, or any documents related to data ownership.
• Third party KYB services:
• Registration information confirmation: By checking the registration information of the enterprise, such as company name, registered address, registration date, etc., the customer's identity is verified and the existence of the enterprise is observed.
• Company document verification: By verifying the company documents provided by the customer, such as business license, organizational code certificate, etc., the legality of the data and the customer's ownership of the data are confirmed.
• Shareholder Information Query: Query the customer's shareholder information to understand the company's equity structure and distribution of ownership.
• Business status check: Check the customer's business status, such as the company's business scope, industry classification, tax situation, etc., to understand the company's business strength and authenticity.

19.  How will you ensure the data meets local & regional legal requirements?
• Through rigorous customer due diligence Conduct an assessment of the legal and policy environment in the location to reduce the loss of data protection caused by legal uncertainty, in order to ensure the legality and compliance of data in the location.

20. What types of data preparation will you support or require?
Will you provide specific data prep services or integrations? Will you support or require things like sharding of data?
• N/A.

21. What tools or methodology will you use to sample and verify the data aligns with your pathway?
How will you confirm the data matches what a client claims, both in type and preparation requirements? How will you prevent sector-size abuse, such as sector padding?
• Data sampling tools: Use common data sampling tools such as random sampling or stratified sampling to obtain a portion of data for validation. Ensure that a sufficient amount of data is sampled from each category or type to make the validation results representative. Data comparison tool: Use open-source data comparison tools to determine whether the data matches in terms of type and content. Data preparation requirement verification: Develop a set of data preparation requirement specifications, verify whether the sampled data meets these requirements, and confirm whether the data matches the customer's claimed data in terms of preparation requirements. To prevent sector size abuse: Continuous monitoring and risk assessment: Establish regular monitoring mechanisms and risk assessment systems to promptly detect and respond to abusive behavior. Monitoring can include real-time monitoring of system operation logs, abnormal access behaviors, etc.

[ghost]

Data Distribution

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

23. What geographic or regional distribution will you require?
• Euro-American region and Pacific Asia region.DataCap will primarily be allocated to customers in the Asia Pacific region. This can make it easier to provide support and guidance to local teams. In the coming months, our service team will further expand to support more regions and customers..

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

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 will allocate unequal amounts based on the evaluation Firstly, conduct a complete KYC audit of the client. For new clients, conduct offline investigations and discussions on who they are, what they will use Filecoin as storage to save, and how to save. Based on this, the first step is to determine whether it meets the qualifications of the verification client. 1. Basic information -Physical documents (company registration information, certificates, etc.) Check the registration information of the company on relevant government websites to see if the information submitted is true 2. Signature information/authorization documents Evidence of authorized signatory acting on behalf of entity For qualified customers: We plan to allocate DataCap in small increments and establish a reputation mechanism. Gradually increase the temporary quota based on the customer's previous performance until the allocated data limit is reached. The introduction of reward and punishment mechanisms allows users who perform well to increase data restrictions over time, The customer should provide a detailed introduction to the use of DataCap, including entity information, examples, the customer's geographical location, requested quotas, copyright statements, etc After completing the information review, we will allocate based on customer ratings.

26. What tooling will you use to verify client deal-making distribution?
For example, the existing datacapstats.io tooling and/or the CID checker bot
• Datacapttats.io tool or CID checker bot.

27. How will clients meet SP distribution requirements?
Will you use software (such as a data-clearinghouse) to programmatically choose and distribute data from clients to SPs?
• Determine the protocols and interfaces supported by the data exchange: including available APIs or SDKs for communication and data transmission with the data exchange. Connect to the data exchange: Use the provided API or SDK to establish a connection with the data exchange, including authentication and authorization processes, to ensure secure access to the data exchange. Query available data: By sending appropriate query requests to the data exchange, a list of available data for allocation can be obtained, which can be based on different filtering criteria. Select the data to be distributed according to the requirements of SP. Data allocation: Using the functions provided by the data exchange, the selected data is distributed from the client to the SP, involving relevant settings and configurations for data transmission, such as data compression, encryption, etc..

28. As an allocator, do you support clients that engage in deal-making with SPs utilizing a VPN?
• support 1. Analyze user data: Collect user data related to VPN connections, including user identification, connection time, and other information 2. Identify VPN servers: Monitor traffic in the network and determine which traffic is associated with VPN by identifying the IP address or other characteristics of the VPN server 3. Provide reports and statistical data: Based on the collected data, provide detailed information about VPN usage to SP. 4. Collaborate with SP to develop policies: Collaborate with SP to develop policies and regulations for the use of VPN, clarify the restrictions and conditions for the use of VPN, and make necessary restrictions or supervision based on the user's VPN usage situation according to these policies. And ensure that operations are carried out within the framework of legal and privacy protection, and comply with relevant data protection regulations; Respect the privacy rights and data protection requirements of users when collecting, storing, and processing user data..

[ghost]

Datacap Allocation Strategy

29. Will you use standardized DataCap allocations to clients?
• Yes

Either in a single size (eg only ever giving 64GiB) or standard scale
30. Allocation Tranche Schedule to clients:
• Firstly, conduct a complete KYC audit of the client to determine whether they meet the qualifications for verifying the client.
• Secondly, for qualified customers, we plan to allocate DataCap in small increments and establish a reputation mechanism.
• Gradually increase the temporary quota based on the customer's previous performance until the allocated data limit is reached. The introduction of a reward and punishment mechanism allows well performing users to increase data restrictions over time.
• Third: First allocation: The amount of DataCap will be determined strictly in accordance with general principles - the smaller of the required 5% of the total DataCap amount or 50% of the weekly allocation rate, whichever is lower
• Fourth: Second allocation and beyond:
• If no SP can achieve more than 25% of the transaction and no modifications are made after the physical warning, we will withhold the unfinished DataCap.
• 75% or more of the granted DataCap has been used up. If the requirements are not met, DataCap will no longer be approved.
• Occasionally, stored data is retrieved to verify its usefulness and stored according to the agreement.
• We have not found any obvious issues and usually approve twice the amount previously allocated. We will regularly monitor the usage of DataCap.
• Maximum overall value for each customer: 500Tib

31. Will you use programmatic or software based allocations?
• Yes

32. What tooling will you use to construct messages and send allocations to clients?
For example, the existing notary registry tooling at https://filplus.fil.org/#/
• Existing notary registration to


33. Describe the process for granting additional DataCap to previously verified clients.
Will you use certain criteria for starting a subsequent allocation request, such as the percentage of DataCap remaining? Will you use open-source tooling such as the Subsequent Allocation (SA) bot, or other automated tooling?
• We will strictly monitor and track the usage of DataCap, and each task will be used to evaluate the customer's reputation. 1. Determine some details of its allocation plan through the use of planning and further investigation. We will check if>75% of dataCap has been used up? Then check if the SP number is the same as the plan, and there are no individual SPs storing more than 25% of transactions. If necessary, ask them to make adjustments; In addition, we will monitor GitHub/Slack messages to detect any risks of self trading The higher the score for geographic distribution, use cases, and mining, the higher the score for the DataCap client. 3. Continuously track customer information, such as DataCap deployment records, relevant mining addresses, and storage providers, to match customer words and actions 4. Establish a reward and punishment mechanism. If a customer is excessively allocated, we will reject additional allocations and remind the filecoin community; If the customer does not allocate DataCap, we will impose penalties through mechanisms such as deduction, quota reduction, blacklist, etc. Any improper behavior regarding the use of DataCap is not allowed. On the contrary, reputable customers offer plans to acquire more DataCap.

[ghost]

Tools and Bookkeeping

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
• dispute discussion & resolution
• community updates & comms *
Address all the tools & software platforms in your process.
• Due diligence: to screen high-quality personnel and provide better construction for the community.
• Customer trading behavior: Ensure healthy trading of SP.
• Tracking the overall allocator operation status: used to ensure the healthy distribution of datacaps to SP.
• Dispute discussion and resolution: bringing new vitality to the fil+ community and providing new suggestions and technical solutions for community construction.
• Community updates and communication: stay up-to-date with new developments in the community.

35. Will you use open-source tooling from the Fil+ team?
How much and which tools will you utilize? If not, please specify the tools you'll use and explain the process (such as GitHub repo, Google spreadsheet, MongoDB).
• Boost: Used for datacap allocation, importing the datacap private key and distributing it to the corresponding SP for use Glif verify: used to view the usage of datacap quotas

36. Where will you keep your records for bookkeeping? How will you maintain transparency in your allocation decisions? 
• GitHub.
• We will publicly distribute decision trackers on Github. Maintain an open attitude towards any audit requests from private and public channels, and all allocation decision records will be accessible and publicly available, supervised by the Filecoin community.

[ghost]

Risk Mitigation, Auditing, Compliance

37. Describe your proposed compliance check mechanisms for your own clients. 

•	 Create records: including DataCap allocation information and related details for each customer, such as dates, allocation amounts, etc.
•	Regular Audit: Conduct regular audits to check whether the storage usage of each customer matches the allocated DataCap. During the audit process, compare actual usage and allocation to ensure that customers do not exceed or abuse.
•	For new customers, we need to conduct a detailed investigation and understanding. We will establish a fair mechanism for offline investigation and discussion on who they are, what they will use Filecoin as storage to save, and how to save.
•	Before approval, we need to collect information, including but not limited to:
•	Physical or personal information
•	Data details and use cases.

38. Describe your process for handling disputes. Highlight response times, transparency, and accountability mechanisms.
• If there are any differences/disputes, the allocation decision discussion should be publicly initiated on Slack or GitHub first. If there are still disputes regarding the decision afterwards, the governance team will make a corresponding ruling within 10 working days when sending a dispute resolution application to the notary public. In addition, we can escalate the dispute issue to the notary office for discussion, and all notaries and management teams will make a decision on the dispute.

39. Detail how you will announce updates to tooling, pathway guidelines, parameters, and process alterations.
• Communicate thoroughly with teams internally before making any changes. This includes meetings or discussions with other notaries and notary governance teams to ensure that everyone has a consensus on the upcoming changes.Publish detailed explanations of changes to tools, path guides, parameters, and processes on Github and the community, ensuring that update notifications include necessary information such as the background, purpose, scope of impact, and relevant timelines of the changes. Before issuing the update notice, it is recommended to conduct a round of publicity and feedback. Make relevant team members aware of the changes and encourage them to provide feedback to ensure transparency and effectiveness of the changes. Based on the results of publicity and feedback, decide whether adjustments or modifications are necessary, and notify all community members. Regular follow-up and evaluation of its effectiveness, based on feedback results, can further optimize and improve tools, path guidelines, parameters, and processes.

40. How long will you allow the community to provide feedback before implementing changes?
• About two weeks.

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?
• Using multiple signatures, the project manager, development engineer, and operations manager each hold a key.
The operations manager is responsible for conducting a background check on the applicant, and once the requirements are met, the project manager will review the project requirements and have the development engineer check the data allocation of the DC node in the application..

42. Will you deploy smart contracts for program or policy procedures? If so, how will you track and fund them?
• N/A

[ghost]

Monetization

43. Outline your monetization models for the services you provide as a notary allocator pathway.
• Pledge and reduction of pledge: The notary distribution method can be based on compliance requirements, requiring SP to pledge or reduce collateral. This can ensure that participants have certain economic incentives to perform their tasks correctly and maintain the normal operation of the network. Service fees: Notarized distribution channels can obtain monetized income by collecting service fees. These service fees can be calculated based on participant usage, transaction volume, or other relevant indicators. The collection of service fees can help support the operation and development of notary distribution channels, and provide sustainable economic returns for participants. Application review: As part of the notary allocation process, application review is required to ensure that the provided applications comply with security, compliance, and technical requirements. For applications that have passed the review, the notary allocation method can charge review fees. This can promote the quality and security of the application, and bring certain economic benefits to the notary distribution channels. Data preparation and distribution: This includes processing, organizing, storing, and distributing data. Notarized distribution channels can obtain monetized income by providing data preparation and distribution services. Data Exchange and Audit: Facilitate participants to exchange and share data within it. The notarization distribution method can obtain economic benefits by charging fees for the use of data exchange or providing audit services. These services can ensure the reliability, traceability, and security of data, and provide trust and value to participants.

44. Describe your organization's structure, such as the legal entity and other business & market ventures.
• Yunxiang Technology Co., Ltd. was established in 2022 with high-tech enterprise focused on blockchain technology and application development and research based on the IPFS distributed storage network Filecoin ecosystem. It focuses on the development of blockchain and distributed storage technologies and platforms. Since its establishment, the following complete technical system has been established: -Research on Blockchain Distributed Storage Cluster Technology -Distributed Storage IDC -FIL mining Organization: YunXiang Technology Nature: Private Company Registered country: China Establishment date: 2022

45. Where will accounting for fees be maintained?
• Matters related to cost accounting may need to be decided through proposals and voting, and corresponding rules and mechanisms should be established. The pledge mechanism of Filecoin network refers to the holder locking FIL tokens in the network as collateral for storing services provided by miners. The specific cost accounting of the pledge mechanism is usually achieved through network protocols and smart contracts, and recorded on the blockchain. The relevant expenses involved in the pledge mechanism may include the pledge rate, pledge reward distribution, etc. These expenses will be accounted for and managed according to the network operation rules. Monetary audits should be conducted by independent auditing agencies to ensure transparency and verifiability. In addition, other stakeholders in the Filecoin community can also participate in the audit process and monitor the results of monetized expense accounting in a transparent and open manner.

[ghost]

Past Experience, Affiliations, Reputation

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

47. How are you connected to the Filecoin ecosystem? Describe your (or your organization's) Filecoin relationships, investments, or ownership.
•Yunxiang Technology Co., Ltd. was established in 2022 with high-tech enterprise focused on blockchain technology、application development and research based on the IPFS distributed storage network Filecoin ecosystem. After FIL became the largest ICO in 2017, we began to research and promote it and strengthen our team.The team members have rich experience and technological accumulation in the blockchain industry, gathering top domestic experts and R&D personnel in the blockchain field, including front-end development engineers, operation and maintenance engineers, blockchain researchers, etc., and providing blockchain technology application consulting and supporting services.We have long used CloudX to contribute to the Filecoin network and have been promoting the FIL ecosystem in the community. In the meantime,we have been committed to creating a high-quality Filecoin ecological application and service platform; Currently through https://www.cloudx.fun/ Served over a thousand customers and contributed over 660PiB of storage space to Filecoin.In the past year, CloudX's reputation has grown steadily, and it has become an official partner of GLIF. It has developed steadily for a long time, and has published more than 100 articles about Filcoin on its own GCR media (WeChat: CloudX Lab official account) ,Twitter account (CloudX Lab) and Tencent content platform for promotion.The vision of Yunxiang Technology is to provide users with more reliable, secure, efficient, and convenient distributed storage services, focusing on the ecological development of fil technology and the establishment of more storage providers to promote the development and application of blockchain technology, and promote the process of file encryption, privacy protection, and data sharing.The vision of Yunxiang Technology is to provide users with more reliable, secure, efficient, and convenient distributed storage services, focusing on the ecological development of fil technology and the establishment of more storage providers to promote the development and application of blockchain technology, and promote the process of file encryption, privacy protection, and data sharing.As of now, there are over 4 million Filecoin tokens in total

48. How are you estimating your client demand and pathway usage? Do you have existing clients and an onboarding funnel?
• User surveys and feedback: Regular user surveys and feedback collection can better understand customer needs and optimize datacap allocation. Data analysis: Evaluate customer needs and datacap channel usage by analyzing data. For example, observe which storage channels are used more frequently and the trend of storage capacity demand. Collaboration with other notaries: Sharing information about customer needs and datacap usage, learning from each other and drawing on experience, can more accurately estimate customer needs and allocate datacaps reasonably.

[galen-mcandrew]

Datacap Request for Allocator

Address

f2o2obeorcnu4zp6zbs6i2pxkzqppxyxommqpsefi

Datacap Allocated

5PiB

[filplus-bot]

The request has been signed by a new Root Key Holder

Message sent to Filecoin Network

bafy2bzaced5gunmpph4osa6gjd35snf352r53f4xfkhhidi4akumzk3onjtsk

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

[galen-mcandrew]

Datacap Request for Allocator

Address

f2o2obeorcnu4zp6zbs6i2pxkzqppxyxommqpsefi

Datacap Allocated

2.5PiB

[filplus-bot]

The request has been signed by a new Root Key Holder

Message sent to Filecoin Network

bafy2bzacedbte4n73jgx4uiyn37zjibj24pcwssguvykxs6kemkrrbfuqza2u

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