NFT-based digital asset management method and apparatus

By minting NFTs at the target address and combining third-party verification procedures, the problem of NFT technology being unable to confirm rights and easy data replication is solved, the independent management of digital assets and intellectual property protection is realized, and the development of the digital cultural market is enhanced.

WO2024239976A1PCT designated stage expired Publication Date: 2024-11-28FIFTH FORCE TECH LTD +1

Patent Information

Application Number
PCT/CN2024/092146
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-19
Filing Date
2024-05-10
Publication Date
2024-11-28

AI Technical Summary

Technical Problem

The existing NFT technology cannot effectively confirm the owners of digital works, and the data files are easily copied, unable to meet the needs of intellectual property protection, and are out of touch with the real world, resulting in the restriction of the development of the digital cultural market.

Method used

By minting NFTs on the target address, combining third-party verification procedures and distributed networks, the independent management and convenient transactions of digital assets are achieved, ensuring the uniqueness and immutability of transactions, and connecting with the real-world ownership certification agencies, Support anonymous and real-name transactions.

Benefits of technology

It realizes the real ownership recognition and intellectual property protection of digital assets, reduces credit costs, improves transaction flexibility and security, and enhances the correlation between digital assets and the real world.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024092146_28112024_PF_FP_ABST
    Figure CN2024092146_28112024_PF_FP_ABST
Patent Text Reader

Abstract

Disclosed in the present invention are an NFT-based digital asset management method and apparatus. The method comprises: receiving a source file casting application for digital assets initiated by a seller; casting a source file into an NFT, forming a record file after casting is completed, and storing same on a destination address, the record file comprising basic information, file information and transaction information; receiving a transaction application for the NFT initiated by a buyer; calling a third-party verification program to verify the source file and the transaction information; when the verification succeeds, updating the transaction information; according to the file information and the updated transaction information, generating a new record file; and maintaining the source file untransferred on the destination address, sending the encrypted new record file to the buyer, and transferring transaction money to the seller. The present invention achieves autonomous management and convenient transaction of digital assets without binding the NFT to any platform, thus achieving arbitrary right authentication and transaction, forming an underlying base protocol of Web3, and greatly reducing credit costs.
Need to check novelty before this filing date? Find Prior Art

Description

Digital asset management method and device based on NFT Technical Field

[0001] The present invention relates to the field of blockchain technology, and in particular to a digital asset management method and device based on NFT. Background Art

[0002] This section is intended to provide a background or context to the embodiments of the invention that are recited in the claims. No statement herein is admitted to be prior art by virtue of its inclusion in this section.

[0003] NFT (Non-Fungible Token), each token can represent a unique digital data. Due to its non-fungible nature, it can be used for digital assets such as paintings, artworks, sounds, videos, game items or other forms of creative works.

[0004] NFTs, considered a gateway to the metaverse, have become highly sought-after in recent years due to their uniqueness. Because of their uniqueness, all artworks, whether in the form of books, text, music, or images, as well as digital collectibles and online games, can be authenticated through NFT's unique and rare value. Currently, over 90% of Ethereum NFTs are traded on Opensea.

[0005] Ethereum's exorbitant gas fees are prohibitively expensive for works of low value or those with unverified market prices. However, if a work isn't minted as an NFT on Ethereum and submitted to an exchange, there's no guarantee it won't be illegally plagiarized or maliciously copied by hackers. The high barrier to entry for Ethereum NFTs undoubtedly hinders active participation by creators and discourages the purchase of most less valuable digital works, undoubtedly hindering the thriving digital cultural market. There are currently some NFTs minted on Layer 2 or other chains (such as GoChain) that are compatible with Ethereum, but the robustness of these systems remains uncertain.

[0006] Summary of the Invention

[0007] The present invention provides an NFT-based digital asset management method to improve existing non-fungible tokens, achieve autonomous management of digital assets, and facilitate transactions. The method includes:

[0008] Receive a request from a seller to mint a source file of a digital asset, where the current owner of the source file is the seller;

[0009] The source file is minted into an NFT. After the minting is completed, a record file is formed and stored at the target address. The record file includes basic information, file information, and transaction information. The basic information is used to describe the basic information of the record file, the file information is used to describe the source file, and the transaction information includes multiple transaction records, each of which is the historical transfer information of the source file;

[0010] Receiving a transaction request for the NFT initiated by the buyer, wherein the transaction request is initiated by the buyer after seeing the description of the source file on the personal homepage of the seller at the target address;

[0011] Call a third-party verification program to verify the source file and transaction information; if the verification is correct, update the transaction information; generate a new record file based on the file information and the updated transaction information;

[0012] Keep the source file at the target address and send the encrypted new record file to the buyer, transferring the transaction amount to the seller.

[0013] The present invention also provides an NFT-based digital asset management device to improve existing non-homogeneous tokens, achieve autonomous management of digital assets, and facilitate transactions. The device includes:

[0014] A casting application receiving module, configured to receive a casting application for a source file of a digital asset initiated by a seller, where the current owner of the source file is the seller;

[0015] The casting module is used to cast the source file into an NFT. After the casting is completed, a record file is formed and stored at the target address. The record file includes basic information, file information and transaction information. The basic information is used to describe the basic information of the record file, the file information is used to describe the source file, and the transaction information includes multiple transaction records, each of which is the historical transfer information of the source file;

[0016] A transaction application receiving module, configured to receive a transaction application initiated by a buyer for the NFT, wherein the transaction application is initiated by the buyer after seeing the description information of the source file on the personal homepage of the seller at the target address;

[0017] The verification module is used to call a third-party verification program to verify the source file and transaction information; if the verification is correct, the transaction information is updated; and a new record file is generated based on the file information and the updated transaction information;

