v5 Notary Allocator Application: Nebula Block

[bq1024]

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+"): Nebula Block
2. Organization Name: Nebula Block
3. On-chain address for Allocator (Provide a NEW unique address. During ratification, you will need to initialize this address on-chain): f1vsrfjdgi3acyi7ijhpu25bhmlat23eenoy52aqa
4. Country of Operation (Where your organization is legally based): Canada
5. Region of Operation (What region will you serve?): All Regions
6. Type of Allocator, diligence process: (Automated/programmatic, Market-based, or Manual (human-in-the-loop at some phase): Market-based and Manual
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): 150PiB

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.

[ghost]

Basic Information

1. Notary Allocator Pathway Name:
Nebula Block

2. Organization:
Nebula Block

3. On Chain Address for Allocator:
TBD

4. Country of Operation:
Canada

5. Region(s) of operation:
North America, Africa , Asia minus GCR, Greater China, Europe, Oceania, Japan, South America, Other

6. Type of Allocator:
Market-based

7. DataCap requested for allocator for 12 months of activity:
150PiB

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?:
No, we will adhere to the same process and standards as in the last round.

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?:
Enterprise Data Clients, 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?:
• Identity Verification: Collect basic information such as the client's legal name, contact details, business registration certificates, etc.
• Background Check: Understand the business model, industry, and market position, verify the existence and legitimacy of the business. Check on the social media accounts, company websites, etc. Check for legal actions, sanctions, or investigations.
• KYC Check: Conduct KYC checks
• Ongoing Monitoring: Continuously monitor whether the client is using Datacap as claimed in a compliant manner.

12. Please specify how many questions you’ll ask, and provide a brief overview of the questions.:
• Can you provide information about your company or yourself?
• Can you provide proof of identity?
• Can you describe your dataset, including its size, type, and whether it is public or private?
• For how long do you plan to keep this dataset stored on Filecoin?
• How frequently do you anticipate accessing and retrieving the stored files?
• Is there a need for real-time or near-real-time access?
• What level of redundancy or data durability is required for the stored files?
• Are there any specific requirements for backup and recovery?
• Are there any specific SLAs you require?
• How do you plan to choose SP?
• Do you already have a list of storage providers to work with?
• How will you be distributing deals across storage providers?

13. Will you use a 3rd-party Know your client (KYC) service?:
No

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 can apply.

15. How do you plan to track the rate at which DataCap is being distributed to your clients?:
We will use CID checker bot and datacapstats.io.

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, Private Commercial/Enterprise, Private Non-Profit/Social Impact

18. How will you verify a client’s data ownership? Will you use 3rd-party KYB (know your business) service to verify enterprise clients?:
If the data is not publicly available, we will request legal documents that can prove the client's ownership, including contracts, licenses, or agreements explicitly stating data ownership.
We will not use 3rd-party KYB service.

19. How will you ensure the data meets local & regional legal requirements?:
We will regularly and randomly retrieve data for manual checks to ensure data meets local & regional legal requirements.

20. What types of data preparation will you support or require?:
We can provide open source tool and SKD for data preparation, including data packing, sharding and distribution. https://github.com/filswan/go-swan-client.

21. What tools or methodology will you use to sample and verify the data aligns with your pathway?:
We will regularly and randomly retrieve data for manual checks to ensure that the data aligns with our pathway.

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?:
Data must be distributed to 5+ geographic regions.

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 won’t require equal percentage distribution, but single SP should not exceed 25% of the total amount. We will require preliminary SP distribution plans.

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

27. How will clients meet SP distribution requirements?:
I’ll recommend clients use Filswan Platform to distribute the data. https://console.filswan.com/dashboard

28. As an allocator, do you support clients that engage in deal-making with SPs utilizing a VPN?:
We will support it if the SPs have a valid reason to use VPN, such as for privacy and security reasons.

DataCap Allocation Strategy

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

30. Allocation Tranche Schedule to clients::
• First: 10%
• Second: 20%
• Third: 35%
• Fourth: 35%
• Max per client overall: 100%

31. Will you use programmatic or software based allocations?:
No, manually calculated & determined

32. What tooling will you use to construct messages and send allocations to clients?:
We will use https://filplus.fil.org/#/

