CN117678189A

CN117678189A - View attestation system and method implemented by blockchain

Info

Publication number: CN117678189A
Application number: CN202280050338.0A
Authority: CN
Inventors: 罗伯特·詹姆斯·马克·海恩
Original assignee: Luo BoteZhanmusiMakeHaien
Current assignee: Luo BoteZhanmusiMakeHaien
Priority date: 2021-05-24
Filing date: 2022-05-13
Publication date: 2024-03-08
Also published as: CA3219456A1; KR20240024108A; WO2022248965A1; EP4348916A1; AU2022279661A1

Abstract

A view attestation verification system is disclosed. The view attestation verification system has a non-homogenous token smart contract module including computer executable code stored in non-volatile memory, a view attestation smart contract module including computer executable code stored in non-volatile memory, a processor, and a verifier network. The non-homogenous token smart contract module, the view attestation smart contract module, the processor, and the verifier network are configured to communicate data of the non-homogenous token to the non-homogenous token smart contract module and generate event metadata based on the data of the non-homogenous token, communicate the event metadata to the view attestation smart contract module, generate an event hash using the verifier network, and communicate the event hash from the verifier network to the view attestation smart contract module.

Description

View attestation system and method implemented by blockchain

Technical Field

The present disclosure relates to an automated system and method for providing (e.g., ensuring) the integrity of views (views) of online content. Embodiments of the present invention verify the authenticity of a view of content by generating and ensuring a proof of view (PoV) of the content using a blockchain. Generating a proof of view (proof of view) of the content may be used to determine the integrity of the content provider channel value, and thus the integrity of the content market exchange or Channel Share Market (CSM).

Background

Currently, views on large platforms are suspect and often counterfeited. The views are primarily used to evaluate and measure traffic on the content provider website, and then their sponsors and advertising revenues come from the view quantity. If the view is counterfeited, altered or manipulated, the economic benefits of the content provider may be distorted. In particular, google and Facebook modes rely on view counts, and content providers are fully compensated for the number of views, even though most of the counted views may not be present.

There is currently no efficient technique to transparently verify view conditions. The integrity and transparency of the view determines the value of the content provider channel. Without a system to verify the integrity of the view, it is difficult for advertisers and content providers to determine the actual value of the channel. Accordingly, there is a need in the art for a system and method for determining the integrity of the channel value of a content provider and, therefore, the integrity of a content marketplace exchange.

Furthermore, there are many drawbacks in conventional systems with regard to attribution, content, and view of non-homogenous tokens (NFTs). For example, existing legacy systems have problems with verifiability of NFT content and explicit attribution of author rights. Further, fraud is typically caused by the inability to verify the authenticity of the NFT. Furthermore, conventional systems often fail to adequately prevent or protect NFT content from being viewed and/or copied by any party other than its owner, where appropriate. Furthermore, conventional systems often fail to provide explicit attribution to events, actions, and other non-material and/or non-digital topics. Also, conventional systems often fail to provide availability of actual content. For example, image links contained in NFTs using conventional systems typically become ineffective over time.

The disclosed example systems and methods are directed to overcoming one or more of the disadvantages set forth above and/or other disadvantages in the prior art.

Disclosure of Invention

In one exemplary aspect, the present disclosure is directed to a view attestation verification system. The view attestation verification system includes a non-homogenous token smart contract module including computer executable code stored in non-volatile memory, a view attestation smart contract module including computer executable code stored in non-volatile memory, a processor, and a verifier network. The non-homogenous token smart contract module, the view attestation smart contract module, the processor, and the verifier network are configured to communicate data of the non-homogenous token to the non-homogenous token smart contract module and generate event metadata based on the data of the non-homogenous token, communicate the event metadata to the view attestation smart contract module, generate an event hash using the verifier network, and communicate the event hash from the verifier network to the view attestation smart contract module. Generating the event hash includes generating a hash database chunk and appending the hash database chunk to a block on the blockchain.

In another exemplary aspect, the present disclosure is directed to a method. The method comprises the following steps: providing a non-homogenous token smart contract module comprising computer executable code stored in non-volatile memory; providing a view attestation smart contract module including computer executable code stored in non-volatile memory; providing a verifier network; the method includes transmitting data of a non-homogenous token to a non-homogenous token smart contract module and generating event metadata based on the data of the non-homogenous token, transmitting the event metadata to a view proving smart contract module, generating an event hash using a verifier network and transmitting the event hash from the verifier network to the view proving smart contract module. Generating the event hash includes generating a hash database chunk and appending the hash database chunk to a block on the blockchain.

In another exemplary aspect, the present disclosure is directed to a view attestation verification system. The view attestation verification system includes a view attestation verification module including computer executable code stored in non-volatile memory and a processor. The view attestation verification module and processor are configured to receive a request for a view of content to view a piece of content, record the view data in a database chunk, hash the database chunk into a hashed database chunk, append the hashed database chunk to a chunk on a blockchain of the view attestation verification system, and compare the view data with the chunk on the blockchain. Blockchains may be publicly available.

In another exemplary aspect, the present disclosure is directed to a method. The method includes receiving a request to sell shares of a channel share market, determining a value of the channel, generating a share distribution based on the value of the channel, and updating the value of the channel. Determining the value of the channel includes determining a content view of the verified channel. Determining the content view amount of the verified channel includes recording the content view data in a database chunk, hashing the database chunk into a hashed database chunk, appending the hashed database chunk to a chunk on a blockchain, and comparing the content view data to the chunk on the blockchain.

Drawings

Attached to the specification is a set of drawings of exemplary embodiments of the present disclosure. Those of ordinary skill in the art will understand that these are merely exemplary embodiments, and that additional and alternative embodiments may exist and remain within the spirit of the disclosure described herein.

FIG. 1 is a schematic diagram of an exemplary computing device in accordance with at least some exemplary embodiments of the invention;

FIG. 2 is a schematic diagram of an exemplary network in accordance with at least some exemplary embodiments of the invention;

FIG. 3 is a diagram of an exemplary hash of a chunk database used in conjunction with a PoV blockchain, according to an embodiment of the present invention;

FIG. 4 is a diagram of an exemplary method for providing view attestation through a blockchain in accordance with embodiments of the invention;

FIG. 5 is an illustration of an exemplary method for providing a channel share market with view certification through a blockchain in accordance with embodiments of the invention; and

fig. 6 is a diagram illustrating exemplary operation of at least some exemplary embodiments of the invention.

Detailed Description

In accordance with embodiments of the present invention, the exemplary systems and methods described herein are used to ensure the integrity and transparency of views of online content in order to determine the value of the content provider's channels. The proof of view (PoV) method is used to provide a transparent system that determines the integrity of such views.

According to an embodiment of the invention, view attestation is utilized within the system to determine the integrity of the content provider channel value and, thus, the integrity of the provided content marketplace exchange. In at least some example embodiments, to ensure accurate and transparent view attestation, the system implements a publicly auditable log. These logs may contain, for example, data associated with the content view, content recommendations, anonymous information about users viewing the content, other relevant data points, or any combination thereof. Those of ordinary skill in the art will appreciate that there are a plurality of data points that may be used with embodiments of the present invention, and embodiments of the present invention contemplate the use of any suitable data points.