[0018] The transaction module is used to keep the source file at the target address without transferring it, send the encrypted new record file to the buyer, and transfer the transaction amount to the seller.

[0019] An embodiment of the present invention also provides a computer device, including a memory, a processor, and a computer program stored in the memory and runnable on the processor, wherein the processor implements the above-mentioned NFT-based digital asset management method when executing the computer program.

[0020] An embodiment of the present invention also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it implements the above-mentioned NFT-based digital asset management method.

[0021] An embodiment of the present invention also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, it implements the above-mentioned NFT-based digital asset management method.

[0022] In an embodiment of the present invention, an application for minting a source file of a digital asset initiated by a seller is received, wherein the current owner of the source file is the seller;

[0023] The source file is minted into an NFT. Upon completion, a record file is created and stored at the target address. The record file includes basic information, file information, and transaction information. The basic information describes the record file, the file information describes the source file, and the transaction information includes multiple transaction records, each of which contains historical transfer information for the source file. A transaction request for the NFT is received from the buyer, initiated after the buyer sees the source file description on the seller's personal homepage at the target address. A third-party verification program is invoked to verify the source file and transaction information. Upon verification, the transaction information is updated. A new record file is generated based on the file information and updated transaction information. The source file remains unchanged at the target address, and the encrypted new record file is sent to the buyer, transferring the transaction proceeds to the seller. Compared to existing solutions that use NFTs to manage digital assets, using NFTs and record files at the target address enables autonomous management of digital assets and facilitates transactions. NFTs do not need to be tied to any platform, allowing for arbitrary ownership confirmation and transactions. This truly becomes the underlying foundational protocol for Web3, significantly reducing the cost of credit in society. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative work. In the drawings:

[0025] FIG1 is a flowchart of a digital asset management method based on NFT in an embodiment of the present invention;

[0026] FIG2 is a schematic diagram of a recording file according to an embodiment of the present invention;

[0027] FIG3 is a schematic diagram of file information according to an embodiment of the present invention;

[0028] FIG4 is an example of a source file according to an embodiment of the present invention;

[0029] FIG5 is a schematic diagram of transaction information according to an embodiment of the present invention;

[0030] FIG6 is a flow chart of a transaction according to an embodiment of the present invention;

[0031] FIG7 is a schematic diagram of a digital asset management device based on NFT in an embodiment of the present invention;

[0032] FIG8 is a schematic diagram of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0033] To make the purpose, technical solutions and advantages of the embodiments of the present invention more clear, the embodiments of the present invention are further described in detail below with reference to the accompanying drawings. Here, the exemplary embodiments of the present invention and their descriptions are used to explain the present invention, but are not intended to limit the present invention.

[0034] The inventors found that NFT also has the following problems:

[0035] 1. NFT cannot confirm the true ownership of digital works

[0036] The current method of confirming NFT ownership is anonymous; whoever holds the private key owns it. This anonymous method of ownership confirmation only meets a narrow range of use cases and is unsuitable for scenarios requiring real-name verification. However, real-name verification is a vastly different use case. Using the ERC721 and ERC1155 protocols, simply submitting a URL corresponding to a digital file (such as an NFT avatar file) to Ethereum creates an anonymous account. Query tools only reveal transaction histories between anonymous accounts, with no way of verifying the original creator or the current owner. There's no way to prove the submitter is the true owner. Intellectual property protection requires, first and foremost, verifiable ownership and, secondly, traceability of the dissemination process. Clearly, NFTs cannot satisfy the demands of real artists seeking to protect the intellectual property rights of their works through NFTs.

[0037] 2. NFT data files can be easily copied and cannot meet the basic needs of intellectual property protection

[0038] The content of smart contract-based NFTs is public, allowing anyone to easily copy the file pointed to by the NFT URL. Even content stored on IPFS can be copied. IPFS simply tells users that a node stores data at a specific address, allowing other nodes to copy the data if they are interested.

[0039] 3. ERC721 and ERC1155 protocols cannot meet the operational needs of intellectual property protection in the real world

[0040] In the real world, changes in file format, size, or even minor content changes do not affect the original intellectual property rights. According to the ERC721 and ERC1155 protocols for NFTs, once an NFT is minted, no modifications are permitted. Even a single-byte change in the file content, storage address, or account information will result in a different NFT product. This is far from the practical requirements for intellectual property identification and protection in the real world.

[0041] Furthermore, using Ethereum anonymous accounts in accordance with the ERC721 and ERC1155 protocols, and because many platforms are compatible with Ethereum ERC20, not only can NFT products be minted and issued on multiple platforms, but even multiple mints can be minted on the same platform by simply changing a single byte. Users cannot trace back from the digital work file to find out how many NFTs with the same source content or similar NFTs exist. For example, if you see a painting and want to check whether there are already NFTs or how many NFTs with similar content exist, this is impossible. Furthermore, while EtherScan can display the contract address, token ID, owner, and previous creation and transfer records, it cannot reveal the data file itself.

[0042] 4. NFTs can be lost

[0043] Due to the limited storage capacity of blockchains, NFTs typically don't store the associated source files on the blockchain, as such files are often very large. Instead, the artwork is typically referenced via a URL. The NFT's content and source file index are separate from the NFT smart contract. These are typically stored on a storage device outside of the blockchain smart contract, whether a centralized server, the cloud, or a distributed file system (IPFS).

[0044] If the centralized server or cloud system that stores the content represented by the NFT and the source file index fails or is damaged, it means that the content is lost. Even if the content represented by the NFT and the source file index are uploaded to IPFS, there is no complete guarantee that the storage medium will not be damaged.

