CN116308325B - Digital asset management method and device based on NFT - Google Patents
Digital asset management method and device based on NFT Download PDFInfo
- Publication number
- CN116308325B CN116308325B CN202310572368.4A CN202310572368A CN116308325B CN 116308325 B CN116308325 B CN 116308325B CN 202310572368 A CN202310572368 A CN 202310572368A CN 116308325 B CN116308325 B CN 116308325B
- Authority
- CN
- China
- Prior art keywords
- transaction
- file
- information
- record
- source file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000007726 management method Methods 0.000 title abstract description 33
- 238000005266 casting Methods 0.000 claims abstract description 50
- 238000000034 method Methods 0.000 claims abstract description 40
- 238000012795 verification Methods 0.000 claims abstract description 36
- 238000003860 storage Methods 0.000 claims description 38
- 238000004590 computer program Methods 0.000 claims description 22
- 238000012546 transfer Methods 0.000 claims description 19
- 238000012545 processing Methods 0.000 claims description 6
- 238000004891 communication Methods 0.000 claims description 5
- 238000004364 calculation method Methods 0.000 claims description 3
- 230000001172 regenerating effect Effects 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 13
- 230000006870 function Effects 0.000 description 6
- 238000012790 confirmation Methods 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 239000000047 product Substances 0.000 description 4
- 230000008859 change Effects 0.000 description 3
- 230000000875 corresponding effect Effects 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 238000010200 validation analysis Methods 0.000 description 3
- RTZKZFJDLAIYFH-UHFFFAOYSA-N Diethyl ether Chemical compound CCOCC RTZKZFJDLAIYFH-UHFFFAOYSA-N 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000006243 chemical reaction Methods 0.000 description 2
- 230000006872 improvement Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000011084 recovery Methods 0.000 description 2
- 235000006679 Mentha X verticillata Nutrition 0.000 description 1
- 235000002899 Mentha suaveolens Nutrition 0.000 description 1
- 235000001636 Mentha x rotundifolia Nutrition 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 239000011449 brick Substances 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 230000002596 correlated effect Effects 0.000 description 1
- 238000005520 cutting process Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000002360 explosive Substances 0.000 description 1
- 239000012467 final product Substances 0.000 description 1
- 239000011521 glass Substances 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000135 prohibitive effect Effects 0.000 description 1
- 238000012552 review Methods 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/12—Payment architectures specially adapted for electronic shopping systems
- G06Q20/123—Shopping for digital content
- G06Q20/1235—Shopping for digital content with control of digital rights management [DRM]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3827—Use of message hashing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3829—Payment protocols; Details thereof insuring higher security of transaction involving key management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
Abstract
The invention discloses a digital asset management method and device based on NFT, the method includes: receiving a source file casting application for the digital asset initiated by a seller; casting the source file into an NFT, forming a record file after casting, and storing the record file on a target address, wherein the record file comprises basic information, file information and transaction information; receiving a transaction application initiated by a buyer for the NFT; calling a third party verification program to verify the source file and the transaction information; updating transaction information when the verification is correct; generating a new record file according to the file information and the updated transaction information; and (3) keeping the source file not transferred on the target address, sending the encrypted new record file to the buyer, and transferring the transaction money to the seller. The invention can realize autonomous management and convenient transaction of digital assets, and does not need to bind the NFT on any platform, thereby realizing any right and transaction. Becomes the bottom base protocol of Web3, and greatly reduces the credit cost.
Description
Technical Field
The invention relates to the technical field of blockchain, in particular to a digital asset management method and device based on NFT.
Background
This section is intended to provide a background or context to the embodiments of the invention that are recited in the claims. The description herein is not admitted to be prior art by inclusion in this section.
NFT (Non-homogeneous Token), each of which may represent a unique digital material, may be used for digital assets such as drawings, artwork, sound, movies, in-game items or other forms of creative work due to its heterogeneous nature.
NFT is considered a knock brick into the meta-universe, unique, and has been touted for several years. Because NFT is unique, all artwork, whether in various forms such as books, words, music or images, even digitized collectibles and online games are considered to be able to verify their unique and rare value by the special authentication means of NFT. More than 90% of ethernet NFTs currently on the market trade on Opensea.
Whereas the Gas fee for too high an ethernet would be too costly for works that are not of high value or for which market validation prices have not been available. However, if the NFT is not cast as the NFT on the ethernet, the NFT cannot be guaranteed to be illegally hacked by a person or hacked into malicious copying by a hacker after being submitted to a transaction center. The too high threshold of ethernet NFT undoubtedly prevents the active participation of the creator, and also makes most less valuable digital works prohibitive, which undoubtedly affects the explosive development of the digital culture market. There are also NFTs cast on Layer2 or other chains (e.g., goschain) that are ethernet compatible, but the robustness of the system is not known.
Disclosure of Invention
The embodiment of the invention provides a digital asset management method based on NFT (network File transfer technology), which is used for improving the existing non-homogeneous general evidence and realizing autonomous management and convenient transaction of digital assets, and comprises the following steps:
receiving a source file casting application for the digital asset initiated by a seller, wherein the current owner of the source file is the seller;
casting the source file into an NFT, forming a record file after casting is completed, and storing the record file on a target address, wherein the record file comprises basic information, file information and transaction information, the basic information is used for describing the basic information of the record file, the file information is used for describing the source file, the transaction information comprises a plurality of transaction records, and each transaction record is history transfer information of the source file;
receiving a transaction application initiated by a buyer aiming at the NFT, wherein the transaction application is initiated after the buyer sees the description information of a source file on a personal homepage of a seller of a target address;
calling a third party verification program to verify the source file and the transaction information; updating transaction information when the verification is correct; generating a new record file according to the file information and the updated transaction information;
And (3) keeping the source file not transferred on the target address, sending the encrypted new record file to the buyer, and transferring the transaction money to the seller.
The embodiment of the invention also provides a digital asset management device based on the NFT, which is used for improving the existing non-homogeneous pass and realizing the autonomous management and convenient transaction of the digital asset, and comprises the following components:
the system comprises a casting application receiving module, a source file casting application receiving module and a processing module, wherein the casting application receiving module is used for receiving a source file casting application for digital assets initiated by a seller, and the current owner of the source file is the seller;
the system comprises a casting module, a storage module and a storage module, wherein the casting module is used for casting the source file into an NFT, forming a record file after casting is completed and storing the record file on a target address, the record file comprises basic information, file information and transaction information, the basic information is used for describing the basic information of the record file, the file information is used for describing the source file, the transaction information comprises a plurality of transaction records, and each transaction record is history transfer information of the source file;
a transaction application receiving module, configured to receive a transaction application initiated by a buyer for the NFT, where the transaction application is initiated after the buyer sees description information of a source file on a personal homepage of a seller at a target address;
The verification module is used for calling a third party verification program to verify the source file and the transaction information; updating transaction information when the verification is correct; generating a new record file according to the file information and the updated transaction information;
and the transaction module is used for keeping the source file not transferred on the target address, sending the encrypted new record file to the buyer and transferring the transaction money to the seller.
The embodiment of the invention also provides computer equipment, which comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor realizes the digital asset management method based on the NFT when executing the computer program.
The embodiment of the invention also provides a computer readable storage medium, wherein the computer readable storage medium stores a computer program, and the computer program realizes the digital asset management method based on the NFT when being executed by a processor.
Embodiments of the present invention also provide a computer program product comprising a computer program which, when executed by a processor, implements the NFT-based digital asset management method described above.
In the embodiment of the invention, a source file casting application for digital assets initiated by a seller is received, wherein the current owner of the source file is the seller;
Casting the source file into an NFT, forming a record file after casting is completed, and storing the record file on a target address, wherein the record file comprises basic information, file information and transaction information, the basic information is used for describing the basic information of the record file, the file information is used for describing the source file, the transaction information comprises a plurality of transaction records, and each transaction record is history transfer information of the source file; receiving a transaction application initiated by a buyer aiming at the NFT, wherein the transaction application is initiated after the buyer sees the description information of a source file on a personal homepage of a seller of a target address; calling a third party verification program to verify the source file and the transaction information; updating transaction information when the verification is correct; generating a new record file according to the file information and the updated transaction information; and (3) keeping the source file not transferred on the target address, sending the encrypted new record file to the buyer, and transferring the transaction money to the seller. Compared with the technical scheme of adopting the NFT to realize digital asset management in the prior art, the method can realize autonomous management and convenient transaction of the digital asset by applying the NFT and the application record file on the target address. The NFT need not be bound to any platform, and any rights and transactions may be implemented. The method is really a bottom-layer foundation protocol of Web3, and greatly reduces the credit cost of society.
Drawings
In order to more clearly illustrate the embodiments of the invention or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art. In the drawings:
FIG. 1 is a flow chart of a method of NFT-based digital asset management in an embodiment of the invention;
FIG. 2 is a schematic diagram of a record file according to an embodiment of the present invention;
FIG. 3 is a diagram of file information according to an embodiment of the present invention;
FIG. 4 is an example of a source file in an embodiment of the invention;
FIG. 5 is a diagram of transaction information according to an embodiment of the present invention;
FIG. 6 is a flow chart of a transaction performed in an embodiment of the present invention;
FIG. 7 is a schematic diagram of an NFT-based digital asset management device in an embodiment of the invention;
fig. 8 is a schematic diagram of a computer device in an embodiment of the invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the embodiments of the present invention will be described in further detail with reference to the accompanying drawings. The exemplary embodiments of the present invention and their descriptions herein are for the purpose of explaining the present invention, but are not to be construed as limiting the invention.
The inventors have found that NFT also has the following problems:
1. NFT cannot authenticate the true ownership of digital work
The NFT's current way of doing so is anonymous, who knows who the private key is. This way of anonymous rights confirmation can only meet small usage scenarios, not fit for scenarios involving real name rights confirmation. Whereas real-name scenes are huge. Through ERC721, ERC1155 protocols, only submitting a URL corresponding to a digital file (such as an NFT header file) to an ethernet, the account is anonymous, only a transaction history record between anonymous accounts can be seen through a query tool, and it is impossible to confirm who is the originality, and also to confirm who is the current owner. Whether the presenter is a real owner cannot be demonstrated. The protection of intellectual property firstly requires ownership confirmation, and secondly, the propagation process is traceable and traceable, and the NFT obviously cannot meet the requirement that a real art creator hopes to protect the intellectual property of the created work by the NFT.
2. The data file of the NFT can be easily copied, and the basic requirement of intellectual property protection can not be met
The content of the NFT based on the smart contract is public, and anyone can easily copy the file archive pointed by the URL of the NFT. Even the stored content placed in the IPFS may be duplicated. IPFS simply tells the user that a node stores data at the relevant address, and if other nodes are interested in the relevant data, it can also make a copy.
3. The ERC721, ERC1155 protocols fail to meet the operational needs of intellectual property protection in the real world
The document format of the file in the real world is changed, the size is changed, and the content is slightly changed, so that the original intellectual property right is not influenced. According to the ERC721, ERC1155 protocols of NFT, once the NFT is cast (Mint), any modifications will not be allowed, any even one byte changes in file content, storage address, account information will occur, and another NFT product will be formed. This is far from the actual operational need for identification and protection of intellectual property rights in the real world.
In addition, according to ERC721, ERC1155 protocols, using ethernet anonymous accounts, since many platforms are compliant platforms for ethernet ERC20, NFT product releases can be cast on multiple platforms, even multiple times on the same platform with only one byte change. The user cannot review how many NFTs of the same content source files or similar NFTs are through the digital work file. For example, if a picture is seen, it is not done to want to see if there is already an NFT, or how many NFTs with similar content. Further, the contract address, and Token ID, owner, and previous creation and transfer records can be found on the Ether Scan, but the data file itself is not visible.
4. NFT may be lost
Due to blockchain storage capacity limitations, NFTs typically do not store associated source file works on the blockchain because such file files are large. It is common practice to point to the artwork at a web site, and the content and source file index represented by the NFT is separate from the storage of the NFT smart contract, which is typically stored on a storage device other than the blockchain smart contract, either as a centralized server, a cloud, or as a distributed file system (IPFS).
A centralized server or cloud system storing the content and source file index represented by the NFT would mean that the content was lost if it were to fail or fail. Even if the content and source file index represented by the NFT are uploaded onto the IPFS, it is not completely guaranteed that the stored media will not be destroyed.
Furthermore, because most NFTs can only link to URLs, this means that the stored content corresponding to the URL can be changed, and once the stored content is changed, the NFT is lost. NFTs that may cost up to purchase if the address connection fails will no longer exist.
5. NFT and real world are split
When digital assets are not linked to the real world, both value and usage categories are greatly limited. In the future, NFT should be able to represent real world assets, correspond to real names of ownership, and communicate with verification confirmation of real world rights certification authorities, and operate in online and offline coordination to truly merge the real world with the virtual world.
To address these issues above, embodiments of the present invention propose a digital asset management scheme based on NFT that is optimized based on existing NFTs, being NFTs cast on target addresses.
FIG. 1 is a flow chart of a method for NFT-based digital asset management in an embodiment of the invention, the method comprising:
step 101, receiving a source file casting application for a digital asset initiated by a seller, wherein the current owner of the source file is the seller;
step 102, casting the source file into an NFT, forming a record file after casting is completed, and storing the record file on a target address, wherein the record file comprises basic information, file information and transaction information, the basic information is used for describing the basic information of the record file, the file information is used for describing the source file, the transaction information comprises a plurality of transaction records, and each transaction record is history transfer information of the source file;
Step 103, receiving a transaction application initiated by a buyer for the NFT, wherein the transaction application is initiated after the buyer sees the description information of the source file on a personal homepage of a seller of a target address;
step 104, calling a third party verification program to verify the source file and the transaction information; updating transaction information when the verification is correct; generating a new record file according to the file information and the updated transaction information;
step 105, keeping the source file not transferred at the target address, sending the encrypted new record file to the buyer, and transferring the transaction money to the seller.
In the embodiment of the invention, the idea of combining the NFT and the target address is mainly adopted because the Opensea has absolute monopoly in the aspects of casting, displaying and trading of the Ethernet NFT, and the market share is up to more than 90%. Leaving such a centralized exchange, the average user wants to complete digital asset NFT validation and transactions, with a high technical threshold. But the first market that NFT started is the digital artwork market, the vast majority of authors are out-of-circle and the vast majority of collectors are out-of-circle, which undoubtedly creates a virtually very serious centralized reliance, incompatible with the core concept of "distributed, independent free, machine trust" advocated by blockchain.
In the embodiment of the application, the target address can be a family cloud, a distributed network (IPFS) or a server, so long as the method can be realized, instead of adopting the Ethernet, thereby overcoming the problem of NFT on the Ethernet at present.
The target address provides a convenient tool for the user to build his home page. Based on homepage, user carries out identity management, anonymity, real name, and privacy opening degree, which is decided by user.
Based on the personal homepage, the user can conveniently publish, cast, display and trade the NFT, and can also build a social network to attract fans, attentives and interested persons to the homepage for interaction and trade. A good IP is humanly provided, storybook, imagine that an author can have more and more free expression and communication ways to interact with supporters, rather than simply speaking the authoring concept and story in the Opensea Description field.
The following describes the scheme of the application in detail.
Receiving a source file casting application for the digital asset initiated by a seller, wherein the current owner of the source file is the seller, step 101;
Wherein, the seller can choose to cast the source file of the own digital asset, and then can issue the description information of the source file to the personal homepage, wherein the description information comprises the source file, the source file index and the like, and the issuing means that a record of the digital asset, namely the description information, is generated.
In step 102, the source file is cast into an NFT, a record file is formed after casting is completed, and the record file is stored in a target address, wherein the record file comprises basic information, file information and transaction information, the basic information is used for describing the basic information of the record file, the file information is used for describing the source file, the transaction information comprises a plurality of transaction records, and each transaction record is history transfer information of the source file;
the source file of the digital asset is cast as an NFT that is unique and can be transacted.
Referring to fig. 2, an example of recording a file in an embodiment of the present invention is shown.
In one embodiment, the basic information includes a length of a record file, a record file description, a file number, a check code, account information of a current owner, a name of the current owner, and whether anonymity exists;
the file number is used to describe the number of the current source file for which the file is recorded.
In an embodiment, the file information further includes a digital fingerprint for any one of similar copy checking, copyright determination, auditing, identification, and digital copyright management of the source file.
Digital fingerprinting refers to the generation of a string of characters from multimedia or picture content that uniquely identifies the current content. The high stability of the final product is ensured, and the influence of operations such as format conversion, editing, cutting and splicing, compression and rotation and the like of video/photo/audio files is effectively avoided. In contrast to hashing, the "fingerprinting" technique is able to determine similarity after some sort of "scaling", "changing the rate of separation", "recoding", etc. has been performed on the original file.
In one embodiment, the file information includes a file record of a source file for casting and a plurality of file records of source files modified for the source file for casting;
each transaction is recorded as all of the history transfer information for each source file.
That is, in embodiments of the present invention, the source file may have multiple copies, e.g., 1000 copies, and then 1000 buyers all have versions after purchasing.
In an embodiment, referring to fig. 3, each file record includes a source file index, a source file length, a source file hash, and whether each source file is valid;
FIG. 4 is an example of a source file in an embodiment of the invention, which may take many forms, including a file of encoded classes, a file of tag classes (e.g., tags of time, place representations), a code file, a video file, an image file, and so forth.
The source file hash is obtained by performing hash calculation on the source file. Who purchases the source file and who owns the copyright.
The source file index is information describing the source file attributes, including information of an creator, creation time, category, keyword, and the like. The cover information of the image and the audio and video is stored in the source file index, so that each buyer can know the work conveniently.
The source file is the biggest characteristic of this scheme, has ensured that the owner's true ownership, i.e. others have no copyright, and only the true owner has copyright, for example, the version of a song belongs to the creator, and ordinary people can only listen to, and cannot be used commercially. Meanwhile, because the guarantee is provided, the transaction information is just recorded on the transaction behavior, and the place (URL) of the file storage can be changed in each transaction, so that the prior NFT does not need to make articles on the URL, and the essence of the transaction object is returned: the digital asset is a source file, not a URL.
Referring to fig. 5, the transaction record includes a transaction record header, a transaction record trailer, account information of a seller, account information of a buyer, whether the buyer is anonymous, a transaction price, a source file hash, a URL, a transaction timestamp;
the transaction record head and the transaction record tail are hash values, the transaction record head of the next transaction record is the transaction record tail of the current transaction record, and the transaction record tail is calculated according to the current transaction record;
the URL is a temporary address where the seller stores the digital asset;
source file hash the hash of the source file for the transaction.
In one embodiment, the transaction information is recorded in a chained billing manner, so that the transaction is guaranteed to be tamper-proof, and each transaction can be traced back conveniently.
Since the transaction record of each NFT adopts a chained accounting mode, each transaction has a transaction timestamp, a hash value is calculated, and each transaction record contains the hash value of the last transaction record, so that the historical transaction record of each NFT cannot be tampered with. Chained billing makes it difficult to alter any one transaction because all subsequent transactions need to be modified accordingly.
An example of a specific record file is given below.
This part is basic information
< FileLength > 65536// Length of record File
< CRC32>0x 1234567// check code
< DID > anonymous/888888888// buyer account information
< name > zhangsukai// buyer name
< Public > yes/no// whether anonymous
< finger print >// digital Fingerprint
< Brief > the is is draw by zhangdaqian
< Index > 888// File reference
This part is file information including file record Original file of source file for casting and file record subfile file of source file modified for source file for casting
< Original file > http:// www.yuxing.com/sourcefile/12345678890. Com// source file index
< Length > 65536// source file Length
< sha256>0 x..the.// source file hash
< availability > yes/no// whether valid
<subfile file>http://www.yuxing.com/sourcefile/1234567890.com
<Length>65536
<sha256>0x.......
<availability>yes/no
<subfile file>http://www.yuxing.com/sourcefile/1234567890.com
<Length>65536
<sha256>0x.......
<availability>yes/no
....
This part is transaction information including a plurality of transaction records Trade information
<Trade Infomation>
"Hash0", "" "Buyer", "yes/no", "" FileHash' "," URL "," Timestamp "," Hash1 "// transaction record formed from file records of source files used for casting
<Trade Infomation>
"Hash1", "Seller", "Buyer", "yes/no", "Price", "FileHash'", "URL", "Timestamp", "Hash 2"// from this transaction record is a file record of a source file modified for a source file used for casting, where Hash1 is a transaction record header, seller is account information of a Seller, buyer is account information of a Buyer, yes/no is whether the Buyer is anonymous, price is a transaction Price, fileHash is a source file Hash, URL is URL, timestamp is a transaction Timestamp, hash2 is a transaction record tail
<Trade Infomation>
"Hash2","Seller","Buyer","yes/no","Price","FileHash'","URL","Timestamp","Hash3"
<Trade Infomation>
"Hash3","Seller","Buyer","yes/no","Price","FileHash'","URL","Timestamp","Hash4"
In step 103, receiving a transaction application initiated by a buyer for the NFT, wherein the transaction application is initiated after the buyer sees the description information of the source file on the personal homepage of the seller at the target address, and in addition, the seller and the buyer can determine to initiate the transaction application after exchanging on the personal homepage of the seller;
in step 104, a third party verification program is called to verify the source file and the transaction information; updating transaction information when the verification is correct; generating a new record file according to the file information and the updated transaction information;
when a buyer initiates a transaction, new transaction information is generated according to the current transaction condition, and the transaction information is not updated at the moment, payment does not occur, and the transaction information is sent to a third party verification program for verification;
FIG. 6 is a flow chart of a transaction performed in an embodiment of the invention, invoking a third party verification program to verify source files and transaction information; updating transaction information upon verification of an error, including:
step 601, calling a third party verification program to read a source file through a URL, and calculating the hash of the source file;
step 602, performing first verification on the calculated hash of the source file and the hash of the source file recorded by the last transaction;
Step 603, if the first verification is correct, calculating a hash of the last transaction record;
step 604, performing a second verification on the calculated hash of the last transaction record and the transaction record tail of the last transaction record;
step 605, if the second verification is correct, generating a new transaction record and adding the new transaction record to the transaction information;
step 606, closing the URL.
After the transaction is completed, the buyer owns the copyright of the source file.
During the transaction, NFT virtually guarantees that the target of the transaction is the source file (digital work itself), rather than the URL, which is a very innovative improvement over existing NFT models. When the transaction is completed, only the current owner (buyer) has the right to do so and the right to open the next transaction.
To address the problem of NFT being lost forever after the user loses the private key, the relief provided by the target address chainless wallet is employed for user recovery, but such recovery tools include, but are not limited to, chainless wallets.
In one embodiment, the account information includes an account name;
the seller has at least one piece of account information;
updating account information of the seller in the file information when receiving a demand of the seller to update the account information in the file information;
Generating a new transaction record and adding the new transaction record to the transaction information;
and generating a new record file according to the file information and the updated transaction information.
In an embodiment, the method further comprises:
when a seller initiates updating of a preset field in transaction information, a new transaction record is generated and added into the transaction information, wherein the preset field is account information of a buyer, a source file hash or a URL;
and generating a new record file according to the file information and the updated transaction information.
That is, the change of multiple accounts of the same owner may be considered a transaction, except for a price of 0, and the fields in the transaction information may be changed, or may be considered a transaction, such as a modification to the source file, where the source file hash is changed.
In practice, whether real name or anonymity is used will be decided by the seller (current owner) himself. The owner, as desired, seems to be more in line with the free spirit and requirements of the platform product. For digital assets with high association with real assets, both buying and selling parties tend to use real names, so that the rights are convenient to confirm. For digital assets that are not highly correlated with real assets, the buying and selling parties may be inclined to use anonymity. Meanwhile, in order to enable the owner to use anonymity in one stage and real name in one stage more flexibly, the owner can complete conversion between anonymity and real name by carrying out one-time transaction, and the relationship between real name account and anonymity account is not exposed. In an application scenario where the demand for copyright validation is high, the release and transaction of data products using the owner real name is recommended, but this is determined by the choice of market. For example, a buyer preparing to spend a large price to buy a picture must tend to choose an NFT that is initially first-named with real name, and a seller that is a real-named user, can trace well to the source and maintain rights in the real world once infringement occurs.
A transfer transaction is carried out between the real name and the anonymous account; the modification of the source file is calculated as a transfer transaction, the URL must be reselected to store the new file, the old file is reserved, and the hash value of the file is changed.
In one embodiment, generating a new record file according to the file information and the updated transaction information includes:
generating basic information according to information of a buyer, wherein the information of the buyer comprises account information of the buyer and the name of the buyer;
and generating a new record file according to the basic information, the file information and the updated transaction information.
The current key is updated after being used for the next use, the encrypted file information is transmitted to the buyer, the file information can be opened only by the buyer, the source file is read through the file index, and other people cannot read the file.
In step 105, the source file is kept not transferred at the destination address, the encrypted new record file is sent to the buyer, and the transaction is transferred to the seller.
In an embodiment, the method further comprises:
and receiving an identity management command of the seller on a personal homepage of the target address, and managing account information of the seller. For example, an account is newly created, and a real name or anonymous account is selected.
In an embodiment, the method further comprises:
on the personal home page of the target address, a communication is made between the seller and the associated person regarding the digital asset.
In an embodiment, the method further comprises:
and calling the display equipment to interact the seller and the digital asset on the target address.
The above embodiments embody virtual presentation functions, and the display device includes, but is not limited to, hardware glasses, holographic 3D display devices, such as VR, showing Box, etc. The target address pushes out a series of holographic 3D display devices (showingBox), so that the created, favorite and collected NFT can interact with voice and shape even when the personalized NFT is near to the eyes, if the target address is matched with an online NFT image object, the ShowingBox can realize offline online second-level binding, and online and offline limit edition is guaranteed. The Showing Box hardware also supports wallet and multi-signature, because of geographical position information and exclusive equipment, the signature of the Showing Box has strong unique identification capability. The Showing Box also provides distributed storage and cluster computing functions at the same time, and becomes an important component of system ecology.
In an embodiment, the method further comprises:
After receiving the transaction facilitation instructions, a recommendation, bid, or auction is conducted on the digital asset.
The above embodiment mainly shows the matching effect of the centralized transaction, the digital asset is published and displayed through the personal homepage APP, and the seller can select the centralized transaction provided at the target address to register the digital asset page of the personal homepage, because the storage structure and format of the digital asset are the same, and the query speed of the centralized transaction can be greatly improved. The centralized exchange plays a role in mediating and matching, and the transaction is still completed through point-to-point between users.
In an embodiment, the method further comprises:
after receiving the query command at the target address, the NFT is queried based on the keywords in the query command.
In the above embodiment, the target address system provides a browser website similar to EtherScan, so that anyone can conveniently inquire digital works, owners, personal homepages and transfer records, and can conveniently search related infringement works, thereby facilitating right maintenance and judicial rescue. If the software is third-party software, a layer of software is packed on the software, and the software browses in the APP.
In an embodiment, the method further comprises:
Generating a plurality of backups from a source file, generating a backup file under a storage directory of the source file, wherein all storage addresses of the backups are described in the backup file, and respectively storing the backups on the storage addresses, and the storage addresses are target addresses or addresses of a distributed storage system.
In the above embodiment, the file name of the backup text file is < hash value of source file.bak >, so that the backup text file can be closed to the source file, and the backup text file and the source file have complete consistency.
In practice, at least 5 backups are performed.
In an embodiment, the method further comprises:
after receiving the backup destroying instruction, the backup aimed at in the destroying instruction is updated;
and after receiving the backup update instruction, regenerating a backup, adding the address of the backup to the backup file, and storing the backup to the address of the backup.
In the above embodiment, the source file may decide whether to destroy based on security requirements, if not destroy, the source file may be directly traded next time, and if destroyed, one will be randomly selected from qualified backup files for formal trading.
The embodiment of the invention also provides a digital asset management device based on the NFT, which is described in the following embodiment. Since the principle of the device for solving the problem is similar to that of the NFT-based digital asset management method, the implementation of the device can refer to the implementation of the NFT-based digital asset management method, and the repetition is omitted.
Fig. 7 is a schematic diagram of an NFT-based digital asset management device according to an embodiment of the invention, including:
a casting application receiving module 701, configured to receive a source file casting application for a digital asset initiated by a seller, where a current owner of the source file is the seller;
a casting module 702, configured to cast the source file into an NFT, form a record file after the casting is completed, and store the record file in a target address, where 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 a plurality of transaction records, where each transaction record is history transfer information of the source file;
a transaction application receiving module 703, configured to receive a transaction application initiated by a buyer for the NFT, where the transaction application is initiated after the buyer sees the description information of the source file on a personal homepage of the seller at the target address;
a verification module 704, configured to invoke a third party verification program to verify the source file and the transaction information; updating transaction information when the verification is correct; generating a new record file according to the file information and the updated transaction information;
The transaction module 705 is configured to keep the source file from being transferred at the destination address, send the encrypted new record file to the buyer, and transfer the transaction money to the seller.
In one embodiment, the basic information includes a length of a record file, a record file description, a file number, a check code, account information of a current owner, a name of the current owner, and whether anonymity exists;
the file number is used to describe the number of the current source file for which the file is recorded.
In an embodiment, the file information further includes a digital fingerprint for any one of similar copy checking, copyright determination, auditing, identification, and digital copyright management of the source file.
In one embodiment, the file information includes a file record of a source file for casting and a plurality of file records of source files modified for the source file for casting;
each transaction is recorded as all of the history transfer information for each source file.
In an embodiment, each file record includes a source file index, a source file length, a source file hash, and whether each source file is valid;
the source file hash is obtained by carrying out hash calculation on the source file;
Whether the corresponding source file can be transacted or not is effectively indicated, and only one file record in all file records corresponds to the source file and can be transacted.
In an embodiment, the transaction record includes a transaction record header, a transaction record trailer, account information for a seller, account information for a buyer, whether the buyer is anonymous, a transaction price, a source file hash, a URL, a transaction timestamp;
the transaction record head and the transaction record tail are hash values, the transaction record head of the next transaction record is the transaction record tail of the current transaction record, and the transaction record tail is calculated according to the current transaction record;
the URL is a temporary address where the seller stores the digital asset;
source file hash the hash of the source file for the transaction.
In one embodiment, the verification module is specifically configured to:
calling a third party verification program to read a source file through a URL, and calculating the hash of the source file;
performing first verification on the calculated hash of the source file and the hash of the source file recorded by the last transaction;
if the first verification is correct, calculating the hash of the last transaction record;
performing a second verification on the calculated hash of the last transaction record and the transaction record tail of the last transaction record;
If the second verification is correct, a new transaction record is generated and added into the transaction information;
closing the URL.
In one embodiment, the account information includes an account name;
the seller has at least one piece of account information;
updating account information of the seller in the file information when receiving a demand of the seller to update the account information in the file information;
generating a new transaction record and adding the new transaction record to the transaction information;
and generating a new record file according to the file information and the updated transaction information.
In an embodiment, the transaction module is further to:
when a seller initiates updating of a preset field in transaction information, a new transaction record is generated and added into the transaction information, wherein the preset field is account information of a buyer, a source file hash or a URL;
and generating a new record file according to the file information and the updated transaction information.
In one embodiment, the transaction information is recorded in a chain billing manner.
In one embodiment, basic information is generated according to information of a buyer, wherein the information of the buyer comprises account information of the buyer and the name of the buyer;
and generating a new record file according to the basic information, the file information and the updated transaction information.
In an embodiment, the transaction module is further to:
calling a third-party program to obtain a current secret key, wherein the current secret key is a PGP public key;
and encrypting the new record file by using the current key, and sending the encrypted new record file to the buyer, wherein the current key is invalid after use.
In an embodiment, the apparatus further comprises a management module 706 for:
and receiving an identity management command of the seller on a personal homepage of the target address, and managing account information of the seller.
In an embodiment, the apparatus further comprises an interaction module 707 for:
on the personal home page of the target address, a communication is made between the seller and the associated person regarding the digital asset.
In one embodiment, the apparatus further comprises a virtual interaction module 708 for:
and calling the display equipment to interact the seller and the digital asset on the target address.
In an embodiment, the apparatus further comprises an intermediary module 709 for:
after receiving the transaction facilitation instructions, a recommendation, bid, or auction is conducted on the digital asset.
In an embodiment, the apparatus further comprises a query module 710 for:
after receiving the query command at the target address, the NFT is queried based on the keywords in the query command.
In an embodiment, the apparatus further comprises a storage management module 711 for:
generating a plurality of backups from a source file, generating a backup file under a storage directory of the source file, wherein all storage addresses of the backups are described in the backup file, and respectively storing the backups on the storage addresses, and the storage addresses are target addresses or addresses of a distributed storage system.
In one embodiment, the storage management module 711 is further configured to:
after receiving the backup destroying instruction, the backup aimed at in the destroying instruction is updated;
and after receiving the backup update instruction, regenerating a backup, adding the address of the backup to the backup file, and storing the backup to the address of the backup.
In summary, the method and the device provided by the embodiment of the invention have the following beneficial effects:
1. NFT gives unique calibration around digital asset itself
According to ERC721, ERC1155 protocols, the NFT of the ethernet is URL-based for the unique calibration of the digital asset, and the NFT is source file-based for the unique calibration of the digital asset, which solves better so that the buyer really owns the source file.
2. The transaction of the NFT may be user-selected whether the anonymous account or the real-name account
The accounts of the ethernet are anonymous and the accounts of the NFT are contractual accounts. NFT provides more options for the user, real-name account binding with digital assets, wider usage scenarios, and ownership identification can extend from online to offline real world. Meanwhile, each transaction of the NFT digital asset is selected to be real-name or anonymous, the same user is supported to transfer the transaction between the real-name account and the anonymous account, the transaction becomes more flexible, and the transaction requirements under different scenes can be met.
3. NFT stores and accounts based on transactions rather than accounts, which is beneficial to saving system overhead, while more conforming to the unique feature of digital asset
After the NFT is initially cast, the source file and initial casting record (the first transaction record in the transaction information) are placed on the destination address or IPFS. After the transaction, the source file is not transferred, that is, the source file is not sent to the buyer account, so that transfer and handover of ownership of the source file (namely digital asset) is completed without increasing system communication and storage cost. Can be opened, downloaded, modified, and replaced with a URL address store, which is the full meaning of ownership for a digital asset. The user has the option to decide whether to download the source file locally, store it in another place, even offline for a period of time, and then put it on the internet, and the user can decide the number of backup to save.
The ethernet book is account-based book accounting, and in fact, digital assets are not identical for each, and do not require a large account to account, each digital asset should be its own book. The account book is stored on the internet, is backed up by a plurality of copies, is guaranteed not to be lost, and can be quickly queried. All parties involved in the transaction, namely the related users of the NFT, store transaction records related to the parties, namely a last transaction record (which indicates that the NFT is purchased) and a next transaction record (which indicates that the NFT is sold), so that the transaction is convenient to check the right, and meanwhile, the buyer is ensured to check the right in the possession period of the NFT.
4. The NFT transaction record adopts a chained accounting mode to ensure that the transaction record cannot be tampered with
The NFT transaction records adopt a chained accounting mode, a Hash is calculated once for each transaction, and the Hash of the last transaction record is recorded simultaneously in the current transaction record. The chained accounting mode ensures that the tracing of the digital asset can be efficiently traced to the first transaction record of the initial casting, and meanwhile, the history transaction and the tampering are difficult to change, and the transaction record needs to be changed all the later.
NFTs have no ledgers, each NFT counts independently, and Hash chains together by front-to-back transaction records. The presentation and transaction of NFT is driven by the seller, who is currently responsible for keeping NFT assets.
5. Introducing a third party verification program to verify transactions
The third party verification program transaction is carried out by the authority during the NFT transaction, and the program is an automatic verification program and has no human intervention at all. The source file is verified to be authentic by the program, payment is authentic, and programmed delivery of ownership is performed after verification is completed. The verification mode can adopt an encryption algorithm mechanism, and the trust is machine trust.
6. The source file and transaction record are stored in a distributed network, and multiple backups are stored to ensure that the source file and the transaction record are not lost
The source file and transaction records of the NFT are stored at the destination address or IPFS, preferably no less than 5, thereby ensuring that the likelihood of NFT digital asset loss is minimized at the most economical and reasonable cost.
An embodiment of the present invention further provides a computer device, and fig. 8 is a schematic diagram of a computer device in the embodiment of the present invention, where the computer device 800 includes a memory 810, a processor 820, and a computer program 830 stored in the memory 810 and capable of running on the processor 820, and when the processor 820 executes the computer program 830, the NFT-based digital asset management method described above is implemented.
The embodiment of the invention also provides a computer readable storage medium, wherein the computer readable storage medium stores a computer program, and the computer program realizes the digital asset management method based on the NFT when being executed by a processor.
Embodiments of the present invention also provide a computer program product comprising a computer program which, when executed by a processor, implements the NFT-based digital asset management method described above.
It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The foregoing description of the embodiments has been provided for the purpose of illustrating the general principles of the invention, and is not meant to limit the scope of the invention, but to limit the invention to the particular embodiments, and any modifications, equivalents, improvements, etc. that fall within the spirit and principles of the invention are intended to be included within the scope of the invention.
Claims (20)
1. A method of NFT-based digital asset management, comprising:
receiving a source file casting application for the digital asset initiated by a seller, wherein the current owner of the source file is the seller;
casting the source file into an NFT, forming a record file after casting is completed, and storing the record file on a target address, wherein the record file comprises basic information, file information and transaction information, the basic information is used for describing the basic information of the record file, the file information is used for describing the source file, the transaction information comprises a plurality of transaction records, and each transaction record is history transfer information of the source file;
receiving a transaction application initiated by a buyer aiming at the NFT, wherein the transaction application is initiated after the buyer sees the description information of a source file on a personal homepage of a seller of a target address;
calling a third party verification program to verify the source file and the transaction information; updating transaction information when the verification is correct; generating a new record file according to the file information and the updated transaction information;
keeping the source file not transferred on the target address, sending the encrypted new record file to the buyer, and transferring the transaction money to the seller;
The transaction record comprises a transaction record head, a transaction record tail, account information of a seller, account information of a buyer, anonymity of the buyer, transaction price, source file hash, URL and transaction timestamp; the transaction record head and the transaction record tail are hash values, the transaction record tail of the last transaction record is the transaction record head of the current transaction record, and the transaction record tail of the current transaction record is calculated according to the current transaction record; the URL is a temporary address where the seller stores the digital asset; source file hash the hash of the source file for the transaction;
calling a third party verification program to verify the source file and the transaction information; updating transaction information upon verification of an error, including: calling a third party verification program to read a source file through a URL, and calculating the hash of the source file; performing first verification on the calculated hash of the source file and the hash of the source file recorded by the last transaction; if the first verification is correct, calculating the hash of the last transaction record; performing a second verification on the calculated hash of the last transaction record and the transaction record tail of the last transaction record; if the second verification is correct, a new transaction record is generated and added into the transaction information; closing the URL.
2. The method of claim 1, wherein the basic information includes a length of a record file, a record file description, a file number, a check code, account information of a current owner, a name of the current owner, whether anonymous;
the file number is used to describe the number of the current source file for which the file is recorded.
3. The method of claim 2, wherein the file information further comprises a digital fingerprint for any of a scene of similarity check, copyright determination, auditing, identification, digital rights management of the source file.
4. The method of claim 1, wherein the file information includes a file record of a source file for casting and a plurality of file records of source files modified for the source file for casting;
each transaction is recorded as all of the history transfer information for each source file.
5. The method of claim 4, wherein each file record includes a source file index, a source file length, a source file hash, and whether each source file is valid;
the source file hash is obtained by carrying out hash calculation on the source file;
whether the corresponding source file can be transacted or not is effectively indicated, and only one file record in all file records corresponds to the source file and can be transacted.
6. The method of claim 1, wherein the account information includes an account name;
the seller has at least one piece of account information;
updating account information of the seller in the file information when receiving a demand of the seller to update the account information in the file information;
generating a new transaction record and adding the new transaction record to the transaction information;
and generating a new record file according to the file information and the updated transaction information.
7. The method as recited in claim 1, further comprising:
when a seller initiates updating of a preset field in transaction information, a new transaction record is generated and added into the transaction information, wherein the preset field is account information of a buyer, a source file hash or a URL;
and generating a new record file according to the file information and the updated transaction information.
8. The method of claim 1, wherein the transaction information is recorded in a chain billing manner.
9. The method of claim 1, wherein generating a new record file based on the file information and the updated transaction information comprises:
generating basic information according to information of a buyer, wherein the information of the buyer comprises account information of the buyer and the name of the buyer;
And generating a new record file according to the basic information, the file information and the updated transaction information.
10. The method of claim 1, wherein transmitting the encrypted new record file to the buyer comprises:
calling a third-party program to obtain a current secret key, wherein the current secret key is a PGP public key;
and encrypting the new record file by using the current key, and sending the encrypted new record file to the buyer, wherein the current key is invalid after use.
11. The method as recited in claim 1, further comprising:
and receiving an identity management command of the seller on a personal homepage of the target address, and managing account information of the seller.
12. The method as recited in claim 1, further comprising:
on the personal home page of the target address, a communication is made between the seller and the associated person regarding the digital asset.
13. The method as recited in claim 1, further comprising:
and calling the display equipment to interact the seller and the digital asset on the target address.
14. The method as recited in claim 1, further comprising:
after receiving the transaction facilitation instructions, a recommendation, bid, or auction is conducted on the digital asset.
15. The method as recited in claim 1, further comprising:
after receiving the query command at the target address, the NFT is queried based on the keywords in the query command.
16. The method as recited in claim 1, further comprising:
generating a plurality of backups from a source file, generating a backup file under a storage directory of the source file, wherein all storage addresses of the backups are described in the backup file, and respectively storing the backups on the storage addresses, and the storage addresses are target addresses or addresses of a distributed storage system.
17. The method as recited in claim 16, further comprising:
after receiving the backup destroying instruction, the backup aimed at in the destroying instruction is updated;
and after receiving the backup update instruction, regenerating a backup, adding the address of the backup to the backup file, and storing the backup to the address of the backup.
18. An NFT-based digital asset management device, comprising:
the system comprises a casting application receiving module, a source file casting application receiving module and a processing module, wherein the casting application receiving module is used for receiving a source file casting application for digital assets initiated by a seller, and the current owner of the source file is the seller;
The system comprises a casting module, a storage module and a storage module, wherein the casting module is used for casting the source file into an NFT, forming a record file after casting is completed and storing the record file on a target address, the record file comprises basic information, file information and transaction information, the basic information is used for describing the basic information of the record file, the file information is used for describing the source file, the transaction information comprises a plurality of transaction records, and each transaction record is history transfer information of the source file;
a transaction application receiving module, configured to receive a transaction application initiated by a buyer for the NFT, where the transaction application is initiated after the buyer sees description information of a source file on a personal homepage of a seller at a target address;
the verification module is used for calling a third party verification program to verify the source file and the transaction information; updating transaction information when the verification is correct; generating a new record file according to the file information and the updated transaction information;
the transaction module is used for keeping the source file not transferred on the target address, sending the encrypted new record file to the buyer and transferring the transaction money to the seller;
the transaction record comprises a transaction record head, a transaction record tail, account information of a seller, account information of a buyer, anonymity of the buyer, transaction price, source file hash, URL and transaction timestamp; the transaction record head and the transaction record tail are hash values, the transaction record tail of the last transaction record is the transaction record head of the current transaction record, and the transaction record tail of the current transaction record is calculated according to the current transaction record; the URL is a temporary address where the seller stores the digital asset; source file hash the hash of the source file for the transaction;
Calling a third party verification program to verify the source file and the transaction information; updating transaction information upon verification of an error, including: calling a third party verification program to read a source file through a URL, and calculating the hash of the source file; performing first verification on the calculated hash of the source file and the hash of the source file recorded by the last transaction; if the first verification is correct, calculating the hash of the last transaction record; performing a second verification on the calculated hash of the last transaction record and the transaction record tail of the last transaction record; if the second verification is correct, a new transaction record is generated and added into the transaction information; closing the URL.
19. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method of any of claims 1 to 17 when executing the computer program.
20. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program which, when executed by a processor, implements the method of any of claims 1 to 17.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310572368.4A CN116308325B (en) | 2023-05-19 | 2023-05-19 | Digital asset management method and device based on NFT |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310572368.4A CN116308325B (en) | 2023-05-19 | 2023-05-19 | Digital asset management method and device based on NFT |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116308325A CN116308325A (en) | 2023-06-23 |
| CN116308325B true CN116308325B (en) | 2023-08-22 |
Family
ID=86785315
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310572368.4A Active CN116308325B (en) | 2023-05-19 | 2023-05-19 | Digital asset management method and device based on NFT |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116308325B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116525077B (en) * | 2023-06-29 | 2023-09-08 | 安翰科技(武汉)股份有限公司 | Processing method and system for artificial intelligent medical instrument test data |
| CN117217748B (en) * | 2023-09-14 | 2024-03-29 | 湖南如艺文化发展有限公司 | Digital cultural artistic ecological platform |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112634052A (en) * | 2021-01-07 | 2021-04-09 | 东元(北京)数字科技有限公司 | Asset transaction method based on block chain technology |
| GB202107343D0 (en) * | 2021-05-23 | 2021-07-07 | Elmon Jacob | A smart contract based blockchain application using non-fungible token for authorized asset sharing |
| CN114567640A (en) * | 2022-03-09 | 2022-05-31 | 杭州电子科技大学 | NFT (network File transfer) authority confirming and circulating method with privacy protection and supervision functions |
| CN114820184A (en) * | 2022-03-14 | 2022-07-29 | 蚂蚁区块链科技(上海)有限公司 | Non-homogeneous evidence-based commodity transaction system and equipment |
| CN114998013A (en) * | 2022-06-01 | 2022-09-02 | 湖南天河文链科技有限公司 | NFT-based digital collection transaction method and system |
| CN115115811A (en) * | 2022-07-07 | 2022-09-27 | 重庆金窝窝网络科技有限公司 | NFT commodity interaction method based on AR technology |
| CN115641133A (en) * | 2022-10-19 | 2023-01-24 | 咪咕文化科技有限公司 | Real-name NFT transaction method, device, equipment and storage medium |
-
2023
- 2023-05-19 CN CN202310572368.4A patent/CN116308325B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112634052A (en) * | 2021-01-07 | 2021-04-09 | 东元(北京)数字科技有限公司 | Asset transaction method based on block chain technology |
| GB202107343D0 (en) * | 2021-05-23 | 2021-07-07 | Elmon Jacob | A smart contract based blockchain application using non-fungible token for authorized asset sharing |
| CN114567640A (en) * | 2022-03-09 | 2022-05-31 | 杭州电子科技大学 | NFT (network File transfer) authority confirming and circulating method with privacy protection and supervision functions |
| CN114820184A (en) * | 2022-03-14 | 2022-07-29 | 蚂蚁区块链科技(上海)有限公司 | Non-homogeneous evidence-based commodity transaction system and equipment |
| CN114998013A (en) * | 2022-06-01 | 2022-09-02 | 湖南天河文链科技有限公司 | NFT-based digital collection transaction method and system |
| CN115115811A (en) * | 2022-07-07 | 2022-09-27 | 重庆金窝窝网络科技有限公司 | NFT commodity interaction method based on AR technology |
| CN115641133A (en) * | 2022-10-19 | 2023-01-24 | 咪咕文化科技有限公司 | Real-name NFT transaction method, device, equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116308325A (en) | 2023-06-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108734576B (en) | Block chain-based educational resource sharing method and system | |
| US11909879B2 (en) | Systems and methods for generating customized non-fungible tokens | |
| CN110110500B (en) | Decentralized image copyright protection system and method with immediate infringement detection function | |
| CN116308325B (en) | Digital asset management method and device based on NFT | |
| McConaghy et al. | Visibility and digital art: Blockchain as an ownership layer on the Internet | |
| EP3635597B1 (en) | Systems and methods of content transaction consensus | |
| US20200143015A1 (en) | Decentralized digital content distribution system and process using block chains | |
| US20190114396A1 (en) | Methods and apparatus for sharing, transferring and removing previously owned digital media | |
| US20190073454A1 (en) | Methods and apparatus for sharing, transferring and removing previously owned digital media | |
| US8571992B2 (en) | Methods and apparatus for title structure and management | |
| US20050273805A1 (en) | Methods and apparatus for a title transaction network | |
| KR102447320B1 (en) | System for providing non-fungible token based copyright property trading platform | |
| US11244032B1 (en) | System and method for the creation and the exchange of a copyright for each AI-generated multimedia via a blockchain | |
| KR20210037274A (en) | Apparatus and method for managing contents | |
| GB2607026A (en) | A smart contract based blockchain application using non-fungible token for authorized asset sharing | |
| US20050289081A1 (en) | Computing system and method for secure sales transactions on a network | |
| US20050289011A1 (en) | Method and system for purchasing copyrighted digital data from independent sales parties | |
| US20150117641A1 (en) | Protection method and system for distributing digital files whether new, second-hand, for rental, exchange or transfer | |
| CN112418851A (en) | Digital copyright registration, transaction and protection method and system | |
| WO2022270551A1 (en) | Nft information management system, and nft information management program | |
| JP2020052990A (en) | Ownership management method of virtual object and related interactive platform | |
| Lavrova et al. | Nft performance and security review | |
| US8965808B1 (en) | Print to e-book conversion | |
| US20230368186A1 (en) | Process for Creation storage retrieval of immutable NFT Non-fungible token based electronic book publishing on a decentralized proof ofstake blockchain | |
| TW202319978A (en) | Native building and minting of non-fungible tokens on a blockchain |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20231007 Address after: 7010-7015, 7th Floor, Building B, No. 2 Xinfeng Street, Deshengmenwai, Xicheng District, Beijing, 100000 (Desheng Park) Patentee after: Beijing Yurui Investment Management Co.,Ltd. Patentee after: Wang Yuxiao Address before: Room B1001, 10 / F, block B, Tiancheng science and technology building, No. 2, Xinfeng street, Deshengmenwai, Xicheng District, Beijing 100088 Patentee before: Beijing Wuli Technology Co.,Ltd. Patentee before: Wang Yuxiao |
|
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 40095806 Country of ref document: HK |