How does the demonstrated workflow upload a dataset to IPFS and retrieve it by hash identifier?
Conditions
- Requires selecting a local file in the request body for the POST endpoint.
- Requires a valid 'queryId' corresponding to previously stored content for the GET endpoint.
Reasoning, step by step
- Expand POST '/ipfs/dataset' and choose a local file.
- Execute the upload request and read the response body to obtain the returned 'Hash'.
- Expand GET '/ipfs/dataset/{queryId}' and enter the returned identifier into 'queryId'.
- Execute the GET request and inspect the response body to see the retrieved file contents.
Example
The clip demonstrates a concrete two-step API workflow: upload a dataset to obtain an IPFS hash identifier, then retrieve the stored content using that identifier.
Common misconceptions
- Assuming the exact hash string is fully reliable from the visible frames; only its role as the returned identifier is clear.
Watch the explanation
Connected concepts
Explore next
Related questions
The same private key must be used because the watermark was generated using that specific key. The system does not record private keys for privacy reasons, so the user must supply the identical key again during verification to prove ownership.
Conditions: A watermark was generated using a private key.; The verification endpoint is called with that watermark-related hash.
The Data Provenance tool is designed to watermark personal data, such as browsing datasets, so that data ownership can be verified later. It allows users to retain proof of possession or attribution when sharing or monetizing their data.
Conditions: Applies to personal data such as browsing datasets.; The tool verifies ownership rather than completing the whole trading process.
The original IPFS hash is used as the 'queryId' path parameter in a POST request to the endpoint '/ipfs/dataset/{queryId}'. Executing this request sends the hash to the watermarking module, which returns a JSON response containing a 'newHash' identifier.
Conditions: Use the previously obtained IPFS hash as 'queryId'.; The request method is POST.; The response includes 'newHash' and other metadata fields.
The video indicates that the file can be downloaded from the 'Download' button located in the response controls area of the Swagger UI, below the response body section.
Conditions: The interface is a Swagger UI page.; The response has been executed and is visible.
A boolean response of 'true' signifies that the verification was successful, confirming that the dataset belongs to the requester. It indicates that the specified number of URL checks passed using the provided private key and alpha threshold.
Conditions: The request has already been executed.; The server returns status '200'.
Answers are generated from source material and independently checked. Consult the original video or creator if something is unclear.