SOURCE VERIFICATION SYSTEM
Publishers can securely register media content (e.g. video, audio, image etc.) by verifying their identity, for example, through a blockchain wallet or other verification mechanism, providing media metadata, and generating a unique fingerprint and hash of the media. The unique fingerprint hash, along with basic metadata such as the URL location or a unique identifier of the media, is stored on the blockchain to link the media to its publisher.
1 . A method for verifying an authenticity of media content using blockchain technology, comprising:
verifying an identity of a publisher;
registering media content on a blockchain by storing unique fingerprint hash of the media along with publisher information;
verifying the media content by comparing a fingerprint hash generated from the media with the hash stored on the blockchain; and
displaying verification results to a viewer.
2 . The method of claim 1 , wherein the fingerprint is generated from at least one of the media content or media metadata.
3 . The method of claim 1 , further including providing a software development kit (SDK) for integrating media registration and verification into third-party systems.
4 . A system for media content authentication, comprising:
one or more computer-readable memory devices storing one or more instructions of the media content authentication;
one or more processors to execute the one or more instructions;
a publisher verification module;
a media registration module for storing media fingerprints and hashes on a blockchain;
a content verification module for comparing media fingerprints with blockchain-stored hashes; and
a user interface for displaying verification results.
5 . The system of claim 4 , further comprising a software development kit (SDK) for integrating media registration and verification into third-party systems.
6 . The system of claim 5 , wherein the SDK includes functions for submitting media details, retrieving fingerprints, and validating publisher identity.
7 . The system of claim 5 , wherein the SDK includes one or more APIs for performing one or more functions.
8 . The system of claim 7 , wherein the one or more functions is selected from:
a first function for submitting media details;
a second function for generating fingerprints and hashes;
a third function for validating hashes and media source; and
a fourth function for confirming publisher identities.
9 . The system of claim 4 , wherein the media registration module is for further storing one or more references to blockchain entries, wherein each of the blockchain entries is configured to link one of the hashes to a respective blockchain record on the blockchain.
10 . The system of claim 4 , wherein the publisher verification module is for validating a signature provided by a publisher using a private key of the publisher.
11 . The system of claim 10 , wherein the signature is a signature of a challenge message sent to a wallet of the publisher.
12 . The system of claim 4 , wherein one or more of a URL location and a unique identifier of the media is further stored on the blockchain.
13 . The system of claim 4 , further comprising:
retrieving, by the system, a fingerprint hash and an item of publisher information prior to comparing the media fingerprints with the blockchain-stored hashes.
14 . The system of claim 4 , further comprising:
generating, by the system, a unique fingerprint of media content subsequent to submitting metadata via an API associated with the media content.
15 . The system of claim 4 , wherein the verification results are displayed by a user interface of a content viewer.
16 . The system of claim 4 , further comprising:
responsive to comparing a media fingerprint of the media fingerprints with a blockchain-stored hash of the blockchain-stored hashes, presenting, by the system, a warning icon indicating that media content associated with the media fingerprint is not on the blockchain.
17 . The system of claim 4 , wherein the blockchain comprises a plurality of transaction blocks, each of the transaction blocks storing a fingerprint hash for a loaded instance of media content.
18 . The system of claim 17 , wherein the one of the transaction blocks includes one or more of:
an identifier of a publisher;
an address of a device; and
an instance of metadata.
19 . The system of claim 18 , wherein the one of the transaction blocks further includes an authentication portion configured to set one or more restrictions on the metadata and the identifier of a publisher.
20 . The system of claim 4 , wherein the one or more instructions include one or more restriction levels.