Data processing method and verification method, device, electronic equipment and storage medium

Abstract

The present disclosure relates to a data processing method and verification method, device, electronic equipment and storage medium. The data processing method comprises: obtaining first identification information corresponding to metadata of a target NFT, wherein the metadata of the target NFT at least includes identification information corresponding to certificate information data associated with the target NFT, and an address of a certificate verification contract used for verifying the target NFT; calling an NFT creation contract to create the target NFT based on the first identification information; obtaining second identification information corresponding to metadata of a certificate NFT associated with the target NFT, wherein the metadata of the certificate NFT at least includes NFT creation contract related information and certificate information data; and calling a certificate creation contract to create the certificate NFT based on the second identification information, wherein the certificate creation contract corresponds to the certificate verification contract.

Description

Technical Field

[0001] This disclosure relates to the field of blockchain technology, and more specifically, to a data processing method, a data verification method, an apparatus, an electronic device, a computer-readable storage medium, and a computer program product. Background Technology

[0002] NFTs (Non-Fungible Tokens) are digital asset rights certificates based on blockchain technology; that is, they are unique cryptographic tokens representing digital assets. Once a digital asset is created as an NFT, it is permanently stored on the blockchain, making it unique and immutable. With the development of blockchain technology, more and more artists, musicians, and content creators are selling their work in the form of NFTs.

[0003] As provably unique tokens, NFTs, even when simplified to a simple JPEG format, represent the traceable value of their owners. The future of NFTs is concrete; Web 2.0 reduced the cost of social interaction among internet users and quickly impacted their online / offline interactions. Web 3.0, by incorporating verification processes into smart contracts, solved the trust issue. With the booming NFT market, NFTs have spread like wildfire, gaining widespread popularity through practical applications in social media, entertainment, and other fields.

[0004] However, NFTs are still in their early stages of development, and many issues remain unresolved. For example, some people steal others' artwork without the original creator's consent and turn it into NFTs for sale on various platforms. Fraudsters also use sleep-minting technology to forge valuable NFTs and defraud others into buying them. Currently, there are no effective methods to prevent or verify NFT theft or forgery. Summary of the Invention

[0005] This disclosure provides a data processing method, a data verification method, an apparatus, an electronic device, a computer-readable storage medium, and a computer program product to at least solve the problem in the aforementioned related technologies of failing to effectively prevent or verify NFT theft or forgery.

[0006] According to a first aspect of the present disclosure, a data processing method is provided, comprising: obtaining first identification information corresponding to the metadata of a target NFT, wherein the first identification information is identification information obtained after the metadata of the target NFT is stored in a blockchain, wherein the metadata of the target NFT includes at least identification information corresponding to certificate information data associated with the target NFT and an address of a certificate verification contract for verifying the target NFT, wherein the identification information corresponding to the certificate information data is identification information obtained after the certificate information data is stored in a blockchain; invoking an NFT creation contract to create the target NFT based on the first identification information; obtaining second identification information corresponding to the metadata of a certificate NFT associated with the target NFT, wherein the metadata of the certificate NFT includes at least information related to the NFT creation contract and the certificate information data, wherein the second identification information is identification information obtained after the metadata of the certificate NFT is stored in a blockchain; and invoking a certificate creation contract to create the certificate NFT based on the second identification information, wherein the certificate creation contract corresponds to the certificate verification contract.

[0007] According to a second aspect of the present disclosure, a data verification method is provided, comprising: invoking a certificate verification contract to verify the target NFT based on the metadata of the target NFT and the metadata of a certificate NFT associated with the target NFT; and outputting a verification result; wherein the target NFT is created by an NFT creation contract based on first identification information corresponding to the metadata of the target NFT, and the certificate NFT is created by a certificate creation contract corresponding to the certificate verification contract based on second identification information corresponding to the metadata of the certificate NFT, the metadata of the target NFT includes at least identification information corresponding to certificate information data associated with the target NFT and the address of the certificate verification contract used to verify the target NFT, the metadata of the certificate NFT includes at least information related to the NFT creation contract and the certificate information data, the first identification information is identification information obtained after the metadata of the target NFT is stored in the blockchain, the identification information corresponding to the certificate information data is identification information obtained after the certificate information data is stored in the blockchain, and the second identification information is identification information obtained after the metadata of the certificate NFT is stored in the blockchain.

[0008] According to a third aspect of the present disclosure, a data processing apparatus is provided, comprising: a first identification information acquisition unit configured to acquire first identification information corresponding to metadata of a target NFT, wherein the first identification information is identification information obtained after the metadata of the target NFT is stored in a blockchain, wherein the metadata of the target NFT includes at least identification information corresponding to certificate information data associated with the target NFT and an address of a certificate verification contract for verifying the target NFT, wherein the identification information corresponding to the certificate information data is identification information obtained after the certificate information data is stored in a blockchain; a target NFT creation unit configured to invoke an NFT creation contract to create the target NFT based on the first identification information; a second identification information acquisition unit configured to acquire second identification information corresponding to metadata of a certificate NFT associated with the target NFT, wherein the metadata of the certificate NFT includes at least information related to the NFT creation contract and the certificate information data, wherein the second identification information is identification information obtained after the metadata of the certificate NFT is stored in a blockchain; and a certificate NFT creation unit configured to invoke a certificate creation contract to create the certificate NFT based on the second identification information, wherein the certificate creation contract corresponds to the certificate verification contract.

[0009] According to a fourth aspect of the present disclosure, a data verification apparatus is provided, characterized in that it includes: a target NFT verification unit configured to invoke a certificate verification contract to verify the target NFT based on the metadata of the target NFT and the metadata of a certificate NFT associated with the target NFT; and a verification result output unit configured to output a verification result; wherein the target NFT is created by an NFT creation contract based on first identification information corresponding to the metadata of the target NFT, and the certificate NFT is created by a certificate creation contract corresponding to the certificate verification contract based on second identification information corresponding to the metadata of the certificate NFT, the metadata of the target NFT includes at least identification information corresponding to the certificate information data associated with the target NFT and the address of the certificate verification contract used to verify the target NFT, the metadata of the certificate NFT includes at least information related to the NFT creation contract and the certificate information data, the first identification information is identification information obtained after the metadata of the target NFT is stored in the blockchain, the identification information corresponding to the certificate information data is identification information obtained after the certificate information data is stored in the blockchain, and the second identification information is identification information obtained after the metadata of the certificate NFT is stored in the blockchain.

[0010] According to a fifth aspect of the present disclosure, an electronic device is provided, comprising: at least one processor; and at least one memory storing computer-executable instructions, wherein the computer-executable instructions, when executed by the at least one processor, cause the at least one processor to perform a data processing method or a data verification method according to the present disclosure.

[0011] According to a sixth aspect of the present disclosure, a computer-readable storage medium is provided that, when instructions in the computer-readable storage medium are executed by at least one processor, causes the at least one processor to perform a data processing method or a data verification method according to the present disclosure.

[0012] According to a seventh aspect of the present disclosure, a computer program product is provided, including computer instructions that, when executed by at least one processor, implement a data processing method or a data verification method according to the present disclosure.

[0013] The technical solutions provided by the embodiments of this disclosure have at least the following beneficial effects:

[0014] According to the data processing and data verification methods disclosed herein, a certificate creation contract creates a certificate NFT associated with the target NFT based on certificate information data associated with the target NFT, and a certificate verification contract uses the certificate NFT associated with the target NFT to verify the target NFT. In other words, a pair of smart contracts (i.e., a certificate creation contract and a certificate verification contract) create an anti-counterfeiting certificate NFT for the target NFT, and the certificate NFT is used to verify the authenticity of the target NFT, ensuring the authenticity of the NFT creation process, preventing fraudulent activities such as SleepMinting, and protecting the rights and interests of NFT creators and NFT collectors.

[0015] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0016] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure, and are not intended to unduly limit this disclosure.

[0017] Figure 1 This is a flowchart illustrating the NFT creation process using related technologies;

[0018] Figure 2 This is a conceptual diagram of data processing and verification according to exemplary embodiments of the present disclosure;

[0019] Figure 3This is a flowchart illustrating a data processing method according to an exemplary embodiment of the present disclosure;

[0020] Figure 4 This is a schematic diagram illustrating the metadata of a target NFT according to an exemplary embodiment of the present disclosure;

[0021] Figure 5 This is a schematic diagram illustrating the metadata of a certificate NFT according to an exemplary embodiment of the present disclosure;

[0022] Figure 6 This is a flowchart illustrating a data verification method according to an exemplary embodiment of the present disclosure;

[0023] Figure 7 This is a flowchart illustrating a specific creation process of a certified NFT according to an exemplary embodiment of the present disclosure;

[0024] Figure 8 This is a flowchart illustrating a specific verification process for a certified NFT according to an exemplary embodiment of the present disclosure;

[0025] Figure 9 This is a block diagram illustrating a data processing apparatus according to exemplary embodiments of the present disclosure;

[0026] Figure 10 This is a block diagram illustrating a data verification apparatus according to an exemplary embodiment of the present disclosure;

[0027] Figure 11 This is a block diagram of an electronic device 1100 according to an exemplary embodiment of the present disclosure. Detailed Implementation

[0028] To enable those skilled in the art to better understand the technical solutions of this disclosure, the technical solutions in the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings.

[0029] It should be noted that the terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this disclosure described herein can be implemented in orders other than those illustrated or described herein. The embodiments described in the following examples do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0030] It should be noted that the phrase "at least one of several items" in this disclosure refers to three parallel cases: "any one of the several items", "a combination of any number of the several items", and "all of the several items". For example, "including at least one of A and B" includes the following three parallel cases: (1) including A; (2) including B; (3) including A and B. Another example is "performing at least one of step one and step two", which means the following three parallel cases: (1) performing step one; (2) performing step two; (3) performing both step one and step two.

