pdp: add /pdp/data-sets/create-and-add client#14
Merged
Conversation
Server.CreateDataSetAndAddPieces wraps Curio's atomic create+add endpoint: the SP submits a single addPieces(dataSetId=0, recordKeeper, ...) on chain from its own wallet, creating a new FWSS-listened data set and adding the supplied pieces in one tx. This is the on-chain phase of the FWSS-pull flow -- /pdp/piece/pull only does the SP-side piece transfer, the on-chain commit goes through this endpoint with the full abi.encode(bytes,bytes) of the EIP-712-signed CreateDataSet+AddPieces extraData. Mirrors synapse-sdk's createDataSetAndAddPiecesApiRequest. Status (and the resulting dataSetId, once mined) is observed via the existing GetDataSetCreationStatus / WaitForDataSetCreation pollers.
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
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.
Server.CreateDataSetAndAddPieces wraps Curio's atomic create+add endpoint: the SP submits a single addPieces(dataSetId=0, recordKeeper, ...) on chain from its own wallet, creating a new FWSS-listened data set and adding the supplied pieces in one tx. This is the on-chain phase of the FWSS-pull flow -- /pdp/piece/pull only does the SP-side piece transfer, the on-chain commit goes through this endpoint with the full abi.encode(bytes,bytes) of the EIP-712-signed CreateDataSet+AddPieces extraData
Mirrors synapse-sdk's createDataSetAndAddPiecesApiRequest. Status (and the resulting dataSetId, once mined) is observed via the existing GetDataSetCreationStatus / WaitForDataSetCreation pollers