[0045] In addition, because most NFTs can only be linked to a URL, this means that the storage content corresponding to the URL can be changed. Once the storage content is changed, the NFT is lost. If the address connection fails, the NFT that you may have spent a lot of money to purchase will no longer exist.

[0046] 5. NFTs are disconnected from the real world

[0047] When digital assets lack a connection to the real world, their value and scope of use are significantly limited. In the future, NFTs must be able to represent real-world assets. They must be linked to the real names of their owners and verified by real-world ownership certification agencies. This integration, through online and offline collaboration, will allow the real and virtual worlds to truly merge.

[0048] To solve the above problems, an embodiment of the present invention proposes a digital asset management solution based on NFT. The NFT is an optimization based on the existing NFT and is an NFT minted at the target address.

[0049] FIG1 is a flow chart of a digital asset management method based on NFT according to an embodiment of the present invention, which includes:

[0050] Step 101: receiving a source file minting application for a digital asset initiated by a seller, wherein the current owner of the source file is the seller;

[0051] Step 102: The source file is minted into an NFT. After the minting is completed, a record file is formed and stored at the target address. The record file includes basic information, file information, and transaction information. The basic information is used to describe the basic information of the record file, the file information is used to describe the source file, and the transaction information includes multiple transaction records, each of which is the historical transfer information of the source file.

[0052] Step 103: Receive a transaction request for the NFT initiated by the buyer, wherein the transaction request is initiated by the buyer after seeing the description information of the source file on the personal homepage of the seller at the target address;

[0053] Step 104: Invoke a third-party verification program to verify the source file and transaction information; if the verification is correct, update the transaction information; and generate a new record file based on the file information and the updated transaction information.

[0054] Step 105: Keep the source file at the target address and do not transfer it. Send the encrypted new record file to the buyer and transfer the transaction amount to the seller.

[0055] In this embodiment of the present invention, the combination of NFTs and target addresses is primarily driven by Opensea's absolute monopoly in the minting, display, and trading of Ethereum NFTs, with a market share exceeding 90%. Without such a centralized exchange, the technical barriers to ownership confirmation and trading of digital NFTs for ordinary users are high. However, the initial market for NFTs was the digital art market, where the vast majority of creators and collectors are outside the blockchain community. This undoubtedly creates a significant de facto reliance on centralization, which is inconsistent with the core principles of blockchain: decentralization, independence, freedom, and machine trust.

[0056] In an embodiment of the present invention, the target address can be a home cloud, a distributed network (IPFS) or a server, as long as the method of the present invention can be implemented, instead of using Ethereum, thereby overcoming the current problems with NFT on Ethereum.

[0057] The target address will provide convenient tools for users to create their own homepages. Based on the homepage, users can manage their identities and decide whether to be anonymous or real-name, and the degree of privacy they want to provide.

[0058] Based on personal homepages, users can not only easily publish, mint, display, and trade NFTs, but also build social networks, attracting fans, followers, and interested parties to their homepages for interaction and transactions. A good IP has a personality and a story. Imagine a creator having more and more free ways to express and communicate with supporters, rather than being limited to simply sharing their creative ideas and stories in the Description field on Opensea.

[0059] The solution of this application is introduced in detail below.

[0060] In step 101, a source file minting application for a digital asset is received from a seller, wherein the current owner of the source file is the seller;

[0061] Among them, the seller can choose to mint the source file of his own digital asset, and then publish the description information of the source file to his personal homepage. The description information includes the source file and the source file index, etc. Publishing means generating a record of the digital asset, that is, the description information.

[0062] In step 102, the source file is minted into an NFT. After the minting is completed, a record file is formed and stored at the target address. The record file includes basic information, file information, and transaction information. The basic information is used to describe the basic information of the record file, the file information is used to describe the source file, and the transaction information includes multiple transaction records, each of which is the historical transfer information of the source file.

[0063] The source file of the digital asset is minted as an NFT, which is unique and can be traded.

[0064] See FIG2 , which is an example of a record file in an embodiment of the present invention.

[0065] In one embodiment, the basic information includes the length of the record file, the record file description, the file number, the checksum, the account information of the current owner, the name of the current owner, and whether it is anonymous;

[0066] The file number is used to describe the number of the current source file to which the record file is directed.

[0067] In one embodiment, the file information further includes a digital fingerprint, which is used for any of the scenarios of similarity checking, copyright determination, review, identification, and digital copyright management of the source file.

[0068] A digital fingerprint is a string of characters generated based on multimedia or image content that uniquely identifies the content. This ensures high stability in the final product, effectively protecting it from the effects of operations such as format conversion, editing, cropping, splicing, compression, and rotation on video, photo, and audio files. Compared to hashing, fingerprinting technology can still determine similarity even after various modifications to the original file, such as scaling, resizing, and re-encoding.

[0069] In one embodiment, the file information includes a file record of a source file used for casting and a plurality of file records of source files modified from the source file used for casting;

[0070] Each transaction record contains all historical transfer information for each source document.

[0071] That is, in the embodiment of the present invention, the source file may have multiple copies, for example 1,000 copies, so that all 1,000 buyers own a version after purchasing.

[0072] In one embodiment, referring to FIG3 , each file record includes a source file index, source file length, source file hash, and whether the source file is valid for each source file;

[0073] FIG4 is an example of a source file in an embodiment of the present invention. The source file may be in various forms, including coding files, tag files (such as tags indicating time and location), code files, video files, image files, and the like.

[0074] The source file hash is calculated by hashing the source file. Whoever purchases the source file owns the copyright.

[0075] The source file index is information describing the source file's attributes, including creator, creation time, category, keywords, and other information. Cover information for images and audio / video content is stored in the source file index, making it easier for buyers and sellers to understand the work.

