v5 Notary Allocator Application: RRM Global

[EthanLauWJ]

v5 Notary Allocator Application

1. Notary Allocator Pathway Name: RRM Global
2. Organization Name: Superb Grace Limited
3. On-chain address for Allocator: f1yjozxfuz2btlroysqgrgyel6o5mbqueeo7cicda
4. Country of Operation: Hong Kong, China
5. Region of Operation: Asia Minus GCR
6. Type of Allocator, diligence process: Manual
7. DataCap requested for allocator for 12 months of activity: 25 PiB

[ghost]

Basic Information

1. Notary Allocator Pathway Name:
RRM Global

2. Organization:
SUPERB GRACE LIMITED

3. On Chain Address for Allocator:
f1yjozxfuz2btlroysqgrgyel6o5mbqueeo7cicda

4. Country of Operation:
HongKong,China

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

6. Type of Allocator:
Manual

7. DataCap requested for allocator for 12 months of activity:
25 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?:
Rigorous data reviews will be conducted to ensure compliance with relevant laws before storing any data, whether from individuals or companies, in Filecoin

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?:
Individuals learning about Filecoin, Small-scale developers or data owners

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?:
Firstly, we conduct a strict review of the data, taking into consideration several aspects such as ownership, copyright, public disclosure, and compliance with the laws of most countries. For instance, data that is not recognized by most countries, such as gambling, pornography, blood, etc., will be rejected by us.
Secondly, we will ask for a list of collaborating Service Providers to verify if they comply with our rules.
Lastly, we have an existing template question and answer mechanism that we use to assist users.

12. Please specify how many questions you’ll ask, and provide a brief overview of the questions.:
According to the existing LDN application template
For example, the answer from question 11

13. Will you use a 3rd-party Know your client (KYC) service?:
Yes. Personal data will require proper KYC of the account. Enterprise data may require proof of business license or any acknowledged validation methods

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

15. How do you plan to track the rate at which DataCap is being distributed to your clients?:
Utilizing existing open-source tools to track daily

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

18. How will you verify a client’s data ownership? Will you use 3rd-party KYB (know your business) service to verify enterprise clients?:
Our data review process is rigorous and comprehensive, covering various aspects such as data ownership, public availability, and compliance with the laws of multiple countries. To verify ownership, we conduct business license verification and check for any watermarks on the data sample. We also check whether the data exists on official websites. Our Enterprise KYB services can be searched on national enterprise information query websites or through popular search engines like Google or Baidu in China. With our thorough data review process, you can trust that the data we provide is reliable and trustworthy.

19. How will you ensure the data meets local & regional legal requirements?:
We have a policy to decline data that is not admissible in most countries

20. What types of data preparation will you support or require?:
Any type of data within the legal framework

21. What tools or methodology will you use to sample and verify the data aligns with your pathway?:
Prevailing Lotus tools along with other accessible open-source tools to compare for analysis and evaluation, after the data is downloaded

Data Distribution

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

23. What geographic or regional distribution will you require?:
We have a preference for LDN to have five physical locations, but we require at least four. EFIL+ must have a minimum of two physical locations, as specified in their original storage request. Our KYB/KYC process may exclude specific geopolitical regions from data storage, as required by local or regional laws, on a case-by-case basis in accordance with our policies.

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?:
According to the existing rules, such as rules of acbot

26. What tooling will you use to verify client deal-making distribution?:
Existing datacaostats.io tooling and CID checker bot

27. How will clients meet SP distribution requirements?:
By complying to existing requirements, with technical support if required

28. As an allocator, do you support clients that engage in deal-making with SPs utilizing a VPN?:
VPN is supported for security purposes, which also aligns with the ideal of web3.

DataCap Allocation Strategy

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

30. Allocation Tranche Schedule to clients::
According to existing standardization rules

31. Will you use programmatic or software based allocations?:
Yes, standardized and software based

32. What tooling will you use to construct messages and send allocations to clients?:
Existing tools

