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

[Allocator Application] <Hong Kong Starry Blue Ocean Technology Co., Limited>< Starry> PR #230 #231

Open
martapiekarska opened this issue Nov 20, 2024 · 1 comment
Labels
Proposal Modifications to improve the operating of Allocator processes.

Comments

@martapiekarska
Copy link
Collaborator

Allocator Application

Application Number

recMbMffNdCmZ053P

Organization Name

Hong Kong Starry Blue Ocean Technology Co., Limited

Organization On-chain Identity

f1fioa3lf45tceovtaiuq7pd6d4sfalevm6ag7ghq

Allocator Pathway Name

Starry

Github PR Number

230

Region of Operation

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

GitHub ID

yangxufengjx987

On-chain address

I have a multisig I want to provide now

Type of Allocator

RFA

Filecoin Community Agreement

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, allocator, or other operating entity
Acknowledge

Type of Allocator and RFA List

RFA: Market-based - Client/SP Fees

Allocator Description

1. Efficient and Fair DataCap Distribution
Dynamic Fee Mechanism: Adjust fees based on market demand and supply to ensure efficient allocation.
Sharding and Random Selection: Shard data and randomly select Storage Providers (SPs) to reduce centralization risks and enhance security.
2. Transparency
Transparent Application Process: Provide a user-friendly GUI for real-time application status tracking.
Public Records: Maintain public records of all DataCap allocations, including transaction details and audit logs.
3. Security
Multi-Signature Verification: Require multi-signature for important operations like DataCap allocation and fee payments.
Regular Audits: Conduct regular audits to ensure compliance with security standards and identify risks.
4. Flexibility
Multiple Payment Options: Offer various payment methods, such as FIL transfers, to accommodate different user preferences.
Customizable Allocation Plans: Allow users to choose from different allocation plans based on their needs.
5. Community Engagement
Anonymous Review Board: Set up an anonymous review board to randomly select reviewers for application evaluations.
User Feedback Mechanism: Establish a feedback mechanism to collect user opinions and suggestions for continuous improvement.

Contributions to EcosystemBuild better data onboarding pathway,Onboard >10PiBs of Data,Data Stewardship: Curate and provide high-quality datasets to be stored on the Filecoin network, enhancing the overall value and utility of the network.

Monetization and Fee structure

Client fees,SP fees.

Target Clients

Web3 developers,Individuals,Open/Public,Commercial/Enterprise,Nonprofit organizations

Client Diligence Check

Automated deterministic

Description of client diligence

Mechanism for Verifying Clients and Establishing Initial Trust
Identity Verification: Clients will fill out a KYC form during registration, providing their full name, email, and country/region. They must upload a government-issued identity document (e.g., passport, ID card) for verification.
Initial Trust Establishment: Initial trust is established through the KYC process, which includes identity verification and a review of the client's data ownership claims.
Mitigating Sybil Attacks
Rate Limits: Implement rate limits on application submissions to prevent automated bots from creating multiple accounts.
Deterministic Rules: Limit the number of accounts that can be created from a single IP address.
Reputation System: Develop a reputation system where clients earn trust scores based on their history of valid transactions and positive reviews.
Verifying Authenticity of Data Ownership Claims
Documentation Requirements: Clients must provide the following:
Data Source: Link or metadata of the data source.
Ownership Proof: Copyright certificates, purchase receipts, or other ownership proofs for private data.
Previous Storage: Answer whether the dataset has been stored on Filecoin before and provide reasons for storing it again.
Data Preparation:
Experience: If the client is a data preparer, they must list previous applications and client IDs.
Preparation Method: Describe how the data will be prepared, including tools and technical details.
Third Party: If the data is prepared by a third party, provide the name and business details of the preparer.
Providing Evidence and Proof for Auditing
Audit Logs: Maintain detailed audit logs of all client interactions, including application submissions, identity verification processes, and data ownership proofs.
Transparent Reporting: Generate regular reports summarizing client diligence activities and provide these to the Governance Team.
Secure Storage: Store all verification documents and audit logs securely using encrypted storage solutions to ensure data integrity and confidentiality.

Type of data

Private encrypted with on-chain deal pricing,Public, open, and retrievable,Proof of concept, network utilities