[0076] The source file is the most significant feature of this solution, guaranteeing true ownership. This means that only the true owner holds copyright, meaning that no one else has access to it. For example, the original version of a song belongs to the creator, and ordinary people can only listen to it, not use it commercially. Furthermore, with this guarantee, transaction information is simply a record of the transaction, and the file storage location (URL) can be changed with each transaction. This eliminates the need for URL manipulation, as with current NFTs. This returns to the essence of the transaction: the digital asset is the source file, not the URL.

[0077] 5 , the transaction record includes a transaction record header, a transaction record footer, the seller's account information, the buyer's account information, whether the buyer is anonymous, the transaction price, the source file hash, the URL, and the transaction timestamp;

[0078] The transaction record header and transaction record tail are hash values, and the transaction record header of the next transaction record is the transaction record tail of the current transaction record, and the transaction record tail is calculated based on the current transaction record;

[0079] The URL is the temporary address where the seller stores the digital asset;

[0080] The source file hash is the hash of the source file for this transaction.

[0081] In one embodiment, the transaction information is recorded using a chain accounting method to ensure that the transaction cannot be tampered with and each transaction can be easily traced back.

[0082] Because each NFT transaction record uses a chain-based accounting system, each transaction has a timestamp and a hash value. Each transaction record also includes the hash value of the previous transaction record. This makes the historical transaction record of an NFT immutable. Chain-based accounting makes it difficult to modify any transaction because all subsequent transactions must be modified accordingly.

[0083] The following is an example of a specific record file.

[0084] / / This part is basic information

[0085] <filelength>65536 / / Record file length

[0086] <crc32>0x1234567 / / Verification code

[0087] <did>anonymous / 88888888 / / Buyer's account information

[0088] <name>zhangsukai / / buyer's name

[0089] <publie>yes / no / / Are you anonymous?

[0090] <fingerprint> / / Digital fingerprint

[0091] <brief>This is drawn by zhangdaqian...... / / Record file description

[0092] <index>888 / / File number

[0093] / / This part is the file information, including the file record of the source file used for casting, the original file, and the file record of multiple source files modified from the source file used for casting, the subfile file.

[0094] <Original file> http: / / www.yuxing.com / sourcefile / 1234567890.com / / Source file index

[0095] <length>65536 / / Source file length

[0096] <sha256>0x....... / / Source file hash

[0097] <availability>yes / no / / Is it valid?

[0098] <subfile file> http: / / www.yuxing.com / sourcefile / 1234567890.com

[0099] <length> 65536

[0100] <sha256> 0x.......

[0101] <availability>yes / no

[0102] <subfile file>http: / / www.yuxing.com / sourcefile / 1234567890.com

[0103] <length> 65536

[0104] <sha256> 0x.......

[0105] <availability>yes / no

[0106] ....

[0107] / / This section contains transaction information, including multiple transaction records.

[0108] <Trade Infomation>

[0109] ″Hash0″,″″,″Buyer″,″yes / no″,″″,″FileHash'″,″URL″,″Timestamp″,″Hash1″ / / Transaction record formed by the file record of the source file used for casting

[0110] <Trade Infomation>

[0111] ″Hash1″, ″Seller″, ″Buyer″, ″yes / no″, ″Price″, ″FileHash'″, ″URL″, ″Timestamp″, ″Hash2″ / / Starting from this transaction record, the file record of the source file modified from the source file used for casting is shown. Among them, Hash1 is the transaction record header, Seller is the seller's account information, Buyer is the buyer's account information, yes / no indicates whether the buyer is anonymous, Price is the transaction price, FileHash is the source file hash, URL is the URL, Timestamp is the transaction timestamp, and Hash2 is the transaction record footer

[0112] <Trade Infomation>

[0113] "Hash2", "Seller", "Buyer", "yes / no", "Price", "FileHash'", "URL", "Timestamp", "Hash3"

[0114] <Trade Infomation>

[0115] "Hash3", "Seller", "Buyer", "yes / no", "Price", "FileHash'", "URL", "Timestamp", "Hash4"

[0116] In step 103, a transaction application for the NFT initiated by the buyer is received, wherein the transaction application is initiated by the buyer after seeing the description information of the source file on the personal homepage of the seller at the target address. In addition, the seller and the buyer may confirm the initiation of the transaction application after communicating on the seller's personal homepage;

[0117] In step 104, a third-party verification program is called to verify the source file and transaction information; if the verification is correct, the transaction information is updated; and a new record file is generated based on the file information and the updated transaction information.

[0118] When a buyer initiates a transaction, new transaction information is generated based on the current transaction status. At this time, the transaction information is not updated and no payment is made. Instead, the transaction information is first sent to a third-party verification program for verification;

[0119] FIG6 is a flowchart of a transaction according to an embodiment of the present invention, in which a third-party verification program is called to verify the source file and transaction information; when the verification is correct, the transaction information is updated, including:

[0120] Step 601: Call a third-party verification program to read a source file through a URL and calculate a hash of the source file.

[0121] Step 602: Perform the first verification of the calculated source file hash with the source file hash of the previous transaction record:

[0122] Step 603: If the first verification is correct, calculate the hash of the previous transaction record;

[0123] Step 604: perform a second verification on the calculated hash of the previous transaction record and the transaction record tail of the previous transaction record;

[0124] Step 605: If the second verification is correct, a new transaction record is generated and added to the transaction information;

[0125] Step 606, close the URL.

[0126] After the transaction is completed, the buyer owns the copyright to the source files.

[0127] During the transaction process, NFT effectively ensures that the subject of the transaction is the original file (the digital work itself), rather than the URL, which is a good innovative improvement to the existing NFT model. When the transaction is completed, only the current owner (buyer) owns the copyright and the right to initiate the next transaction.