In one embodiment of the invention, the Merkle hash tree will be used to minimize the amount of data to be stored while still maintaining the assurance that the database has never been changed. In the hash tree, each view is hashed before being combined with other hashes until a final top hash (top hash) is reached. Each top hash may represent all data stored in a particular data log. Those of ordinary skill in the art will appreciate that there are a variety of methods for hashing a chunk of data, and that embodiments of the present invention contemplate the use of any suitable method of hashing and storing a chunk of data.

Those of ordinary skill in the art will appreciate that there are a variety of hash algorithms that may be used with embodiments of the present invention, and embodiments of the present invention contemplate the use of any suitable hash algorithm.

In an exemplary embodiment of the invention, the system utilizes a database that is partitioned into chunks. In an exemplary embodiment, each time a new chunk is created in the PoV blockchain, a new chunk may be created. The top hash of the current chunk is added to each new chunk in the PoV blockchain. For example, an exemplary embodiment is shown in fig. 3. In alternative embodiments, the entire database may be a single file, or the entire database may be stored in a blockchain. In still other embodiments, the frequency with which the database is published to the PoV blockchain may be less than the frequency with which blocks are created each time. Those of ordinary skill in the art will appreciate that there are a variety of ways to format and record databases on blockchains, and that embodiments of the present invention contemplate the use of any suitable formatting and recording method.

In at least some example embodiments of the present invention, the entire database may be stored in a blockchain. Each view log entry may be stored in the blockchain as a separate transaction or data entry. View log entry transactions may also act as view rewards transfer transactions. View log entries may be published to the blockchain by viewers and/or by the system such that, for example, neither party can review the log entries. For another example, the entire PoV chunk may be stored in the blockchain as a single transaction or data entry. In still other embodiments, the frequency with which the database is published to the PoV blockchain may be less than the frequency with which blocks are created each time. The databases on the blockchain may be formatted and recorded using any suitable technique. The exemplary embodiments disclosed herein may be used with any suitable formatting and/or recording method.

In at least some example embodiments of the invention, the system may be configured to use advanced methods to ensure that only views verified by the PoV method are counted. According to these embodiments, views that are considered to be verified will be added to a publicly accessible database containing anonymous data about the views. In alternative embodiments, the system may be configured with an open source tool to ensure transparency and accountability of the system. With these tools, the user and third party can review the data to ensure its accuracy and trustworthiness. Although the view data may be anonymous, individual users may generate their own unique IDs to verify whether the views recorded for their IDs are accurate and not manipulated. According to these embodiments, to ensure that the data stored within the publicly accessible PoV database reflects actual data that is authentic, some or substantially all of the view data may be sent to both the verification system and to the server hosting the content. This allows the system to automatically check whether the data in the view database of the server is accurate and not altered. In some embodiments of the invention, the system further includes an application that automatically checks whether a view on the blockchain is verified and matches a view on the public database. The system may automatically provide an alert notification if there is any corruption or alteration of the detected data. In this way, the system prevents multiple ways that the user might try to manipulate view counts and audience metrics as follows: (i) automatically repeating viewing of video (cyclic viewing); (ii) attempting to load multiple videos in parallel; (iii) loading video in the hidden window/tab; and (iv) attempting to manipulate the analysis without actually viewing the video. Alternatively, in at least some example embodiments, the example disclosed PoV databases may be stored using, for example, a computing device as described herein with respect to fig. 1 and 2. For example, the computing devices described herein with respect to fig. 1 and 2 may allow or prevent (e.g., disallow) free access to the exemplary disclosed PoV database and view data attestation.

In at least some example embodiments of the invention, the system provides for internal market trading of shares in a content channel. Thus, the system enables content creators/publishers to fund additional growth and development of their content by issuing shares in their channels and future content products. According to embodiments of the present invention, a creator/publisher may sell a portion of its channels to stakeholders at a price set by the creator/publisher. The sales may be made in encrypted currency, partial ownership issues, or other currency or similar issues. In at least some example embodiments, participation in a channel may provide the same percentage of future revenue to stakeholders in the channel based on their ownership in the channel. In some cases, stakeholders in the channel may resell their shares through the content market exchange based on the current market value of the shares. Much like other markets (e.g., securities markets), restrictions or constraints may be imposed on the transfer based on one or more preset rules. Those of ordinary skill in the art will appreciate that there are numerous rules and limitations that may be utilized and that embodiments of the present invention contemplate the use of any suitable rules or limitations.

According to an embodiment of the invention, the system calculates the current market value of the shares in the channel. In at least some example embodiments of the invention, the system calculates the value of shares in the channel by considering one or more data points selected from the group including, but not limited to, a verification view (PoV) of the content, a revenue source of the channel, a recommendation engine, and other key parameters. Those of ordinary skill in the art will appreciate that there are many key parameters and other data points that can be used to calculate the share value in a channel as well as the total channel value, and that embodiments of the present invention contemplate the use of any such data points and key parameters. In fact, the system provides a trade that works much like an on-line spot trade where buyers can bid/offer and set limits on buying or selling available shares on the trade index.

Turning now to FIG. 1, an illustrative representation of a computing device suitable for use with embodiments of the system of the present disclosure is shown. The computing device 100 may generally include: a central processing unit (CPU, 101), optionally further processing units, comprising a Graphics Processing Unit (GPU); random access memory (RAM, 102); motherboard 103, or alternatively/additionally, a storage medium (e.g., hard disk drive, solid state drive, flash memory, cloud storage); an operating system (OS, 104); one or more application software 105; a display element (e.g., monitor, capacitive touch screen) 106; and one or more input/output devices/means 107 including one or more communication interfaces (e.g., RS232, ethernet, wifi, bluetooth, USB). Useful examples include, but are not limited to, personal computers, servers, tablets, smartphones, or other computing devices. In a preferred embodiment of the present invention, multiple computing devices may be operatively linked in a manner that distributes and shares one or more resources to form a computer network (e.g., a clustered computing device and a server farm/cluster).

Various examples of such general multi-unit computer networks, their typical configurations, and many standardized communication links suitable for embodiments of the present disclosure are well known to those skilled in the art, as explained in more detail and illustrated by fig. 2, which will be discussed below.

According to exemplary embodiments of the present disclosure, data may be transferred to, stored by, and/or transferred by a Local Area Network (LAN) or Wide Area Network (WAN) to a user of the system. According to the previous embodiment, the system may include a plurality of servers, mining hardware, computing devices, or any combination thereof, communicatively connected via one or more LANs and/or WANs. Those of ordinary skill in the art will appreciate that there are numerous ways in which a system may be configured, and that embodiments of the present disclosure contemplate the use of any configuration.

Referring to fig. 2, a schematic overview of a system according to an embodiment of the present disclosure is shown. The system includes one or more application servers 203 for electronically storing information used by the system. Applications in server 203 may retrieve and manipulate information in storage and exchange information over WAN201 (e.g., the internet). Applications in server 203 may also be used to manipulate remotely stored information and process and analyze data stored remotely over WAN201 (e.g., the internet).

According to an exemplary embodiment, as shown in FIG. 2, information exchange over WAN 201 or other network may occur over one or more high-speed connections. In some cases, the high-speed connection may be over-the-air (OTA), through a networked system, directly to one or more WANs 201, or directed through one or more routers 202. The routers 202 are entirely optional and one or more routers 202 may or may not be utilized in accordance with other embodiments of the present disclosure. Those of ordinary skill in the art will appreciate the variety of ways in which the presence server 203 may be connected to the WAN 201 to exchange information, and that embodiments of the present disclosure contemplate the use of any method of connecting to a network to exchange information. Further, while the present application relates to high speed connections, embodiments of the present disclosure may use any speed connection.