[0031] Currently, NFTs can be created through smart contracts that conform to some common protocols (such as the ERC-721 protocol). Figure 1 This is a flowchart illustrating the NFT creation process using related technologies. (Refer to...) Figure 1 In step 101, the NFT creator can upload the NFT (digital file) to centralized cloud storage or a decentralized blockchain (e.g., IPFS or AR) to obtain the corresponding identification information, such as a token (i.e., a unique identifier). Here, the digital file can be any digitizable file such as an image, video, audio, or digital (virtual) artwork. In step 102, the NFT creator can organize the NFT's metadata based on the identification information corresponding to the NFT and store it in a decentralized blockchain (e.g., IPFS or AR) to obtain the identification information corresponding to the NFT's metadata, such as a token. In step 103, an NFT is created based on the identification information corresponding to the NFT's metadata through a smart contract. Specifically, the smart contract can generate unique identification information, such as a token, for the identification information corresponding to the NFT's metadata; this unique identification information is the NFT. Here, a token can be a hash value obtained through a hash algorithm. Because hash algorithms are one-way and collision-resistant, each hash value can uniquely correspond to one original content and cannot be tampered with. Therefore, each token can be used to uniquely identify the corresponding data.

[0032] SleepMinting is a method of NFT forgery that uses smart contracts to forge the NFT creator and the NFT creation process. For example, a fraudster can copy the original files of an NFT created by a famous artist, create an NFT in the artist's name, and forge transaction records to make it appear as if the NFT was traded from the artist's account, thus defrauding others into buying the NFT. In other words, a fraudster can bypass the creator's (i.e., the famous artist's) account by writing a vulnerable smart contract and forge an NFT in the creator's name.

[0033] Since NFT creation contracts are written by the developers themselves, it's impossible to control the individual actions of fraudsters who subjectively create backdoors. Therefore, upgrading common protocols (e.g., ERC-721) to include data auditing can defend against this type of SleepMinting fraud. Furthermore, while NFT trading platforms can implement data verification to prevent NFT listings from being fraudulently created using SleepMinting, this cannot prevent the creation of NFTs using SleepMinting fraud.

[0034] To address the aforementioned issues, this disclosure provides a data processing method and a data verification method. Through a pair of smart contracts (i.e., one smart contract creates a certificate NFT with relevant certificate data for the target NFT, and the other smart contract verifies the validity of the certificate data), an anti-counterfeiting certificate NFT is created for the target NFT. This certificate NFT is then used to verify the authenticity of the target NFT. In other words, the target NFT can be protected through an NFT mechanism, thereby ensuring the authenticity of the NFT creation process, preventing fraudulent activities such as SleepMinting, and protecting the rights of NFT creators and collectors. This disclosure utilizes the immutability of blockchain technology to store the certificate information data of the certificate NFT, enabling the certificate NFT to be used to verify the authenticity of the target NFT.

[0035] Below, we will refer to Figures 2 to 11 This disclosure will describe in detail the data processing method and apparatus, as well as the data verification method and apparatus, according to this disclosure.

[0036] Figure 2 This is a conceptual diagram of data processing and verification according to exemplary embodiments of the present disclosure.

[0037] Reference Figure 2Regarding the data processing, firstly, the user (e.g., an NFT creator) creates the target NFT based on the data used to verify it using an NFT creation contract on the blockchain. That is, the user authorizes the NFT creation contract to create the target NFT. Here, the NFT creation contract refers to the smart contract used to create the NFT. The target NFT can refer to the NFT created by the NFT creator for its NFT object (e.g., digital files such as images or videos). Furthermore, an NFT creator is not the same as an NFT creator; the NFT creator can create the NFT or authorize an NFT creator to create it. Subsequently, after the target NFT is created, the user (e.g., the NFT creator) creates a certificate NFT related to the target NFT using a certificate creation contract on the blockchain, based on the data used to verify the target NFT and related information. That is, the user authorizes the certificate creation contract to create the certificate NFT. Here, the certificate creation contract refers to the smart contract used to create the certificate NFT. After creation, both the target NFT and the certificate NFT are stored in the NFT creator's account.

[0038] Because both the creation processes of the target NFT and the certificate NFT use information that uniquely identifies each other—that is, the creation process of the target NFT uses information that uniquely identifies the certificate information, and the creation process of the certificate NFT uses information that uniquely identifies the target NFT—the target NFT can be associated with its certificate NFT, and the certificate NFT can be used to verify the authenticity of the target NFT. Furthermore, during the creation of the certificate NFT, the certificate creation contract can interact with a third-party oracle (e.g., the Chainlink oracle network) to obtain the certificate NFT's metadata from the blockchain storing the certificate NFT's metadata (e.g., IPFS, AR, etc.) and verify its correctness, ensuring that the created certificate NFT is indeed the certificate NFT of the target NFT. Here, a third-party oracle refers to a server that connects off-chain data to on-chain smart contracts. Since the blockchain where the certificate creation contract resides and the blockchain storing the certificate NFT's metadata are different chains, the certificate creation contract cannot directly obtain the certificate NFT's metadata and needs to obtain it through a third-party oracle.

[0039] For the data verification process, users can verify the target NFT by calling a certificate verification contract through a client. For example, when a user sees a target NFT and its related information on a trading platform, they can use a client (e.g., a browser) to call the certificate verification contract using web3.js. The user inputs the relevant information of the target NFT into the certificate verification contract. Based on this information, the certificate verification contract interacts with a third-party oracle (e.g., the Chainlink oracle network) to obtain the metadata of the target NFT and the certificate NFT from a blockchain (e.g., IPFS, AR, etc.) that stores the metadata of the target NFT and the metadata of the associated certificate NFT. This allows the certificate verification contract to verify the authenticity of the target NFT. Here, the certificate creation contract used in the NFT creation process and the certificate verification contract used in the NFT verification process are a pair of smart contracts. Because the blockchain where the certificate verification contract resides is a different chain from the blockchain storing the metadata of the target NFT and the certificate NFT, the certificate verification contract cannot directly obtain the metadata of the target NFT and the certificate NFT; it needs to obtain the metadata of the certificate NFT through a third-party oracle.

[0040] Therefore, through the data processing and data verification processes disclosed above, a pair of smart contracts (a certificate creation contract and a certificate verification contract) can be used to create an anti-counterfeiting certificate NFT for the target NFT, and the authenticity of the target NFT can be verified through the relevant data of the certificate NFT, thus preventing NFT fraud.

[0041] Figure 3 This is a flowchart illustrating a data processing method according to an exemplary embodiment of the present disclosure.

[0042] Reference Figure 3 In step 301, the first identification information corresponding to the metadata of the target NFT can be obtained. Here, the target NFT may refer to the NFT created by the NFT creator for its NFT object (e.g., digital files such as images and videos).

[0043] According to exemplary embodiments of this disclosure, the metadata of the target NFT may include identification information corresponding to the NFT and any descriptive information related to the NFT. Here, the identification information corresponding to the NFT may be identification information obtained after the NFT is stored in a blockchain or cloud storage, used to indicate the storage address of the NFT. Of course, the metadata of the target NFT is not limited to the information described above.

[0044] According to exemplary embodiments of this disclosure, in order to generate a target NFT with a certificate, the metadata of the target NFT needs to include at least the data used to verify the target NFT. For example, the metadata of the target NFT may also include, but is not limited to, identification information corresponding to the certificate information data associated with the target NFT, and the address of the certificate verification contract used to verify the target NFT. Here, the certificate information data may include data used by the certificate verification contract to verify the target NFT. The identification information corresponding to the certificate information data may be identification information obtained after the certificate information data is stored in the blockchain, used to indicate the address where the certificate information data is stored. The address of the certificate verification contract refers to the storage address of the certificate verification contract in the blockchain. Here, the identification information may be, but is not limited to, a hash value generated by a hash algorithm, called a token, used to uniquely identify the corresponding data.

[0045] Figure 4 This is a schematic diagram illustrating the metadata of a target NFT according to an exemplary embodiment of the present disclosure.

[0046] Reference Figure 4 The metadata of the target NFT may include the identification information corresponding to the NFT, the description information corresponding to the NFT, the certificate verification contract address, and the identification information corresponding to the certificate information data.

[0047] According to exemplary embodiments of this disclosure, the certificate information data may include, but is not limited to, at least one of the following: NFT target address, NFT creation contract address, certificate verification contract address, NFT creator account address, NFT creator public key, NFT creator signature, and NFT creator signature expiration time. Here, the NFT target address refers to the storage address of the NFT target in a blockchain or cloud storage. The NFT creation contract address refers to the storage address of the NFT creation contract in a blockchain. The certificate verification contract address refers to the storage address of the certificate verification contract in a blockchain. The NFT creator account address refers to the address where the target NFT and its certificate NFT are stored after creation. The hash value of the NFT creator public key is the NFT creator account address and can be used for NFT creator encryption or decryption. The NFT creator signature is obtained by encrypting other certificate information data in the certificate information data, excluding the NFT creator signature, using the NFT creator private key. In other words, the certificate information data (JSON data) excluding the NFT creator's signature can be encrypted using the NFT creator's private key. Then, the encrypted NFT creator's signature is added to the certificate information data (JSON data). This way, by using asymmetric encryption to confirm the NFT creator's authorization of the certificate creation contract, the certificate creation contract is bound to the NFT creator. Therefore, the NFT creator's signature expiration time refers to the time when the NFT creator's authorized signature expires; that is, after the NFT creator's signature expires, the NFT creator's signature becomes invalid. Of course, the certificate information data disclosed herein is not limited to the above data and can include other certificate information data that may be verified as needed, for subsequent verification of the target NFT by the certificate verification contract.