33. Describe the process for granting additional DataCap to previously verified clients.:
To ensure the accuracy of customer data, we require customers to disclose their addresses, set up tracking records, and rigorously investigate the customer's stored data. We will also introduce a special customer rating database to monitor customer performance. In cases of low-scoring or poor performance, the customer will receive a warning or punishment. Conversely, we will offer public praise for customers with high data authenticity and storage data diversity. Finally, we will seek the support of community volunteers to participate in monitoring activities.

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:
Existing tools such as
• client discoverability & applications - spreadsheet tracking and meetings
• due diligence & investigation - publicly available information and meetings
• bookkeeping - spreadsheet
• on-chain message construction - current filplus.fil.org website
• client deal-making behavior - current CID checker bot
• tracking overall allocator health - current CID checker bot
• dispute discussion & resolution - GitHub notary governance repo
• community updates & comms - Slack and GitHub

Tools and Bookkeeping

35. Will you use open-source tooling from the Fil+ team?:
Yes, almost all official tools such as git hub, https://filecoin.tools/ , Google Spreadsheet, filplus checker app BOT, AC BOT, large datacap requests BOT, GitHub repository, etc

36. Where will you keep your records for bookkeeping? How will you maintain transparency in your allocation decisions?:
GitHub (https://github.com/filecoin-project/filecoin-plus-client-onboarding) and official website

Risk Mitigation, Auditing, Compliance

37. Describe your proposed compliance check mechanisms for your own clients.:
The information in question shall undergo a daily review, with all existing official tools utilized to provide support for any data stored by new clients within the framework of the law

38. Describe your process for handling disputes. Highlight response times, transparency, and accountability mechanisms.:
We utilize https://filecoin.notion.site/T-T-Dispute-Tracker-d28b93677cb544b48e77b585856601cf , and conduct a daily review of the information and guarantee a response time that does not exceed 48 hours. It is imperative to conduct a stringent analysis of the data to ensure its integrity, and we will take immediate action to remove its data cap if any issues arise. At present, we do not anticipate any unforeseen disputes

39. Detail how you will announce updates to tooling, pathway guidelines, parameters, and process alterations.:
Announce and remind in slack or GitHub

40. How long will you allow the community to provide feedback before implementing changes?:
1 Week

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?:
LEDGER will be used to protect notarized address, and only the person in charge of technology has the right to sign

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

Monetization

43. Outline your monetization models for the services you provide as a notary allocator pathway.:
RRM Global launched the R-DataCap10X joint packaging product where users provide Filecoin as pledge, and the platform bears cost of storage hardware, IDC service fees (electricity fees) and technical operation and maintenance services. Both parties jointly bear Gas and real data fees. Users get 50% of output income. The contract period is up to 540 days, the product is already sealed upon delivery, and the pledged Filecoin will be returned after the contract expires. The commencement of output for the product occurs immediately after the batch sale is ended, starting from the next day (T+1), where T represents the date when the batch sale is completed

44. Describe your organization's structure, such as the legal entity and other business & market ventures.:
Please check the about us section of our website for this question https://www.rrmglobal.io/aboutUs

45. Where will accounting for fees be maintained?:
Our notary service will not incur any accounting fees.

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.:
We offer cloud mining and IPFS storage solutions in multiple global locations. Our advanced data centers have a storage capacity of over 1,000 PiB. Our Filecoin storage mining requires powerful hardware for PoRep and PoSt mechanisms. We outsource computation to reduce the need for expensive GPUs and promote user participation through hashrate pooling.

48. How are you estimating your client demand and pathway usage? Do you have existing clients and an onboarding funnel?:
We conducted a thorough analysis of a substantial number of LDN applications, with a particular focus on the allocation of official quotas and the efficacy of data management practices. Our evaluation encompassed a comprehensive assessment of the utilization of available resources and the maintenance of our proprietary data. Our findings provide valuable insights into the optimization of LDN processes and the application of best practices in data governance.

[kevzak]

Datacap Request for Allocator

Address

f22dfonsrkelpms453jr63h3elyw2lyxlrw2fkuyq

Datacap Allocated

5PiB

[filplus-bot]

The request has been signed by a new Root Key Holder

Message sent to Filecoin Network

bafy2bzacebnb55u73wzitmct6rx4umx4qvopqyxpoloxyurd2lu7m536bhwu6

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

[Kevin-FF-USA]

Hi @EthanLauWJ

Wanted to send a friendly check in.
As of this comment date, haven't seen any client applications or DataCap disbursements for the organization. Inactive organizations are in the process of being reviewed to see if still wanting to remain in program. If you would like this pathway to remain active as an Allocator, kindly asking that you reply to the proposal with your timeline for onboarding pathway or plan for action to clients.

1078 | SUPERB GRACE LIMITED, RRM Global | Manual | Bookkeeping | Hong Kong | #1078 | f03018026

[EthanLauWJ]

Hi Kevin, Thanks for the reminder! I'll chat with my guys and get back to you. On 11 Jun 2024, at 7:36 AM, Kevin ***@***.***> wrote: Hi @EthanLauWJ<https://github.com/EthanLauWJ> Wanted to send a friendly check in. As of this comment date, haven't seen any client applications or DataCap disbursements for the organization. Inactive organizations are in the process of being reviewed to see if still wanting to remain in program<filecoin-project/Allocator-Governance#6>. If you would like this pathway to remain active as an Allocator, kindly asking that you reply to the proposal <filecoin-project/Allocator-Governance#6> with your timeline for onboarding pathway or plan for action to clients. 1078<https://github.com/filecoin-project/Allocator-Registry/blob/main/Allocators/1078.json> | SUPERB GRACE LIMITED, RRM Global | Manual | Bookkeeping<https://github.com/EthanLauWJ/RRM-Global> | Hong Kong | #1078<#1078> | f03018026<https://filecoinpulse.pages.dev/allocator/f03018026/#pageparamsallocator_id> — Reply to this email directly, view it on GitHub<#1078 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AYKIHBHW35LUHD6RYNJAGQTZGY2ARAVCNFSM6AAAAABCBKCQZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJZGQ4TMMJSGQ>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[EthanLauWJ]

Hi Kevin, We are currently in shortage of FIL for pledge, most are allocated to GLIF for loans. On 11 Jun 2024, at 7:36 AM, Kevin ***@***.***> wrote: Hi @EthanLauWJ<https://github.com/EthanLauWJ> Wanted to send a friendly check in. As of this comment date, haven't seen any client applications or DataCap disbursements for the organization. Inactive organizations are in the process of being reviewed to see if still wanting to remain in program<filecoin-project/Allocator-Governance#6>. If you would like this pathway to remain active as an Allocator, kindly asking that you reply to the proposal <filecoin-project/Allocator-Governance#6> with your timeline for onboarding pathway or plan for action to clients. 1078<https://github.com/filecoin-project/Allocator-Registry/blob/main/Allocators/1078.json> | SUPERB GRACE LIMITED, RRM Global | Manual | Bookkeeping<https://github.com/EthanLauWJ/RRM-Global> | Hong Kong | #1078<#1078> | f03018026<https://filecoinpulse.pages.dev/allocator/f03018026/#pageparamsallocator_id> — Reply to this email directly, view it on GitHub<#1078 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AYKIHBHW35LUHD6RYNJAGQTZGY2ARAVCNFSM6AAAAABCBKCQZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJZGQ4TMMJSGQ>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[Kevin-FF-USA]

Hi @EthanLauWJ
Tonight is the final night to provide a timeline for activity to this Allocator. If we don't hear from you in filecoin-project/Allocator-Governance#6 this Allocator pathway will be sunset and you will need to reapply in order to receive DataCap again.

If you wish to remain active, please respond to Issue 6 with a timeline /or/ roadmap.

Warmly,
-Kevin

https://docs.google.com/presentation/d/1yx-C1urFX7I_A1kmhJTXBy8R42770ZnST0WoQaZzTd0/edit?usp=drive_link
and https://docs.google.com/presentation/d/1pmrRvAyxP56ZjMpcItVbiuJcAvYNQ_YDyD3n6FtX5Co/edit?usp=drive_link