Description of Data Diligence

Verifying Clients Are Within Program Scope
Scope Verification: Review data nature and ensure it aligns with Fil+ program criteria.
Ensuring Data Meets Legal Requirements
Legal Compliance: Verify data complies with local and regional laws (e.g., GDPR, CCPA).
Data Ownership: Require clients to provide ownership proofs (e.g., copyright certificates, purchase receipts).
Data Sampling and Verification
Data Sampling: Perform random and stratified sampling to ensure data quality and authenticity.
Verification Tools: Use hash functions and IPFS to verify data integrity and match initial claims.
Proofs of Diligence for Audit
Audit Logs: Maintain detailed logs of verification processes.
Verification Reports: Generate reports detailing data verification steps and outcomes.
Ownership Proofs: Keep copies of all ownership and compliance documents.
By implementing these measures, Starry Allocator ensures thorough data diligence and provides transparent evidence for audits.

Data Preparation

Other existing ecosystem tooling,Singularity

Replicas required, verified by CID checker

3+

Distribution required

Equal distribution of deals across regions

Number of Storage Providers required

3+

Retrieval Requirements

Public data highly retrievable over Spark.

Allocation Tranche Schedule TypeStandardized scaling tranche schedule.

512

Will you use FIDL tooling, such as allocator.tech and other bots?

Yes, all available tools

GitHub Bookkeeping Repo Link

https://github.com/yangxufengjx987/Starry

Success metrics

Number of clients,Amount of data onboarded, daily & aggregate,Number of paid deals,Retrievability of data,Number of returning client customers,Speed of allocations (TTD)

Timeline to begin allocating to clients

1 week from RKH approval

Funnel: Expected DataCap usage over 12 months

100-200PiB

Risk mitigation strategies

Protecting Organization and Reputation
Operational Security (OpSec):
Access Controls: Limit access to sensitive systems and data.
Data Encryption: Encrypt all sensitive data.
Regular Audits: Conduct regular security audits.
User Agreements:
Terms of Service: Clearly define acceptable use and consequences for violations.
Privacy Policy: Explain data handling practices.
Abuse Prevention
Alerts and Monitoring:
Real-Time Alerts: Set up alerts for suspicious activities.
Activity Logs: Maintain logs of user activities.
Throttling Mechanisms:
Rate Limits: Limit the number of requests from a single IP address.
Account Lockout: Temporarily lock accounts after multiple failed login attempts.
Reputation System:
Trust Scores: Assign trust scores based on user behavior and history.
By implementing these strategies, Starry Allocator aims to protect its organization, reputation, and pathway from abuse while maintaining a secure and reliable system.

Dispute Resolutions

Internal Disputes (Between Starry Allocator and Clients)
Communication: Address disputes through clear and timely communication.
Escalation Process: Define a clear escalation process for unresolved issues.
Mediation: Use internal mediation to resolve conflicts.
External Disputes (With Other Notaries or Fil+ Governance Team)
Documentation: Maintain detailed records and evidence of all decisions.
Appeals: Allow clients to appeal decisions to the Fil+ Governance Team.
Transparency: Provide transparent and detailed explanations for all actions.

Compliance Audit Check

Spark tools remain an excellent tool, and in the initial phase, we still rely on the bot reports from Spark tools.

Moreover, all applications and allocations can be recorded and traced on our website.

Compliance Report content presented for audit

Success metric: onchain report of data onboarded,Success metric: onchain data report,Client Diligence: Client statements, client provided verification,Client Diligence: KYC/KYB report on clients,Data Compliance: Data Samples,Compliance: CID report.

Connections to Filecoin Ecosystem

Code contributor,Developer,Storage provider,Big data contributor

Slack ID

Starry

@martapiekarska martapiekarska added the Proposal Modifications to improve the operating of Allocator processes. label Nov 20, 2024
@yangxufengjx987
Copy link

The Starry team is working on the website platform and will be launching it soon!

Of course, we sincerely acknowledge that during the early development phase, there may be some minor issues. We request understanding and welcome valuable feedback from the community to help us improve.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Proposal Modifications to improve the operating of Allocator processes.
Projects
None yet
Development

No branches or pull requests

2 participants