[0048] Return to reference Figure 3 In step 302, an NFT creation contract can be invoked to create the target NFT based on the first identifier information. Specifically, after receiving the first identifier information, the NFT creation contract can generate an identifier (e.g., a token) to identify the first identifier information; this generated identifier is the target NFT. After the target NFT is created, the NFT creation contract will store the target NFT in the NFT creator's account.

[0049] In step 303, the second identification information corresponding to the metadata of the certificate NFT associated with the target NFT can be obtained. Here, in order for the certificate NFT to be used to verify the target NFT, the metadata of the certificate NFT may include at least NFT creation contract information and certificate information data. NFT creation contract information refers to information related to the event of the NFT creation contract creating the target NFT. The second identification information corresponding to the metadata of the certificate NFT may be identification information obtained after the metadata of the certificate NFT is stored on the blockchain, used to indicate the storage address of the metadata of the certificate NFT.

[0050] Figure 5 This is a schematic diagram illustrating the metadata of a certificate NFT according to an exemplary embodiment of the present disclosure.

[0051] Reference Figure 5 The metadata of a certificate NFT may include NFT creation contract information and certificate information data. According to an exemplary embodiment of this disclosure, NFT creation contract information may include, but is not limited to, the address of the NFT creation contract and the digital identifier (e.g., token ID) of the target NFT within the NFT creation contract. After the NFT creation contract creates the target NFT (i.e., the target token), the NFT creation contract universally uses the digital identifier (i.e., token ID) to mark and record the target NFT. For example, if the target NFT is the 100th NFT created by the NFT creation contract, then 100 can be used to mark the target NFT; therefore, the token ID of the target NFT is 100. In other words, the NFT creation contract and the token ID can uniquely identify an NFT. Therefore, NFT creation contract information may include the address of the NFT creation contract and the digital identifier of the target NFT within the NFT creation contract, thereby uniquely identifying the target NFT. Of course, the information related to NFT creation contracts is not limited to this. For example, the information related to NFT creation contracts may not include the digital identifier of the target NFT in the NFT creation contract, but may include the identifier information (token) of the target NFT, that is, the token value of the target NFT itself, and so on.

[0052] Return to reference Figure 3 In step 304, a certificate creation contract can be invoked to create a certificate NFT based on the second identification information. This certificate creation contract corresponds to the certificate verification contract. Specifically, after receiving the second identification information, the certificate creation contract can generate an identifier (e.g., a token) to identify the second identification information; this generated identifier is the certificate NFT. After the certificate NFT is created, the certificate creation contract will store it in the NFT creator's account.

[0053] According to an exemplary embodiment of this disclosure, before creating a certificate NFT, the certificate creation contract verifies the metadata of the certificate NFT. Only after the metadata of the certificate NFT is verified to be correct will the second identification information be used to create the certificate NFT, thereby ensuring that the created certificate NFT is indeed the certificate NFT of the target NFT.

[0054] According to exemplary embodiments of this disclosure, at least one piece of data related to the metadata of the certificate NFT can be verified, and if each piece of data is verified to be correct, the metadata of the certificate NFT is verified to be correct, thereby initiating the creation of the certificate NFT. If any verified data is incorrect, the creation of the certificate NFT is terminated. For example, at least one of the following can be verified: the certificate verification contract address, second identification information, and the certificate NFT creator.

[0055] According to exemplary embodiments of this disclosure, the certificate verification contract address in the metadata of a certificate NFT can be verified to prevent the certificate NFT from being created incorrectly or from being unusable for verification after creation. This is because if the certificate verification contract address in the metadata of the certificate NFT is incorrect, it indicates that the certificate verification contract does not correspond to the certificate creation contract that created the certificate NFT, which will lead to the certificate NFT being created incorrectly or unusable for verification after creation. Since the certificate creation contract and the certificate verification contract are a pair of contracts, if the certificate verification contract address is correct, the certificate creation contract address is also correct; therefore, only the correctness of the certificate verification contract address needs to be verified. The certificate verification contract address in the metadata of the certificate NFT is obtained by querying the blockchain storing the metadata of the certificate NFT using a third-party oracle based on the second identification information corresponding to the metadata of the certificate NFT. After obtaining the certificate verification contract address in the metadata of the certificate NFT, the correctness of the certificate verification contract address in the metadata of the certificate NFT can be verified based on the actual certificate verification contract address. Since the certificate creation contract and the certificate verification contract are a pair of contracts, the certificate creation contract can determine the address of the actual certificate verification contract; that is, the address of the actual certificate verification contract is determined through the address of the certificate creation contract. For example, if the certificate verification contract address in the metadata of the certificate NFT matches the actual certificate verification contract address, then the certificate verification contract address in the metadata of the certificate NFT is determined to be correct. Otherwise, the certificate verification contract address in the metadata of the certificate NFT is determined to be incorrect, and the creation of the certificate NFT is terminated.

[0056] According to exemplary embodiments of this disclosure, it is possible to verify whether the second identification information corresponding to the metadata of the certificate NFT has been used in the certificate creation contract, thereby preventing a single certificate NFT from corresponding to multiple NFTs. This is because if the second identification information has been used in the certificate creation contract, it indicates that the certificate NFT already corresponds to other NFTs, which would result in the certificate NFT corresponding to multiple NFTs, thus compromising verification reliability. In other words, the metadata of the certificate NFT should correspond to a unique identification information. Therefore, it is possible to query the creation record of the certificate creation contract to see if the second identification information has been used in creation prior to the certificate creation contract. If it is determined that the second identification information has not been used, then the second identification information is determined to be correct. Otherwise, the second identification information is determined to be incorrect, and the creation of the certificate NFT is terminated.

[0057] According to an exemplary embodiment of this disclosure, it is possible to verify whether the certificate NFT creator is correct, that is, to verify whether the certificate NFT creator is the actual NFT creator (i.e., the creator of the target NFT), thereby preventing non-NFT creators from forging certificate NFTs. This is because the creator of the target NFT and the creator of the certificate NFT should be the same person (i.e., the NFT creator), otherwise there may be cases where non-NFT creators forge certificate NFTs. According to an exemplary embodiment of this disclosure, it is possible to verify whether the certificate NFT creator is the actual NFT creator by verifying (1) whether the certificate NFT creation account address is the account address of the current certificate NFT creator and (2) whether the certificate NFT creation account address is the account address of the NFT creator. If both of the above two verifications pass, it is determined that the certificate NFT creator is the actual NFT creator; otherwise, it is determined that the certificate NFT creator is not the actual NFT creator, and the creation of the certificate NFT is terminated. Therefore, the correctness of the certificate NFT creator can be verified by verifying the correctness of the certificate NFT creation account address and the consistency between the NFT creator's public key in the certificate NFT's metadata and the certificate NFT creation account address.

[0058] For example, asymmetric encryption methods (e.g., signing with the private key of the certificate NFT creation account and decrypting with the public key of the certificate creation contract) can be used to determine whether the address of the certificate NFT creation account is the same as the address of the certificate NFT creator. For instance, the certificate creation contract sends pre-defined information to the certificate NFT creation account. The certificate NFT creation account uses its private key to encrypt and sign the pre-defined information and sends the signature to the certificate creation contract. The certificate creation contract uses its public key to decrypt the signature and verifies whether the decrypted data matches the pre-defined information. If they match, the address of the certificate NFT creation account is determined to be the address of the certificate NFT creator. If they do not match or the signature is not received, the address of the certificate NFT creation account is determined not to be the address of the certificate NFT creator. If the address of the certificate NFT creation account is determined to be the address of the certificate NFT creator, the NFT creator's account address is obtained based on the NFT creator's public key in the certificate NFT's metadata, and compared with the certificate NFT creation account address. If the NFT creator's account address matches the certificate NFT creation account address, the certificate NFT creator is determined to be correct; otherwise, the certificate NFT creator is determined to be incorrect.

[0059] Of course, this disclosure is not limited to the process described above for verifying the correctness of the metadata of a certificate NFT, and any possible methods or data may be used to verify the correctness of the metadata of a certificate NFT.

[0060] Figure 6 This is a flowchart illustrating a data verification method according to an exemplary embodiment of the present disclosure. When according to the present disclosure... Figure 3 After the data processing method shown creates the target NFT with a certificate, the user can then use it according to this disclosure. Figure 6 The data verification method shown verifies the target NFT to verify its authenticity.

[0061] Reference Figure 7 In step 601, a certificate verification contract can be invoked to verify the target NFT based on the metadata of the target NFT and the metadata of the certificate NFT associated with the target NFT; in step 602, the verification result can be output.

[0062] According to exemplary embodiments of this disclosure, NFT creation contract information can be input into a certificate verification contract, and the metadata of the target NFT and the certificate NFT can be obtained through the certificate verification contract based on the NFT creation contract information. Here, NFT creation contract information refers to information related to the event in which the NFT creation contract creates the target NFT. For example, NFT creation contract information may include, but is not limited to, the address of the NFT creation contract and the digital identifier (e.g., token ID) of the target NFT in the NFT creation contract. This disclosure does not limit the content of NFT creation contract information; for example, NFT creation contract information may also include identification information corresponding to the target NFT or identification information corresponding to the object of the target NFT, or these identification information may be used instead of the digital identifier.

