Why must the same private key be used for watermark verification?
Conditions
- A watermark was generated using a private key.
- The verification endpoint is called with that watermark-related hash.
Reasoning, step by step
- Recall that the watermark was created using a specific private key.
- Understand that the system does not store the private key.
- Provide the exact same private key array during the verification request.
Example
For the watermark verification step to succeed, the 'key' supplied to '/dp/wm/{queryId}' must be the same private key used when generating the watermark. The video explicitly states that private keys are not recorded for privacy reasons; the user must provide the same key again.
Common misconceptions
- Assuming the system stores the user's private key. The video explicitly states that private keys are not recorded for privacy reasons; the user must provide the same key again, or the system may generate one on the fly during watermark creation.
Watch the explanation
Connected concepts
Explore next
Related questions
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'.
The alpha threshold should be set to 7 when the dataset or file contains exactly seven URLs and the goal is to verify that all seven URLs are correct and belong to the user. Setting it to 7 requires all seven checks to pass.
Conditions: The dataset/file is described as having seven URLs.; The intended verification is that all seven are correct and belong to the user.; 'alpha' is an integer query parameter.
Answers are generated from source material and independently checked. Consult the original video or creator if something is unclear.