[0128] In order to solve the problem that NFT is lost forever after the user loses the private key, the relief measures provided by the off-chain wallet of the target address are used for users to recover, but this recovery tool includes but is not limited to the off-chain wallet.

[0129] In one embodiment, the account information includes an account name;

[0130] The seller has at least one account information;

[0131] Upon receiving a request from the seller to update the account information in the file information, updating the seller's account information in the file information;

[0132] Generate a new transaction record and add it to the transaction information;

[0133] Generate a new record file based on the file information and the updated transaction information.

[0134] In one embodiment, the method further comprises:

[0135] When the seller initiates an update of a preset field in the transaction information, a new transaction record is generated and added to the transaction information. The preset field is the buyer's account information, source file hash or URL;

[0136] Generate a new record file based on the file information and the updated transaction information.

[0137] That is, changes in multiple accounts of the same owner can be considered as one transaction, except that the price is 0. In addition, the fields in the transaction information can be changed, which can also be considered as one transaction. For example, if some modifications are made to the source file, the source file hash will change.

[0138] In specific implementation, the decision to use real names or anonymous accounts will be made by the seller (current owner). This choice, based on the owner's needs, seems to better align with the spirit of freedom and the platform's product requirements. For digital assets with a strong correlation to real assets, both buyers and sellers will tend to use real names to facilitate ownership verification. For digital assets with a weak correlation to real assets, both buyers and sellers may prefer anonymous accounts. Furthermore, to provide owners with greater flexibility in switching between anonymous and real names, the switch between anonymous and real names can be completed in a single transaction, without exposing the relationship between the real-name and anonymous accounts. For applications with high copyright verification requirements, using the owner's real name for the release and trading of data products is recommended, but this is determined by market preferences. For example, a buyer preparing to spend a large sum on a painting will likely prefer an NFT initially issued with a real name, and where the seller is a real-name user. This allows for easier tracing and enforcement of copyright infringement in the real world.

[0139] The transfer between real-name and anonymous accounts is a transfer transaction; and the modification of the source file is also considered a transfer transaction. At this time, the URL must be re-selected to store the new file, and the old file is also retained. At the same time, the hash value of the file is also changed.

[0140] In one embodiment, a new record file is generated based on the file information and the updated transaction information, including:

[0141] Generate basic information based on the buyer's information, wherein the buyer's information includes the buyer's account information and the buyer's name;

[0142] Generate a new record file based on the basic information, file information and updated transaction information.

[0143] The current key will be updated after use for the next time, and the encrypted file information will be passed to the buyer to ensure that only the buyer can open the file information and read the source file through the file index. No one else has the right to read it.

[0144] In step 105, the source file is kept at the target address without being transferred, the encrypted new record file is sent to the buyer, and the transaction amount is transferred to the seller.

[0145] In one embodiment, the method further comprises:

[0146] Receive the seller's identity management commands on the target address's personal homepage and manage the seller's account information, such as creating a new account and selecting a real-name or anonymous account.

[0147] In one embodiment, the method further comprises:

[0148] On the personal homepage of the target address, the seller and related personnel communicate about digital assets.

[0149] In one embodiment, the method further comprises:

[0150] Call the display device to interact with the seller and the digital asset at the target address.

[0151] The above embodiments embody the virtual display function, and display devices include but are not limited to hardware glasses and holographic 3D display devices such as VR and Showing Box. Target Address has launched a series of holographic 3D display devices (Showing Box), which allow users to create, like, and collect NFTs right in front of their eyes. Some personalized NFTs can even interact with voice and body. If combined with offline NFT images, Showing Box can also achieve offline and online binding in seconds, ensuring limited editions both online and offline. Showing Box hardware also supports wallets and multi-signatures. Because it has geographic location information and is a dedicated device, the signature of the Showing Box has strong unique identification capabilities. Showing Box also provides distributed storage and cluster computing functions, becoming an important part of the system ecosystem.

[0152] In one embodiment, the method further comprises:

[0153] After receiving transaction promotion instructions, recommend, bid or auction digital assets.

[0154] The above embodiment primarily demonstrates the matching effect of centralized transactions. Digital assets are published and displayed through the personal homepage app. Sellers can choose to register their digital asset page on the centralized exchange provided by the target address. Because the storage structure and format of digital assets are the same, centralized exchanges significantly increase query speed. Centralized exchanges act as intermediaries and matchmakers, but transactions are still completed peer-to-peer between users.

[0155] In one embodiment, the method further comprises:

[0156] After receiving the query command at the target address, the NFT is queried based on the keywords in the query command.

[0157] In the above embodiment, the target address system will provide a browser website similar to EtherScan, allowing anyone to easily query digital works, owners, personal homepages, and transfer records. It can also easily search for infringing works, facilitating rights holders' rights protection and legal assistance. If it is third-party software, it should be wrapped in a layer and browsed in its own app.

[0158] In one embodiment, the method further comprises:

[0159] Generate multiple backups of the source file, and generate a backup file under the storage directory of the source file. The backup file describes all storage addresses of the backups, and stores the multiple backups at the storage addresses respectively. The storage addresses are the target addresses or the addresses of the distributed storage system.

[0160] In the above embodiment, the file name of the backup text file is <hash value of the source file.BAK>, so that it can be linked to the source file, and the contents of the backup and source files are completely consistent.

[0161] During specific implementation, at least 5 backups should be made.

[0162] In one embodiment, the method further comprises:

[0163] After receiving the backup destruction instruction, destroy the backup specified in the instruction and update the backup file;

[0164] After receiving the backup update instruction, a backup is regenerated, the backup address is added to the backup file, and the backup is stored at the backup address.

[0165] In the above embodiment, the source file can be destroyed based on confidentiality requirements. If it is not destroyed, it can be traded directly next time. If it is destroyed, a qualified backup file will be randomly selected for the formal transaction.