[0063] According to exemplary embodiments of this disclosure, the certificate verification contract can communicate with a third-party oracle (e.g., the Chainlink oracle network). The third-party oracle, based on NFT creation contract information, retrieves the target NFT's metadata from a blockchain storing the target NFT's metadata (e.g., IPFS, AR, etc.). Specifically, the certificate verification contract and the third-party oracle are on the same blockchain. The certificate verification contract can publish a metadata retrieval request containing NFT creation contract information. After the third-party oracle receives this request from the blockchain, it retrieves the target NFT's metadata from the blockchain storing the target NFT's metadata (which is not on the same blockchain as the certificate verification contract and the third-party oracle) based on the NFT creation contract information, and publishes the retrieved target NFT's metadata on the blockchain. The certificate verification contract can then retrieve the target NFT's metadata from the blockchain.

[0064] According to exemplary embodiments of this disclosure, a certificate verification contract can communicate with a third-party oracle (e.g., the Chainlink oracle network) to obtain the metadata of the certificate NFT from the blockchain storing the metadata of the certificate NFT based on second identification information. Specifically, the certificate verification contract and the third-party oracle are on the same blockchain. The certificate verification contract can publish a metadata retrieval request containing the second identification information. After the third-party oracle receives the metadata retrieval request from the blockchain, it retrieves the metadata of the certificate NFT from the blockchain storing the metadata of the certificate NFT (which is not on the same blockchain as the certificate verification contract and the third-party oracle) based on the second identification information, and publishes the obtained metadata of the certificate NFT on the blockchain. The certificate verification contract can then retrieve the metadata of the certificate NFT from the blockchain.

[0065] According to an exemplary embodiment of this disclosure, based on NFT creation contract information, identification information corresponding to the metadata of the certificate NFT is obtained from the certificate creation contract, namely, second identification information; and based on the second identification information, the metadata of the certificate NFT is obtained from the blockchain (e.g., IPFS, AR, etc.) storing the metadata of the certificate NFT through a third-party oracle.

[0066] According to exemplary embodiments of this disclosure, at least one piece of data in the metadata of the target NFT and at least one piece of data in the metadata of the certificate NFT can be verified separately. If each verified piece of data is correct, it can be determined that the target NFT is genuine, that is, it can be determined that the target NFT was created or authorized by the NFT creator of the transaction record on the target NFT metadata, and a verification result indicating the authenticity of the target NFT is output. Once any piece of data is detected to be incorrect, it can be determined that the target NFT is forged by another party, and a prompt indicating that the authenticity of the target NFT is at risk is output. This disclosure does not limit the order of the verification process for each piece of data. For example, each piece of data can be verified simultaneously. For another example, each piece of data can be verified sequentially, and if any data fails verification, the verification is terminated and a verification result is output. For another example, at least one piece of data in the metadata of the target NFT can be verified first, and if the verification passes, at least one piece of data in the metadata of the certificate NFT can then be verified. For another example, at least one piece of data in the metadata of the certificate NFT can be verified first, and if the verification passes, at least one piece of data in the metadata of the target NFT can then be verified.

[0067] According to an exemplary embodiment of this disclosure, a first verification of the target NFT can be performed based on the metadata of the target NFT; if the first verification passes, a second verification of the target NFT can be performed based on the metadata of the certificate NFT.

[0068] According to an exemplary embodiment of this disclosure, the first verification may include verifying at least one piece of data in the metadata of the target NFT, and if the verification result of at least one piece of data is unsuccessful, then a verification result indicating that the authenticity of the target NFT is at risk is output.

[0069] For example, the data verified in the first verification may include, but is not limited to, at least one of the following: the certificate verification contract address in the metadata of the target NFT and the NFT creator account address in the metadata of the target NFT. (1) When verifying the certificate verification contract address in the metadata of the target NFT, the consistency between the certificate verification contract address in the metadata of the target NFT and the called certificate verification contract address can be verified. If the certificate verification contract address in the metadata of the target NFT is consistent with the called certificate verification contract address, it indicates that the certificate verification contract address in the metadata of the target NFT is correct, and the verification result of the certificate verification contract address in the metadata of the target NFT is passed. If they are inconsistent, it indicates that the certificate verification contract address in the metadata of the target NFT is incorrect, and the verification result of the certificate verification contract address in the metadata of the target NFT is failed, and the verification result that the authenticity of the target NFT is at risk is output. (2) When verifying the NFT creator account address in the metadata of the target NFT, the consistency between the NFT creator account address in the metadata of the target NFT and the NFT creator account address in the transaction record (i.e., the address pointed to by "to" in the creation record in the transaction record). If the NFT creator account address in the target NFT's metadata matches the NFT creator account address in the transaction record, the NFT creator account address in the target NFT's metadata is correct, and the verification result for the NFT creator account address in the target NFT's metadata is passed. If they do not match, the NFT creator account address in the target NFT's metadata is incorrect, the verification result for the NFT creator account address in the target NFT's metadata is failed, and a verification result indicating that the authenticity of the target NFT is at risk is output. The first verification in this disclosure is not limited to the above verification process and may also include verification processes for other data in the target NFT's metadata as needed or configured.

[0070] According to an exemplary embodiment of this disclosure, the second verification may include verifying at least one piece of data in the metadata of the certificate NFT, and if the verification result of at least one piece of data is unsuccessful, then a verification result indicating that the authenticity of the certificate NFT is at risk is output.

[0071] For example, the data verified by the second verification may include, but is not limited to, at least one of the following: NFT creator public key, NFT creator signature, NFT creator signature expiration time, NFT target address, NFT creation contract address, and certificate verification contract address. (1) When verifying the NFT creator public key, the NFT creator account address can be obtained based on the NFT creator public key in the metadata of the certificate NFT, and the consistency between the obtained NFT creator account address and the NFT creator account address in the metadata of the target NFT can be verified to determine whether the public key on the certificate NFT belongs to the NFT creator. Here, the hash value of the NFT creator public key can be used to deduce the NFT creator account address. Therefore, the NFT creator account address can be obtained by hashing the NFT creator public key. If the obtained NFT creator account address is consistent with the NFT creator account address in the metadata of the target NFT, it indicates that the public key on the certificate NFT belongs to the NFT creator, and the verification result of the NFT creator public key in the metadata of the certificate NFT is determined to be passed. If they are inconsistent, it means that the public key on the certificate NFT is not the NFT creator's public key. In this case, the verification result of the NFT creator's public key in the metadata of the certificate NFT is determined to be unsuccessful, and the verification result that the authenticity of the target NFT is at risk is output. (2) When verifying the NFT creator's signature, the NFT creator's public key in the metadata of the certificate NFT is used to decrypt the NFT creator's signature in the metadata of the certificate NFT, and the consistency of the data obtained after decryption with the other certificate information data in the certificate information data other than the NFT creator's signature is verified (for example, the data obtained after decryption is compared with other certificate information data item by item) to verify whether the metadata of the certificate NFT has been authorized by the NFT creator. If each item of data after decryption is consistent with the corresponding item of data in other certificate information data, it means that the metadata of the certificate NFT has been authorized by the NFT creator, and the verification result of the NFT creator's signature in the metadata of the certificate NFT is passed. If they are inconsistent, it means that the metadata of the certificate NFT is not authorized by the NFT creator. In this case, the verification result of the NFT creator signature in the metadata of the certificate NFT will be unsuccessful, and the verification result that the authenticity of the target NFT is at risk will be output. (3) When verifying the expiration time of the NFT creator signature, verify the matching of the expiration time of the NFT creator signature in the metadata of the certificate NFT with the creation time or on-chain time of the target NFT to verify whether there is an expired creation.After the NFT creation contract completes the creation of the target NFT, information related to the creation time or on-chain time is recorded on the blockchain. If the creation time or on-chain time is within the expiration time of the NFT creator's signature, that is, the two match, it means that the target NFT was created within the valid time authorized by the NFT creator. Therefore, the creation of the target NFT is authorized by the NFT creator, and the verification result of the expiration time of the NFT creator's signature in the metadata of the certificate NFT is passed. If the creation time or on-chain time exceeds the expiration time of the NFT creator's signature, that is, the two do not match, it means that the target NFT was created outside the valid time authorized by the NFT creator. It means that the creation of the target NFT is not authorized by the NFT creator, and the verification result of the expiration time of the NFT creator's signature in the metadata of the certificate NFT is failed, and the verification result that the authenticity of the target NFT is at risk is output. (4) When verifying the NFT target address, the consistency between the NFT target address in the metadata of the certificate NFT and the NFT target address in the metadata of the target NFT is verified to verify whether the NFT target corresponding to the certificate NFT is correct. If the NFT target address in the metadata of the certificate NFT is consistent with the NFT target address in the metadata of the target NFT, it means that the NFT target corresponding to the certificate NFT is correct, and the verification result of the NFT target address in the metadata of the certificate NFT is passed. If they are inconsistent, it means that the NFT target corresponding to the certificate NFT is incorrect, and the verification result of the NFT target address in the metadata of the certificate NFT is failed, and the verification result that the authenticity of the target NFT is at risk is output. (5) When verifying the NFT creation contract address, verify the consistency between the NFT creation contract address in the metadata of the certificate NFT and the NFT creation contract address in the metadata of the target NFT, so as to verify whether the target NFT corresponding to the certificate NFT is created by the NFT creation contract. If the NFT creation contract address in the metadata of the certificate NFT is consistent with the NFT creation contract address in the metadata of the target NFT, it means that the target NFT corresponding to the certificate NFT is created by the NFT creation contract, and the verification result of the NFT creation contract address in the metadata of the certificate NFT is passed. If they are inconsistent, it means that the target NFT corresponding to the certificate NFT is not created by the NFT creation contract. In this case, the verification result of the NFT creation contract address in the metadata of the certificate NFT is unsuccessful, and the verification result that the authenticity of the target NFT is at risk is output. (6) When verifying the certificate verification contract address, verify the consistency between the certificate verification contract address in the metadata of the certificate NFT and the certificate verification contract address in the metadata of the target NFT, so as to verify whether the certificate NFT is verified by the certificate verification contract specified by the target NFT.If the certificate verification contract address in the metadata of the certificate NFT matches the certificate verification contract address in the metadata of the target NFT, it means that the certificate NFT is verified by the certificate verification contract specified by the target NFT, and the verification result of the certificate verification contract address in the metadata of the certificate NFT is passed. If they do not match, it means that the certificate NFT is not verified by the certificate verification contract specified by the target NFT, and the verification result of the certificate verification contract address in the metadata of the certificate NFT is failed, and the verification result that the authenticity of the target NFT is at risk is output. The second verification disclosed herein is not limited to the above verification process, and can also skip some of the above verification processes as needed or set (for example, if the user passes the address of the NFT target when initiating verification, verification (4) needs to be performed, otherwise verification (4) can be skipped), or a verification process for other data in the metadata of the certificate NFT can be added.