The components or modules of the system may be connected to the server 203 through the WAN 201 or other network in a variety of ways. For example, a component or module may be connected to a system by: i) Through computing device 212 directly connected to WAN 201, ii) through computing devices 205, 206 connected to WAN 201 via routing device 204, or iii) through computing devices 208, 210 connected to wireless access point 207. Those of ordinary skill in the art will appreciate that there are numerous ways in which components or modules may be connected to the server 203 through the WAN 201 or other network, and that embodiments of the present disclosure contemplate using any method of connecting to the server 203 through the WAN 201 or other network. Further, server 203 may include a personal computing device, such as a smart phone, that acts as a host to which other computing devices are connected.

The communication device of the system may be any circuit or other device for transmitting data over one or more networks or to one or more peripheral devices attached to the system, or system modules or components. Suitable communication means may include, but are not limited to, a wireless connection, a wired connection, a cellular connection, a data port connection,A connection, a Near Field Communication (NFC) connection, or any combination thereof. Common in the artThe skilled artisan will appreciate that there are a variety of communication devices that can be used with embodiments of the present disclosure, and embodiments of the present disclosure contemplate the use of any communication device.

The exemplary disclosed systems and methods may be used in any suitable application that provides for visual attestation (PoV) of online content. For example, the exemplary disclosed systems and methods may be used in any suitable application to ensure that content, such as internet content, available on the internet, has actually been viewed by users, such as consumers. The exemplary disclosed systems and methods may be used, for example, in any application that provides a PoV (e.g., verifying that a user actually views content) affects the valuation or compensation of a given website or platform (e.g., based on advertising revenue associated with the number of users viewing content).

Turning now to FIG. 4, an exemplary method for providing view attestation through a blockchain is shown in accordance with an embodiment of the present invention. The process begins at 400 with the system providing a PoV for one or more online content. At step 402, the system receives a content view event, typically by a user requesting to view a piece of content. The content may be any form of text, graphics, multimedia or other audio/video or other digital or analog work. Those of ordinary skill in the art will appreciate that there are many types of content that can be used with embodiments of the present invention and that embodiments of the present invention contemplate the use of any suitable type of content. An exemplary disclosed content view may include content viewed using any desired web browser (e.g., google Chrome, apple Safari, microsoft Internet Explorer, mozilla Firefox, opera, or any other suitable web browser). The exemplary disclosed content views may also include content viewed using any suitable Application Programming Interface (API) or application (e.g., a mobile device application, a web application, a hybrid application, or any other suitable type of application). The exemplary disclosed content views may also include content viewed on any suitable device (e.g., a smart television or any other suitable type of streaming media device).

At step 404, the content views are recorded by the system and those associated with the system, as the system includes those that mine and record transactions (e.g., views) on the system's associated blockchain. The view record may be digitally signed by the viewer and/or the system. In an exemplary embodiment of the present invention, the chunks of the database where the view may be recorded are then hashed (step 406). Any suitable digital signature scheme may be used with the exemplary embodiments of this invention, and the exemplary embodiments of this invention may be used with any suitable type of digital signature.

At step 408, each hash database chunk will be appended to a chunk on the blockchain ledger at the next entry for the chunk on the blockchain. At this point, each recorded view can be verified at any time as the PoV blockchain is available for review. Since the data is stored in an off-centered manner, any third party can prove that each top hash added to the PoV blockchain is accurate and unchanged. This allows any third party to verify that the log added within each new chunk on the blockchain has not been tampered with, altered, branched or forked. At this point, the process ends at step 410.

Turning now to FIG. 5, an illustration of an exemplary method for providing a channel share market with view certification through a blockchain is shown in accordance with an embodiment of the present invention. The process begins at step 500, where a user issues a request to sell shares in a channel. The system receives a request to sell shares at step 502 and parses the information in the request for use in generating a share distribution. The information associated with the request may include, but is not limited to, the size of the share offered (e.g., total amount of money, cryptocurrency or other compensation desired from the sale, or maximum percentage of channels offered).

At step 504, the system generates the value of the channel involved in the distribution of the shares. In at least some example embodiments, the value of a channel may be based on the number of verified content views retrieved from a PoV blockchain associated with the system or channel. Other data points may also be used to generate the value including, but not limited to, the growth rate of the channel, the number of subscribers to the channel, the history of the channel and stock release, or any combination thereof. Those of ordinary skill in the art will appreciate that there are a large number of data points that can be used with embodiments of the present invention to determine the value of a channel, and that embodiments of the present invention contemplate the use of any suitable data points.

At step 506, the system generates a share distribution based at least in part on the channel value and/or information associated with the request. Once generated, the system provides the generated share distribution to the user (step 508). A share distribution may be purchased at step 510.

If no shares are purchased, the system may reissue the shares for sale. In some embodiments, the share distribution may be recalculated at one or more points, for example, by recalculating the sales price for each of the channels, or by reevaluating the channel value, before the shares are reissued for sale.

If the share distribution is successful and underwrited, the system will distribute the relevant shares to those who invest in the channel or otherwise purchase the shares (step 512). Rights and revenues may then be transferred to the purchasing user as specified in the share distribution.

At step 514, the system continues to monitor and update channel value as shares are issued to various purchasers. The user who purchased the shares can sell part of his own shares to others as long as the share distribution rules allow. Generally, the issue will be priced at the current price of the system. However, in other embodiments, the system may allow for more complex means of trading (e.g., offers, options). At this point, the process terminates at step 516.

In at least some example embodiments, an example view attestation verification system may include a view attestation verification module including computer executable code stored in non-volatile memory and a processor. The view attestation verification module and processor may be configured to receive a request for a view of content to view a piece of content, record content data in a database chunk, hash the database chunk into a hashed database chunk, append the hashed database chunk to a chunk on a blockchain of the view attestation verification system, and compare the content view data to the chunk on the blockchain. Blockchains may be publicly available. The blockchain may be available for review by any third party. Each top hash added to the blockchain may be audited by any third party. Each new block added to the blockchain may be audited by any third party. The content segments may be text data, graphics data, multimedia data, audio data, and/or visual data. The content view may be an internet web page view. The view attestation verification system may include multiple parties that participate in mining and recording transactions on a blockchain. The view attestation verification module and the processor may be configured to provide a unique ID to a user, the unique ID being associated with data on the blockchain corresponding to content view data of the user. The user may use the unique ID to ensure (e.g., compare) that the data on the blockchain corresponding to the user's content view data is accurate. The view attestation verification system may automatically compare the content view data to the tiles on the blockchain. The view attestation verification system may automatically provide alert notifications when content view data does not match a tile. The view attestation verification system may be separate (e.g., substantially completely separate) from any entity or party. For example, the view attestation verification system may be an off-centered financial system that may operate without a central financial entity. The view attestation verification system may utilize a smart contract on a blockchain similar to, for example, the exemplary disclosed blockchain described herein. For example, the view attestation verification system may utilize a de-centralization application using blockchain, such as described herein, to perform financial functions. In at least some example embodiments, the view attestation verification system can utilize intelligent contracts on blockchains to capture, verify, and authenticate (e.g., and enforce) contract terms between agreed-upon parties. Thus, the view attestation verification system may provide protocols and transactions performed between entities (e.g., anonymous entities) without the use of a central entity or external law enforcement. For example, the view attestation verification system may allow data of the smart contract to be encrypted and exist on the blockchain (e.g., data recorded in the blockchain may not be modified, lost, or deleted).

