Validating authenticity of electronic documents shared via computer networks

Inventors

Deery, Brian • Snow, Paul • PAOLINI-SUBRAMANYA, Mahesh

Assignees

Inveniam Capital Partners Inc

Interested in licensing this patent?

MTEC can help explore whether this patent might be available for licensing for your application.

Publication Number

US-11863686-B2

Patent

Publication Date

2024-01-02

Expiration Date


Abstract

Authentication of electronic document is based on multiple digital signatures incorporated into a blockchain. Structured data, metadata, and instructions may be hashed to generate the multiple digital signatures for distribution via the blockchain. Any peer receiving the blockchain may then verify an authenticity of an electronic document based on any one or more of the multiple digital signatures incorporated into the blockchain.

Core Innovation

Validating authenticity of network-shared electronic documents is performed using blockchain-distributed digital signatures generated from hashing original-version electronic data. The signatures represent the created version and are used to verify whether a current version of the electronic document is an authentic copy of the original version.

A verification server and/or a trusted peer device recomputes a verification hash for a current document version. The recomputed hash is compared with corresponding signatures or creational values stored in the blockchain, where mismatches indicate that the current version is inauthentic and trigger a fraud alert.

The document content described as being hashed can include structured data, metadata, and instructions, and the blockchain can store verification information derived from these elements. Multiple digital signatures may be used, with peer-side verification using any one or more signatures, including a verification-threshold scheme based on match counts.

Claims Coverage

The identified independent claims are clm-00001, clm-00007, and clm-00013. Each includes a core set of inventive features: receiving a blockchain recording a creational hash for an original/created version, retrieving metadata for a current version, generating a current hash by hashing only that metadata, comparing creational versus current hash values, determining inauthenticity when the hashes do not match, and generating a fraud alert.

Blockchain-stored creational hash for an original version

Receiving, by the server, a blockchain recording a creational hash value representing a created version of the electronic document.

Metadata-only current hash generation

Generating, by the server, a current hash value by hashing only the current metadata associated with the current version of the electronic document.

Creational versus current comparison and fraud-alert outcome

Comparing, by the server, the creational hash value received via the blockchain to the current hash value generated by the hashing of only the current metadata; in response to failure to match, determining that the current version is not an authentic copy of the original version and generating a fraud alert indicating inauthenticity.

System for blockchain-based authenticity verification using metadata-only hashing

A system comprising a hardware processor and memory storing instructions that perform operations including receiving a blockchain recording a creational hash value for an original version, retrieving metadata associated with a current version, generating a current hash by hashing only the metadata, incorporating the current hash into the blockchain, comparing the creational and current hash values, determining non-authenticity when hashes do not match, and generating a fraud alert.

Memory device instructions for blockchain authenticity verification using metadata-only hashing

A memory device storing instructions that perform operations including receiving a blockchain recording a creational hash value for an original version, retrieving metadata associated with a current version, generating a current hash by hashing only the metadata, incorporating the current hash into the blockchain, comparing the creational and current hash values, determining non-authenticity when hashes do not match, and generating a fraud alert.

Across clm-00001, clm-00007, and clm-00013, authenticity verification is based on comparing a blockchain-recorded creational hash value for an original/created version against a current hash value generated by hashing only metadata for the current version. The claimed flow determines that the current version is not an authentic copy when the hashes fail to match and generates a fraud alert indicating inauthenticity.

Stated Advantages

Documented Applications

No documented applications found

JOIN OUR MAILING LIST

Stay Connected with MTEC

Keep up with active and upcoming solicitations, MTEC news and other valuable information.