[0072] According to the data processing and data verification methods disclosed herein, a certificate NFT associated with the target NFT can be created through a certificate creation contract based on certificate information data associated with the target NFT, and the target NFT can be verified using the certificate NFT associated with the target NFT through a certificate verification contract. In other words, an anti-counterfeiting certificate NFT is created for the target NFT through a pair of smart contracts (i.e., a certificate creation contract and a certificate verification contract), and the target NFT is verified through the certificate NFT, thereby ensuring the authenticity of the target NFT and preventing fraudulent activities such as SleepMinting.

[0073] Below, refer to Figure 7 and Figure 8 The process of creating a certified NFT and verifying the corresponding certificate according to the exemplary method described in this disclosure is described in detail.

[0074] Figure 7 This is a flowchart illustrating a specific creation process of a certified NFT according to an exemplary embodiment of the present disclosure.

[0075] Reference Figure 7 In step 701, the NFT object (e.g., digital files such as images and videos) can be uploaded to a blockchain (e.g., but not limited to, IPFS or AR) or cloud storage to obtain the token corresponding to the NFT object (which may be called the first token).

[0076] In step 702, certificate information data can be organized and uploaded to a blockchain (e.g., but not limited to, IPFS or AR) to obtain a token corresponding to the certificate information data (which may be called a second token). The certificate information data may include, but is not limited to, at least one of the following: NFT target address, NFT creation contract address, certificate verification contract address, NFT creator account address, NFT creator public key, NFT creator signature, and NFT creator signature expiration time.

[0077] Furthermore, this disclosure does not restrict the execution order of steps 701 and 702. For example, step 701 can be executed first, followed by step 702, or step 702 can be executed first, followed by step 701, or they can be executed simultaneously.

[0078] In step 703, the metadata of the target NFT can be organized and uploaded to the blockchain (e.g., but not limited to, IPFS or AR) to obtain the token corresponding to the metadata of the target NFT (which may be called the third token). Here, the metadata of the target NFT may include, but is not limited to, descriptive information related to the NFT, the first token, the second token, and the address of the verification certificate contract used to verify the target NFT.

[0079] In step 704, the obtained third token can be passed to the NFT creation contract in the blockchain. The NFT creation contract generates a corresponding token (which can be called the fourth token) based on the third token. The fourth token is the target NFT, meaning the target NFT creation is complete. After the target NFT is created, it can be stored in the NFT creator's account. In addition, when the target NFT is created, the token ID of the target NFT in the NFT creation contract can also be obtained.

[0080] In step 705, the metadata of the certificate NFT can be organized and uploaded to the blockchain (e.g., but not limited to, IPFS or AR) to obtain the token corresponding to the certificate NFT's metadata (which can be called the fifth token). Here, the certificate NFT's metadata may include, but is not limited to, the NFT creation contract address, token ID, and certificate information data.

[0081] In step 706, the obtained fifth token is passed to the certificate creation contract in the blockchain. The certificate creation contract verifies the correctness of the metadata of the certificate NFT. For example, the certificate creation contract may verify the correctness of the metadata of the certificate NFT from, but is not limited to, the following aspects: (1) verifying whether the certificate verification contract address in the metadata of the certificate NFT is correct to prevent incorrect certificate creation and unverifiable certificates after creation. (2) verifying whether the token corresponding to the metadata of the certificate NFT (i.e., the fifth token) has been used in the certificate creation contract to prevent one certificate from corresponding to multiple target NFTs. (3) verifying whether the creator of the certificate NFT is the NFT creator to prevent non-NFT creators from forging the certificate NFT. If any data verification fails, the creation of the certificate NFT is terminated in step 707.

[0082] In step 708, after verifying that the metadata of the certificate NFT is correct, the certificate creation contract generates a corresponding token (which can be called the sixth token) based on the fifth token. The sixth token is the certificate NFT, meaning the certificate NFT creation is complete. After the certificate NFT is created, it can be stored in the NFT creator's account.

[0083] Figure 8 This is a flowchart illustrating a specific verification process for a certified NFT according to an exemplary embodiment of the present disclosure.

[0084] Reference Figure 8 In step 801, the certificate verification contract can be invoked via web3.js through a client (e.g., a browser, application, etc.), and the NFT creation contract address and the token ID of the target NFT in the NFT creation contract can be entered into the certificate verification contract.

[0085] In step 802, the certificate verification contract can read the metadata of the target NFT from the blockchain (e.g., IPFS or AR, etc.) that stores the metadata of the target NFT, based on the NFT creation contract address and the token ID of the target NFT in the NFT creation contract, through a Chainlink third-party oracle.

[0086] In step 803, the certificate verification contract can obtain the token corresponding to the metadata of the certificate NFT from the certificate NFT creation contract based on the NFT creation contract address and the token ID of the target NFT in the NFT creation contract (i.e., Figure 7The fifth token in the chain is used to read the metadata of the certificate NFT from the blockchain (e.g., IPFS or AR) that stores the metadata of the target NFT, through a Chainlink third-party oracle. This disclosure does not restrict the execution order of steps 802 and 803. For example, they can be executed simultaneously, or step 802 can be executed first and then step 803, or step 803 can be executed first and then step 802.

[0087] In step 804, the certificate verification contract can perform verification on the metadata of the target NFT. For example, but not limited to, it can perform verification on the certificate verification contract address and the NFT creator account address in the metadata of the target NFT, respectively. If any data verification fails, in step 805, a verification result indicating that the target NFT is at risk of fraud is output.

[0088] In step 806, if the verification of the certificate NFT's metadata passes, the certificate verification contract can perform verification on the certificate NFT's metadata. For example, but not limited to, it can separately verify the NFT target address, NFT creation contract address, certificate verification contract address, NFT creator account address, NFT creator public key, NFT creator signature, and NFT creator signature expiration time within the certificate NFT's metadata. If any data verification fails, in step 805, a verification result indicating a fraud risk associated with the target NFT is output.

[0089] In step 807, if the verification of the metadata of the certificate NFT is successful, the output indicates that the target NFT is a genuine verification result.

[0090] Figure 9 This is a block diagram illustrating a data processing apparatus according to an exemplary embodiment of the present disclosure.

[0091] Reference Figure 9 The data processing apparatus 900 according to an exemplary embodiment of the present disclosure may include a first identification information acquisition unit 901, a target NFT creation unit 902, a second identification information acquisition unit 903, and a certificate NFT creation unit 904.

[0092] The first identification information acquisition unit 901 can acquire the first identification information corresponding to the metadata of the target NFT. Here, the target NFT may refer to the NFT created by the NFT creator for its NFT object (e.g., digital files such as images and videos).

[0093] According to exemplary embodiments of this disclosure, the metadata of the target NFT may include identification information corresponding to the NFT and any descriptive information related to the NFT. Here, the identification information corresponding to the NFT may be identification information obtained after the NFT is stored in a blockchain or cloud storage, used to indicate the storage address of the NFT. Of course, the metadata of the target NFT is not limited to the information described above.

[0094] According to exemplary embodiments of this disclosure, in order to generate a target NFT with a certificate, the metadata of the target NFT needs to include at least the data used to verify the target NFT. For example, the metadata of the target NFT may also include, but is not limited to, identification information corresponding to the certificate information data associated with the target NFT, and the address of the certificate verification contract used to verify the target NFT. Here, the certificate information data may include data used by the certificate verification contract to verify the target NFT. The identification information corresponding to the certificate information data may be identification information obtained after the certificate information data is stored in the blockchain, used to indicate the address where the certificate information data is stored. The address of the certificate verification contract refers to the storage address of the certificate verification contract in the blockchain.

[0095] According to exemplary embodiments of this disclosure, certificate information data may include, but is not limited to, at least one of the following: NFT target address, NFT creation contract address, certificate verification contract address, NFT creator account address, NFT creator public key, NFT creator signature, and NFT creator signature expiration time. Of course, the certificate information data of this disclosure is not limited to the above data and may include other certificate information data that may be verified as needed, for subsequent verification of the target NFT by the certificate verification contract.

[0096] The target NFT creation unit 902 can invoke an NFT creation contract to create a target NFT based on the first identification information. Specifically, the target NFT creation unit 902 can generate an identifier (e.g., a token) from the first identification information through the NFT creation contract; this generated identifier is the target NFT. After the target NFT is created, the target NFT creation unit 902 can store the target NFT in the NFT creator's account through the NFT creation contract.

[0097] The second identification information acquisition unit 903 can acquire the second identification information corresponding to the metadata of the certificate NFT related to the target NFT. Here, in order for the certificate NFT to be used to verify the target NFT, the metadata of the certificate NFT may include at least NFT creation contract related information and certificate information data. The NFT creation contract related information refers to information related to the event of the NFT creation contract creating the target NFT. The second identification information corresponding to the metadata of the certificate NFT may be identification information obtained after the metadata of the certificate NFT is stored in the blockchain, which is used to indicate the storage address of the metadata of the certificate NFT.

[0098] According to exemplary embodiments of this disclosure, NFT creation contract information may include, but is not limited to, the address of the NFT creation contract and the digital identifier (e.g., token ID) of the target NFT in the NFT creation contract. Of course, NFT creation contract information is not limited to this; for example, it may not include the digital identifier of the target NFT in the NFT creation contract, but may include the target NFT's token information, i.e., the token value of the target NFT itself, and so on.

[0099] The certificate NFT creation unit 904 can invoke a certificate creation contract to create a certificate NFT based on the second identification information. This certificate creation contract corresponds to the certificate verification contract. Specifically, the certificate NFT creation unit 904 can use the certificate creation contract to generate an identifier (e.g., a token) to identify the second identification information; this generated identifier is the certificate NFT. After the certificate NFT is created, the certificate NFT creation unit 904 can use the certificate creation contract to store the certificate NFT in the NFT creator's account.

[0100] According to an exemplary embodiment of this disclosure, the certificate NFT creation unit 904 can verify the metadata of the certificate NFT before creating the certificate NFT through a certificate creation contract. Only after the metadata of the certificate NFT has been verified to be correct will the certificate NFT be created using the second identification information, thereby ensuring that the created certificate NFT is indeed the certificate NFT of the target NFT.

[0101] According to an exemplary embodiment of this disclosure, the certificate NFT creation unit 904 can verify at least one piece of data related to the metadata of the certificate NFT. If each piece of data is verified correctly, the metadata of the certificate NFT is verified as correct, and the creation of the certificate NFT begins. If any verified data is incorrect, the creation of the certificate NFT is terminated. For example, the certificate NFT creation unit 904 can verify at least one of the following: the certificate verification contract address, the second identification information, and the certificate NFT creator. According to an exemplary embodiment of this disclosure, the certificate NFT creation unit 904 can verify whether the certificate verification contract address in the metadata of the certificate NFT is correct, thereby preventing the certificate NFT from being created incorrectly or the created certificate NFT from being unusable for verification. This is because if the certificate verification contract address in the metadata of the certificate NFT is incorrect, it indicates that the certificate verification contract does not correspond to the certificate creation contract that created the certificate NFT, which will lead to the certificate NFT being created incorrectly or the created certificate NFT being unusable for verification. The certificate verification contract address in the metadata of the certificate NFT can be obtained by querying the blockchain storing the metadata of the certificate NFT using a third-party oracle based on the second identification information corresponding to the metadata of the certificate NFT. After obtaining the certificate verification contract address from the certificate NFT's metadata, its correctness can be verified based on the actual certificate verification contract address. Since the certificate creation contract and the certificate verification contract are a pair, the certificate creation contract determines the address of the actual certificate verification contract; that is, the actual certificate verification contract address is determined through the address of the certificate creation contract. For example, if the certificate verification contract address in the certificate NFT's metadata matches the actual certificate verification contract address, then the certificate verification contract address in the certificate NFT's metadata is determined to be correct. Otherwise, the certificate verification contract address in the certificate NFT's metadata is determined to be incorrect, and the creation of the certificate NFT is terminated.

[0102] According to an exemplary embodiment of this disclosure, the certificate NFT creation unit 404 can verify whether the second identifier corresponding to the metadata of the certificate NFT has been used in the certificate creation contract, thereby preventing a single certificate NFT from corresponding to multiple NFTs. This is because if the second identifier information has been used in the certificate creation contract, it indicates that the certificate NFT already corresponds to other NFTs, which would result in the certificate NFT corresponding to multiple NFTs and a loss of verification reliability. In other words, the metadata of the certificate NFT should correspond to a unique identifier. Therefore, the creation record of the certificate creation contract can be queried to see if the second identifier information has been used in creations prior to the certificate creation contract. If it is determined that the second identifier information has not been used, then the second identifier information is determined to be correct. Otherwise, the second identifier information is determined to be incorrect, and the creation of the certificate NFT is terminated.

[0103] According to an exemplary embodiment of this disclosure, the certificate NFT creation unit 904 can verify whether the certificate NFT creator is correct, that is, verify whether the certificate NFT creator is the NFT creator (i.e., the creator of the target NFT) himself, thereby preventing non-NFT creators from forging the certificate NFT. This is because the creator of the target NFT and the creator of the certificate NFT should be the same person (i.e., the NFT creator), otherwise there may be a situation where non-NFT creators forge the certificate NFT. According to an exemplary embodiment of this disclosure, the certificate NFT creation unit 904 can verify whether the certificate NFT creator is the NFT creator by verifying (1) whether the certificate NFT creation account address is the account address of the current certificate NFT creator and (2) whether the certificate NFT creation account address is the account address of the NFT creator. If both of the above two verifications pass, it is determined that the certificate NFT creator is the NFT creator; otherwise, it is determined that the certificate NFT creator is not the NFT creator, and the creation of the certificate NFT is terminated. Therefore, the correctness of the certificate NFT creator can be verified by verifying the correctness of the account address used to create the certificate NFT and the consistency between the NFT creator's public key in the certificate NFT's metadata and the account address used to create the certificate NFT.

[0104] For example, asymmetric encryption methods (e.g., signing with the private key of the certificate NFT creation account and decrypting with the public key of the certificate creation contract) can be used to determine whether the certificate NFT creation account address is the same as the certificate NFT creator's account address. If the certificate NFT creation account address is determined to be the same as the certificate NFT creator's account address, the NFT creator's account address is derived based on the NFT creator's public key in the certificate NFT's metadata, and the consistency between the derived NFT creator's account address and the certificate NFT creation account address is verified. If the derived NFT creator's account address matches the certificate NFT creation account address, the certificate NFT creator is determined to be correct; otherwise, the certificate NFT creator is determined to be incorrect.

[0105] Of course, this disclosure is not limited to the process described above for verifying the correctness of the metadata of a certificate NFT, and any possible methods or data may be used to verify the correctness of the metadata of a certificate NFT.

[0106] Figure 10 This is a block diagram illustrating a data verification apparatus according to an exemplary embodiment of the present disclosure.

[0107] Reference Figure 10 The data verification apparatus 1000 according to an exemplary embodiment of the present disclosure may include a target NFT verification unit 1001 and a verification result output unit 1002.

[0108] The target NFT verification unit 1001 can invoke a certificate verification contract to verify the target NFT based on its metadata and the metadata of the certificate NFT associated with it. The verification result output unit 1002 can output the verification result.

[0109] According to an exemplary embodiment of this disclosure, the target NFT verification unit 1001 can input NFT creation contract related information into a certificate verification contract, and obtain the metadata of the target NFT and the certificate NFT based on the NFT creation contract related information through the certificate verification contract. Here, NFT creation contract related information refers to information related to the event of the NFT creation contract creating the target NFT. For example, NFT creation contract related information may include, but is not limited to, the address of the NFT creation contract and the digital identifier (e.g., token ID) of the target NFT in the NFT creation contract. This disclosure does not limit the content of NFT creation contract related information. For example, NFT creation contract related information may also include the identification information corresponding to the target NFT or the identification information corresponding to the object of the target NFT, or these identification information may be used to replace the digital identifier. According to an exemplary embodiment of this disclosure, the target NFT verification unit 1001 can communicate with a third-party oracle (e.g., Chainlink oracle network) through the certificate verification contract, and use the third-party oracle to obtain the target NFT metadata from the blockchain (e.g., IPFS, AR, etc.) storing the target NFT metadata based on the NFT creation contract related information. The target NFT verification unit 1001 can communicate with a third-party oracle (e.g., the Chainlink oracle network) through a certificate verification contract, and use the third-party oracle to obtain the metadata of the certificate NFT from the blockchain storing the metadata of the certificate NFT based on the second identification information.

[0110] According to an exemplary embodiment of this disclosure, the target NFT verification unit 1001 can obtain the identification information corresponding to the metadata of the certificate NFT from the certificate creation contract based on the NFT creation contract information, that is, the second identification information; and obtain the metadata of the certificate NFT from the blockchain (e.g., IPFS, AR, etc.) that stores the metadata of the certificate NFT based on the second identification information through a third-party oracle.

[0111] According to an exemplary embodiment of this disclosure, the target NFT verification unit 1001 can verify at least one piece of data in the metadata of the target NFT and at least one piece of data in the metadata of the certificate NFT. If each verified piece of data is correct, it can be determined that the target NFT is genuine, that is, it can be determined that the target NFT was created or authorized by the NFT creator in the transaction record on the target NFT metadata, and the verification result output unit 1002 can output a verification result indicating that the target NFT is genuine. Once an incorrect piece of data is detected, the target NFT verification unit 1001 can determine that the target NFT has been forged by someone else, and the verification result output unit 1002 can output a prompt indicating that there is a risk to the authenticity of the target NFT.

[0112] According to an exemplary embodiment of this disclosure, the target NFT verification unit 1001 may perform a first verification on the target NFT based on the metadata of the target NFT; if the first verification passes, it may perform a second verification on the target NFT based on the metadata of the certificate NFT.

[0113] According to an exemplary embodiment of this disclosure, the first verification performed by the target NFT verification unit 1001 may include verifying at least one piece of data in the metadata of the target NFT. If the verification result of at least one piece of data is unsuccessful, the verification result output unit 1002 outputs a verification result indicating that there is a risk to the authenticity of the target NFT.

[0114] For example, the data verified by the first verification performed by the target NFT verification unit 1001 may include, but is not limited to, at least one of the following: the certificate verification contract address in the metadata of the target NFT and the NFT creator account address in the metadata of the target NFT. (1) The target NFT verification unit 1001 verifies the consistency between the certificate verification contract address in the metadata of the target NFT and the called certificate verification contract address. If the certificate verification contract address in the metadata of the target NFT is consistent with the called certificate verification contract address, it means that the certificate verification contract address in the metadata of the target NFT is correct, and the verification result of the certificate verification contract address in the metadata of the target NFT is passed. If they are inconsistent, it means that the certificate verification contract address in the metadata of the target NFT is incorrect, and the verification result of the certificate verification contract address in the metadata of the target NFT is failed, and the verification result output unit 1002 outputs the verification result that the authenticity of the target NFT is at risk. (2) The target NFT verification unit 1001 verifies the consistency between the NFT creator account address in the metadata of the target NFT and the NFT creator account address in the transaction record (i.e., the address pointed to by "to" in the creation record of the transaction record). If the NFT creator account address in the metadata of the target NFT is consistent with the NFT creator account address in the transaction record, it indicates that the NFT creator account address in the metadata of the target NFT is correct, and the verification result of the NFT creator account address in the metadata of the target NFT is passed. If they are inconsistent, it indicates that the NFT creator account address in the metadata of the target NFT is incorrect, and the verification result of the NFT creator account address in the metadata of the target NFT is failed. The verification result output unit 1002 outputs the verification result that the authenticity of the target NFT is at risk. The first verification of this disclosure is not limited to the above verification process, and may also include a verification process for other data in the metadata of the target NFT as needed or set.

[0115] According to an exemplary embodiment of this disclosure, the second verification performed by the target NFT verification unit 1001 may include verifying at least one piece of data in the metadata of the certificate NFT. If the verification result of at least one piece of data is unsuccessful, the verification result output unit 1002 outputs a verification result indicating that there is a risk to the authenticity of the target NFT.

[0116] For example, the data verified by the second verification performed by the target NFT verification unit 1001 may include, but is not limited to, at least one of the following: NFT creator public key, NFT creator signature, NFT creator signature expiration time, NFT target address, NFT creation contract address, and certificate verification contract address. (1) The target NFT verification unit 1001 obtains the NFT creator account address based on the NFT creator public key in the metadata of the certificate NFT, and verifies the consistency between the obtained NFT creator account address and the NFT creator account address in the metadata of the target NFT, so as to determine whether the public key on the certificate NFT belongs to the NFT creator. Here, the hash value of the NFT creator public key can be used to derive the NFT creator account address. Therefore, the NFT creator account address can be obtained by hashing the NFT creator public key. If the obtained NFT creator account address is consistent with the NFT creator account address in the metadata of the target NFT, it indicates that the public key on the certificate NFT belongs to the NFT creator, and the verification result of the NFT creator public key in the metadata of the certificate NFT is determined to be passed. If they are inconsistent, it means that the public key on the certificate NFT is not the NFT creator's public key. In this case, the verification result of the NFT creator's public key in the metadata of the certificate NFT is determined to be unsuccessful, and the verification result output unit 1002 outputs the verification result that the authenticity of the target NFT is at risk. (2) The target NFT verification unit 1001 uses the NFT creator's public key in the metadata of the certificate NFT to decrypt the NFT creator's signature in the metadata of the certificate NFT, and verifies the consistency between the data obtained after decryption and the other certificate information data in the certificate information data except for the NFT creator's signature (for example, comparing the data obtained after decryption with other certificate information data item by item) to verify whether the metadata of the certificate NFT has been authorized by the NFT creator. If each item of data after decryption is consistent with the corresponding item of data in other certificate information data, it means that the metadata of the certificate NFT has been authorized by the NFT creator, and the verification result of the NFT creator's signature in the metadata of the certificate NFT is successful. If they are inconsistent, otherwise it means that the metadata of the certificate NFT is not authorized by the NFT creator. In this case, the verification result of the NFT creator signature in the metadata of the certificate NFT is unsuccessful, and the verification result output unit 1002 outputs the verification result that the authenticity of the target NFT is at risk. (3) The target NFT verification unit 1001 verifies the matching between the expiration time of the NFT creator signature in the metadata of the certificate NFT and the creation time or on-chain time of the target NFT to verify whether there is an expired creation.After the NFT creation contract completes the creation of the target NFT, information related to the creation time or on-chain time is recorded on the blockchain. If the creation time or on-chain time is within the expiration time of the NFT creator's signature, that is, the two match, it means that the target NFT was created within the valid time authorized by the NFT creator. Therefore, the creation of the target NFT is authorized by the NFT creator, and the verification is successful. If the creation time or on-chain time exceeds the expiration time of the NFT creator's signature, that is, the two do not match, it means that the target NFT was created outside the valid time authorized by the NFT creator. Therefore, the creation of the target NFT is not authorized by the NFT creator. The verification result of the expiration time of the NFT creator's signature in the metadata of the certificate NFT is unsuccessful, and the verification result output unit 1002 outputs the verification result that the authenticity of the target NFT is at risk. (4) The target NFT verification unit 1001 verifies the consistency between the NFT target address in the metadata of the certificate NFT and the NFT target address in the metadata of the target NFT to verify whether the NFT target corresponding to the certificate NFT is correct. If the NFT target address in the metadata of the certificate NFT is consistent with the NFT target address in the metadata of the target NFT, it means that the NFT target corresponding to the certificate NFT is correct, and the verification result of the NFT target address in the metadata of the certificate NFT is passed. If they are inconsistent, it means that the NFT target corresponding to the certificate NFT is incorrect, and the verification result of the NFT target address in the metadata of the certificate NFT is failed. The verification result output unit 1002 outputs the verification result that the authenticity of the target NFT is at risk. (5) The target NFT verification unit 1001 verifies the consistency between the NFT creation contract address in the metadata of the certificate NFT and the NFT creation contract address in the metadata of the target NFT, so as to verify whether the target NFT corresponding to the certificate NFT is created by the NFT creation contract. If the NFT creation contract address in the metadata of the certificate NFT is consistent with the NFT creation contract address in the metadata of the target NFT, it means that the target NFT corresponding to the certificate NFT is created by the NFT creation contract, and the verification result of the NFT creation contract address in the metadata of the certificate NFT is passed. If they are inconsistent, it means that the target NFT corresponding to the certificate NFT is not created by the NFT creation contract. In this case, the verification result of the NFT creation contract address in the metadata of the certificate NFT is unsuccessful, and the verification result output unit 1002 outputs the verification result that the authenticity of the target NFT is at risk. (6) The target NFT verification unit 1001 verifies the consistency between the certificate verification contract address in the metadata of the certificate NFT and the certificate verification contract address in the metadata of the target NFT, so as to verify whether the certificate NFT is verified by the certificate verification contract specified by the target NFT.If the certificate verification contract address in the metadata of the certificate NFT matches the certificate verification contract address in the metadata of the target NFT, it means that the certificate NFT is verified by the certificate verification contract specified by the target NFT, and the verification result of the certificate verification contract address in the metadata of the certificate NFT is passed. If they do not match, it means that the certificate NFT is not verified by the certificate verification contract specified by the target NFT, and the verification result of the certificate verification contract address in the metadata of the certificate NFT is failed, and the verification result output unit 1002 outputs the verification result that the authenticity of the target NFT is at risk. The first verification of this disclosure is not limited to the above verification process, and can also skip some of the above verification processes as needed or set (for example, if the user enters the address of the NFT target when initiating verification, verification (4) needs to be performed, otherwise verification (4) can be skipped), or a verification process for other data in the metadata of the certificate NFT can be added.

[0117] Figure 11 This is a block diagram of an electronic device 1100 according to an exemplary embodiment of the present disclosure.

[0118] Reference Figure 11 The electronic device 11 includes at least one memory 1101 and at least one processor 1102. The at least one memory 1101 stores a set of computer-executable instructions. When the set of computer-executable instructions is executed by the at least one processor 1102, a data processing method and a data verification method according to exemplary embodiments of the present disclosure are performed.

[0119] As an example, electronic device 1100 may be a PC, tablet, personal digital assistant, smartphone, or other device capable of executing the aforementioned set of instructions. Here, electronic device 1100 is not necessarily a single electronic device, but may be a collection of any devices or circuits capable of executing the aforementioned instructions (or instruction sets) individually or in combination. Electronic device 1100 may also be part of an integrated control system or system manager, or may be configured to interconnect with a portable electronic device locally or remotely (e.g., via wireless transmission) through an interface.

[0120] In electronic device 1100, processor 1102 may include a central processing unit (CPU), a graphics processing unit (GPU), a programmable logic device, a dedicated processor system, a microcontroller, or a microprocessor. By way of example and not limitation, processor may also include analog processors, digital processors, microprocessors, multi-core processors, processor arrays, network processors, etc.

[0121] The processor 1102 can execute instructions or code stored in the memory 1101, which can also store data. Instructions and data can also be sent and received over a network via a network interface device, which can employ any known transmission protocol.

[0122] The memory 1101 may be integrated with the processor 1102, for example, by arranging RAM or flash memory within an integrated circuit microprocessor. Alternatively, the memory 1101 may include a separate device, such as an external disk drive, a storage array, or other storage device usable by any database system. The memory 1101 and the processor 1102 may be operatively coupled, or may communicate with each other, for example, via I / O ports, network connections, etc., enabling the processor 1102 to read files stored in the memory.

[0123] In addition, electronic device 1100 may also include a video display (such as a liquid crystal display) and a user interaction interface (such as a keyboard, mouse, touch input device, etc.). All components of electronic device 1100 can be interconnected via a bus and / or network.

[0124] According to exemplary embodiments of the present disclosure, a computer-readable storage medium storing instructions may also be provided, wherein when the instructions are executed by at least one processor, they cause at least one processor to perform a data processing method and a data verification method according to the present disclosure. Examples of computer-readable storage media herein include: read-only memory (ROM), random access programmable read-only memory (PROM), electrically erasable programmable read-only memory (EEPROM), random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), flash memory, non-volatile memory, CD-ROM, CD-R, CD+R, CD-RW, CD+RW, DVD-ROM, DVD-R, DVD+R, DVD-RW, DVD+RW, DVD-RAM, BD-ROM, BD-R, BD-R LTH, BD-RE, Blu-ray or optical disc storage, hard disk drive (HDD), solid-state drive (SSD), card storage (such as multimedia cards, secure digital (SD) cards, or ultra-fast digital (XD) cards), magnetic tape, floppy disk, magneto-optical data storage device, optical data storage device, hard disk, solid-state drive, and any other device configured to store a computer program and any associated data, data files, and data structures in a non-transitory manner and to provide the computer program and any associated data, data files, and data structures to a processor or computer so that the processor or computer can execute the computer program. The computer program in the aforementioned computer-readable storage medium can run in an environment deployed in computer devices such as clients, hosts, agent devices, servers, etc. Furthermore, in one example, the computer program and any associated data, data files, and data structures are distributed across a networked computer system, such that the computer program and any associated data, data files, and data structures are stored, accessed, and executed in a distributed manner through one or more processors or computers.

[0125] According to exemplary embodiments of the present disclosure, a computer program product may also be provided, wherein the instructions in the computer program product can be executed by a processor of a computer device to perform a data processing method and a data verification method according to exemplary embodiments of the present disclosure.

[0126] According to the data processing and data verification methods disclosed herein, a counterfeit-proof certificate NFT can be created for a target NFT through a pair of smart contracts, and the authenticity of the target NFT can be verified using the certificate NFT, ensuring the authenticity of the NFT creation process, preventing fraudulent activities such as SleepMinting, and protecting the rights and interests of NFT creators and NFT collectors.

[0127] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0128] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A data processing method, characterized in that, include: Obtain first identification information corresponding to the metadata of the target NFT. The first identification information is the identification information obtained after the metadata of the target NFT is stored in the blockchain. The metadata of the target NFT includes at least identification information corresponding to the certificate information data associated with the target NFT and the address of the certificate verification contract used to verify the target NFT. The identification information corresponding to the certificate information data is the identification information obtained after the certificate information data is stored in the blockchain. Invoke the NFT creation contract to create the target NFT based on the first identification information; Obtain second identification information corresponding to the metadata of the certificate NFT associated with the target NFT, wherein the metadata of the certificate NFT includes at least the information related to the NFT creation contract and the certificate information data, and the second identification information is the identification information obtained after the metadata of the certificate NFT is stored in the blockchain; The certificate creation contract is invoked to create the certificate NFT based on the second identification information, wherein the certificate creation contract corresponds to the certificate verification contract.

2. The method as described in claim 1, characterized in that, The certificate information data includes data used by the certificate verification contract to verify the target NFT.

3. The method as described in claim 2, characterized in that, The certificate information data includes at least one of the following: NFT object address, NFT creation contract address, certificate verification contract address, NFT creator account address, NFT creator public key, NFT creator signature, and NFT creator signature expiration time.

4. The method as described in claim 1, characterized in that, The information related to the NFT creation contract includes the address of the NFT creation contract and the digital identifier of the target NFT in the NFT creation contract.

5. The method as described in claim 1, characterized in that, Before creating the certificate NFT based on the second identification information, the method further includes: Verify the metadata of the certificate NFT; The step of creating the certificate NFT based on the second identification information includes: If the metadata of the certificate NFT is verified to be correct, the certificate NFT is created based on the second identification information.

6. The method as described in claim 5, characterized in that, The verification of the metadata of the certificate NFT includes: Verify at least one piece of data related to the metadata of the certificate NFT; If each piece of data is verified to be correct, then the metadata of the certificate NFT is verified to be correct. The at least one piece of data includes at least one of the following: certificate verification contract address, the second identification information, and certificate NFT creator.

7. The method as described in claim 6, characterized in that, When at least one piece of data includes a certificate verification contract address, the verification of the metadata of the certificate NFT includes: If the certificate verification contract address matches the actual certificate verification contract address, then the certificate verification contract address in the metadata of the certificate NFT is determined to be correct, wherein the actual certificate verification contract address is determined by the address of the certificate creation contract. Wherein, if at least one piece of data includes the second identification information, the verification of the metadata of the certificate NFT includes: Determine whether the second identification information has been used in the certificate creation contract; If the second identification information has not been used in the certificate creation contract, the second identification information is determined to be correct; Wherein, if at least one piece of data includes the creator of the certificate NFT, the verification of the metadata of the certificate NFT includes: The method of signing with the private key of the certificate NFT creation account and decrypting with the public key of the certificate creation contract is used to determine whether the certificate NFT creation account address is the account address of the certificate NFT creator. If it is determined that the certificate NFT creation account address is the account address of the certificate NFT creator, the NFT creator account address is obtained based on the NFT creator's public key in the certificate NFT's metadata, and the NFT creator account address is compared with the certificate NFT creation account address; If the NFT creator's account address matches the certificate NFT creation account address, the certificate NFT creator is determined to be correct.

8. A data verification method, characterized in that, include: Invoke the certificate verification contract to verify the target NFT based on the target NFT's metadata and the metadata of the certificate NFT associated with the target NFT; Output the verification results; The target NFT is created by an NFT creation contract based on the first identifier information corresponding to the metadata of the target NFT, and the certificate NFT is created by a certificate creation contract corresponding to the certificate verification contract based on the second identifier information corresponding to the metadata of the certificate NFT. The metadata of the target NFT includes at least the identifier information corresponding to the certificate information data associated with the target NFT, and the address of the certificate verification contract used to verify the target NFT. The metadata of the certificate NFT includes at least the information related to the NFT creation contract and the certificate information data. The first identification information is the identification information obtained after the metadata of the target NFT is stored in the blockchain. The identification information corresponding to the certificate information data is the identification information obtained after the certificate information data is stored in the blockchain. The second identification information is the identification information obtained after the metadata of the certificate NFT is stored in the blockchain.

9. The method as described in claim 8, characterized in that, The verification of the target NFT based on the metadata of the target NFT and the metadata of the certificate NFT associated with the target NFT includes: The target NFT is first verified based on its metadata; If the first verification passes, the target NFT is then verified a second time based on the metadata of the certificate NFT.

10. The method as described in claim 9, characterized in that, The first verification includes: Verify at least one piece of data in the metadata of the target NFT; The output verification result includes: If the verification result of at least one of the data is unsuccessful, then a verification result indicating that the authenticity of the target NFT is at risk is output.

11. The method as described in claim 10, characterized in that, The at least one piece of data includes the certificate verification contract address in the metadata of the target NFT and the NFT creator account address in the metadata of the target NFT. Verifying each of the at least one piece of data in the metadata of the target NFT includes: If the certificate verification contract address in the metadata of the target NFT is consistent with the certificate verification contract address that is invoked, then the verification result of the certificate verification contract address in the metadata of the target NFT is passed. If the NFT creator account address in the metadata of the target NFT matches the NFT creator account address in the transaction record, then the verification result of the NFT creator account address in the metadata of the target NFT is passed.

12. The method as described in claim 9, characterized in that, The second verification includes: Verify at least one piece of data in the metadata of the certificate NFT; The output verification result includes: If the verification result of at least one of the data is unsuccessful, a verification result indicating that the authenticity of the certificate NFT is at risk will be output.

13. The method as described in claim 12, characterized in that, The at least one piece of data includes the NFT creator's public key, NFT creator's signature, NFT creator's signature expiration time, NFT target address, NFT creation contract address, and certificate verification contract address from the metadata of the certificate NFT. The verification of at least one piece of data in the metadata of the certificate NFT includes: The NFT creator's account address is obtained based on the NFT creator's public key in the metadata of the certificate NFT. If the obtained NFT creator's account address is consistent with the NFT creator's account address in the metadata of the target NFT, then the verification result of the NFT creator's public key in the metadata of the certificate NFT is passed. The NFT creator's public key in the metadata of the certificate NFT is used to decrypt the NFT creator's signature in the metadata of the certificate NFT. If the data obtained after decryption is consistent with the other certificate information data in the certificate information data except for the NFT creator's signature, then the verification result of the NFT creator's signature in the metadata of the certificate NFT is passed. If the expiration time of the NFT creator's signature in the metadata of the certificate NFT matches the creation time or on-chain time of the target NFT, then the verification result of the expiration time of the NFT creator's signature in the metadata of the certificate NFT is passed. If the NFT target address in the metadata of the certificate NFT is consistent with the NFT target address in the metadata of the target NFT, then the verification result of the NFT target address in the metadata of the certificate NFT is passed. If the NFT creation contract address in the metadata of the certificate NFT is consistent with the NFT creation contract address in the metadata of the target NFT, then the verification result of the NFT creation contract address in the metadata of the certificate NFT is passed. If the certificate verification contract address in the metadata of the certificate NFT is consistent with the certificate verification contract address in the metadata of the target NFT, then the verification result of the certificate verification contract address in the metadata of the certificate NFT is passed.

14. An electronic device, characterized in that, include: At least one processor; At least one memory that stores computer-executable instructions. The computer-executable instructions, when executed by the at least one processor, cause the at least one processor to perform the data processing method as described in any one of claims 1 to 7 or the data verification method as described in any one of claims 8 to 13.

15. A computer-readable storage medium, characterized in that, When the instructions in the computer-readable storage medium are executed by at least one processor, the at least one processor causes the at least one processor to perform the data processing method as claimed in any one of claims 1 to 7 or the data verification method as claimed in any one of claims 8 to 13.

Images