In at least some example embodiments, an example method may include receiving a request to sell shares of a channel share market, determining a value of the channel, generating a share distribution based on the value of the channel, and updating the value of the channel. Determining the value of the channel may include determining a content view of the verified channel. Determining the content view quantity of the verified channel may include recording the content view data in a database chunk, hashing the database chunk into a hashed database chunk, appending the hashed database chunk to a chunk on a blockchain, and comparing the content view data to the chunk on the blockchain. The value of the channel may be based on the number of verified content views retrieved from the blockchain. The example method may further include issuing channel shares to users who issue purchase channel shares based on the shares. The value of a channel may be based on data points such as the growth rate of the channel, the number of subscribers of the channel, the history of the channel, and/or the history of stock distribution. Updating the value of the channel may include determining an update amount of the content view of the verified channel.

In at least some example embodiments, the method may include receiving a request for a view of content to view a piece of content, recording the view of content data in a database chunk, hashing the database chunk into a hashed database chunk, appending the hashed database chunk to a chunk on a blockchain, and comparing the view of content data to the chunk on the blockchain. Each new block added to the blockchain may be auditable by any third party. The content view may be an internet web page view. The example method may further include providing the user with a unique ID associated with data on the blockchain corresponding to the user's content view data. The user may use the unique ID to ensure (e.g., compare) that the data on the blockchain corresponding to the user's content view data is accurate.

In at least some example embodiments, an example disclosed view attestation verification system may include a view attestation verification module including computer executable code stored in non-volatile memory, a processor, and a plurality of computing devices. The view attestation verification module, processor, and plurality of computing devices may be configured to receive a request to sell shares of a channel, determine a value of the channel, generate a share distribution based on the value of the channel, and update the value of the channel. Determining the value of the channel may include determining a content view of the verified channel. Determining the verified content view quantity may include transmitting data of the content segments between the plurality of computing devices. Determining the content view quantity of the verified channel may include providing unique ID data to the user, recording content view data corresponding to the data of the transmitted content segments in a database chunk, hashing the database chunk into a hashed database chunk, appending the hashed database chunk to a chunk on the blockchain, and comparing the content view data to the chunk by determining whether both the content view data and the chunk on the blockchain contain unique ID data. The blockchain may be publicly available and accessible through a third party computing device. The view attestation verification module, the processor, and the plurality of computing devices may also be configured to issue shares of a channel to a user based on the share issue purchase channel shares and utilize intelligent contracts on the blockchain. The blockchain may be available for review by any third party. Each top hash added to the blockchain may be auditable by any third party. Each new block added to the blockchain may be auditable by any third party. The data of the content segments may be selected from the group consisting of text data, graphics data, multimedia data, audio data, and visual data. The verified content view may be selected from the group of an internet web view, an application view, a streaming media device view including a smart television view, and combinations thereof. Transferring data of content segments between multiple computing devices may include streaming video data between the multiple computing devices over a local area network or a wide area network. The view attestation verification system may include multiple parties that participate in mining and recording transactions on a blockchain. The view attestation verification module, the processor, and the plurality of computing devices may be configured to compare the content view data with the unique ID data to ensure that data on the blockchain corresponding to the content view data of the user is accurate. The view attestation verification system may automatically compare the content view data to the tiles on the blockchain. The view attestation verification system may provide an alert notification when the content view data does not include unique ID data.

In at least some example embodiments, the example disclosed methods may include receiving a request to sell shares of a channel, determining a value of the channel, generating a share distribution based on the value of the channel, and updating the value of the channel. Determining the value of the channel may include determining a content view of the verified channel. Determining the verified content view quantity may include transmitting data of the content segments between the plurality of computing devices. Determining the content view quantity of the verified channel may include providing unique ID data to the user, recording content view data corresponding to the data of the transmitted content segments in a database chunk, hashing the database chunk into a hashed database chunk, appending the hashed database chunk to a chunk on the blockchain, and comparing the content view data to the chunk by determining whether the content view data and the chunk on the blockchain contain unique ID data. The blockchain may be publicly available and accessible through a third party computing device. The exemplary disclosed method may further include issuing channel shares to users who issue purchase channel shares based on the shares, and utilizing intelligent contracts on the blockchain. The value of the channel may be based on the number of verified content views retrieved from the blockchain. The value of a channel may be based on data points from the group consisting of the rate of growth of the channel, the number of subscribers of the channel, the history of the channel, and the history of stock release. Updating the value of the channel may include determining an update amount of the content view of the verified channel.

In at least some example embodiments, the example disclosed methods may include receiving a request to sell shares of a channel, determining a value of the channel, generating a share distribution based on the value of the channel, and updating the value of the channel. Determining the value of the channel may include determining a content view of the verified channel. Determining the verified content view quantity may include transmitting data of the content segments between the plurality of computing devices. Determining the content view quantity of the verified channel may include providing unique ID data to the user, recording content view data corresponding to the data of the transmitted content segments in a database chunk, hashing the database chunk into a hashed database chunk, appending the hashed database chunk to a chunk on the blockchain, and comparing the content view data to the chunk by determining whether the content view data and the chunk on the blockchain contain unique ID data. The exemplary disclosed method may further include issuing channel shares to users who issue purchase channel shares based on the shares. The blockchain may be publicly available and accessible through a third party computing device. The content view data may be stored on a computing device that prevents public access to the content view data. The value of the channel may be based on the number of verified content views retrieved from the blockchain. The value of the channel may be based on data points selected from the group consisting of the growth rate of the channel, the number of subscribers of the channel, the history of the channel, and the history of stock release.

Fig. 6 illustrates another exemplary embodiment of the exemplary disclosed systems and methods. Fig. 6 illustrates an exemplary process for providing a PoV of a non-homogenous token (NFT). NFT may be represented by tokens, records, and/or any other suitable type of blockchain item. NFT may operate in conjunction with a smart contract executing in a blockchain using a smart contract module (e.g., manipulated through the smart contract). As exemplarily disclosed herein, the exemplary disclosed systems and methods may include an NFT smart contract module and a PoV smart contract module. NFT may also be implemented through a blockchain network, such as a proprietary blockchain network (e.g., NFT may be an integral part of a blockchain network, without involving a smart contract). In at least some example embodiments, NFT may be used in conjunction with non-blockchain use cases such as centralized storage. For example, the centralized storage may be operated by a trusted organization or one or more entities (e.g., multiple parties) that may be responsible for the integrity and accessibility of some or substantially all of the NFT content data (e.g., may be stored in the CDN, a database, a file server, and/or any other suitable technique for storing data).

The exemplary disclosed NFT may be a unique token that may be recorded in a blockchain and may include metadata describing the content, author, ownership, and/or any other suitable data or details of the NFT. For example, the NFT may be included (e.g., may exist) in a dedicated blockchain (e.g., serving a purpose associated with the PoV of the NFT). For another example, NFT may be included (e.g., may exist) in any suitable blockchain for supporting smart contracts (e.g., ethernet), or any other suitable type of executable file that may interact with the blockchain. For example, NFT agent intelligence contracts may be deployed to ethernet blockchains. For example, an NFT agent intelligence contract may represent a core entry point that interacts with (e.g., processes) NFTs on a blockchain. The NFT agent intelligence contract may pass any suitable function call to its child intelligence contract (e.g., containing the actual script for providing the function). Possession of the proxy smart contract may allow for efficient (e.g., simple) security and functional upgrades of NFTs by maintaining or maintaining the same original smart contract address while changing the underlying smart contract that represents the NFT logic (e.g., in the future).

For another example, a DeFi NFT may operate similar to that described above for the NFT agent Smart contracts, but may not include or involve a centralized Smart contract that manages the NFT (e.g., part or all of the NFT). In at least some example embodiments, a decentralized short lifecycle intelligence contract may be used to manage NFT operations. For another example, in at least some example embodiments, the NFT may be included in or exist outside of a blockchain that uses strong cryptography that may protect the content of the NFT.

The exemplary disclosed NFT may include any suitable metadata. For example, an exemplary disclosed NFT may include metadata for a token type and/or a token version. The exemplary disclosed NFT may also include author metadata such as author name, author address, author contact information, and/or author signature. The exemplary disclosed NFT may include metadata including license information, current owner metadata, content hash metadata, and/or extension metadata.

The exemplary disclosed NFT may include any suitable type of NFT content. For example, an exemplary disclosed NFT may include one or more data files including image data, audio recording data, video data, program source code, executable scripts, compiled executable programs, digital items, data sets, and/or any other suitable data file. The exemplary disclosed NFT content may include one or more events, a series of events, a set of independent events, and/or any other suitable event. Exemplary disclosed NFT content may also include ranking or title information, trophy information, achievement information, web page information, address or other identifier information, information related to business secrets, information about proprietary technology, invention or research information, industrial project information, research information, and/or information about physical objects. Exemplary disclosed NFT content may include information regarding technical drawings, charts, plans, procedures, and/or methods. The exemplary disclosed NFT content may also include information about rights, such as ownership, admission permissions, priority, author rights, and/or any other suitable rights.

The exemplary disclosed NFT may include any suitable type of attribute. NFT attributes may include author and/or creator attributes such as digital signatures, biometric signatures, virtual signatures, unsigned, and/or any other suitable author and/or creator attribute types. NFT attributes may include owner attributes such as exclusive owners, partial owners, tenants, licensees, and/or any other suitable owner attribute type. NFT attributes may also include viewer or user attribute types.

The exemplary disclosed systems and methods may involve or include any suitable type of NFT action, such as creating an NFT, transferring or selling (e.g., allocating) an NFT, editing or modifying an NFT, renting an NFT, viewing an NFT, revealing hidden NFT content, locking an NFT and/or destroying or disabling an NFT.

The exemplary disclosed systems and methods may include any suitable features, processes, and/or characteristics related to NFT lifecycle. For example, the exemplary disclosed systems and methods may include any suitable features, processes, and/or characteristics associated with creating NFTs. An author or delegated creator may cast an NFT of desired content (e.g., particular content) using any suitable technique. For example, the exemplary disclosed systems and methods may use open source programs or applications (e.g., casting applications) or online casting resources (e.g., casting websites) that may be dedicated to the purpose of casting NFTs. For another example, NFT may be cast based on direct interactions (e.g., user direct interactions) of NFT intelligence contracts on a blockchain. In at least some example embodiments (e.g., in use cases) in which a blockchain (e.g., a dedicated blockchain) is used to operate the NFT, casting may be provided (e.g., may be held) based on direct interaction with the blockchain (e.g., based on a user interacting directly with the blockchain) and/or by a casting program or application such as a casting application or casting website. In at least some example embodiments, the creator of the NFT may provide metadata and/or content of the NFT prior to the start of casting. The NFT metadata and/or content may then be processed by any suitable technique, such as a program or application (e.g., a casting application), a casting website, a smart contract, and/or a blockchain.

In at least some example embodiments, new tokens may be recorded in the blockchain as a result of NFT creation operations and stored at a desired (e.g., specific) blockchain address (e.g., wallet) with additional metadata including information provided during creation. For example, the metadata may include a unique NFT content hash that may be used to identify NFT content. For another example, NFT content may be transferred (e.g., data sent) to a data store (e.g., a secure data store, such as a secure vault) as shown in fig. 6 (e.g., to confirm or ensure its presence according to the terms of the secure vault). NFT creation (e.g., successful NFT creation) may be logged to a PoV network (e.g., similar to the example disclosed PoV systems described herein, which may operate as a PoV of an NFT system with the example disclosed NFT systems and methods) and may be used for future reference and verification.

The exemplary disclosed NFT may be non-variable (e.g., by design). For example, changes (e.g., any changes) made to the metadata of the NFT may trigger the issuance of copies of the NFT with the changed metadata and/or the destruction of the original NFT. These changes may be recorded by a PoV (e.g., similar to the exemplary disclosed PoV system described herein, which may operate as a PoV of an NFT system with the exemplary disclosed NFT systems and methods) for future reference and verification.

The exemplary disclosed systems and methods may include any suitable features, processes, and/or characteristics associated with selling NFTs. The sale (e.g., NFT ownership sale) may be made between the current owner of the NFT and the buyer of the NFT. Ownership of the NFT may also be sold, transferred, licensed, or otherwise transferred using a third party entity or platform (e.g., auction, hosting service, and/or any suitable marketplace). The current ownership of the NFT may be verified by checking one or more corresponding records in the PoV network (e.g., similar to the example disclosed PoV system described herein, which may operate as a PoV of the NFT system with the example disclosed NFT systems and methods) using verification software, verification websites, and/or any other suitable technique. In at least some example embodiments, the buyer may pay a price for the NFT and the seller may send the NFT token to the buyer's wallet or make a transfer payment by any other suitable technique. The new owner or third party assisting in the sale may update the owner metadata of the NFT being exchanged through the sales API, by interacting directly with the NFT smart contract, and/or through any other suitable technique. Successful sales may be recorded by a PoV system (e.g., similar to the exemplary disclosed PoV system described herein, which may operate as a PoV of an NFT system with the exemplary disclosed NFT system and method) for future reference and verification. In at least some example embodiments, the transfer may be an automated sale through a smart contract method, an automated sale through a third party service, or a manual sale through a smart contract method.

The exemplary disclosed systems and methods may include any suitable features, processes, and/or characteristics related to editing metadata of an NFT. For example, the author of the NFT content and/or the current owner of the NFT may update the metadata of the NFT. The author may update the authoring information using the author signature used during NFT creation. In at least some example embodiments, if a token is created without a signature, the owner (e.g., any owner) of the NFT may alter the author metadata. For another example, the current owner or owners may update metadata regarding NFT ownership. For further example, the current owner or owners may update the expansion metadata of the NFT token.

The exemplary disclosed systems and methods may include any suitable features, processes, and/or characteristics related to viewing the contents of the NFT. For example, in the case of open content, NFT metadata may contain an http link and hash value for the content data. Any party or entity (e.g., anyone) may read the link and view and/or download the content. For example, content may be verified using a content hash record from NFT metadata.

For another example, in the case of secure vault open content, the metadata of the NFT may contain both a content hash and a secure vault link. Any party or entity (e.g., anyone) may read the link and view and/or download the content. Content may be verified using a content hash record from NFT metadata. Availability of content may be provided (e.g., guaranteed) by one or more secure libraries.

Further for example, in the case of secure vault closed content, the metadata of the NFT may contain both a content hash and a secure vault link. An owner of an NFT token (e.g., no other party or entity) may be able to decode encrypted NFT content using, for example, a private key. The decoded content may be verified using a content hash record from NFT metadata. Availability of content may be provided (e.g., guaranteed) by one or more secure libraries. For another example, the exemplary disclosed systems and methods may utilize hybrid content that includes both an open portion and an encrypted portion.

The exemplary disclosed systems and methods may include any suitable features, processes, and/or characteristics associated with locking NFTs. If fraudulent activity is suspected, entities such as trusted authorities may lock or unlock NFTs (e.g., certain NFTs) during investigation. For example, if an author claims that its original work is replicated and another NFT containing the author work has been created, the NFT may be locked. For example, the exemplary disclosed systems and methods may provide for review of relevant facts and PoV records such that an entity, such as a trusted authority, may identify an original NFT (e.g., based on the exemplary processes disclosed herein) and lock one or more fraudulent NFTs to prevent use of the one or more fraudulent NFTs. The exemplary disclosed systems and methods may also provide an unlocking function that may be used in situations or situations where the NFT is falsely locked, surveys have shown or proven that the suspicious NFT is legitimate or compliant, and/or any other suitable situations or situations.

The exemplary disclosed systems and methods may include any suitable features, processes, and/or characteristics related to destroying and/or disabling NFTs. An owner of an NFT (e.g., any proprietary owner of an NFT) may destroy an NFT by destroying a token (e.g., an actual token). The destruction of the NFT may also be recorded by the PoV (e.g., similar to the exemplary disclosed PoV system described herein, which may operate as a PoV of the NFT system with the exemplary disclosed NFT system and method) to confirm or ensure that other copies of the NFT (e.g., any possible other copies) may be identified (e.g., easily identified) as counterfeit.

In at least some example embodiments and as shown, for example, in fig. 6, the example disclosed systems and methods may include a secure library. The exemplary disclosed PoV network may use any suitable technique (e.g., in the form of a Merkle tree) to store and maintain (e.g., maintain) a record of hashed NFT content and NFT interactions. The exemplary disclosed systems and methods may utilize (e.g., allocate) a secure vault to store the actual content of the NFT. One or more secure libraries may be assigned to each content hash record. As another example, some content records may not have a secure library assigned to them. Any desired number of secure libraries may be connected to the exemplary disclosed PoV network. Each secure vault may have its own storage terms. The secure library may be (e.g., or may include) a blockchain capable of storing data, or may be or may include any suitable data storage device, such as a file server, a database, a cloud storage device, and/or any other suitable storage device. Each secure vault may accept one or more types of NFT content. The secure vault may obtain NFT content store authentication. NFT content may or may not use encryption when stored. In at least some example embodiments, the secure vault may be associated with benefits of participating in NFT content storage, such as by receiving rewards from stored NFT offerings, collecting storage fees (e.g., disposable or recurring prices or fees), collecting annual storage fees, receiving storage free of charge, and/or any other suitable benefits.

Fig. 6 illustrates an exemplary operation of an exemplary disclosed PoV of NFT systems and methods. For example, as described above, the exemplary disclosed PoV system may provide the PoV of the NFT by operating with the exemplary disclosed NFT system. As shown in fig. 6 and described, for example, herein, the exemplary disclosed systems and methods may provide for creating NFTs, recording NFT events by PoV, providing event hashes, and assigning secure libraries to secure libraries. As shown in fig. 6, the exemplary disclosed systems and methods may verify NFT events by PoV without or with the use of a secure vault.

In at least some example embodiments, creating the NFT may include converting an existing NFT to a PoV-enabled NFT. The exemplary disclosed systems and methods may include any suitable software modules for communicating with a desired blockchain network to access, send, and receive NFTs (e.g., wallets (e.g., wrap wallets)). The example disclosed wrap wallet may be included in an example disclosed non-homogenous token smart contract module, an example disclosed view attestation smart contract module, an example disclosed verifier network, and/or an example disclosed independent wallet module of systems and methods.

For example, any suitable blockchain operating NFT of other (e.g., third party) standards and/or specifications (e.g., operating with the exemplary disclosed systems and methods) may include software (e.g., wallet) that may be automated by NFT translator software of the exemplary disclosed systems and methods and/or a wrap smart contract that operates alone and may be monitored by NFT translator software. For example, NFT converter software may be included in an exemplary disclosed wrap wallet of the exemplary disclosed systems and methods. For example, the exemplary disclosed NFT translator software may be part of the exemplary disclosed verifier network, or may exist as a separate module (e.g., a stand-alone module or solution).

An owner of an existing NFT (e.g., an external or foreign NFT) may send the existing NFT to an exemplary disclosed wrap wallet or wrap smart contract of an exemplary disclosed system and method, and may provide valid data to the exemplary disclosed wrap wallet or wrap smart contract of the exemplary disclosed system and method to receive wallet addresses. In doing so, the owner of the existing NFT may convert the existing NFT into a view-justifying enabled NFT (POV-enabled NFT).

When such an incoming existing NFT is detected by the example disclosed system and method in the example disclosed wrap wallet or wrap smart contract, and there is valid data to receive the wallet address, the example disclosed translator software may store some or substantially all of the data from the existing NFT (e.g., the original external NFT) and may initiate creation of a copy of the new NFT (e.g., the PoV-enabled NFT) in a view-justification enabled environment. The exemplary disclosed systems and methods may also burn, delete, or invalidate existing NFTs (e.g., original NFTs) to ensure that NFTs are not replicated (e.g., cannot be replicated). Data (e.g., records) of NFTs that have been converted to PoV-enabled NFTs (e.g., as new NFTs) may be added to the exemplary disclosed verifier network. Further, verification hashes may be recorded to the PoV by the exemplary disclosed systems and methods.

In at least some example embodiments, the example disclosed converter software may operate multiple wallets and smart contracts simultaneously through multiple blockchains (e.g., different blockchains). The exemplary disclosed systems and methods may thus provide NFT translation to a PoV-enabled NFT, translation of the NFT between blockchains or any other suitable NFT-enabled media.

An exemplary disclosed view attestation verification system may include a non-homogenous token smart contract module including computer executable code stored in non-volatile memory, a view attestation smart contract module including computer executable code stored in non-volatile memory, a processor, and a verifier network. The non-homogenous token smart contract module, the view attestation smart contract module, the processor, and the verifier network may be configured to transmit data of the non-homogenous token to the non-homogenous token smart contract module and generate event metadata based on the data of the non-homogenous token, transmit the event metadata to the view attestation smart contract module, and generate an event hash using the verifier network and transmitting the event hash from the verifier network to the view attestation smart contract module. Generating the event hash may include generating a hash database chunk and appending the hash database chunk to a block on the blockchain. The exemplary disclosed system may also include a secure data store. The heterogeneous token smart contract module, the view attestation smart contract module, the processor, the verifier network, and the secure data store may be configured to communicate event metadata and event hashes to the secure data store and store the event metadata and event hashes in the secure data store. The heterogeneous token smart contract module, the view attestation smart contract module, the processor, the verifier network, and the secure data store may be configured to retrieve metadata using an event hash stored in the secure data store. The heterogeneous token smart contract module, the view proof smart contract module, the processor, the verifier network, and the secure data store may be configured to assign storage identification data to an event hash stored in the secure data store. The heterogeneous token smart contract module, the view attestation smart contract module, the processor, and the verifier network may be configured to verify the proposed event metadata by using the view attestation smart contract module and the verifier network to compare the proposed event metadata with the event metadata. The heterogeneous token smart contract module, the view attestation smart contract module, the processor, and the verifier network may be configured to communicate verification result data to the user based on comparing the proposed event metadata to the event metadata. The proposed event metadata may be data of ownership of the non-homogenous token. The data of the non-homogenous tokens may be non-homogenous token creation data, which may be recorded as an event hash to a view-justifying smart contract module. The data of the non-homogenous tokens may be changed from metadata of the non-homogenous tokens, which may be recorded as an event hash to the view-justifying smart contract module. The data of the non-homogenous tokens may be data of sales or destruction of the non-homogenous tokens, which is recorded as an event hash to the view-justifying smart contract module.

An exemplary disclosed method may include: providing a non-homogenous token smart contract module comprising computer executable code stored in non-volatile memory; providing a view attestation smart contract module including computer executable code stored in non-volatile memory; providing a verifier network; the method includes transmitting data of a non-homogenous token to a non-homogenous token smart contract module and generating event metadata based on the data of the non-homogenous token, transmitting the event metadata to a view proving smart contract module, and generating and transmitting an event hash from the verifier network to the view proving smart contract module using the verifier network. Generating the event hash may include generating a hash database chunk and appending the hash database chunk to a block on the blockchain. The exemplary disclosed method may further include transmitting the event metadata and the event hash to a secure data store and storing the event metadata and the event hash in the secure data store. The exemplary disclosed method may further include retrieving metadata using the event hash stored in the secure data store. The exemplary disclosed method may further include assigning storage identification data to the event hashes stored in the secure data store. The exemplary disclosed method may further include verifying the proposed event metadata by using the view attestation smart contract module and the verifier network to compare the proposed event metadata with the event metadata. The exemplary disclosed method may further include transmitting verification result data to the user based on comparing the proposed event metadata with the event metadata.

An exemplary disclosed view attestation verification system may include a non-homogenous token smart contract module including computer executable code stored in non-volatile memory, a view attestation smart contract module including computer executable code stored in non-volatile memory, a processor, a verifier network, and a secure data store. The non-homogenous token smart contract module, the view attestation smart contract module, the processor, the verifier network, and the secure data store may be configured to transfer data of the non-homogenous token to the non-homogenous token smart contract module and generate event metadata based on the data of the non-homogenous token, transfer the event metadata to the view attestation smart contract module, generate an event hash using the verifier network, transfer the event hash from the verifier network to the view attestation smart contract module, transfer the event metadata and the event hash to the secure data store, store the event metadata and the event hash in the secure data store, and assign the storage identification data to the event hash stored in the secure data store. Generating the event hash may include generating a hash database chunk and appending the hash database chunk to a block on the blockchain. The heterogeneous token smart contract module, the view attestation smart contract module, the processor, the verifier network, and the secure data store may be configured to retrieve metadata using an event hash stored in the secure data store. The non-homogenous token smart contract module, the view attestation smart contract module, the processor, the verifier network, and the secure data store may be configured to verify the proposed event metadata by using the view attestation smart contract module and the verifier network to compare the proposed event metadata to the event metadata.

The exemplary disclosed systems and methods may provide efficient techniques for verifying a view of content (e.g., internet content that may be viewed by an internet user). For example, the exemplary disclosed systems and methods may provide a user with transparent techniques to verify that online content has actually been viewed using a public ledger. The exemplary disclosed systems and methods may thus provide an efficient technique for determining the value of a content provider's channel (e.g., for the purpose of compensating based on advertising or other criteria that depend on how much given content is viewed by a user, such as a consumer). For example, the exemplary disclosed systems and methods may verify whether the intended target audience has actually viewed the content of a given provider (e.g., and advertisements that may be co-located with the content). Further, the exemplary disclosed systems and methods may provide efficient techniques for providing attribution, content, and viewing of NFTs.

Conventionally, a computer program comprises a finite sequence of computing instructions or program instructions. It should be appreciated that a programmable device or computing apparatus may receive such a computer program and produce a technical effect by processing its computing instructions.

A programmable device or computing means includes one or more microprocessors, microcontrollers, embedded microcontrollers, programmable digital signal processors, programmable means, programmable gate arrays, programmable array logic, memory means, application specific integrated circuits, or the like, which may be suitably employed or configured to process computer program instructions, execute computer logic, store computer data, or the like. It should be appreciated that the computing device may include a computer-readable storage medium, and that the medium may be internal or external, removable and replaceable, or fixed. It should also be appreciated that the computing device may include a basic input/output system (BIOS), firmware, operating systems, databases, etc., which may include, interface with, or support the software and hardware described herein.

Embodiments of the systems described herein are not limited to applications involving conventional computer programs or programmable devices running them. For example, it is contemplated that embodiments of the present disclosure claimed herein may include optical computers, quantum computers, analog computers, and the like.

Regardless of the type of computer program or computing device involved, the computer program may be loaded onto a computing device to produce a particular machine, which performs any and all of the functions described. This particular machine (or network configuration thereof) provides techniques for performing any and all of the described functions.

Any combination of one or more computer readable media may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Illustrative examples of the computer readable storage medium may include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

The data store may include one or more of a database, a file storage system, a relational data storage system, or any other data system or structure configured to store data. The data store may be a relational database that works in conjunction with a relational database management system (RDBMS) to receive, process, and store data. The data store may include one or more databases for storing information related to the processing of movement information and estimation information, and one or more databases configured for storing and retrieving movement information and estimation information.

The computer program instructions may be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner. The instructions stored in the computer-readable memory constitute an article of manufacture including computer-readable instructions for implementing any and all of the described functions.

The computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or in a portion of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Elements depicted in the flowchart and block diagrams throughout the figures imply logical boundaries between elements. However, the depicted elements and their functions may be implemented as part of an overall software structure, as separate software components or modules, or as components or modules employing external routines, code, services, etc., or any combination of these, in accordance with software or hardware engineering practices. All such embodiments are within the scope of the present disclosure. In view of the foregoing, it will be appreciated that the elements of the block diagrams and flowchart illustrations support combinations of means for performing the specified functions, combinations of steps for performing the specified functions, program instruction means for performing the specified functions and the like.

It should be understood that the computer program instructions may include computer executable code. A variety of languages for expressing computer program instructions are possible, including, but not limited to C, C ++, java, javaScript, assembly language, lisp, HTML, perl, and the like. These languages may include assembly language, hardware description language, database programming language, functional programming language, imperative programming language, and the like. In some embodiments, computer program instructions may be stored, compiled or interpreted to run on a computing device, a programmable data processing device, a processor, or a heterogeneous combination of processor architectures, or the like. Without limitation, embodiments of the systems described herein may take the form of network-based computer software, including client/server software, software-as-a-service, peer-to-peer software, and the like.

In some embodiments, a computing device enables execution of computer program instructions comprising a plurality of programs or threads. Multiple programs or threads may be processed more or less simultaneously to enhance processor utilization and facilitate substantially simultaneous functionality. By way of implementation, any and all methods, program code, program instructions, etc. described herein may be implemented in one or more threads. A thread may generate other threads that may themselves be assigned priorities associated with it. In some embodiments, the computing device may process the threads based on priority or based on any other order of instructions provided in the program code.

The verbs "process" and "execute" are used interchangeably to refer to execution, processing, interpretation, compilation, assembly, linking, loading, any and all combinations of the foregoing, and the like, unless clearly stated otherwise or clear from the context. Thus, embodiments that process computer program instructions, computer-executable code, etc. may act on instructions or code as appropriate in any and all ways just described.

The functions and operations presented herein are not inherently related to any particular computing device or other apparatus. Various general-purpose systems may also be used with programs in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatus to perform the required method steps. The required structure for a variety of these systems, as well as equivalent variations, will be apparent to those of ordinary skill in the art. In addition, embodiments of the present disclosure are not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the present teachings as described herein, and any references to specific languages are provided for use in the implementation and best mode of practicing embodiments of the invention as disclosed herein. Embodiments of the present disclosure are well suited to a variety of computer network systems over a variety of topologies. Within this field, the configuration and management of large networks includes storage devices and computing devices communicatively coupled to different computing and storage devices through a network (e.g., the internet, also referred to as a "network" or "world wide web").

Throughout this disclosure and elsewhere, block diagrams and flowcharts illustrate methods, apparatus (e.g., systems) and computer program products. Each element in the block diagrams and flowchart illustrations, and each respective combination of elements in the block diagrams and flowchart illustrations, illustrates the functionality of a method, apparatus, and computer program product. Any and all such functions ("described functions") may be implemented by: by computer program instructions; by a dedicated, hardware-based computer system; through a combination of dedicated hardware and computer instructions; through a combination of general-purpose hardware and computer instructions, etc. -any and all of which may be referred to generally herein as "components," modules, "or" systems.

While the foregoing drawings and description set forth functional aspects of the disclosed systems, no particular arrangement of software for implementing these functional aspects should be inferred from the description unless explicitly stated or apparent from the context.

Each element in the flowchart illustrations may depict a step or a set of steps of a computer-implemented method. Furthermore, each step may comprise one or more sub-steps. For purposes of illustration, these steps (as well as any and all other steps identified and described above) are presented in sequence. It should be understood that embodiments may contain alternative sequences of steps that are suitable for the particular application of the technology disclosed herein. All such variations and modifications are intended to be within the scope of the present disclosure. Depiction and description of steps in any particular order is not intended to exclude embodiments having steps in a different order unless the particular application requires, is explicitly stated, or is clear from the context.

The functions, systems, and methods described herein can be employed and presented in a variety of languages. The individual systems may be presented in one or more languages and the language may be easily changed at any point in the above described process or method. Those of ordinary skill in the art will appreciate that the system may be provided in a variety of languages, and embodiments of the present disclosure contemplate the use of any language.

While various embodiments are disclosed, other embodiments of the disclosure will become apparent to those skilled in the art from this detailed description. Some aspects of the disclosure may be practiced without implementing some of the features described. It should be understood that some details are not described in detail so as not to unnecessarily obscure the present disclosure. The present disclosure is capable of numerous modifications in various obvious aspects, all without departing from the spirit and scope of the present disclosure. Accordingly, the drawings and description are to be regarded as illustrative in nature and not as restrictive.

Claims

1. A proof of view verification system, comprising:

a non-homogenous token smart contract module comprising computer executable code stored in non-volatile memory;

a view attestation smart contract module including computer executable code stored in the non-volatile memory;

A processor; and

a verifier network;

wherein the non-homogenous token smart contract module, the view attestation smart contract module, the processor, and the verifier network are configured to:

transmitting data of a non-homogenous token to the non-homogenous token smart contract module and generating event metadata based on the data of the non-homogenous token;

transmitting the event metadata to the view attestation smart contract module; and is also provided with

Generating an event hash using the verifier network and transmitting the event hash from the verifier network to the view-proving smart contract module;

wherein generating the event hash includes generating a hash database chunk and appending the hash database chunk to a block on a blockchain.

2. The proof of view verification system of claim 1, further comprising a secure data store.

3. The proof-of-view verification system of claim 2, wherein the heterogeneous token smart contract module, the view proof smart contract module, the processor, the verifier network, and the secure data store are configured to send the event metadata and the event Ha Xichuan to the secure data store and store the event metadata and the event hash in the secure data store.

4. The proof-of-view verification system of claim 3, wherein the heterogeneous token smart contract module, the proof-of-view smart contract module, the processor, the verifier network, and the secure data store are configured to retrieve metadata using an event hash stored in the secure data store.

5. The proof-of-view verification system of claim 2, wherein the heterogeneous token smart contract module, the proof-of-view smart contract module, the processor, the verifier network, and the secure data store are configured to assign storage identification data to event hashes stored in the secure data store.

6. The proof-of-view verification system of claim 1, wherein the heterogeneous token smart contract module, the proof-of-view smart contract module, the processor, and the verifier network are configured to verify 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.

7. The proof-of-view verification system of claim 6, wherein the heterogeneous token smart contract module, the proof-of-view smart contract module, the processor, and the verifier network are configured to communicate verification result data to a user based on comparing the proposed event metadata to the event metadata.

8. The proof of view verification system of claim 6, wherein the proposed event metadata is data of ownership of the non-homogenous token.

9. The proof-of-view verification system of claim 1, wherein the data of the non-homogenous tokens is non-homogenous token creation data that is recorded as the event hash to the proof-of-view smart contract module.

10. The proof-of-view verification system of claim 1, wherein the data of the non-homogenous token is changed data from metadata of the non-homogenous token, the changed data being recorded as the event hash to the proof-of-view smart contract module.

11. The proof-of-view verification system of claim 1, wherein the data of the non-homogenous tokens is data of sales or destruction of the non-homogenous tokens, the sales or destruction data being recorded as the event hash to the proof-of-view smart contract module.

12. The proof-of-view verification system of claim 1, wherein the non-homogenous token smart contract module, the proof-of-view smart contract module, the processor, and the verifier network are configured to convert the non-homogenous token to a proof-of-view enabled non-homogenous token.

13. A method, comprising:

providing a non-homogenous token smart contract module comprising computer executable code stored in non-volatile memory;

providing a view proving smart contract module comprising computer executable code stored in the non-volatile memory;

providing a verifier network;

Generating an event hash using the verifier network and communicating the event hash from the verifier network to the view-proving smart contract module,

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

15. The method of claim 14, further comprising retrieving metadata using an event hash stored in the secure data store.

16. The method of claim 14, further comprising assigning storage identification data to event hashes stored in the secure data store.

17. The method of claim 13, further comprising verifying proposed event metadata by using the view attestation smart contract module and the verifier network to compare the proposed event metadata with the event metadata.

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

19. A proof of view verification system, comprising:

a processor;

a verifier network; and

a secure data storage device is provided that is configured to store data,

wherein the non-homogenous token smart contract module, the view attestation smart contract module, the processor, the verifier network, and the secure data store are configured to:

transmitting the event metadata to the view attestation smart contract module;

sending the event metadata and the event Ha Xichuan to the secure data store and storing the event metadata and the event hash in the secure data store; and is also provided with

Assigning storage identification data to event hashes stored in the secure data store,

20. The proof-of-view verification system of claim 19, wherein the heterogeneous token smart contract module, the proof-of-view smart contract module, the processor, the verifier network, and the secure data store are configured to retrieve metadata using an event hash stored in the secure data store.

21. The proof-of-view verification system of claim 19, wherein the heterogeneous token smart contract module, the proof-of-view smart contract module, the processor, the verifier network, and the secure data store are configured to verify 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.