[0166] The present invention also provides an NFT-based digital asset management device, as described in the following embodiments. Since the principle of solving the problem of this device is similar to that of the NFT-based digital asset management method, the implementation of this device can refer to the implementation of the NFT-based digital asset management method, and the repeated parts will not be repeated.

[0167] FIG7 is a schematic diagram of an NFT-based digital asset management device according to an embodiment of the present invention, including:

[0168] The minting application receiving module 701 is configured to receive a minting application for a source file of a digital asset initiated by a seller, wherein the current owner of the source file is the seller;

[0169] The minting module 702 is used to mint the source file into an NFT. After the minting is completed, a record file is generated and stored at the target address. The record file includes basic information, file information, and transaction information. The basic information is used to describe the basic information of the record file, the file information is used to describe the source file, and the transaction information includes multiple transaction records, each of which is the historical transfer information of the source file.

[0170] A transaction application receiving module 703 is configured to receive a transaction application initiated by a buyer for the NFT, wherein the transaction application is initiated by the buyer after seeing the description of the source file on the personal homepage of the seller at the target address;

[0171] Verification module 704 is used to call a third-party verification program to verify the source file and transaction information; if the verification is correct, update the transaction information; and generate a new record file based on the file information and the updated transaction information;

[0172] The transaction module 705 is used to keep the source file at the target address without transferring it, send the encrypted new record file to the buyer, and transfer the transaction amount to the seller.

[0173] In one embodiment, the basic information includes the length of the record file, the record file description, the file number, the checksum, the account information of the current owner, the name of the current owner, and whether it is anonymous;

[0174] The file number is used to describe the number of the current source file to which the record file is directed.

[0175] In one embodiment, the file information further includes a digital fingerprint, which is used for any of the scenarios of similarity checking, copyright determination, review, identification, and digital copyright management of the source file.

[0176] In one embodiment, the file information includes a file record of a source file used for casting and a plurality of file records of source files modified from the source file used for casting;

[0177] Each transaction record contains all historical transfer information for each source document.

[0178] In one embodiment, each file record includes the source file index, source file length, source file hash, and validity of each source file.

[0179] The source file hash is obtained by hashing the source file;

[0180] Whether it is valid indicates whether the corresponding source file can be traded. Among all file records, only one file record corresponding to the source file can be traded.

[0181] In one embodiment, the transaction record includes a transaction record header, a transaction record footer, the seller's account information, the buyer's account information, whether the buyer is anonymous, the transaction price, the source file hash, the URL, and the transaction timestamp;

[0182] The transaction record header and transaction record tail are hash values, and the transaction record header of the next transaction record is the transaction record tail of the current transaction record, and the transaction record tail is calculated based on the current transaction record;

[0183] The URL is the temporary address where the seller stores the digital asset;

[0184] The source file hash is the hash of the source file for this transaction.

[0185] In one embodiment, the verification module is specifically configured to:

[0186] Call a third-party verification program to read the source file through the URL and calculate the hash of the source file;

[0187] Perform the first verification on the calculated source file hash and the source file hash of the previous transaction record;

[0188] If the first verification is correct, calculate the hash of the previous transaction record;

[0189] Perform a second verification on the calculated hash of the previous transaction record and the transaction record tail of the previous transaction record;

[0190] If the second verification is correct, a new transaction record is generated and added to the transaction information;

[0191] Close the URL.

[0192] In one embodiment, the account information includes an account name;

[0193] The seller has at least one account information;

[0194] Upon receiving a request from the seller to update the account information in the file information, updating the seller's account information in the file information;

[0195] Generate a new transaction record and add it to the transaction information;

[0196] Generate a new record file based on the file information and the updated transaction information.

[0197] In one embodiment, the transaction module is further configured to:

[0198] When the seller initiates an update of a preset field in the transaction information, a new transaction record is generated and added to the transaction information. The preset field is the buyer's account information, source file hash or URL;

[0199] Generate a new record file based on the file information and the updated transaction information.

[0200] In one embodiment, the transaction information is recorded using a chain accounting method.

[0201] In one embodiment, basic information is generated based on the buyer's information, where the buyer's information includes the buyer's account information and the buyer's name;

[0202] Generate a new record file based on the basic information, file information and updated transaction information.

[0203] In one embodiment, the transaction module is further configured to:

[0204] Calling a third-party program to obtain a current key, where the current key is a PGP public key;

[0205] The new record file is encrypted with the current key and sent to the buyer. The current key becomes invalid after use.

[0206] In one embodiment, the apparatus further includes a management module 706 configured to:

[0207] Receive the seller's identity management command on the target address's personal homepage and manage the seller's account information.

[0208] In one embodiment, the apparatus further includes an interaction module 707 configured to:

[0209] On the personal homepage of the target address, the seller and related personnel communicate about digital assets.

[0210] In one embodiment, the apparatus further includes a virtual interaction module 708 for:

[0211] Call the display device to interact with the seller and the digital asset at the target address.

[0212] In one embodiment, the apparatus further includes an intermediary module 709 configured to:

[0213] After receiving transaction promotion instructions, recommend, bid or auction digital assets.

[0214] In one embodiment, the apparatus further includes a query module 710 configured to:

[0215] After receiving the query command at the target address, the NFT is queried based on the keywords in the query command.

[0216] In one embodiment, the apparatus further includes a storage management module 711 configured to:

[0217] Generate multiple backups of the source file, and generate a backup file under the storage directory of the source file. The backup file describes all storage addresses of the backups, and stores the multiple backups at the storage addresses respectively. The storage addresses are the target addresses or the addresses of the distributed storage system.

[0218] In one embodiment, the storage management module 711 is further configured to:

