Skip to content

PDP - Optimise Curio Guided Setup for PDP SP Onboarding #474

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

Open
6 of 10 tasks
TippyFlitsUK opened this issue Apr 14, 2025 · 0 comments · May be fixed by #483
Open
6 of 10 tasks

PDP - Optimise Curio Guided Setup for PDP SP Onboarding #474

TippyFlitsUK opened this issue Apr 14, 2025 · 0 comments · May be fixed by #483

Comments

@TippyFlitsUK
Copy link
Contributor

Checklist

  • This is not a question or a support request. If you have any Curio related questions, please ask in the discussion forum.
  • This is not a new feature request. If it is, please file a feature request instead.
  • I have searched on the issue tracker and the discussion forum, and there is no existing related issue or discussion.
  • I am running the Latest release, or the most recent RC(release candidate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.

Curio component

  • PoRep Pipeline
  • Snap Deals
  • Market
  • IPNI provider
  • Curio UI
  • Other

Improvement Suggestion

The current Curio guided setup requires new PDP Storage Providers to select a sector size during the onboarding process. However, this step doesn’t quite align with how PDP works. PDP doesn’t rely on sectors at all - its proof set sizes are arbitrary and fully flexible, allowing SPs to structure their data however they like. To better reflect this difference and avoid confusion during onboarding, could we add a dedicated PDP option to this step in the guided setup? This would help make the process clearer for new participants and better represent PDP’s unique architecture.

Open to other suggestions as well if there’s a better way to handle this!

@LexLuthr LexLuthr linked a pull request Apr 17, 2025 that will close this issue
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant