Digital asset certificate management device and method thereof

Abstract

The digital asset storage and management device includes a processing element that responds to an instruction to access a computer-readable instruction from a storage element to automatically generate a virtual electronic wallet associated with an identity credential, generate metadata associated with a digital asset file, invoke a smart contract on a blockchain to mint a non-fungible token based on the metadata, and record the non-fungible token in the virtual electronic wallet.

Description

[Technical Field]

[0001] This invention relates to the management of digital asset notarization, and more particularly to a digital asset notarization management device and corresponding method using non-fungible tokens. [Previous Technology]

[0002] Digital asset notarization has begun to utilize blockchain networks to prove the existence of digital assets.

[0003] However, the ever-increasing prices of Bitcoin and Ethereum have gradually raised the transaction costs associated with blockchain-based notarization, further discouraging users from notarizing or even trading digital assets. Furthermore, blockchain transactions require management through e-wallets, which are not user-friendly for ordinary consumers or businesses, thus affecting their willingness to notarize and retain authorization records for digital assets.

[0004] Therefore, how to reduce and simplify the management complexity of existing digital asset notarization is a problem that those skilled in the art urgently want to solve. [Summary of the Invention]

[0005] According to one embodiment of this case, a digital asset storage and management device includes: a processing element; and a storage element coupled to the processing element, wherein the storage element stores a plurality of computer-readable instructions, and the processing element, in response to an instruction, accesses the plurality of computer-readable instructions from the storage element to execute: automatically generating a virtual electronic wallet associated with a user's identity credential; generating a hash associated with a user's digital asset profile; generating a Uniform Resource Identifier (URI) associated with the digital asset profile; calling a smart contract on a blockchain to mint a non-fungible token based on the hash and the URI; and generating a related... The system includes a webpage for storing information about the non-fungible token (NFG); and a virtual wallet for recording transactions associated with the NFG. The virtual wallet, automatically generated based on the user's identity credentials, further includes: a user identification code generated after successful verification of the user's identity by a third-party verification platform as a first separate key; an identity credential generated after successful verification of the user's identity by the third-party verification platform as a second separate key; a set password as a third separate key; and, according to a separate key verification rule, using the first, second, and third separate keys to form a private key to perform a digital signature and establish the virtual wallet.

[0006] In some embodiments, the split key verification rule is to use either the second split key or the third split key, along with the first split key, to form the private key to establish the virtual electronic wallet. The first split key and the third split key are stored in different storage devices, and the split key verification rule that forms the private key is reset after the minting of the non-fungible tokens is completed.

[0007] In some embodiments, the processing element further associates the non-fungible token with the virtual wallet.

[0008] In some embodiments, the hash code is the token name of the non-fungible token.

[0009] In some embodiments, the hash code and the Uniform Resource Identifier are metadata for the smart contract to mint the non-fungible token.

[0010] In some embodiments, the evidence storage webpage associated with the non-fungible token records a digital asset description information of the non-fungible token, including file name, digital asset file size, and digital asset file creation date.

[0011] According to another aspect of this case, a digital asset storage and management method includes: verifying a user's identity information to generate an identity certificate; automatically generating a virtual electronic wallet associated with the identity certificate; generating a hash code and a Uniform Resource Identifier associated with the digital asset file based on the user's digital asset file; calling a smart contract on a blockchain to mint a non-fungible token based on the hash code and the Uniform Resource Identifier; and updating the virtual electronic wallet to record the non-fungible token, wherein automatically generating the virtual electronic wallet associated with the identity certificate further includes: generating a first split key based on a user identification code after the user's identity is verified by a third-party verification platform; generating a second split key based on an identity certificate after the user's identity is verified by the third-party verification platform; generating a third split key based on a set password; and forming a private key using the first split key, the second split key, and the third split key according to a split key verification rule to execute a digital signature and establish the virtual electronic wallet.

[0012] In some embodiments, the split key verification rule is to use either the second split key or the third split key, along with the first split key, to form the private key to establish the virtual electronic wallet. The first split key and the third split key are stored in different storage devices, and the split key verification rule that forms the private key is reset after the minting of the non-fungible tokens is completed.

[0013] In some embodiments, the digital asset notarization management method further includes: generating a notarization webpage associated with the nonfungible token based on the Uniform Resource Identifier.

[0014] In some embodiments, the evidence storage webpage records digital asset profile information of the non-fungible token, including the profile name, the size of the digital asset profile, and the creation date of the digital asset profile.

[0015] Based on the above, this case provides a digital asset storage and management device and method, which integrates blockchain network, digital authentication service and non-fungible token (NFT) minting through decentralized application, thereby simplifying the management complexity of existing digital asset storage while improving the identity verification security mechanism.

Implementation Method

[0017] The spirit of this case will be clearly explained below with diagrams and detailed description. Anyone with ordinary knowledge in the relevant technical field can make changes and modifications based on the technology taught in this case after understanding the embodiments of this case, without departing from the spirit and scope of this case.

[0018] The terminology used herein is for the purpose of describing specific embodiments only and is not intended to limit the scope of this application. Singular forms such as “a,” “this,” “this,” “this,” and “the” as used herein also include plural forms.

[0019] The terms "coupled" or "connected" as used herein can refer to two or more components or devices making direct physical contact with each other, or making indirect physical contact with each other, or to two or more components or devices operating or acting on each other.

[0020] The terms 'include', 'including', 'have', 'contain', etc. used in this document are all open-ended terms, meaning that they include but are not limited to.

[0021] The term "and / or" as used herein includes any or all of the things mentioned.

[0022] The terms used herein, unless otherwise specified, generally have their ordinary meaning in the context of the art, the subject matter, and the specific content. Certain terms used to describe the subject matter will be discussed below or elsewhere in this specification to provide additional guidance to those skilled in the art in describing the subject matter.

[0023] Since blockchain transactions require management through e-wallets, the management of e-wallets is not easy for ordinary consumers or businesses to use, thus affecting their willingness to store and authorize records of digital assets. Accordingly, this case provides a digital asset storage and management device and method that integrates blockchain networks, digital authentication services, and non-fungible token (NFT) minting through decentralized applications, simplifying the complexity of existing digital asset storage management.

[0024] Please refer to Figure 1, which is a schematic diagram of a digital asset storage and management device according to some embodiments of this case. The digital asset storage and management device 100 manages the storage and authorization records of users' digital assets through blockchain. In some embodiments, a user can connect to the digital asset storage and management device 100 through a user device 200 to mint non-fungible tokens of the user's digital assets.

[0025] In some embodiments, the digital asset notarization management device 100 includes a processing element 110 and a storage element 120 connected wirelessly or wiredly to the processing element 110. The storage element 120 is configured to store at least a plurality of computer-readable instructions. The processing element 110 is electrically coupled to the storage element 120 and configured to access the computer-readable instructions from the storage element 120 in response to an instruction to execute a decentralized application 121 to manage the notarization and authorization records of a user's digital assets through a blockchain, wherein the instruction may originate from an instruction generated by a user operating a human-machine interface. In some embodiments, the decentralized application 121 may display a digital asset notarization management webpage on a user device's human-machine interface, through which the user can upload digital asset files for non-fungible token minting. In further embodiments, the processing element 110 may be a central processing unit, a controller, or other processing circuitry. The storage element 120 may be a hard drive, flash memory, or other storage medium.

[0026] Figure 2 shows a schematic diagram of the functional modules of a digital asset evidence management device according to some embodiments of this invention. In some embodiments, the processing element 110 executes a decentralized application 121 to implement a transaction record management module 1211, a notary file management module 1212, a hash code generation module 1213, a Uniform Resource Identifier (URI) generation module 1214, an identity authentication module 1215, a virtual electronic wallet generation module 1216, a non-fungible token (NFG) management module 1217, and an NFG trading module 1218 of the digital asset evidence management device 100. In some embodiments, this decentralized application 121 may support the Bitcoin blockchain, the Ethereum blockchain, the Ethereum Virtual Machine (EVM) blockchain, sidechains (FTM, Optimism, Arbitrum, xDAI, or Celo), or other blockchain environments compatible with smart contracts. In some embodiments, this invention further deploys an Application Binary Interface (ABI) 1219 on the blockchain. The decentralized application 121 can call the smart contract related to minting non-fungible tokens through the ABI 1219 based on the transmitted digital asset file metadata, so as to mint non-fungible tokens based on the metadata.

[0027] In some embodiments, the transaction record management module 1211 is used to record the transaction records of the user's virtual electronic wallet. For example, the transaction record management module 1211 records the minting fee records generated when non-fungible tokens are minted, non-fungible token transfer transaction records, etc.

[0028] In some embodiments, the notary file management module 1212 is used to manage and store digital asset files uploaded by users for non-fungible token minting. In other embodiments, users may choose not to upload digital asset files, but only upload the hash code corresponding to the digital asset file. In this embodiment, the notary file management module 1212 is used to store the hash code. In other embodiments, the storage location of the digital asset file may also be recorded for users to query later.

[0029] In some embodiments, the hash code generation module 1213 is used to generate a hash code for a user-uploaded digital asset file. For example, the hash code generation module 1213 converts the user-uploaded digital asset file using a predetermined hash function to generate a hash code as the file code. The predetermined hash function is a hash function used with the blockchain authentication system protocol. The hash function calculates the hash code that can represent the file and uses it as metadata when minting non-fungible tokens. The above-described method of generating hash codes is only one embodiment and is not limited thereto.

[0030] In some embodiments, the Uniform Resource Identifier (URI) generation module 1214 is used to generate a URI corresponding to a digital asset file uploaded by a user and a webpage. For example, when a user uploads a digital asset file, the URI generation module 1214 generates a URI associated with the uploaded file based on the uploaded digital asset file, and generates a webpage corresponding to this URI after minting. In some embodiments, when a user uploads a digital asset file for non-fungible token (NFToken) minting, the URI generation module 1214 generates a resource identifier as metadata during NFToken minting. After NFToken minting is completed, the URI generation module 1214 generates a webpage corresponding to this URI, recording relevant information about the digital asset file, including information such as: user basic information, the file name of this NFToken minting, file size, file creation date, etc., for the user to subsequently query this webpage through the decentralized application 121.

[0031] In some embodiments, the identity authentication module 1215 is used to verify the user's identity. For example, the identity authentication module 1215 can use open authorization (OAuth) to verify the user's identity using a third-party verification platform, which verifies the user's email, fingerprint, retinal image, or credentials. If the user's identity verification is successful, the third-party verification platform generates a user identity token ID for the identity authentication module 1215.

[0032] In some embodiments, the virtual wallet generation module 1216 is used to automatically create a user-specific virtual wallet. For example, after the identity authentication module 1215 receives the user's identity credentials returned by the third-party verification platform, the virtual wallet generation module 1216 will automatically create the user-specific virtual wallet based on these credentials. Traditionally, users are not familiar with how to create a virtual wallet, and even if they can create one themselves, they still have to remember and record their private keys, which presents the problem of difficulty in preserving them. Furthermore, even if the private key is stored in all of the user's physical wallets, there is a risk that the physical wallets may be lost. If the virtual wallet is stored in an online exchange, because it is centrally stored, there is also the risk of potential ethical problems associated with online exchanges, and if the private key is stolen, the assets in the virtual wallet may be stolen. Therefore, to solve the above problems, this solution, in addition to automatically creating a user-specific virtual wallet, dynamically generates a verification rule. Based on this rule, it generates multiple separate keys stored in different locations. By combining some or all of these separate keys, a complete private key is formed, and the user-specific virtual wallet is automatically created based on this public-private key. Because multiple separate keys are stored in different locations, the risks associated with centralized storage are avoided.

[0033] Figure 4 illustrates a method for creating a virtual electronic wallet according to an embodiment of this invention. The virtual electronic wallet creation method 400 can be executed by the virtual electronic wallet generation module 1216 of the digital asset storage and management device 100 in Figure 2. It should be understood that, unless otherwise specified, the order of operations in the virtual electronic wallet creation method 400 mentioned in this embodiment can be adjusted according to actual needs, and may even be executed simultaneously or partially simultaneously. Furthermore, in different embodiments, these operations can be adaptively added, replaced, and / or omitted.

[0034] Please refer to Figure 4. In the virtual e-wallet creation method 400, firstly, in step 401, the decentralized application 121 obtains the verified user identifier (UID). For example, after a user successfully verifies their identity through an open authorization (OAuth) platform using a third-party verification platform, the third-party verification platform returns the user identifier (UID) to the identity authentication module 1215 of the decentralized application 121, which stores the user identifier.

[0035] Next, in step 402, a split-key verification rule is dynamically generated. After the decentralized application 121 successfully verifies its identity on the third-party verification platform, a split-key verification rule is dynamically generated, including the number of split keys to be generated and the number of split keys required to form a complete private key. In some embodiments, a split-key verification rule may dynamically generate three split keys, and require any two or more of these split keys to be verified to form a complete private key. However, it is worth noting that the above-described split-key verification rule is only one implementation method. In other implementation methods, other numbers of split keys may be dynamically generated, and other proportions of split keys may be used for verification to form a complete private key.

[0036] Next, in step 403, the required split keys are generated and saved according to the split key verification rules. In some embodiments, according to the above split key verification rules, the three dynamically generated split keys are: the user identification code returned by the third-party verification platform after the user's identity verification is passed as the first split key; the identity certificate generated by the third-party verification platform after the user's identity verification is passed as the second split key; and the password entered by the user or dynamically generated by the decentralized application 121 as the third split key. In some embodiments, this password may be stored in a browser or a third-party storage device.

[0037] Next, in step 404, a correct private key is generated according to the split-key verification rules. In some embodiments, any two of the three dynamically generated split keys are used for verification according to the split-key verification rules to establish a public / private key. Based on this, digital signing can be performed based on the public / private key to establish a virtual electronic wallet and return the virtual electronic wallet address. In some embodiments, any two of the three split keys are the first split key and any one of the second and third split keys. Since this case requires multiple split keys to be verified to form a complete private key, and these multiple split keys are stored in different locations, the risk of centralized storage can be avoided and security can be improved.

[0038] In some embodiments, the non-fungible token management module 1217 is used to record the non-fungible tokens minted by the user. For example, after a user uploads a digital asset profile and mints non-fungible tokens based on that profile, the non-fungible token management module 1217 records the newly minted non-fungible tokens. In another embodiment, if a user performs a non-fungible token transfer transaction, the non-fungible token management module 1217 records the addition or reduction of non-fungible tokens, thereby allowing the user to know their non-fungible token holdings based on this record.

[0039] In some embodiments, the non-fungible token (NFT) trading module 1218 is used to perform NFT transfer functions. For example, when a user wants to transfer NFT, they can use the NFT trading module 1218 to transfer the corresponding NFT to another person's virtual wallet account. In other embodiments, if the user has other virtual wallets, they can also use the NFT trading module 1218 to transfer the corresponding NFT to other virtual wallet accounts used by the user.

[0040] Please refer to Figure 3, which is a flowchart of a digital asset evidence management method according to some embodiments of this case. Please also refer to Figures 1 to 4. In the digital asset evidence management method 300, the user's identity is first verified in step 301. For example, the identity authentication module 1215 can use a third-party verification platform to verify the user's identity through open authorization (OAuth). Once the user's identity verification is successful, the third-party verification platform generates the user's identity credentials.

[0041] After confirming the user, a virtual electronic wallet is generated in step 302. For example, a user-exclusive virtual electronic wallet is automatically created based on the user's identity credentials. The method for creating the virtual electronic wallet is shown in Figure 4 above and will not be described again here.

[0042] After generating a user-specific virtual electronic wallet, in step 303, a digital asset file is uploaded, generating a hash code for the digital asset file. For example, the user can upload a digital asset file to the digital asset storage management device 100 for non-fungible token minting through a digital asset storage management webpage displayed on the user's device's human-computer interface via the decentralized application 121. In some embodiments, the digital asset file is, for example, a digital image file created by the user.

[0043] Next, a digital asset file notarization process is performed, that is, a non-fungible token (NFT) minting process is conducted based on this digital asset file. First, in step 304, metadata for the NFT is generated. In one embodiment, the hash code and resource identifier of the digital asset file are used as the metadata for minting the NFT. The metadata and the virtual wallet address are transmitted to the subsequent smart contract for NFT minting. The hash code can be the token name of the minted NFT. The Uniform Resource Identifier (URI) can be the token number of the minted NFT.

[0044] In step 305, the metadata of the generated non-fungible token is transmitted to the smart contract program interaction interface 1219 deployed on the blockchain. For example, the smart contract program interaction interface 1219 calls the smart contract related to minting the non-fungible token based on the transmitted metadata, so as to perform non-fungible token minting according to the metadata. In one embodiment, the metadata is sent to the address of the called smart contract, and the smart contract performs non-fungible token minting according to the input metadata. The non-fungible token minting process is a known technique and will not be described in detail here. In step 306, a non-fungible token for a digital asset file is generated. In one embodiment, the non-fungible token records the hash code of the digital asset file and a Uniform Resource Identifier. The hash code of the digital asset file is the token name of this non-fungible token. The non-fungible token is stored in a virtual electronic wallet address.

[0045] In step 307, query the minting result of this non-fungible token. For example, a user can query whether the non-fungible token has been minted through decentralized application 121. Once the non-fungible token has been minted, the user's non-fungible token holdings will be updated accordingly. The Uniform Resource Identifier can be the token number of the minted non-fungible token.

[0046] In step 308, a Uniform Resource Identifier webpage is generated based on the minted non-fungible token, recording relevant information of the digital asset file, including file information such as: user basic information, file name of this non-fungible token, file size, file creation date, etc., for users to query this webpage through decentralized application 121 later.

[0047] Since each non-fungible token in this case has a corresponding notarization webpage, this case allows users to verify whether a digital asset file has been notarized. Users can upload a digital asset file to be verified and generate a hash code based on this file. The hash code is used to query the non-fungible token of the digital asset file and redirects the user to the notarization webpage corresponding to that file. If the notarization webpage does not exist, it means that the digital asset file has not been notarized.

[0048] In another embodiment, if the user already has a dedicated virtual electronic wallet, the verification method for digital asset notarization is shown in Figure 5. First, in step 501, the user's identity is verified. For example, the identity authentication module 1215 can use a third-party verification platform to verify the user's identity through open authorization (OAuth). If the user's identity verification is successful, the third-party verification platform will send the user identification code back to the identity authentication module 1215.

[0049] After confirming the user, in step 502, the user's stored private key is retrieved according to the private key verification rules. In one embodiment, if the private key verification rules require any two of the three private keys to be verified and combined into a complete private key, in addition to using the user identification code returned by the third-party verification platform as the first private key, this case can retrieve the identity certificate generated by the third-party verification platform for user identity verification, or the password entered by the user and stored in the browser or third-party storage device as the second private key to be verified and combined into a complete private key. Accordingly, digital signing can be performed based on this private key to execute the minting of non-fungible tokens for digital asset files. The minting and storage process is shown in steps 303 to 308 of Figure 3, and will not be described again here.

[0050] In another embodiment, if a user already has a dedicated virtual electronic wallet, the split-key verification rules can be reset after digital asset notarization. That is, a new split-key verification rule is generated. For example, after digital asset notarization, the decentralized application 121 dynamically generates a new split-key verification rule, including the number of split keys to be generated and the number of split keys required to form a complete private key. Then, the required split keys are generated and saved according to the split-key verification rule. Therefore, when performing new digital asset notarization subsequently, the required public and private keys can be generated based on the reset split-key verification rule.

[0051] In summary, this case provides a digital asset storage and management device and method that integrates blockchain network, digital authentication service and non-fungible token (NFT) minting through decentralized application, thereby simplifying the management complexity of existing digital asset storage.

[0052] Although the present invention has been disclosed above by way of embodiments, it is not intended to limit the present invention. Anyone with ordinary knowledge in the art may make some modifications and refinements without departing from the spirit and scope of the present invention. Therefore, the scope of protection of the present invention shall be determined by the appended claims. [Simplified Explanation of the Diagram]