[0219] After receiving the backup destruction instruction, destroy the backup specified in the instruction and update the backup file;

[0220] After receiving the backup update instruction, a backup is regenerated, the backup address is added to the backup file, and the backup is stored at the backup address.

[0221] In summary, the method and apparatus proposed in the embodiments of the present invention have the following beneficial effects:

[0222] 1. NFT provides uniqueness around the digital asset itself

[0223] According to the ERC721 and ERC1155 protocols, Ethereum's NFT uniqueness identification of digital assets is based on the URL, while NFT uniqueness identification of digital assets is based on the source file, which is a better solution and allows the buyer to truly own the source file.

[0224] 2. Users can choose to use anonymous or real-name accounts for NFT transactions

[0225] Ethereum accounts are anonymous, while NFT accounts are contract accounts. NFTs offer users more options, allowing real-name accounts to be linked to digital assets, expanding their use cases and extending ownership verification from online to offline. Furthermore, each NFT digital asset transaction allows users to choose whether to trade with a real name or anonymously, and users can transfer between their real-name and anonymous accounts, making transactions more flexible and adaptable to diverse trading scenarios.

[0226] 3. NFT is stored and recorded based on transactions rather than accounts, which helps save system overhead and is more in line with the uniqueness of digital assets.

[0227] After the NFT is initially minted, the source file and the initial minting record (the first transaction record in the transaction information) are placed at the target address or on IPFS. In subsequent transactions, the source file is not transferred, that is, the source file is not sent to the buyer's account, thus ensuring that the transfer of ownership of the source file (i.e., digital asset) is completed without increasing system communication and storage overhead. The ability to open, download, modify, and store at a different URL address is the entire meaning of ownership of a digital asset. Users have the option to decide whether to download the source file locally, store it elsewhere, or even offline for a period of time before putting it online. Users can also decide the number of backups to save.

[0228] Ethereum's accounting is based on account-based ledgers. In reality, each digital asset is unique, and a single, centralized ledger isn't necessary. Each digital asset should have its own ledger. This ledger is stored online with multiple backups, ensuring it's protected and easily accessible. All parties involved in a transaction—that is, users of the NFT—have their own transaction records stored, including the previous transaction (indicating the purchase of the NFT) and the next transaction (indicating the sale of the NFT). This facilitates ownership verification and reconciliation during transactions, while also ensuring that buyers can verify ownership of the NFT throughout their ownership period.

[0229] 4. NFT transaction records use chain accounting to ensure that they cannot be tampered with

[0230] NFT transaction records use a chained accounting method, where a hash is calculated for each transaction, and the current transaction record also records the hash of the previous transaction record. This chained accounting method, on the one hand, ensures that digital assets can be traced back to the first transaction record of initial minting, and on the other hand, it makes it very difficult to modify or tamper with historical transactions. To modify a transaction record, all subsequent transaction records must be modified as well.

[0231] NFTs don't have a central ledger; each NFT is independently accounted for, linked together by a hash of previous and subsequent transaction records. The display and trading of NFTs are driven by the seller, and the current owner is responsible for the safekeeping of the NFT asset.

[0232] 5. Introduce third-party verification procedures to verify transactions

[0233] NFT transactions are conducted through a third-party verification process conducted by the title verification agency. This process is automated and requires no human intervention. The program verifies the authenticity of the source file and the payment. Once verification is complete, the programmatic transfer of ownership takes place. Verification can utilize an encryption algorithm, and trust is machine-based.

[0234] 6. Source files and transaction records are stored in a distributed network with multiple backups to ensure they are not lost.

[0235] The source files and transaction records of NFT are stored at the target address or IPFS. It is recommended to have no less than 5, so as to ensure that the possibility of loss of NFT digital assets is reduced to the lowest possible level at the most economical and reasonable cost.

[0236] An embodiment of the present invention also provides a computer device. Figure 8 is a schematic diagram of a computer device in an embodiment of the present invention. The computer device 800 includes a memory 810, a processor 820, and a computer program 830 stored on the memory 810 and executable on the processor 820. When the processor 820 executes the computer program 830, the above-mentioned NFT-based digital asset management method is implemented.

[0237] An embodiment of the present invention also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it implements the above-mentioned NFT-based digital asset management method.

[0238] An embodiment of the present invention also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, it implements the above-mentioned NFT-based digital asset management method.

[0239] It will be understood by those skilled in the art that embodiments of the present invention may be provided as methods, systems, or computer program products. Thus, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0240] The present invention is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0241] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0242] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0243] The specific embodiments described above further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above description is only a specific embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.< / availability> < / sha256> < / length> < / availability> < / sha256> < / length> < / availability> < / length> < / index> < / brief> < / fingerprint> < / publie> < / name> < / did> < / filelength>

Claims

1. A digital asset management method based on NFT, characterized in that: include: Receive a source file minting application for a digital asset initiated by a seller, where the current owner of the source file is the seller; The source file is cast into an NFT. After the casting is completed, a record file is formed and stored at the target address. The record file includes basic information, file information and transaction information. The basic information is used to describe the basic information of the record file, the file information is used to describe the source file, and the transaction information includes multiple transaction records, each of which is the historical transfer information of the source file; Receiving a transaction application for the NFT initiated by the buyer, wherein the transaction application is initiated by the buyer after seeing the description information of the source file on the personal homepage of the seller at the target address; Call a third-party verification program to verify the source file and transaction information; if the verification is correct, update the transaction information; generate a new record file based on the file information and the updated transaction information; Keep the source file at the target address without transferring it, send the encrypted new record file to the buyer, and transfer the transaction amount to the seller.

