Closed Destore2023 closed 6 days ago
Kevin-FF-USA
commented
10 months ago Hi @Destore2023 Wanted to let you know this application has been received. Once you complete and submit the include Airtable (form) information - the public answers will be posted in a thread below soon. If you have any questions - please let me know.
Kevin-FF-USA
commented
10 months ago Hi @Destore2023, Wanted to let you know this application has been received. Once you complete and submit the include Airtable (form) information - the public answers will be posted in a thread below soon. If you have any questions - please let me know.
Kevin-FF-USA
commented
10 months ago Hi @Destore2023,
Thanks for submitting to become and Allocator! Wanted to confirm this application has been received along with your completed Airtable form.
ghost
commented
10 months ago 1. Notary Allocator Pathway Name: Destore
2. Organization: ByteBase
3. On Chain Address for Allocator: f1rppfznglfb7uyn3k6sfzeh47yq54ptvia5ixwsq
4. Country of Operation: Greater China
5. Region(s) of operation: Africa , Asia minus GCR, Greater China, Europe, Oceania, Japan, North America, South America
6. Type of Allocator: Manual
7. DataCap requested for allocator for 12 months of activity: 120PiB
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 continue following what we have done in the past and use the same due diligence process as previous notary rounds.
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
10. Who are your target clients?: Individuals learning about Filecoin, Small-scale developers or data owners, Enterprise Data Clients, Other (specified above)
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?: As a member of the Filecoin community, due diligence on clients is essential to ensure the security and integrity of the network. Here’s a detailed process for performing due diligence on clients:
Identity Verification: Verify the identity of the client through official documents such as government-issued IDs, passports, or any other relevant identification. This helps in ensuring that the client is who they claim to be.
Background Check: Conduct a background check on the client to assess their reputation, history, and any potential red flags. This may involve checking for any criminal records, financial stability, or previous involvement in fraudulent activities.
Legal Compliance: Ensure that the client complies with all relevant laws and regulations in their country, especially those related to data protection, privacy, and financial transactions. This includes verifying their compliance with anti-money laundering (AML) and know your customer (KYC) regulations. A client paid lawyer team will be helped for that if necessary.
Financial Viability: Assess the financial stability and viability of the client to determine their ability to fulfill their commitments within the Filecoin network. This may involve reviewing their financial statements, credit history, and any other relevant financial information.
Reputation and References: Gather information about the client’s reputation within their country and seek references from previous corperted SPs, DPs or Notaries in the Slack channel. This can provide valuable insights into the client’s trustworthiness and reliability.
Technical Capability: Evaluate the client’s technical capabilities and infrastructure to ensure they have the necessary resources and expertise to participate in the Filecoin network effectively and securely.
By following these detailed steps, the Filecoin community can effectively perform due diligence on clients to safeguard the network and its participants.
12. Please specify how many questions you’ll ask, and provide a brief overview of the questions.: We have a total of 18 questions to be asked to the client. Please refer the link for detail Link: https://www.wenjuan.com/s/qAVFfuN/
13. Will you use a 3rd-party Know your client (KYC) service?: Yes, Tianyancha will be used for the 3rd party KYC provider if necessary. LINK https://www.tianyancha.com/
14. Can any client apply to your pathway, or will you be closed to only your own internal clients? (eg: bizdev or self-referral): No. We will open applications to users in all fields.
15. How do you plan to track the rate at which DataCap is being distributed to your clients?: We will continue to track the distribution on our website and use the DC Reminder to check the percentage of DataCap distributed. Distributed tracker https://www.bytebase.cn/#/dashboard DC Reminder https://www.bytebase.cn/#/
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, Other (specified elsewhere), 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?: Verifying a client’s data ownership can be done through various methods, depending on the specific context and requirements. Here are a few common approaches:
Digital Signatures: Clients can digitally sign their data using cryptographic techniques, such as asymmetric key pairs. The recipient can then verify the signature using the client’s public key, ensuring that the data has not been tampered with and originates from the claimed owner.
Blockchain Attestations: Utilizing a blockchain, clients can register their data ownership by creating a transaction that includes a cryptographic proof of ownership. This transaction is then recorded on the blockchain, providing an immutable and transparent record of ownership.
Multi-factor Authentication: Implementing multi-factor authentication methods, such as SMS codes, email verification, or biometric authentication, can help to verify the identity of the client and their ownership of the data.
Legal Documentation: Clients can provide legal documentation, such as contracts, licenses, or intellectual property rights, to prove their ownership of the data. This may involve the use of notarization or other legal processes.
Yes, trusted 3rd Parties can help us to independently verify the client’s data ownership.
19. How will you ensure the data meets local & regional legal requirements?: We will ask the data owner to provide the pass of certification from Data Security Law of the People's Republic of China. https://www.gov.cn/zhengce/zhengceku/2022-06/10/content_5695078.htm The working flow like below: The client shows the certification->DC granted The client can not show the certification->refused When the client starts data on-boarding, we will do 2-3 times spot checks, once the data does not meet the requirement, the rest DataCap will be taken back and disclose it to the community.
20. What types of data preparation will you support or require?: We will ask clients to prepare the CAR file themself. We can also introduce Dcent, Filedrive, those professional DP from Filecoin community to help clients. We support various preparation methods, such as Singularity, Lotus, Graph split etc.
21. What tools or methodology will you use to sample and verify the data aligns with your pathway?: If we are the DP, there will be no problems with this. When the customer prepares the CAR file, a random manual spot check is performed to ensure that the risk of sector size abuse such as sector padding is mitigated.
22. How many replicas will you require to meet programmatic requirements for distribution?: 5+
23. What geographic or regional distribution will you require?: SP in China ≥ 4 different provinces in China SP out of China ≥ 2 countries. Note: Provinces in China are the same administrative units as states in the United States.
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?: No, we will allocate the DC based on the client's request. No, we won't ask for the distribution plan unless the client hasn't prepared enough pledge FIL.
26. What tooling will you use to verify client deal-making distribution?: We will use the existing CID checker bot and datacapstats.io to assist us in verification. At the same time, we will use the browsers or dashboard to make further confirmation. Browser :https://filfox.info/en/deal https://filscan.io Glif: https://explorer.glif.io/ Dashboard: https://datacapstats.io/clients
27. How will clients meet SP distribution requirements?: According to the SP requirement. In addition, customers should clarify the SP plan and specific distribution on Github in advance, and use tools such as Bot to check whether the number of SPs meets the requirement of at least 4 SP after storage.
28. As an allocator, do you support clients that engage in deal-making with SPs utilizing a VPN?: Yes, we will support the customers who use VPN. But we will ask for a disclaimer from the client to make sure they list out all the VPN IP addresses, and keep that record in GitHub.
29. Will you use standardized DataCap allocations to clients?: No, client specific
30. Allocation Tranche Schedule to clients:: First: 25% • Second: 25% • Third: 25% • Fourth: 25% • Max per client overall: 20 PiB
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?: Email, Slack, Telegram,
33. Describe the process for granting additional DataCap to previously verified clients.: Check the KYC/KYB file, if it's correct, we'll assign the DC directly by triggering the SA bot for the client address.
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 We will publish our contact information on Pluskit's official website, Slack, Github. And we usually receive application requests from clients through Slack, Github and email, and guide clients in the application process.
• due diligence & investigation -KYC/KYB Baidu encyclopedia, Qichacha, Tianyancha, Wikiglobal, regional government websites, portal information, etc -Socail media Official website, Wechat public account, Weibo, Linkdin, Twitter, Facebook, Medium, etc -Website Whois,Tencent cloud, etc.
• bookkeeping We will record through online tools such as Google Docs, Graphite Docs, github, and offline Docs.
• on-chain message construction Filecoin tools:https://filecoin.tools/ FilecoinPLUS:https://datacapstats.io/clients Glif:https://explorer.glif.io/ Filedrive:https://filplus.info/ Filfox:https://filfox.info/en/deal Filscan: https://filscan.io/tipset/dsn/
• client deal-making behavior Filecoin tools:https://filecoin.tools/ FilecoinPLUS:https://datacapstats.io/clients Glif:https://explorer.glif.io/ Filedrive:https://filplus.info/ Filfox:https://filfox.info/en/deal Filscan: https://filscan.io/tipset/dsn/
• tracking overall allocator health datacapstats.io, SA bot, etc. • dispute discussion & resolution Github、Email、Zoom、Slack • community updates & comms Github、Email、Slack
35. Will you use open-source tooling from the Fil+ team?: Yes, we will use the open-source tooling.
36. Where will you keep your records for bookkeeping? How will you maintain transparency in your allocation decisions?: We will keep it both in our website and GitHub repo. https://www.bytebase.cn/#/dashboard https://github.com/Destore2023/2024_DataCap_Bookkeeping.git
37. Describe your proposed compliance check mechanisms for your own clients.: • Tracking and auditing DataCap distribution of allocated datacap For regular applications, We will pre-formulate the main scoring standards and the corresponding DataCap allocation standards, and publish them on Github for all community members to consult and strictly follow the standards. In addition, we will record the allocation results of all allocation results, including regular applications, LDN, E-Fil, etc.), in a timely manner and publish them to be monitored by the whole community on Github.
• The clients' downstream usage of DataCap We will implement clear downstream usage standards for clients and require them to commit to compliance and disclosure of usage. Before re-allocation, we will check the actual usage, and continue to allocate according to the standard if it meets the requirements. If it does not meet the requirements, it will be given 2 reminders and warnings, and if the client still violates the rules, the application will no longer be assigned, and it will be notified in slack. There is a maximum of 2 consecutive opportunities for client violations.
• Client compliance standards We would ask that clients to meet enterprise compliance, data compliance, SP compliance, storage compliance. Corporate compliance:
• The enterprise should be legally existing. • Possess of the right to legally store data. Data compliance: • The data type and content must meet the requirements of the registration location • Data is allowed to be publicly/privately stored on the Filecoin, whether it is own data or third-party data. SP compliance: • Number of SPS and allocation ratio • Location of the SP and IP address area • Support retrieval Storage compliance: • No abuse • Support retrieval
• The stored data is valid Before datacap allocation, we will ask the client to clarify the above information, the total amount of datacap requested, and the estimated weekly datacap usage. All these must meet our requirements. At the same time,we will ask clients to publish their usage on Github every 2 weeks. After datacap allocation, w will check every 2 weeks whether the client has feedbacks on the issue of their application, whether datacap usage meets our requirements, and whether it is used in the way promised in advance.
38. Describe your process for handling disputes. Highlight response times, transparency, and accountability mechanisms.: 1.We will avoid disputes as much as possible by setting clear standards and following up datacap usage throughout the process. In the event of dispute with the client, we will:.Make an initial response on Github within 3 working days.
2, We will find out the situation and explain it on Github within 2 working days. We will disclose non-private information related to the client in view of the dispute. If information is private, we will contact PL and send the information to PL via email and request PL to publish the verification results on Github. For the part related to the dispute that we am not clear about, we will communicate with the client and ask them to explain on Github and provide relevant evidence.
• Make an initial response on Github within 3 working days. Then, we will find out the situation and explain it on Github within 2 working days.
• Actively submit evidence related to the dispute on Github. If it involves private information, we will contact PL and send the information to PL by email, requesting PL to publish the verification results on Github.
• We promise there will be no private deals that violate community norms if we are elected as allocators.
39. Detail how you will announce updates to tooling, pathway guidelines, parameters, and process alterations.: So far no announcement, but if we have something to share, we will take it in the Slack, GitHub,
40. How long will you allow the community to provide feedback before implementing changes?: 7-14 days
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?: A Ledger will be used to store the keys associated with the DataCap allocation address securely.
4 people will be 2 teams, one keeps the GitHub account and one keeps the Ledger access.
42. Will you deploy smart contracts for program or policy procedures? If so, how will you track and fund them?: So far, NO.
43. Outline your monetization models for the services you provide as a notary allocator pathway.: There are several potential monetization models for the services offered as a allocator:
44. Describe your organization's structure, such as the legal entity and other business & market ventures.: Shanghai ByteBase Technology Co., Ltd (referred to as ByteBase), was established and incorporated in Shanghai at the end of 2020. ByteBase is a standing portal for blockchain storage application platforms and a storage base for decentralized application development. 2021, ByteBase is officially the notary for Filecoin Plus Greater China and the first notary to launch storage subject validation, sample data verification and storage gateway distribution. ByteBase privacy storage platform is a general-purpose privacy storage SaaS solution developed by ByteBase Technology, based on its compatibility with the Filecoin Plus self-verification platform. It makes full use of the characteristics of blockchain's non-tamperability and anti-forgery traceability, and widely integrates the global idle storage resource nodes built by the current head blockchain storage projects to provide more credible, secure and cost-effective storage services for many application scenarios, such as public trust organizations, copyright maintenance, important backup, subject self-certification and mass storage, so as to further build and explore a sustainable blockchain application ecology.
45. Where will accounting for fees be maintained?: Payment address: f1rppfznglfb7uyn3k6sfzeh47yq54ptvia5ixwsq All accounting related to our fees, including mechanisms for staking, burning, or releasing funds, will be meticulously maintained on-chain.
46. If you've received DataCap allocation privileges before, please link to prior notary applications.: Notary Application: ByteBase · Issue #689 · filecoin-project/notary-governance (github.com) Notary Application: ByteBase · Issue #419 · filecoin-project/notary-governance (github.com) Notary Application: ByteBase · Issue #169 · filecoin-project/notary-governance (github.com)
47. How are you connected to the Filecoin ecosystem? Describe your (or your organization's) Filecoin relationships, investments, or ownership.: 1.2022.10 - The first private data use case in Greater China Region supported – Project Beacon. 2.2022.06 - ByteBase became the R3 notary of the Filecoin community in the Greater China region. 3.Uses the Filecoin Network to Keep a Competitive Edge in the Photo Sharing Industry” 4.2022.01 – Power Dealer launched, to improve the sealing capability of verified deals for SPs 5.2021.01-12 - ByteBase has developed the ""ByteBase Data Storage Platform"" based on the storage provider's hardware. The platform utilizes the IPFS protocol to provide individuals and enterprises with more cost-effective distributed data backup services. 6.2021.07 - ByteBase became the R2 notary, 98.6TiB DC was allocated, and More than 25+ hours per week working on the Filecoin community. Client: We have communicated with data owners dozens of times to explain what Filecoin is and how it works to save your storage cost. Register such as Project Beacon, Xinshu Photo in the community ect. SPs: Help SP optimize Lotus and boost module, on boarding data for IPFS Force, Origin storage, Xingkong IPFS, IPFS storage, etc. Notaries: We have held online meetings during the COVID-19 time,, and offline gathering with well-known notaries such as Canza Finance, Piknik, NWG , Greater Heat,Kernel Logical, m ND Labs, etc. Community: Frequently appears in various Slack channels, helping community members, participating in biweekly community governance meetings, and attending offline meetings in Hong Kong, Singapore, and Turkey.
48. How are you estimating your client demand and pathway usage? Do you have existing clients and an onboarding funnel?: We will hire a full-time BD person to develop new data owners. I estimate that it is completely feasible to allocate my target of 120PiB in 2024. I've approved a number of applications as a notary, we have some existing public clients. We usually get clients' applications through Email, Github and Slack
kevzak
commented
8 months ago f2bqrqbxlrubzwdhwjdutccxsozk6p4i7lvml3vma
Datacap Allocated
5PiB
filplus-bot
commented
8 months ago bafy2bzacec3y66f7ngrc6hvml5z3vr2m6bh5butx7f7n5ks2v34jssxixsjyw
galen-mcandrew
commented
3 months ago f2bqrqbxlrubzwdhwjdutccxsozk6p4i7lvml3vma
Datacap Allocated
5PiB
filplus-bot
commented
3 months ago bafy2bzacec6ch2mlyap26qt6kgg5q7a6xhxq6734gg6fyg6nhs52wlkkyqqpw
galen-mcandrew
commented
3 months ago galen-mcandrew
commented
3 weeks ago f2bqrqbxlrubzwdhwjdutccxsozk6p4i7lvml3vma
Datacap Allocated
10PiB
filplus-bot
commented
2 weeks ago bafy2bzacedcgxtb55qzz6pbed3hdjgg5m2nlkr623fpihc6w5baqaddqn3lau
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
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.