pdp: propose proof set transfer to sp after filling#640
Merged
Conversation
proof sets track assembling/proposed/transferred state with durable piece count. client fills proof sets up to MaxPiecesPerProofSet, then proposes transfer to the SP via proposeDataSetStorageProvider. partially filled sets are also proposed on schedule completion. accept CommPv2 piece CIDs alongside legacy CommP. validate piece sizes for PDP (power of two, <= 1 GiB minus FR32 overhead).
parkan
force-pushed
the
feat/pdp-proofset-handoff
branch
from
71e8c24 to
5d5f863
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
client creates proof sets and adds pieces, then calls
proposeDataSetStorageProvider to hand off to the actual sp.
replaces the broken model where client was acting as on-chain
storage provider.
piece count on PDPProofSet, replacing deal-state-based occupancy