[0016] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments conforming to the present invention and, together with the specification, serve to explain the technical solutions of the embodiments of the present invention. Figure 1 is a schematic diagram of a digital asset evidence management device according to some embodiments of the present invention. Figure 2 is a schematic diagram of a functional module of a digital asset evidence management device according to some embodiments of the present invention. Figure 3 is a flowchart of a digital asset evidence management method according to some embodiments of the present invention. Figure 4 shows a virtual electronic wallet creation method according to an embodiment of the present invention. Figure 5 shows a verification method according to an embodiment of the present invention.

Claims

1. A digital asset storage and management device, comprising: One processing element; The processor also includes a storage element coupled to the processing element, wherein the storage element stores a plurality of computer-readable instructions, and the processing element accesses the plurality of computer-readable instructions from the storage element in response to an instruction to execute: automatically generating a virtual electronic wallet associated with a user's identity credential; generating a hash associated with a user's digital asset profile; generating a Uniform Resource Identifier (URI) associated with the digital asset profile; invoking a smart contract on a blockchain to mint a non-fungible token (NFT) based on the hash and the URI; generating a notarized webpage associated with the NFT based on the URI to record information about the NFT; and using the virtual electronic wallet to record transactions associated with the NFT, wherein the virtual electronic wallet automatically generated based on the user's identity credential further includes: a user identification code generated after the user's identity is verified by a third-party verification platform as a first separate key; The identity credential generated after the user's identity is verified by the third-party verification platform is used as a second separate key; a set password is used as a third separate key; and according to a separate key verification rule, a private key is formed using the first separate key, the second separate key, and the third separate key to perform a digital signature and establish the virtual electronic wallet.

2. The digital asset storage management device as described in claim 1, wherein the split key verification rule is to use either the second split key or the third split key, together with the first split key, to form the private key to establish the virtual electronic wallet, wherein the first split key and the third split key are stored in different storage devices, and the split key verification rule is reset after the minting of non-fungible tokens is completed.

3. The digital asset storage management device as described in claim 1, wherein the processing element further associates the non-fungible token with the virtual e-wallet.

4. The digital asset storage management device as described in claim 1, wherein the hash code is the token name of the non-fungible token.

5. The digital asset storage management device as described in claim 1, wherein the hash code and the Uniform Resource Identifier are metadata for the smart contract to mint the non-fungible token.

6. The digital asset notarization management device as described in claim 1, wherein the notarization webpage records digital asset file information of the non-fungible token, including file name, digital asset file size and digital asset file creation date.

7. A digital asset notarization management method, executed by a digital asset notarization management device, the method comprising the following steps: Performed by a processing element: verifying a user's identity information to generate an identity certificate; automatically generating a virtual electronic wallet associated with the identity certificate; generating a hash code and a Uniform Resource Identifier (URI) associated with the user's digital asset file; calling a smart contract on a blockchain to mint a non-fungible token (NFT) based on the hash code and the URI; and updating the virtual electronic wallet to record the NFT, wherein the virtual electronic wallet automatically generated based on the identity certificate further comprises: A first separate key is generated based on a user identification code obtained after the user's identity has been verified by a third-party verification platform. A second separate key is generated based on the identity certificate verified by the third-party verification platform; a third separate key is generated based on a set password; and a private key is formed using the first separate key, the second separate key, and the third separate key according to a separate key verification rule to perform a digital signature and establish the virtual electronic wallet.

8. The digital asset storage management method as described in claim 7, wherein the split key verification rule is to use either the second split key or the third split key, together with the first split key, to form the private key to establish the virtual electronic wallet, wherein the first split key and the third split key are stored in different storage devices, and the split key verification rule is reset after the minting of non-fungible tokens is completed.

9. The digital asset evidence management method as described in claim 7 further includes: The processing element generates a certificate webpage associated with the non-fungible token based on the Uniform Resource Identifier.

10. The digital asset notarization management method as described in claim 9, wherein the notarization webpage records digital asset file information of the non-fungible token, including file name, digital asset file size and digital asset file creation date.

Images