# US 12,015,712 B2 · System and method for proof of view via blockchain

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 12,015,712 B2
- Document ID: US12015712B2
- Status: Granted
- Kind: B2
- Application number: 17/328,695
- Filed: 2021-05-24
- Published: 2021-09-09
- Granted: 2024-06-18
- Earliest claimed: 2018-02-07
- Assignees: Verasity Limited
- Applicants: Verasity Limited
- Inventors: Robert James Mark Hain
- Web page: https://patentgrep.com/patent/US12015712B2

## CPC

- G06F 16/9024: {Graphs; Linked lists (G06F16/9027 takes precedence)}
- H04L 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)}
- G06Q 20/065: {using e-cash}
- G06Q 20/3827: {Use of message hashing}
- G06Q 20/385: {using an alias or single-use codes}
- G06Q 20/40145: {Biometric identity checks}
- G06Q 20/4016: {involving fraud or risk level assessment in transaction processing}
- G06Q 30/0225: {Avoiding frauds}
- G06Q 30/0248: {Avoiding fraud}
- H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- H04L 9/3297: {involving time stamps, e.g. generation of time stamps}
- H04N 21/2407: {Monitoring of transmitted content, e.g. distribution time, number of downloads (arrangements for monitoring programmes for broadcast or for distribution combined with broadcast H04H20/14)}
- H04N 21/254: Management at additional data server, e.g. shopping server, rights management server {(arrangements for maintenance or administration in data networks H04L41/00; network services using third party service providers H04L67/53)}
- H04N 21/44222: {Analytics of user selections, e.g. selection of programmes or purchase activity (monitoring of user selections in data processing systems G06F11/34; arrangements for monitoring the user's behaviour or opinions in broadcast systems H04H60/33)}
- H04N 21/812: {involving advertisement data (advertising per se G06Q30/02)}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L 2209/56: Financial cryptography, e.g. electronic payment or e-cash
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- H04N: PICTORIAL COMMUNICATION, e.g. TELEVISION

## Abstract

A Proof of View verification system is disclosed. The Proof of View verification system has a Non-Fungible Token smart contract module, comprising computer-executable code stored in non-volatile memory, a Proof of View smart contract module, comprising computer-executable code stored in non-volatile memory, a processor, and a verifier network. The Non-Fungible Token smart contract module, the Proof of View smart contract module, the processor, and the verifier network are configured to transfer a data of a non-fungible token to the Non-Fungible Token smart contract module and generate an event metadata based on the data of the non-fungible token, transfer the event metadata to the Proof of View smart contract module, and generate an event hash using the verifier network and transferring the event hash from the verifier network to the Proof of View smart contract module.

## Claims

### Claim 1

A Proof of View verification system, comprising:
a Non-Fungible Token smart contract module, comprising computer-executable code stored in non-volatile memory;
a Proof of View smart contract module, comprising computer-executable code stored in non-volatile memory;
a processor; and
a verifier network;
wherein the Non-Fungible Token smart contract module, the Proof of View smart contract module, the processor, and the verifier network are configured to:
transfer a data of a non-fungible token to the Non-Fungible Token smart contract module and generate an event metadata based on the data of the non-fungible token;
transfer the event metadata to the Proof of View smart contract module; and
generate an event hash using the verifier network and transferring the event hash from the verifier network to the Proof of View smart contract module;
wherein generating the event hash includes generating a hashed database chunk and appending the hashed database chunk to a block on a blockchain.

### Claim 2 (depends on 1)

The Proof of View verification system of claim 1, further comprising a secure data storage.

### Claim 3 (depends on 2)

The Proof of View verification system of claim 2, wherein the Non-Fungible Token smart contract module, the Proof of View smart contract module, the processor, the verifier network, and the secure data storage are configured to transfer the event metadata and the event hash to the secure data storage and store the event metadata and the event hash in the secure data storage.

### Claim 4 (depends on 3)

The Proof of View verification system of claim 3, wherein the Non-Fungible Token smart contract module, the Proof of View smart contract module, the processor, the verifier network, and the secure data storage are configured to retrieve a metadata using the event hash stored in the secure data storage.

### Claim 5 (depends on 2)

The Proof of View verification system of claim 2, wherein the Non-Fungible Token smart contract module, the Proof of View smart contract module, the processor, the verifier network, and the secure data storage are configured to assign a storage identification data to the event hash stored in the secure data storage.

### Claim 6 (depends on 1)

The Proof of View verification system of claim 1, wherein the Non-Fungible Token smart contract module, the Proof of View smart contract module, the processor, and the verifier network are configured to verify a proposed event metadata by using the Proof of View smart contract module and the verifier network to compare the proposed event metadata to the event metadata.

### Claim 7 (depends on 6)

The Proof of View verification system of claim 6, wherein the Non-Fungible Token smart contract module, the Proof of View smart contract module, the processor, and the verifier network are configured to transfer a verification result data to a user based on comparing the proposed event metadata to the event metadata.

### Claim 8 (depends on 6)

The Proof of View verification system of claim 6, wherein the proposed event metadata is data of ownership of the non-fungible token.

### Claim 9 (depends on 1)

The Proof of View verification system of claim 1, wherein the data of the non-fungible token is non-fungible token creation data that is recorded to the Proof of View smart contract module as the event hash.

### Claim 10 (depends on 1)

The Proof of View verification system of claim 1, wherein the data of the non-fungible token is data of changes to the metadata of the non-fungible token that is recorded to the Proof of View smart contract module as the event hash.

### Claim 11 (depends on 1)

The Proof of View verification system of claim 1, wherein the data of the non-fungible token is data of a sale or a destruction of the non-fungible token that is recorded to the Proof of View smart contract module as the event hash.

### Claim 12 (depends on 1)

The Proof of View verification system of claim 1, wherein the Non-Fungible Token smart contract module, the Proof of View smart contract module, the processor, and the verifier network are configured to convert the non-fungible token to a Proof of View enabled non-fungible token.

### Claim 13

A method, comprising:
providing a Non-Fungible Token smart contract module, comprising computer-executable code stored in non-volatile memory;
providing a Proof of View smart contract module, comprising computer-executable code stored in non-volatile memory;
providing a verifier network;
transferring a data of a non-fungible token to the Non-Fungible Token smart contract module and generating an event metadata based on the data of the non-fungible token;
transferring the event metadata to the Proof of View smart contract module; and
generating an event hash using the verifier network and transferring the event hash from the verifier network to the Proof of View smart contract module;
wherein generating the event hash includes generating a hashed database chunk and appending the hashed database chunk to a block on a blockchain.

### Claim 14 (depends on 13)

The method of claim 13, further comprising transferring the event metadata and the event hash to a secure data storage and storing the event metadata and the event hash in the secure data storage.

### Claim 15 (depends on 14)

The method of claim 14, further comprising retrieving a metadata using the event hash stored in the secure data storage.

### Claim 16 (depends on 14)

The method of claim 14, further comprising assigning a storage identification data to the event hash stored in the secure data storage.

### Claim 17 (depends on 13)

The method of claim 13, further comprising verifying a proposed event metadata by using the Proof of View smart contract module and the verifier network to compare the proposed event metadata to the event metadata.

### Claim 18 (depends on 17)

The method of claim 17, further comprising transferring a verification result data to a user based on comparing the proposed event metadata to the event metadata.

### Claim 19

A Proof of View verification system, comprising:
a Non-Fungible Token smart contract module, comprising computer-executable code stored in non-volatile memory;
a Proof of View smart contract module, comprising computer-executable code stored in non-volatile memory;
a processor;
a verifier network; and
a secure data storage;
wherein the Non-Fungible Token smart contract module, the Proof of View smart contract module, the processor, the verifier network, and the secure data storage are configured to:
transfer a data of a non-fungible token to the Non-Fungible Token smart contract module and generate an event metadata based on the data of the non-fungible token;
transfer the event metadata to the Proof of View smart contract module;
generate an event hash using the verifier network and transfer the event hash from the verifier network to the Proof of View smart contract module;
transfer the event metadata and the event hash to the secure data storage and store the event metadata and the event hash in the secure data storage; and
assign a storage identification data to the event hash stored in the secure data storage;
wherein generating the event hash includes generating a hashed database chunk and appending the hashed database chunk to a block on a blockchain.

### Claim 20 (depends on 19)

The Proof of View verification system of claim 19, wherein the Non-Fungible Token smart contract module, the Proof of View smart contract module, the processor, the verifier network, and the secure data storage are configured to retrieve a metadata using the event hash stored in the secure data storage.

### Claim 21 (depends on 19)

The Proof of View verification system of claim 19, wherein the Non-Fungible Token smart contract module, the Proof of View smart contract module, the processor, the verifier network, and the secure data storage are configured to verify a proposed event metadata by using the Proof of View smart contract module and the verifier network to compare the proposed event metadata to the event metadata.