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

Pull Mode Policy Requirements and Design #331

Open
Tracked by #269
xinaxu opened this issue Sep 15, 2023 · 0 comments
Open
Tracked by #269

Pull Mode Policy Requirements and Design #331

xinaxu opened this issue Sep 15, 2023 · 0 comments

Comments

@xinaxu
Copy link
Contributor

xinaxu commented Sep 15, 2023

Requirements

Introduction

The Policy Engine enables clients to customize how deal proposals are managed. Policies are flexible tools clients can use to ensure their specific conditions are met. Service Providers (SPs) can query deal proposals without infringing upon these policies.

Singularity V1 already supports some deal making API for SP to self service deal making. In V2, we're going to take it further with more flexibility.

Service Provider Grouping

By default, SPs are automatically categorized into multiple groups using ipinfo queries. For instance, an SP f012345 might be assigned to:

  • Texas
  • USA
  • NA
  • Verison Inc.

Clients have the flexibility to modify these group assignments. Additionally, they can create custom groupings. For instance, if SPs f012345 and f012346 are from the same organization, they could be grouped under known_org.

Note: Policies can be tailored to either individual SPs or SP groups. This facilitates granular control like limiting replicas within geographical boundaries or allowing only specific SP groups to propose verified deals.

Policies

Number of deals per unique Piece

  • Ensures that each data piece doesn't have excessive replicas, irrespective of the SP group.

Deals Count Per Unique Piece & SP Group:

Allows restrictions such as:

  • An SP can seal a specific pieceCID only once.
  • A company can seal a specific pieceCID only once.
  • Limiting replicas to three per country.

Deal Start Delay for SP/SP Group

  • Clients can specify a time frame to ensure SPs initiate sealing promptly.
  • SPs can adjust this time frame to match their sealing capacity and pace.

Deal Duration

  • Clients set the acceptable deal duration that aligns with their operational needs
  • SPs can adjust the deal's lifespan to match their comfort level regarding risks and rewards

Permission for Verified Deals

  • Designates which SPs are authorized to propose verified deals and use datacap

Total Deal Size Limit

  • Caps the volume of deals each SP or SP group can propose. For verified deals, this also restricts the datacap usage for each SP or group

Pending Deal Size

  • Prevents SPs or SP groups from excessively proposing deals without executing the sealing process.

Notes

Clients can apply, mix, and customize these policies to best fit their operational and business objectives.

@github-project-automation github-project-automation bot moved this to 🍇 Backlog in ActionArena Sep 15, 2023
@xinaxu xinaxu changed the title Pull Mode Policy Design Pull Mode Policy Requirements and Design Sep 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🍇 Backlog
Development

No branches or pull requests

1 participant