33. Describe the process for granting additional DataCap to previously verified clients.:
We will use the Subsequent Allocation(SA) bot.

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:
• client discoverability & applications: Github
• due diligence & investigation: Github and governance meetings
• bookkeeping: Google Spreadsheets
• on-chain message construction: https://filplus.fil.org/#/
• client deal-making behavior: CID checker bot and https://datacapstats.io/
• tracking overall allocator health: CID checker bot and https://datacapstats.io/
• dispute discussion & resolution: GitHub and slack
• community updates & comms *: GitHub and slack

Tools and Bookkeeping

35. Will you use open-source tooling from the Fil+ team?:
Yes, we will use CID checker bot, notary-governance Github repo and Google Spreadsheet.

36. Where will you keep your records for bookkeeping? How will you maintain transparency in your allocation decisions?:
Public GitHub and Google spreadsheets.

Risk Mitigation, Auditing, Compliance

37. Describe your proposed compliance check mechanisms for your own clients.:
We will check datacapstats.io at least twice a week.We will use tools such as CID checker bot to track the datacap distribution twice a week. And we will sync with clients each month regarding the project progress and datacap distribution.
Before the project starts, we will clearly state all the rules to the client. If the client seriously violates the rules, we will consider stopping further allocations unless the client provides a reasonable explanation

38. Describe your process for handling disputes. Highlight response times, transparency, and accountability mechanisms.:
We will create an issue on the notary governance GitHub repository for disputes, and anyone is welcome to join the discussion. We will respond within two days.

39. Detail how you will announce updates to tooling, pathway guidelines, parameters, and process alterations.:
We will announce on channels including Slack, GitHub, and also notify clients directly.

40. How long will you allow the community to provide feedback before implementing changes?:
It depends on the nature of the change, but in my opinion, one month is a reasonable timeframe for a comprehensive discussion of the issue.
We will actively participate in the discussion on Slack and the Notary Governance GitHub repository.

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?:
We use Ledger Nano S Plus to structure and secure the address.

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

Monetization

43. Outline your monetization models for the services you provide as a notary allocator pathway.:
We do not have monetization models.

44. Describe your organization's structure, such as the legal entity and other business & market ventures.:
Nebula Block, headquartered in Montreal Canada, is a leading Web3 infrastructure provider. Nebula Block is celebrated for delivering a complete range of Web3 hosting solutions globally. Our expertise lies in delivering tailored turnkey datacenter services, featuring high-performance GPUs and bare metal offerings, in addition to decentralized computing, storage, and Blockchain as a Service solutions. Our dedication is to fuel innovation and maintain excellence in Web3 infrastructure. Here is our compay website: https://www.nebulablock.com/

45. Where will accounting for fees be maintained?:
There won't be an accounting for fees.

Past Experience, Affiliations, Reputation

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

47. How are you connected to the Filecoin ecosystem? Describe your (or your organization's) Filecoin relationships, investments, or ownership.:
As a member of the Filecoin community, Nebula Block Data has developed tools and platform to help the Filecoin ecosystem grow - NBFS POOL(https://nbfspool.com/#/) provides professional and security Filecoin hosting solutions. - IPFS Computing Router(https://github.com/Nebula-Block-Data/ipfs-computing-router) enables users to store and fetch datasets from the closest IPFS node and upload the training result to the same node available. We were selected as minerX fellow, participated in early-stage testing, and helped improve Louts and other ecosystem projects .

48. How are you estimating your client demand and pathway usage? Do you have existing clients and an onboarding funnel?:
Currently, we are encountering a large demand for data storage from both our existing and potential clients. Most of the clients contacted us via our company website or directly by email.

[galen-mcandrew]

Datacap Request for Allocator

Address

f2ugbpgnae63gcz77xx6z35v465yrhwdxkpupkjfq

Datacap Allocated

5PiB

[filplus-bot]

The request has been signed by a new Root Key Holder

Message sent to Filecoin Network

bafy2bzaceakhabcbtt3x4w5n2swu3ptqbjznbo3dtfaraeqnnxgq2r2ov6oow

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

[Kevin-FF-USA]

Hi @bq1024

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.

1068 | Nebula Block | Manual | Bookkeeping | North America | #1068 | f03019861

[Kevin-FF-USA]

Hi @bq1024
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