2. The method according to claim 1, characterized in that The basic information includes the length of the record file, the record file description, the file number, the checksum, the account information of the current owner, the name of the current owner, and whether it is anonymous; The file number is used to describe the number of the current source file to which the record file is directed.

3. The method according to claim 2, characterized in that The file information also includes a digital fingerprint, which is used in any scenario of similarity checking, copyright determination, review, identification, and digital copyright management of the source file.

4. The method according to claim 1, characterized in that The file information includes a file record of a source file used for casting and a plurality of file records of source files modified from the source file used for casting; Each transaction record contains all the historical transfer information of each source document.

5. The method according to claim 4, characterized in that Each file record includes the source file index, source file length, source file hash, and validity of each source file; The source file hash is obtained by hashing the source file; Whether it is valid indicates whether the corresponding source file can be traded. Among all file records, only one file record corresponding to the source file can be traded.

6. The method according to claim 4, characterized in that The transaction record includes a transaction record header, a transaction record footer, the seller's account information, the buyer's account information, whether the buyer is anonymous, the transaction price, the source file hash, the URL, and the transaction timestamp; Among them, the transaction record header and transaction record tail are hash values, and the transaction record tail of the previous transaction record is the transaction record header of the current transaction record, and the transaction record tail of the current transaction record is calculated based on the current transaction record; The URL is the temporary address where the seller stores the digital asset; The source file hash is the hash of the source file for this transaction.

7. The method according to claim 6, characterized in that Call a third-party verification program to verify the source file and transaction information; if the verification is correct, update the transaction information, including: Call a third-party verification program to read a source file through a URL and calculate a hash of the source file; The calculated source file hash is first verified with the source file hash of the previous transaction record; If the first verification is correct, calculate the hash of the previous transaction record; The calculated hash of the previous transaction record is verified for the second time with the transaction record tail of the previous transaction record; If the second verification is correct, a new transaction record is generated and added to the transaction information; Close the URL.

8. The method according to claim 6, characterized in that Account information includes account name; The seller has at least one account information; Upon receiving a request from the seller to update the account information in the file information, updating the seller's account information in the file information; Generate a new transaction record and add it to the transaction information; Generate a new record file based on the file information and the updated transaction information.

9. The method according to claim 6, characterized in that Also includes: When the seller initiates an update of a preset field in the transaction information, a new transaction record is generated and added to the transaction information, wherein the preset field is the buyer's account information, source file hash or URL; Generate a new record file based on the file information and the updated transaction information.

10. The method according to claim 1, characterized in that The transaction information is recorded in a chain-entry manner.

11. The method according to claim 1, characterized in that Generate a new record file based on the file information and updated transaction information, including: Generate basic information based on the buyer's information, where the buyer's information includes the buyer's account information and the buyer's name; Generate a new record file based on the basic information, file information and updated transaction information.

12. The method according to claim 1, characterized in that Send the encrypted new record file to the buyer, including: Call a third-party program to obtain a current key, where the current key is a PGP public key; The new record file is encrypted with the current key and sent to the buyer. The current key becomes invalid after use.

13. The method according to claim 1, characterized in that Also includes: Receive the seller's identity management command on the target address's personal homepage and manage the seller's account information.

14. The method according to claim 1, wherein: Also includes: On the personal homepage of the target address, the seller and related personnel communicate about digital assets.

15. The method according to claim 1, wherein: Also includes: Call the display device to interact with the seller and the digital asset at the target address.

16. The method according to claim 1, wherein: Also includes: After receiving transaction facilitation instructions, digital assets are recommended, bid or auctioned.

17. The method according to claim 1, wherein: Also includes: After receiving the query command at the target address, the NFT is queried based on the keywords in the query command.

18. The method of claim 1, wherein: Also includes: Generate multiple backups of the source file, and generate a backup file in the storage directory of the source file. The backup file describes all storage addresses of the backups, and stores the multiple backups in the storage addresses respectively. The storage addresses are target addresses or addresses of distributed storage systems.

19. The method according to claim 18, characterized in that Also includes: After receiving the backup destruction instruction, destroy the backup specified in the instruction and update the backup file; After receiving the backup update instruction, a backup is regenerated, the address of the backup is added to the backup file, and the backup is stored at the address of the backup.

20. A digital asset management device based on NFT, characterized in that: include: A casting application receiving module, used to receive a casting application for a source file of a digital asset initiated by a seller, wherein the current owner of the source file is the seller; A casting module is used to cast the source file into an NFT. After the casting is completed, a record file is formed and stored at the target address. The record file includes basic information, file information and transaction information. The basic information is used to describe the basic information of the record file, and the file information is used to describe the source file. The transaction information includes multiple transaction records, each of which is the historical transfer information of the source file; A transaction application receiving module, used to receive a transaction application initiated by a buyer for the NFT, wherein the transaction application is initiated by the buyer after seeing the description information of the source file on the personal homepage of the seller at the target address; The verification module is used to call a third-party verification program to verify the source file and transaction information; when the verification is correct, the transaction information is updated; and a new record file is generated based on the file information and the updated transaction information; The transaction module is used to keep the source file at the target address without transferring it, send the encrypted new record file to the buyer, and transfer the transaction amount to the seller.

21. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method according to any one of claims 1 to 19 is implemented.

22. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 19 is implemented.

23. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 19 is implemented.

Citation Information

Patent Citations

  • Method and device for determining ownership of blockchain machine generated data

    CN114070554A

  • Original picture protection method based on block chain

    CN114218533A

  • Data transaction method, device and system based on NFT, electronic device and medium

    CN114581089A

  • Digital collection transaction method and system based on NFT

    CN114998013A

  • NFT transaction management system based on decentralized autonomous organization

    CN115271962A

Cited By

  • Digital collection right confirmation method and system based on block chain

    CN120429845A