WO2022082360A1 - 数字资产转移*** - Google Patents

数字资产转移*** Download PDF

Info

Publication number
WO2022082360A1
WO2022082360A1 PCT/CN2020/121885 CN2020121885W WO2022082360A1 WO 2022082360 A1 WO2022082360 A1 WO 2022082360A1 CN 2020121885 W CN2020121885 W CN 2020121885W WO 2022082360 A1 WO2022082360 A1 WO 2022082360A1
Authority
WO
WIPO (PCT)
Prior art keywords
asset
digital
digital asset
blockchain
blockchain system
Prior art date
Application number
PCT/CN2020/121885
Other languages
English (en)
French (fr)
Inventor
鲜丹
郭玮
於雷
刘良辉
Original Assignee
威富通科技有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 威富通科技有限公司 filed Critical 威富通科技有限公司
Priority to PCT/CN2020/121885 priority Critical patent/WO2022082360A1/zh
Priority to CN202080002607.7A priority patent/CN112513908A/zh
Publication of WO2022082360A1 publication Critical patent/WO2022082360A1/zh

Links

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/38—Payment protocols; Details thereof
    • G06Q20/389—Keeping log of transactions for guaranteeing non-repudiation of a transaction
    • 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
    • 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
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange

Definitions

  • the present application relates to the field of computer technology, in particular to a digital asset transfer system.
  • Digital assets include digital gift cards, stored value cards, membership cards, coupons, points, etc.
  • the transfer of digital assets mainly adopts the method of offline file transfer. Specifically, when the digital asset belonging to A is to be transferred to B, A puts the asset number and asset password of the digital asset to which it belongs into a file, encrypts the file, and then sends the file to B. After obtaining the file, B decrypts the file, obtains the asset number and asset password of the digital asset in the file, and also obtains the ownership of the digital asset.
  • This application provides a digital asset transfer system that helps to clearly confirm the ownership of digital assets.
  • a first aspect provides a digital asset transfer system
  • the digital asset transfer system includes a business system and a blockchain system
  • the business system is used to generate digital assets
  • the blockchain system is used to set all The attribute information of the digital asset, the digital asset and the attribute information of the digital asset are stored in the blockchain configured by the blockchain system, and the attribute information of the digital asset includes the asset attribution and asset transfer time;
  • the business system is used to transfer the digital asset;
  • the blockchain system is used to update the attribute information of the digital asset according to the transfer situation of the digital asset, and store the updated attribute information in the the blockchain.
  • a computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being executed by the processor When realizing the operations performed by the above-mentioned digital asset transfer system.
  • a computer-readable storage medium where a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, the operations performed by the above-mentioned digital asset transfer system are implemented.
  • a computer program product comprising instructions which, when run on a computer, cause the computer to perform the operations performed by the digital asset transfer system described above.
  • the digital asset transfer system includes a business system and a blockchain system.
  • the blockchain system can store the digital assets and their attribute information generated by the business system to the blockchain configured by the blockchain system.
  • the blockchain system can continuously update the attribute information of the digital asset and store it in the blockchain according to the transfer situation of the digital asset. Since the attribute information of the digital asset includes asset ownership and asset transfer time, the transfer process of the digital asset is recorded in the blockchain configured by the blockchain system. Due to the immutability of the blockchain, the ownership of the digital asset can be clearly confirmed according to the transfer process of the digital asset recorded in the blockchain.
  • FIG. 1 is a schematic structural diagram of a blockchain system provided by an embodiment of the present application.
  • FIG. 2 is a schematic diagram of a blockchain provided by an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a process for generating a block provided by an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of a digital asset transfer system provided by an embodiment of the present application.
  • Fig. 5 is an operation flow chart of a digital asset transfer system provided by an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of another digital asset transfer system provided by an embodiment of the present application.
  • FIG. 7 is a schematic diagram of interaction between a business system and a blockchain system provided by an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a computer device provided by an embodiment of the present application.
  • FIG. 1 is a schematic structural diagram of a blockchain system provided by an embodiment of the present application.
  • the blockchain system 100 refers to a system for sharing data between nodes.
  • the blockchain system 100 may include multiple nodes 101 , and multiple nodes 101 may refer to the system in the blockchain system 100 . each client.
  • Each node 101 can receive input information during normal work, and maintain shared data within the blockchain system 100 based on the received input information.
  • an information connection may exist between each node 101 in the blockchain system 100, and information transmission may be performed between the nodes 101 through the information connection.
  • any node 101 in the blockchain system 100 receives input information
  • other nodes 101 in the blockchain system 100 obtain the input information according to the consensus algorithm, and store the input information as data in the shared data , so that the data stored on all nodes 101 in the blockchain system 100 are consistent.
  • Each node 101 in the blockchain system 100 has a corresponding node identifier, and each node 101 in the blockchain system 100 can store the node identifiers of other nodes 101 in the blockchain system 100, In order to subsequently broadcast the generated block to other nodes 101 in the blockchain system 100 according to the node identifiers of other nodes 101 .
  • Each node 101 may maintain a node identification list, and store the node name and the node identification in the node identification list correspondingly.
  • the node identification can be IP (Internet Protocol, Internet Protocol) address and any other information that can be used to identify the node 101 .
  • Each node 101 in the blockchain system 100 stores an identical blockchain.
  • the blockchain consists of multiple blocks.
  • the founding block includes a block header and a block body.
  • the block header stores the input information feature value, version number, timestamp and difficulty value.
  • the block body stores Input information;
  • the next block of the genesis block takes the genesis block as the parent block, the next block also includes the block header and the block body, and the block header stores the input information characteristic value of the current block, the parent block's
  • the block header feature value, version number, timestamp, and difficulty value, and so on make the block data stored in each block in the blockchain associated with the block data stored in the parent block, ensuring that Security of the information entered in the block.
  • the node 101 where the blockchain is located receives the input information, it verifies the input information, and after the verification is completed, the input information is stored in the memory pool , and update the hash tree used to record the input information; after that, update the update timestamp to the time when the input information was received, and try different random numbers, and perform the eigenvalue calculation multiple times, so that the calculated eigenvalues can be Satisfy the following formula:
  • SHA256 is the eigenvalue algorithm used to calculate the eigenvalue
  • version (version number) is the version information of the relevant block protocol in the blockchain
  • prev_hash is the block header eigenvalue of the parent block of the current block
  • merkle_root is the input information
  • the node 101 where the blockchain is located sends the newly generated blocks to the other nodes 101 in the blockchain system 100 where it is located according to the node identifiers of the other nodes 101 in the blockchain system 100, and the other nodes 101 pair with each other.
  • the newly generated block is verified and added to the blockchain where it is stored after verification is complete.
  • the blockchain system 100 has computer technologies such as distributed data storage, point-to-point transmission, consensus mechanism, and encryption algorithm.
  • the blockchain system 100 is a distributed shared ledger and database, which has the characteristics of decentralization, non-tampering, full traces, traceability, collective maintenance, openness and transparency, etc. These features ensure the shared openness, authenticity, integrity, security and reliability of the blockchain.
  • FIG. 4 is a schematic structural diagram of a digital asset transfer system provided by an embodiment of the present application.
  • the digital asset transfer system may include a business system 401 and a blockchain system 402 .
  • the business system 401 can realize the generation and transfer of digital assets, and the transfer of digital assets can include distribution, sale, and the like.
  • the blockchain system 402 may be the blockchain system 100 described in the embodiments of FIGS. 1-3 above.
  • Step 501 The business system 401 generates digital assets.
  • the business system 401 can generate digital assets belonging to the business system 401, that is, the business system 401 owns the ownership of the digital assets.
  • the digital assets may include digital gift cards, stored-value cards, membership cards, coupons, points, etc., which are not uniquely limited in this embodiment of the present application.
  • the digital asset may consist of data such as asset number, asset value, and asset validity period, and the digital asset may not contain an asset password.
  • Step 502 the blockchain system 402 sets the attribute information of the digital asset, and stores the digital asset and the attribute information of the digital asset in the blockchain configured by the blockchain system 402 .
  • the attribute information of the digital asset may include the asset ownership and asset transfer time of the digital asset, and further, may also include the asset status of the digital asset, and the like.
  • the blockchain system 402 can set the initial attribute information of the digital asset, specifically the initial asset ownership and asset transfer time of the digital asset, and further, can also set the initial digital asset. Asset status.
  • the blockchain system 402 when the blockchain system 402 stores the digital asset and the attribute information of the digital asset in the blockchain configured by the blockchain system 402, the blockchain system 402 can store the digital asset and the attribute information of the digital asset based on the digital asset and the attribute information of the digital asset. Generate a block and add the block to the configured blockchain.
  • the blockchain system 402 can upload the digital asset and the attribute information of the digital asset on the chain according to the smart contract, that is, generate a block storing the digital asset and the attribute information of the digital asset according to the smart contract, and store the block. added to the shared blockchain. In this way, the digital asset and the attribute information of the digital asset cannot be tampered with.
  • Step 503 The business system 401 transfers the digital asset.
  • the digital asset transaction proceeds, the digital asset will be continuously transferred.
  • the business system 401 can distribute, sell, etc. the digital asset to change the ownership of the digital asset.
  • Step 504 The blockchain system 402 updates the attribute information of the digital asset according to the transfer situation of the digital asset, and stores the updated attribute information in the blockchain.
  • the blockchain system 402 can update the attribute information of the digital asset and store it in the blockchain.
  • the blockchain system 402 when the blockchain system 402 stores the updated attribute information in the blockchain, the blockchain system 402 can generate a block according to the updated attribute information, and add the block to the configured blockchain .
  • the blockchain system 402 can upload the updated attribute information on the chain according to the smart contract, that is, generate a block storing the updated attribute information according to the smart contract, and add the block to the shared blockchain. In this way, the updated attribute information cannot be tampered with.
  • the blockchain system 402 stores the relevant information (including but not limited to attribute information) of the digital asset to the blockchain, the stored information can be associated with the digital asset identifier, so that the subsequent information can be The digital asset identifier obtains the relevant information of the digital asset from the blockchain.
  • the digital asset identifier is used to uniquely identify the digital asset, for example, the digital asset identifier may be the asset number of the digital asset, etc., which is not uniquely limited in this embodiment of the application.
  • the digital asset transfer system includes a business system 401 and a blockchain system 402 .
  • the blockchain system 402 can store the digital assets generated by the business system 401 and their attribute information in the blockchain configured by the blockchain system 402 .
  • the blockchain system 402 can continuously update the attribute information of the digital asset and store it in the blockchain according to the transfer situation of the digital asset. Since the attribute information of the digital asset includes asset ownership and asset transfer time, the transfer process of the digital asset is recorded in the blockchain configured by the blockchain system 402 . Due to the immutability of the blockchain, the ownership of the digital asset can be clearly confirmed according to the transfer process of the digital asset recorded in the blockchain.
  • the business system 401 may be a server cluster composed of multiple servers. Referring to FIG. 6 , the business system 401 may include an asset issuance server 4011 , an asset distribution server 4012 and a distribution server 4013 .
  • the interaction process between the business system 401 and the blockchain system 402 may be as shown in FIG. 7 .
  • the interaction process between the asset issuing server 4011 and the blockchain system 402 may include the following steps:
  • Step 701 The asset issuing server 4011 generates a digital asset, and calls the smart contract asset initialization interface to send the first interface message carrying the digital asset to the blockchain system 402.
  • the asset issuing server 4011 is the initial owner of the digital asset.
  • the first interface message can be JSON (JavaScript Object Notation, JavaScript Object Notation) format message.
  • JSON JavaScript Object Notation, JavaScript Object Notation
  • the first interface packet may also be a packet in other formats, which is not uniquely limited in this embodiment of the present application.
  • the asset issuing server 4011 can also connect to the blockchain system 402, and then call the smart contract asset initialization interface to send the first interface message to the blockchain system 402.
  • the asset issuance server 4011 can send a digital certificate to the blockchain system 402; the blockchain system 402 can check the validity of the digital certificate when receiving the digital certificate sent by the asset issuance server 4011, and the digital certificate In the case of passing the legality check, a verification success notification message is returned to the asset issuance server 4011; the asset issuance server 4011 can call the smart contract asset initialization interface when receiving the verification success notification message returned by the blockchain system 402 to Send the first interface message to the blockchain system 402 .
  • the digital certificate (Digital Certificate) may be issued and approved by the blockchain system 402 , that is, it may be obtained from the blockchain system 402 .
  • the blockchain system 402 can perform a hash operation on the public key of the asset issuing server 4011 according to a hash algorithm to obtain a digest of the public key of the asset issuing server 4011, and then use its own private key to pair the assets according to the encryption algorithm.
  • the digest of the public key of the issuing server 4011 is encrypted to obtain encrypted information.
  • the blockchain system 402 can issue the hash algorithm, the encryption algorithm, the public key of the asset issuance server 4011, and the encrypted information to the asset issuance server 4011 as a digital certificate of the asset issuance server 4011.
  • the operation of verifying the validity of the digital certificate may be: the blockchain system 402 receives the digital certificate sent by the asset issuance server 4011.
  • the blockchain system 402 receives the digital certificate sent by the asset issuance server 4011.
  • the encryption algorithm contained in the digital certificate use your own public key to decrypt the encrypted information contained in the digital certificate to obtain the first information; according to the hash algorithm contained in the digital certificate, the digital certificate
  • the public key of the asset issuance server 4011 contained in the Hash operation is performed to obtain the second information; if the first information is the same as the second information, it can be determined that the validity of the digital certificate has passed; If the information is different, it can be determined that the validity verification of the digital certificate fails.
  • the blockchain system 402 can determine that the identity of the asset issuing server 4011 is legal when the legality verification of the digital certificate is passed, and can return a verification success notification message to the asset issuing server 4011 . After the asset issuing server 4011 receives the verification success notification message, it is successfully connected to the blockchain system 402 .
  • the blockchain system 402 can determine that the identity of the asset issuing server 4011 is illegal, and can return a verification failure notification message to the asset issuing server 4011; the asset issuing server 4011 When receiving the verification failure notification message returned by the blockchain system 402, it is confirmed that the connection with the blockchain system 402 has failed. At this time, the asset issuing server 4011 can directly end the operation or try to reconnect to the blockchain system 402.
  • Step 702 When receiving the first interface message, the blockchain system 402 sets the attribute information of the digital asset, and stores the digital asset and the attribute information of the digital asset in the blockchain.
  • the blockchain system 402 When the blockchain system 402 receives the first interface message, it can first verify the first interface message; if the first interface message is successfully verified, then set the attribute information of the digital asset, and set the attribute information of the digital asset.
  • the digital asset and the attribute information of the digital asset are stored in the blockchain; in the case that the first interface message verification fails, an error reminder message is returned to the asset issuing server 4011, and the operation is ended, and the asset issuing server 4011 receives the
  • the smart contract asset initialization interface can be called again to send the first interface message to the blockchain system 402 .
  • the operation performed by the blockchain system 402 for verifying the first interface message is similar to the operation performed by a device in the related art for verifying a message, which is not described in detail in this embodiment of the present application.
  • the asset attribution of the digital asset can be set as the asset distribution server identifier
  • the asset transfer time of the digital asset can be set as the receiving time of the first interface message
  • the The asset status of a digital asset is pending sale.
  • the asset distribution server identifier is used to uniquely identify the asset distribution server 4012 .
  • the asset distribution server identifier may be the UUID (Universally Unique Identifier, Universal Unique Identifier), MAC (Media Access Control, Media Access Control) address, IP address, or factory serial number of the asset distribution server 4012, and the embodiment of the present application There is no unique limitation on this.
  • the asset distribution server 4011 uses the asset distribution server 4012 to sell the digital assets to which the asset distribution server 4011 belongs, so the blockchain system 402 can directly set the asset attribution of the digital assets generated by the asset distribution server 4011 to asset distribution Server ID.
  • the asset distribution server identification may be pre-stored in the blockchain system 402 .
  • the blockchain system 402 can also send the digital asset to the asset distribution server 4012 according to the asset distribution server identifier, so that the asset distribution server 4012 can follow up.
  • the digital asset can be sold.
  • the operation of the blockchain system 402 sending the digital asset to the asset distribution server 4012 according to the asset distribution server identifier is similar to the operation of one device sending information to the other device according to the identifier of the other device in the related art.
  • the example does not elaborate on this.
  • the blockchain system 402 can call the distribution interface according to the identifier of the asset distribution server to send the message carrying the digital asset to the asset distribution server 4012 .
  • smart contracts are based on the trusted and immutable data of the blockchain, and can automatically execute some pre-defined rules and terms.
  • smart contracts are stored in blocks of the blockchain in the form of on-chain code.
  • the server can call smart contracts through the contract interface to perform specific operations.
  • the contract logic can be executed, so that the asset issuing server 4011 sends the first interface message to the blockchain system 402, the blockchain system 402 sets the attribute information of the digital asset, The blockchain system 402 stores the digital assets and their attribute information to the blockchain for this series of operations.
  • the interaction process between the asset distribution server 4012 and the blockchain system 402 may include the following steps:
  • Step 703 When the asset distribution server 4012 detects the distribution operation for the digital asset, it calls the smart contract asset distribution interface to send the second interface message carrying the digital asset and the distribution server identifier to the blockchain system 402.
  • the asset distribution server 4012 is used to distribute digital assets generated by the asset distribution server 4011 .
  • the distribution operation for the digital asset refers to an operation of transferring the digital asset to the distribution server 4013 .
  • the asset distribution server 4012 detects the distribution operation, it can obtain the distribution server identifier for uniquely identifying the distribution server 4013 .
  • the distribution server identifier may be the UUID, MAC address, IP address, or factory serial number of the distribution server 4013, which is not uniquely limited in this embodiment of the present application.
  • the second interface message may be a message in JSON format.
  • the second interface packet may also be a packet in other formats, which is not uniquely limited in this embodiment of the present application.
  • the asset distribution server 4012 can also connect to the blockchain system 402, and then call the smart contract asset distribution interface to send the second interface message to the blockchain system 402.
  • the asset distribution server 4012 can send the digital certificate to the blockchain system 402; the blockchain system 402 can check the validity of the digital certificate when receiving the digital certificate sent by the asset distribution server 4012, and in the digital certificate In the case of passing the legality verification, a verification success notification message is returned to the asset distribution server 4012; the asset distribution server 4012 can call the smart contract asset distribution interface when receiving the verification success notification message returned by the blockchain system 402 to Send the second interface message to the blockchain system 402 .
  • the blockchain system 402 can perform a hash operation on the public key of the asset distribution server 4012 according to a hash algorithm to obtain a digest of the public key of the asset distribution server 4012, and then use its own private key to pair the assets according to the encryption algorithm.
  • the digest of the public key of the distribution server 4012 is encrypted to obtain encrypted information.
  • the blockchain system 402 can issue the hash algorithm, the encryption algorithm, the public key of the asset distribution server 4012, and the encrypted information to the asset distribution server 4012 as a digital certificate of the asset distribution server 4012.
  • the operation of the blockchain system 402 to verify the legality of the digital certificate sent by the asset distribution server 4012 is similar to the operation of the blockchain system 402 to verify the legality of the digital certificate sent by the asset distribution server 4011. This is not repeated in the application embodiment.
  • the blockchain system 402 can determine that the identity of the asset distribution server 4012 is legal when the legality verification of the digital certificate is passed, and can return a verification success notification message to the asset distribution server 4012 . After the asset distribution server 4012 receives the verification success notification message, it is successfully connected to the blockchain system 402 .
  • the blockchain system 402 can determine that the identity of the asset distribution server 4012 is illegal, and can return a verification failure notification message to the asset distribution server 4012; the asset distribution server 4012 When the verification failure notification message returned by the blockchain system 402 is received, it is confirmed that the connection with the blockchain system 402 has failed, and the operation can be ended directly or the blockchain system 402 can be tried to be reconnected.
  • Step 704 When receiving the second interface message, the blockchain system 402 sends the digital asset to the distribution server 4013 according to the distribution server identifier, and updates the digital asset when receiving the first confirmation response returned by the distribution server 4013 The asset belonging to the distribution server identifier, update the asset transfer time of the digital asset to the reception time of the first confirmation response, and store the asset ownership and asset transfer time of the digital asset in the blockchain.
  • the blockchain system 402 When the blockchain system 402 receives the second interface message, it can first verify the second interface message; if the second interface message is successfully verified, it can then send the message to the distribution server 4013 according to the distribution server identifier. The digital asset; in the case that the verification of the second interface message fails, an error reminder message is returned to the asset distribution server 4012, and the operation is ended. When the asset distribution server 4012 receives the error reminder message, it can re-call the smart contract asset distribution interface to send the second interface message to the blockchain system 402 .
  • the operation performed by the blockchain system 402 to verify the second interface packet is similar to the operation performed by a certain device in the related art to verify a certain packet, which is not described in detail in this embodiment of the present application.
  • the operation of the blockchain system 402 sending the digital asset to the distribution server 4013 according to the identification of the distribution server is similar to the operation of one device sending information to the other device according to the identification of the other device in the related art. This is not explained in detail.
  • the blockchain system 402 can call the distribution interface according to the distribution server identifier to send the message carrying the digital asset to the distribution server 4013 .
  • the first confirmation response is used to confirm that the digital asset has been received.
  • the distribution server 4013 may return a first confirmation response to the blockchain system 402 after receiving the digital asset sent by the blockchain system 402 .
  • the blockchain system 402 can An error reminder message is sent to the asset distribution server 4012.
  • the asset distribution server 4012 receives the error reminder message, it can re-call the smart contract asset distribution interface to send the second interface message to the blockchain system 402.
  • the contract logic can be executed, so that the asset distribution server 4012 sends the second interface message to the blockchain system 402, and the blockchain system 402 sends the digital asset to the distribution server 4013. And when receiving the first confirmation response returned by the distribution server 4013, this series of operations of updating the attribute information of the digital asset and storing it in the blockchain.
  • the interaction process between the distribution server 4013 and the blockchain system 402 may include the following steps:
  • Step 705 When the distribution server 4013 detects the sale operation for the digital asset, it calls the smart contract asset sale interface to send the third interface message carrying the digital asset and the user ID to the blockchain system 402.
  • the distribution server 4013 is a secondary distribution organization of digital assets, and can purchase digital assets from the asset distribution server 4012 .
  • the selling operation for the digital asset refers to the operation of selling the digital asset to the user.
  • the distribution server 4013 detects the selling operation, it can obtain the user ID used to uniquely identify the user who purchased the digital asset.
  • the user identifier may be the user's phone number, instant messaging account, etc., which is not uniquely limited in this embodiment of the present application.
  • the third interface message may be a message in JSON format.
  • the third interface packet may also be a packet in other formats, which is not uniquely limited in this embodiment of the present application.
  • the distribution server 4013 can also connect to the blockchain system 402, and then call the smart contract asset sale interface to send the third interface message to the blockchain system 402.
  • the distribution server 4013 can send a digital certificate to the blockchain system 402; the blockchain system 402 can check the validity of the digital certificate when receiving the digital certificate sent by the distribution server 4013, and the validity of the digital certificate In the case of passing the verification, a verification success notification message is returned to the distribution server 4013; the distribution can call the smart contract asset sale interface to the blockchain system 402 when receiving the verification success notification message returned by the blockchain system 402. Send the third interface packet.
  • the blockchain system 402 can perform a hash operation on the public key of the distribution server 4013 according to the hash algorithm to obtain a digest of the public key of the distribution server 4013, and then use its own private key to the distribution server 4013 according to the encryption algorithm.
  • the digest of the public key is encrypted to obtain the encrypted information.
  • the blockchain system 402 can issue the hash algorithm, the encryption algorithm, the public key of the distribution server 4013, and the encrypted information to the distribution server 4013 as the digital certificate of the distribution server 4013.
  • the operation of the blockchain system 402 to verify the legality of the digital certificate sent by the distribution server 4013 is similar to the operation of the blockchain system 402 to verify the legality of the digital certificate sent by the asset issuing server 4011. This application This embodiment is not repeated here.
  • the blockchain system 402 can determine that the identity of the distribution server 4013 is legal when the validity verification of the digital certificate is passed, and can return a verification success notification message to the distribution server 4013 . After the distribution server 4013 receives the verification success notification message, it is successfully connected to the blockchain system 402 .
  • the blockchain system 402 can determine that the identity of the distribution server 4013 is illegal when the validity verification of the digital certificate fails, and can return a verification failure notification message to the distribution server 4013; the distribution server 4013 receives the When the verification failure notification message returned by the blockchain system 402 confirms that the connection with the blockchain system 402 has failed, the operation can be terminated directly or the blockchain system 402 can be tried to be reconnected.
  • Step 706 When receiving the third interface message, the blockchain system 402 updates the attribute information of the digital asset, and stores the updated attribute information in the blockchain.
  • the blockchain system 402 When the blockchain system 402 receives the third interface message, it can first verify the third interface message; if the third interface message is successfully verified, then update the attribute information of the digital asset; When the third interface packet verification fails, an error reminder message is returned to the distribution server 4013, and the operation is ended. When the distribution server 4013 receives the error reminder message, it can re-call the smart contract asset sale interface to send the blockchain system 402 Send a third interface packet.
  • the operation performed by the blockchain system 402 to verify the third interface packet is similar to the operation performed by a certain device in the related art to verify a certain packet, which is not described in detail in this embodiment of the present application.
  • step 706 may be: when the blockchain system 402 receives the third interface message, send an asset sale notification message carrying the digital asset and the user ID to the asset issuance server 4011; the asset issuance server 4011 When receiving the asset sale notification message, send the digital asset and the asset password of the digital asset to the user terminal according to the user ID, and return a second confirmation response to the blockchain system 402; the blockchain system 402 receives During the second confirmation response, update the asset of the digital asset to be the user ID, update the asset transfer time of the digital asset to be the receiving time of the second confirmation response, update the asset status of the digital asset to be sold, and update the digital asset to be sold.
  • the asset ownership, asset transfer time and asset status are stored in the blockchain.
  • the asset issuing server identifier is used to uniquely identify the asset issuing server 4011 .
  • the asset issuance server identifier may be the UUID, MAC address, IP address, or factory serial number of the asset issuance server 4011, which is not uniquely limited in this embodiment of the present application.
  • the operation of the blockchain system 402 to send the asset sale notification message carrying the digital asset and the user identification to the asset issuance server 4011 according to the identification of the asset issuance server is related to the operation of one device to the other device according to the identification of the other device.
  • the operation of sending information by the device is similar, which is not described in detail in this embodiment of the present application.
  • the blockchain system 402 can call the issuance interface according to the identification of the asset issuance server to send an asset sale notification message carrying the digital asset and the user identification to the asset issuance server 4011 .
  • the operation of the asset issuing server 4011 sending the digital asset and the asset password of the digital asset to the user terminal according to the user identification is similar to the operation of a device in the related art sending certain information to the user terminal according to the user identification. This is not described in detail in the application examples.
  • the asset issuing server 4011 may send the digital asset and the asset password of the digital asset to the user terminal by means of a short message or an application message push according to the user identification.
  • the second confirmation response is used to confirm that the digital asset and its asset password have been sent to the user.
  • the asset issuing server 4011 may return a second confirmation response to the blockchain system 402 after sending the digital asset and its asset password to the user terminal.
  • the blockchain system 402 can send an error reminder message to the distribution server 4013.
  • the distribution server 4013 receives the error reminder message, it can re-call the smart contract asset sale interface to send the third interface message to the blockchain system 402. .
  • the contract logic can be executed, so that the distribution server 4013 sends the third interface message to the blockchain system 402, and the blockchain system 402 instructs the asset issuing server 4011 to send the message to the user.
  • the asset issuing server 4011 can also perform digital asset write-off, which may specifically include the following steps (1)-step (4).
  • the asset issuance server 4011 calls the smart contract asset verification interface to send the fourth interface message carrying the digital asset identifier to the blockchain system 402 .
  • the fourth interface message may be a message in JSON format.
  • the fourth interface packet may also be a packet in other formats, which is not uniquely limited in this embodiment of the present application.
  • the blockchain system 402 queries the latest asset status of the digital asset according to the digital asset identifier.
  • the blockchain system 402 When the blockchain system 402 receives the fourth interface message, it can first verify the fourth interface message; in the case that the fourth interface message is successfully verified, the digital asset can be queried according to the digital asset identifier. If the verification of the fourth interface message fails, return an error reminder message to the asset issuing server 4011, and end the operation. When the asset issuing server 4011 receives the error reminder message, it can re-call the smart contract asset core The pin interface is used to send the fourth interface message to the blockchain system 402 .
  • the operation performed by the blockchain system 402 for verifying the fourth interface message is similar to the operation performed by a device in the related art for verifying a message, which is not described in detail in this embodiment of the present application.
  • the blockchain system 402 sets the asset status of the digital asset to be written off, and sets the asset write-off time of the digital asset to the time of the fourth interface message. After receiving the time, store the asset status and asset write-off time of the digital asset in the blockchain, and return a write-off notification message to the asset issuing server 4011.
  • the operation of the blockchain system 402 to store the asset status and asset write-off time of the digital asset to the blockchain is similar to the operation of the above-mentioned blockchain system 402 to store the attribute information of the digital asset to the blockchain. This is not repeated in the application embodiment.
  • the blockchain system 402 when the asset status of the digital asset is to be sold, the blockchain system 402 generates an alarm reminder message, and sends the alarm reminder message to the asset issuance server 4011.
  • the smart contract asset write-off interface can be called again to send the fourth interface message to the blockchain system 402 .
  • the asset issuing server 4011 Since the asset issuing server 4011 has sent the digital asset and its asset password to the user terminal, the digital asset has been sold to the user. If the asset status of the digital asset recorded in the blockchain system 402 is to be sold at this time, it means that there is a problem with the sale of the digital asset, so the blockchain system 402 can send an alarm reminder message to the asset issuance server 4011 to remind the asset issuance server. 4011 There is a problem with the sale of this digital asset.
  • the asset issuing server 4011 When receiving the write-off notification message, the asset issuing server 4011 writes off the digital asset.
  • the asset issuing server 4011 can write off the digital asset.
  • the contract logic can be executed, so that the asset issuing server 4011 sends the fourth interface message to the blockchain system 402, and the blockchain system 402 sets the digital asset write-off Information and a write-off notification message are returned to the asset issuing server 4011, and the asset issuing server 4011 writes off the digital asset in this series of operations.
  • the digital asset transfer system is based on the blockchain architecture, which can realize that all digital asset transfer processes are recorded in the blockchain, which cannot be tampered with, so as to provide a public credibility certificate of the digital asset transfer relationship, It can greatly improve the efficiency of digital asset ownership confirmation.
  • the transfer of digital asset ownership is safe and reliable.
  • each digital asset transfer link is realized by calling the smart contract transaction interface, and the transfer information is recorded in the blockchain, the digital asset transaction results cannot be tampered with or denied, and the entire digital asset transfer process can be traced.
  • neither the asset distribution server 4012 nor the distribution server 4013 can obtain the asset password, so that the risk of password leakage can be eliminated.
  • the asset password only exists in the asset issuance server 4011 during the digital asset distribution process. Only when the digital asset is sold to the user, the asset password is sent to the user through the asset issuance server 4011, thereby ensuring the security of the digital asset to the greatest extent. In this way, the security and exclusivity of digital assets during the transfer process can be guaranteed.
  • the asset issuing server 4011 , the asset distribution server 4012 , and the distribution server 4013 in the business system 401 can all query the relevant information of digital assets from the blockchain system 402 .
  • the business system 401 can call the smart contract asset query interface to send the fifth interface message carrying the digital asset identifier to the blockchain system 402 .
  • the blockchain system 402 obtains all the information of the digital asset from the blockchain according to the digital asset identifier, and sends all the information of the digital asset to the business system 401 .
  • the fifth interface message may be a message in JSON format.
  • the fifth interface packet may also be a packet in other formats, which is not uniquely limited in this embodiment of the present application.
  • the blockchain system 402 When the blockchain system 402 receives the fifth interface message, it can first verify the fifth interface message; in the case of successful verification of the fifth interface message, the block chain system 402 can download the message from the blockchain according to the digital asset identifier. Obtain all the information of the digital asset; in the case that the fifth interface message verification fails, return an error reminder message to the business system 401, and end the operation, when the business system 401 receives the error reminder message, it can re-call the intelligent The contract asset query interface is used to send the fifth interface message to the blockchain system 402 .
  • the operation performed by the blockchain system 402 to verify the fifth interface packet is similar to the operation performed by a certain device in the related art to verify a certain packet, which is not described in detail in this embodiment of the present application.
  • the contract logic can be executed, so that the business system 401 sends the fifth interface message to the blockchain system 402, and the blockchain system 402 queries all the information of the digital asset and returns This series of operations for the business system 401 .
  • the business system 401 may also include a notary server, and the notary server, as an optional participant, may be responsible for notarization in the digital asset transaction.
  • the notary server can be used for notarization of digital asset transfer from asset issuing server 4011 to asset distribution server 4012, and can also be used for notarization of digital asset transfer from asset distribution server 4012 to distribution server 4013, and can also be used for notarization of digital asset transfer from asset distribution server 4013 to distribution server 4013. Notarization of user's digital asset transfer.
  • FIG. 8 is a schematic structural diagram of a computer device according to an embodiment of the present application.
  • the above-mentioned digital asset transfer system can be realized by the computer device 8 .
  • the computer device 8 includes: a processor 80, a memory 81, and a computer program 82 stored in the memory 81 and running on the processor 80.
  • the processor 80 executes the computer program 82, the above-mentioned embodiments are implemented. Operations performed by the digital asset transfer system.
  • Computer device 8 may be a general purpose or special purpose computer device.
  • the computer device 8 may be a server cluster composed of multiple servers.
  • FIG. 8 is only an example of the computer device 8, and does not constitute a limitation on the computer device 8. It may include more or less components than the one shown, or combine some components, or different components , for example, it may also include input and output devices, network access devices, and so on.
  • the processor 80 may be a central processing unit (Central Processing Unit, CPU), the processor 80 can also be other general-purpose processors, digital signal processors (Digital Signal Processor, DSP), application-specific integrated circuits (Application Specific Integrated Circuit, ASIC), off-the-shelf Programmable Gate Array (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • a general-purpose processor may be a microprocessor or it may be any conventional processor.
  • the memory 81 may in some embodiments be an internal storage unit of the computer device 8 , such as a hard disk or memory of the computer device 8 .
  • the memory 81 may also be an external storage device of the computer device 8 in other embodiments, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) equipped on the computer device 8 card, Flash Card, etc.
  • the memory 81 may also include both an internal storage unit of the computer device 8 and an external storage device.
  • the memory 81 is used to store an operating system, an application program, a boot loader (BootLoader), data, and other programs, such as program codes of computer programs, and the like.
  • the memory 81 can also be used to temporarily store data that has been output or is to be output.
  • a computer-readable storage medium is also provided, and a computer program is stored in the storage medium.
  • the computer program is executed by the processor, the operations performed by the digital asset transfer system in the above-mentioned embodiments are implemented.
  • the computer-readable storage medium may be a ROM (Read-Only Memory, read-only memory), RAM (Random Access Memory, random access memory), CD-ROM (Compact Disc) Read-Only Memory), magnetic tapes, floppy disks, and optical data storage devices, etc.
  • the computer-readable storage medium mentioned in this application may be a non-volatile storage medium, in other words, may be a non-transitory storage medium.
  • a computer program product comprising instructions that, when executed on a computer, cause the computer to perform the operations performed by the digital asset transfer system of the above-described embodiments.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • Finance (AREA)
  • Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Technology Law (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

一种数字资产转移***，属于计算机技术领域。数字资产转移***包括业务***和区块链***；业务***，用于生成数字资产；区块链***，用于设置所述数字资产的属性信息，将所述数字资产和所述数字资产的属性信息存储到区块链***配置的区块链，所述数字资产的属性信息包括资产归属和资产转移时间；业务***，用于对所述数字资产进行转移；区块链***，用于根据所述数字资产的转移情况，更新所述数字资产的属性信息，将更新后的属性信息存储到所述区块链。该***可以将数字资产的转移过程记录到区块链***配置的区块链。由于区块链的不可篡改性，所以根据区块链中记录的该数字资产的转移过程可以明确确认该数字资产的所有权。

Description

数字资产转移*** 技术领域
本申请涉及计算机技术领域，特别涉及一种数字资产转移***。
 背景技术
随着数字货币的兴起，大量的数字资产交易出现。数字资产包括数字化的礼品卡、储值卡、会员卡、优惠券、积分等。
目前，数字资产转移主要采用线下文件转移的方式。具体地，当要将属于A的数字资产转移到B时，A将自身所属的数字资产的资产编号和资产密码放入一个文件，并对该文件进行加密，然后将该文件发送给B。B获取到该文件后，对该文件进行解密，得到该文件中的数字资产的资产编号和资产密码，也就得到了该数字资产的所有权。
然而，在上述数字资产转移过程中，A将数字资产转移给B后，A仍旧拥有该数字资产的资产编号和资产密码。由于该数字资产是线下转移，所以转移关系难以确认，从而导致该数字资产的归属难以确定。
 技术问题
本申请提供了一种数字资产转移***，有助于明确确认数字资产的所有权。
 技术解决方案
第一方面，提供了一种数字资产转移***，所述数字资产转移***包括业务***和区块链***；所述业务***，用于生成数字资产；所述区块链***，用于设置所述数字资产的属性信息，将所述数字资产和所述数字资产的属性信息存储到所述区块链***配置的区块链，所述数字资产的属性信息包括资产归属和资产转移时间；所述业务***，用于对所述数字资产进行转移；所述区块链***，用于根据所述数字资产的转移情况，更新所述数字资产的属性信息，将更新后的属性信息存储到所述区块链。
第二方面，提供了一种计算机设备，所述计算机设备包括存储器、处理器以及存储在所述存储器中并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现上述数字资产转移***执行的操作。
第三方面，提供了一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序被处理器执行时实现上述数字资产转移***执行的操作。
第四方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述数字资产转移***执行的操作。
 有益效果
在本申请中，数字资产转移***包括业务***和区块链***。区块链***可以将业务***生成的数字资产和其属性信息存储到区块链***配置的区块链。并且，在业务***对该数字资产进行转移的过程中，区块链***可以根据该数字资产的转移情况，不断更新该数字资产的属性信息并将其存储到区块链。由于该数字资产的属性信息包括资产归属和资产转移时间，因而该数字资产的转移过程都被记录到区块链***配置的区块链。由于区块链的不可篡改性，所以根据区块链中记录的该数字资产的转移过程可以明确确认该数字资产的所有权。
 附图说明
图1是本申请实施例提供的一种区块链***的结构示意图；
图2是本申请实施例提供的一种区块链的示意图；
图3是本申请实施例提供的一种生成区块的过程示意图；
图4是本申请实施例提供的一种数字资产转移***的结构示意图；
图5是本申请实施例提供的一种数字资产转移***的操作流程图；
图6是本申请实施例提供的另一种数字资产转移***的结构示意图；
图7是本申请实施例提供的一种业务***与区块链***之间的交互示意图；
图8是本申请实施例提供的一种计算机设备的结构示意图。
 本发明的实施方式
为使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请实施方式作进一步地详细描述。
应当理解的是，本申请提及的“多个”是指两个或两个以上。为了便于清楚描述本申请的技术方案，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
在对本申请实施例进行解释说明之前，先对区块链的相关内容予以说明。
图1是本申请实施例提供的一种区块链***的结构示意图。参见图1，区块链***100是指用于进行节点与节点之间数据共享的***，区块链***100中可以包括多个节点101，多个节点101可以是指区块链***100中各个客户端。每个节点101在进行正常工作可以接收到输入信息，并基于接收到的输入信息维护区块链***100内的共享数据。为了保证区块链***100内的信息互通，区块链***100中的每个节点101之间可以存在信息连接，节点101之间可以通过该信息连接进行信息传输。比如，当区块链***100中的任意节点101接收到输入信息时，区块链***100中的其他节点101便根据共识算法获取该输入信息，将该输入信息作为共享数据中的数据进行存储，使得区块链***100中全部节点101上存储的数据一致。
对于区块链***100中的每个节点101，均具有与其对应的节点标识，而且区块链***100中的每个节点101均可以存储有区块链***100中其他节点101的节点标识，以便后续根据其他节点101的节点标识，将生成的区块广播至区块链***100中的其他节点101。每个节点101中可维护一个节点标识列表，将节点名称和节点标识对应存储至该节点标识列表中。其中，节点标识可为IP（Internet Protocol，互联网协议）地址以及其他任一种能够用于标识节点101的信息。
区块链***100中的每个节点101均存储一条相同的区块链。参见图2，区块链由多个区块组成，创始块中包括区块头和区块主体，区块头中存储有输入信息特征值、版本号、时间戳和难度值，区块主体中存储有输入信息；创始块的下一区块以创始块为父区块，下一区块中同样包括区块头和区块主体，区块头中存储有当前区块的输入信息特征值、父区块的区块头特征值、版本号、时间戳和难度值，并以此类推，使得区块链中每个区块中存储的区块数据均与父区块中存储的区块数据存在关联，保证了区块中输入信息的安全性。
在生成区块链中的各个区块时，参见图3，区块链所在的节点101在接收到输入信息时，对输入信息进行校验，完成校验后，将输入信息存储至内存池中，并更新其用于记录输入信息的哈希树；之后，将更新时间戳更新为接收到输入信息的时间，并尝试不同的随机数，多次进行特征值计算，使得计算得到的特征值可以满足下述公式：
SHA256（SHA256（version+prev_hash+merkle_root+ntime+nbits+x））＜TARGET
其中，SHA256为计算特征值所用的特征值算法；version（版本号）为区块链中相关区块协议的版本信息；prev_hash为当前区块的父区块的区块头特征值；merkle_root为输入信息的特征值；ntime为更新时间戳的更新时间；nbits为当前难度，在一段时间内为定值，并在超出固定时间段后再次进行确定；x为随机数；TARGET为特征值阈值，该特征值阈值可以根据nbits确定得到。
这样，当计算得到满足上述公式的随机数时，便可将信息对应存储，生成区块头和区块主体，得到当前区块。随后，区块链所在节点101根据区块链***100中其他节点101的节点标识，将新生成的区块分别发送给其所在的区块链***100中的其他节点101，由其他节点101对新生成的区块进行校验，并在完成校验后将新生成的区块添加至其存储的区块链中。
区块链***100具有分布式数据存储、点对点传输、共识机制、加密算法等计算机技术。区块链***100是一个分布式的共享账本和数据库，具有去中心化、不可篡改、全程留痕、可以追溯、集体维护、公开透明等特点。这些特点保证了区块链的共享开放、真实完整和安全可靠。
下面对本申请实施例提供的数字资产转移***进行详细地解释说明。
图4是本申请实施例提供的一种数字资产转移***的结构示意图。参见图4，该数字资产转移***可以包括业务***401和区块链***402。
业务***401可以实现数字资产的生成和转移，该数字资产的转移可以包括分销、出售等。区块链***402可以是上述图1-图3实施例中所述的区块链***100。
接下来对业务***401和区块链***402在数字资产转移过程中执行的操作进行说明。参见图5，具体可以包括如下步骤501-步骤504。
步骤501：业务***401生成数字资产。
业务***401可以生成属于业务***401的数字资产，即业务***401拥有该数字资产的所有权。
该数字资产可以包括数字化的礼品卡、储值卡、会员卡、优惠券、积分等，本申请实施例对此不作唯一限定。该数字资产可以由资产编号、资产数值、资产有效期等数据组成，该数字资产可以不含资产密码。
步骤502：区块链***402设置该数字资产的属性信息，将该数字资产和该数字资产的属性信息存储到区块链***402配置的区块链。
该数字资产的属性信息可以包括该数字资产的资产归属和资产转移时间，进一步地，还可以包括该数字资产的资产状态等。
业务***401生成该数字资产后，区块链***402可以设置该数字资产初始的属性信息，具体可以设置该数字资产初始的资产归属和资产转移时间，进一步地，还可以设置该数字资产初始的资产状态。
其中，区块链***402将该数字资产和该数字资产的属性信息存储到该区块链***402配置的区块链时，区块链***402可以根据该数字资产和该数字资产的属性信息生成区块，并将该区块添加到配置的区块链中。
区块链***402可以根据智能合约将该数字资产和该数字资产的属性信息上链，也即根据智能合约生成存储有该数字资产和该数字资产的属性信息的区块，并将该区块添加到共享的区块链中。如此，该数字资产和该数字资产的属性信息将不可被篡改。
步骤503：业务***401对该数字资产进行转移。
随着数字资产交易的进行，该数字资产会不断被转移。比如，业务***401可以对该数字资产进行分销、出售等，以改变该数字资产的所有权。
步骤504：区块链***402根据该数字资产的转移情况，更新该数字资产的属性信息，将更新后的属性信息存储到该区块链。
该数字资产转移后，该数字资产的属性会发生变化，因而区块链***402可以更新该数字资产的属性信息并将其存储到该区块链。
其中，区块链***402将更新后的属性信息存储到该区块链时，区块链***402可以根据更新后的属性信息生成区块，并将该区块添加到配置的区块链中。
区块链***402可以根据智能合约将更新后的属性信息上链，也即根据智能合约生成存储有更新后的属性信息的区块，并将该区块添加到共享的区块链中。如此，更新后的属性信息将不可被篡改。
值得注意的是，区块链***402在将该数字资产的相关信息（包括但不限于属性信息）存储至区块链时，可以将所存储的信息与数字资产标识进行关联，以便后续可以根据该数字资产标识从区块链中获取该数字资产的相关信息。
该数字资产标识用于唯一标识该数字资产，如该数字资产标识可以为该数字资产的资产编号等，本申请实施例对此不作唯一限定。
在本申请实施例中，数字资产转移***包括业务***401和区块链***402。区块链***402可以将业务***401生成的数字资产和其属性信息存储到区块链***402配置的区块链。并且，在业务***401对该数字资产进行转移的过程中，区块链***402可以根据该数字资产的转移情况，不断更新该数字资产的属性信息并将其存储到区块链。由于该数字资产的属性信息包括资产归属和资产转移时间，因而该数字资产的转移过程都被记录到区块链***402配置的区块链。由于区块链的不可篡改性，所以根据区块链中记录的该数字资产的转移过程可以明确确认该数字资产的所有权。
在一种可选的实施方式中，业务***401可以是由多个服务器组成的服务器集群。参见图6，业务***401可以包括资产发行服务器4011、资产分发服务器4012和分销服务器4013。
这种情况下，业务***401与区块链***402之间的交互过程可以如图7所示。
参见图7，资产发行服务器4011与区块链***402之间的交互过程可以包括如下步骤：
步骤701：资产发行服务器4011生成数字资产，并调用智能合约资产初始化接口以向区块链***402发送携带有该数字资产的第一接口报文。
资产发行服务器4011是该数字资产的初始权属人。
第一接口报文可以是JSON（JavaScript Object Notation，JavaScript对象表示法）格式的报文。当然，第一接口报文也可以是其他格式的报文，本申请实施例对此不作唯一限定。
可选地，资产发行服务器4011在调用智能合约资产初始化接口之前，还可以先连接到区块链***402，再调用智能合约资产初始化接口来向区块链***402发送第一接口报文。
具体地，资产发行服务器4011可以向区块链***402发送数字证书；区块链***402可以在接收到资产发行服务器4011发送的数字证书时，检验该数字证书的合法性，在该数字证书的合法性校验通过的情况下，向资产发行服务器4011返回校验成功通知消息；资产发行服务器4011可以在接收到区块链***402返回的校验成功通知消息时，调用智能合约资产初始化接口以向区块链***402发送第一接口报文。
数字证书（Digital Certificate）可以是通过区块链***402签发认可的，也即可以是从区块链***402取得的。
示例地，区块链***402可以根据哈希算法，对资产发行服务器4011的公钥进行哈希运算，得到资产发行服务器4011的公钥的摘要，然后根据加密算法，使用自己的私钥对资产发行服务器4011的公钥的摘要进行加密，得到加密信息。区块链***402可以将该哈希算法、该加密算法、资产发行服务器4011的公钥、该加密信息作为资产发行服务器4011的数字证书下发到资产发行服务器4011。
这种情况下，区块链***402在接收到资产发行服务器4011发送的数字证书时，检验该数字证书的合法性的操作可以为：区块链***402在接收到资产发行服务器4011发送的数字证书时，根据该数字证书中包含的加密算法，使用自己的公钥对该数字证书中包含的加密信息进行解密，得到第一信息；根据该数字证书中包含的哈希算法，对该数字证书中包含的资产发行服务器4011的公钥进行哈希运算，得到第二信息；若第一信息与第二信息相同，则可以确定该数字证书的合法性校验通过；若第一信息与第二信息不同，则可以确定该数字证书的合法性校验失败。
区块链***402在该数字证书的合法性校验通过的情况下，可以确定资产发行服务器4011的身份合法，则可以向资产发行服务器4011返回校验成功通知消息。资产发行服务器4011接收到该校验成功通知消息后，即成功连接到区块链***402。
进一步地，区块链***402在该数字证书的合法性校验失败的情况下，可以确定资产发行服务器4011的身份非法，则可以向资产发行服务器4011返回校验失败通知消息；资产发行服务器4011接收到区块链***402返回的校验失败通知消息时，确认与区块链***402的连接失败，此时资产发行服务器4011可以直接结束操作或者尝试重新连接区块链***402。
步骤702：区块链***402在接收到第一接口报文时，设置该数字资产的属性信息，将该数字资产和该数字资产的属性信息存储到区块链。
区块链***402在接收到第一接口报文时，可以先对第一接口报文进行校验；在第一接口报文校验成功的情况下，再设置该数字资产的属性信息，将该数字资产和该数字资产的属性信息存储到区块链；在第一接口报文校验失败的情况下，向资产发行服务器4011返回出错提醒消息，并结束操作，资产发行服务器4011接收到该出错提醒消息时，可以重新调用智能合约资产初始化接口来向区块链***402发送第一接口报文。
其中，区块链***402对第一接口报文进行校验的操作与相关技术中某一设备对某一报文进行校验的操作类似，本申请实施例对此不进行详细阐述。
其中，区块链***402设置该数字资产的属性信息时，可以设置该数字资产的资产归属为资产分发服务器标识，设置该数字资产的资产转移时间为第一接口报文的接收时间，设置该数字资产的资产状态为待出售。
资产分发服务器标识用于唯一标识资产分发服务器4012。比如，资产分发服务器标识可以是资产分发服务器4012的UUID（Universally Unique Identifier，通用唯一识别码）、MAC（Media Access Control，介质访问控制）地址、IP地址、或出厂序列号等，本申请实施例对此不作唯一限定。
本申请实施例中，资产发行服务器4011借助资产分发服务器4012来销售资产发行服务器4011所属的数字资产，因而区块链***402可以直接将资产发行服务器4011生成的数字资产的资产归属设置为资产分发服务器标识。资产分发服务器标识可以预存在区块链***402中。
进一步地，区块链***402将该数字资产和该数字资产的属性信息存储到区块链后，还可以根据资产分发服务器标识将该数字资产发送给资产分发服务器4012，以便资产分发服务器4012后续可以对该数字资产进行销售。
其中，区块链***402根据资产分发服务器标识将该数字资产发送给资产分发服务器4012的操作与相关技术中一个设备根据另一个设备的标识向该另一个设备发送信息的操作类似，本申请实施例对此不进行详细阐述。比如，区块链***402可以根据资产分发服务器标识调用分发接口来向资产分发服务器4012发送携带有该数字资产的报文。
值得注意的是，智能合约是基于区块链可信的不可篡改的数据，可以自动化的执行一些预先定义好的规则和条款。在区块链架构中，智能合约以链上代码的形式储存在区块链的区块中。服务器可以通过合约接口调用智能合约，来执行特定的操作。
本申请实施例中，通过调用智能合约资产初始化接口，可以执行合约逻辑，来实现资产发行服务器4011向区块链***402发送第一接口报文、区块链***402设置数字资产的属性信息、区块链***402存储数字资产及其属性信息至区块链的这一系列操作。
参见图7，资产分发服务器4012与区块链***402之间的交互过程可以包括如下步骤：
步骤703：资产分发服务器4012在检测到针对该数字资产的分销操作时，调用智能合约资产分销接口以向区块链***402发送携带有该数字资产和分销服务器标识的第二接口报文。
资产分发服务器4012用于分销资产发行服务器4011生成的数字资产。
针对该数字资产的分销操作是指将该数字资产转移到分销服务器4013的操作。资产分发服务器4012检测到该分销操作时，可以获取到用于唯一标识分销服务器4013的分销服务器标识。分销服务器标识可以是分销服务器4013的UUID、MAC地址、IP地址、或出厂序列号等，本申请实施例对此不作唯一限定。
第二接口报文可以是JSON格式的报文。当然，第二接口报文也可以是其他格式的报文，本申请实施例对此不作唯一限定。
可选地，资产分发服务器4012在调用智能合约资产分销接口之前，还可以先连接到区块链***402，再调用智能合约资产分销接口来向区块链***402发送第二接口报文。
具体地，资产分发服务器4012可以向区块链***402发送数字证书；区块链***402可以在接收到资产分发服务器4012发送的数字证书时，检验该数字证书的合法性，在该数字证书的合法性校验通过的情况下，向资产分发服务器4012返回校验成功通知消息；资产分发服务器4012可以在接收到区块链***402返回的校验成功通知消息时，调用智能合约资产分销接口以向区块链***402发送第二接口报文。
示例地，区块链***402可以根据哈希算法，对资产分发服务器4012的公钥进行哈希运算，得到资产分发服务器4012的公钥的摘要，然后根据加密算法，使用自己的私钥对资产分发服务器4012的公钥的摘要进行加密，得到加密信息。区块链***402可以将该哈希算法、该加密算法、资产分发服务器4012的公钥、该加密信息作为资产分发服务器4012的数字证书下发到资产分发服务器4012。
这种情况下，区块链***402校验资产分发服务器4012发送的数字证书的合法性的操作与上述区块链***402校验资产发行服务器4011发送的数字证书的合法性的操作类似，本申请实施例对此不再赘述。
区块链***402在该数字证书的合法性校验通过的情况下，可以确定资产分发服务器4012的身份合法，则可以向资产分发服务器4012返回校验成功通知消息。资产分发服务器4012接收到该校验成功通知消息后，即成功连接到区块链***402。
进一步地，区块链***402在该数字证书的合法性校验失败的情况下，可以确定资产分发服务器4012的身份非法，则可以向资产分发服务器4012返回校验失败通知消息；资产分发服务器4012接收到区块链***402返回的校验失败通知消息时，确认与区块链***402的连接失败，可以直接结束操作或者尝试重新连接区块链***402。
步骤704：区块链***402在接收到第二接口报文时，根据分销服务器标识向分销服务器4013发送该数字资产，并在接收到分销服务器4013返回的第一确认响应时，更新该数字资产的资产归属为分销服务器标识，更新该数字资产的资产转移时间为第一确认响应的接收时间，将该数字资产的资产归属和资产转移时间存储到区块链。
区块链***402在接收到第二接口报文时，可以先对第二接口报文进行校验；在第二接口报文校验成功的情况下，再根据分销服务器标识向分销服务器4013发送该数字资产；在第二接口报文校验失败的情况下，向资产分发服务器4012返回出错提醒消息，并结束操作，资产分发服务器4012接收到该出错提醒消息时，可以重新调用智能合约资产分销接口来向区块链***402发送第二接口报文。
其中，区块链***402对第二接口报文进行校验的操作与相关技术中某一设备对某一报文进行校验的操作类似，本申请实施例对此不进行详细阐述。
其中，区块链***402根据分销服务器标识将该数字资产发送给分销服务器4013的操作与相关技术中一个设备根据另一个设备的标识向该另一个设备发送信息的操作类似，本申请实施例对此不进行详细阐述。比如，区块链***402可以根据分销服务器标识调用分销接口来向分销服务器4013发送携带有该数字资产的报文。
第一确认响应用于确认已接收到该数字资产。分销服务器4013可以在接收到区块链***402发送的该数字资产后，向区块链***402返回第一确认响应。
可选地，若区块链***402在根据分销服务器标识向分销服务器4013发送该数字资产后，在预定的时间内未接收到分销服务器4013返回的第一确认响应，则区块链***402可以向资产分发服务器4012发送出错提醒消息，资产分发服务器4012接收到该出错提醒消息时，可以重新调用智能合约资产分销接口来向区块链***402发送第二接口报文。
本申请实施例中，通过调用智能合约资产分销接口，可以执行合约逻辑，来实现资产分发服务器4012向区块链***402发送第二接口报文、区块链***402向分销服务器4013发送数字资产并在接收到分销服务器4013返回的第一确认响应时，更新数字资产的属性信息并将其存储至区块链的这一系列操作。
参见图7，分销服务器4013与区块链***402之间的交互过程可以包括如下步骤：
步骤705：分销服务器4013在检测到针对该数字资产的出售操作时，调用智能合约资产出售接口以向区块链***402发送携带有该数字资产和用户标识的第三接口报文。
分销服务器4013是数字资产的二级经销机构，可在资产分发服务器4012采购数字资产。
针对该数字资产的出售操作是指将该数字资产出售给用户的操作。分销服务器4013检测到该出售操作时，可以获取到用于唯一标识购买该数字资产的用户的用户标识。该用户标识可以是用户的电话号码、即时通讯账号等，本申请实施例对此不作唯一限定。
第三接口报文可以是JSON格式的报文。当然，第三接口报文也可以是其他格式的报文，本申请实施例对此不作唯一限定。
可选地，分销服务器4013在调用智能合约资产出售接口之前，还可以先连接到区块链***402，再调用智能合约资产出售接口来向区块链***402发送第三接口报文。
具体地，分销服务器4013可以向区块链***402发送数字证书；区块链***402可以在接收到分销服务器4013发送的数字证书时，检验该数字证书的合法性，在该数字证书的合法性校验通过的情况下，向分销服务器4013返回校验成功通知消息；分销可以在接收到区块链***402返回的校验成功通知消息时，调用智能合约资产出售接口以向区块链***402发送第三接口报文。
示例地，区块链***402可以根据哈希算法，对分销服务器4013的公钥进行哈希运算，得到分销服务器4013的公钥的摘要，然后根据加密算法，使用自己的私钥对分销服务器4013的公钥的摘要进行加密，得到加密信息。区块链***402可以将该哈希算法、该加密算法、分销服务器4013的公钥、该加密信息作为分销服务器4013的数字证书下发到分销服务器4013。
这种情况下，区块链***402校验分销服务器4013发送的数字证书的合法性的操作与上述区块链***402校验资产发行服务器4011发送的数字证书的合法性的操作类似，本申请实施例对此不再赘述。
区块链***402在该数字证书的合法性校验通过的情况下，可以确定分销服务器4013的身份合法，则可以向分销服务器4013返回校验成功通知消息。分销服务器4013接收到该校验成功通知消息后，即成功连接到区块链***402。
进一步地，区块链***402在该数字证书的合法性校验失败的情况下，可以确定分销服务器4013的身份非法，则可以向分销服务器4013返回校验失败通知消息；分销服务器4013接收到区块链***402返回的校验失败通知消息时，确认与区块链***402的连接失败，可以直接结束操作或者尝试重新连接区块链***402。
步骤706：区块链***402在接收到第三接口报文时，更新该数字资产的属性信息，将更新后的属性信息存储到区块链。
区块链***402在接收到第三接口报文时，可以先对第三接口报文进行校验；在第三接口报文校验成功的情况下，再更新该数字资产的属性信息；在第三接口报文校验失败的情况下，向分销服务器4013返回出错提醒消息，并结束操作，分销服务器4013接收到该出错提醒消息时，可以重新调用智能合约资产出售接口来向区块链***402发送第三接口报文。
其中，区块链***402对第三接口报文进行校验的操作与相关技术中某一设备对某一报文进行校验的操作类似，本申请实施例对此不进行详细阐述。
具体地，步骤706的操作可以为：区块链***402在接收到第三接口报文时，向资产发行服务器4011发送携带有该数字资产和该用户标识的资产出售通知消息；资产发行服务器4011在接收到该资产出售通知消息时，根据该用户标识将该数字资产和该数字资产的资产密码发送给用户终端，向区块链***402返回第二确认响应；区块链***402在接收到第二确认响应时，更新该数字资产的资产归属为该用户标识，更新该数字资产的资产转移时间为第二确认响应的接收时间，更新该数字资产的资产状态为已出售，将该数字资产的资产归属、资产转移时间和资产状态存储到区块链。
资产发行服务器标识用于唯一标识资产发行服务器4011。比如，资产发行服务器标识可以是资产发行服务器4011的UUID、MAC地址、IP地址、或出厂序列号等，本申请实施例对此不作唯一限定。
其中，区块链***402根据资产发行服务器标识向资产发行服务器4011发送携带有该数字资产和该用户标识的资产出售通知消息的操作与相关技术中一个设备根据另一个设备的标识向该另一个设备发送信息的操作类似，本申请实施例对此不进行详细阐述。比如，区块链***402可以根据资产发行服务器标识调用发行接口来向资产发行服务器4011发送携带有该数字资产和该用户标识的资产出售通知消息。
其中，资产发行服务器4011根据该用户标识将该数字资产和该数字资产的资产密码发送给用户终端的操作与相关技术中某一设备根据用户标识将某一信息发送到用户终端的操作类似，本申请实施例对此不进行详细阐述。比如，资产发行服务器4011可以根据该用户标识，以短信或者应用消息推送的方式将该数字资产和该数字资产的资产密码发送给用户终端。
第二确认响应用于确认已将该数字资产及其资产密码发送给用户。资产发行服务器4011可以在将该数字资产及其资产密码发送给用户终端后，向区块链***402返回第二确认响应。
可选地，若区块链***402在向资产发行服务器4011发送携带有该数字资产和该用户标识的资产出售通知消息后，在预定的时间内未接收到资产发行服务器4011返回的第二确认响应，则区块链***402可以向分销服务器4013发送出错提醒消息，分销服务器4013接收到该出错提醒消息时，可以重新调用智能合约资产出售接口来向区块链***402发送第三接口报文。
本申请实施例中，通过调用智能合约资产出售接口，可以执行合约逻辑，来实现分销服务器4013向区块链***402发送第三接口报文、区块链***402指示资产发行服务器4011向用户发送数字资产及其资产密码、区块链***402更新数字资产的属性信息并将其存储至区块链的这一系列操作。
进一步地，资产发行服务器4011在将该数字资产和该数字资产的资产密码发送给用户终端后，还可以进行数字资产核销，具体可以包括如下步骤（1）-步骤（4）。
（1）资产发行服务器4011调用智能合约资产核销接口以向区块链***402发送携带有数字资产标识的第四接口报文。
第四接口报文可以是JSON格式的报文。当然，第四接口报文也可以是其他格式的报文，本申请实施例对此不作唯一限定。
（2）区块链***402在接收到第四接口报文时，根据该数字资产标识查询该数字资产最新的资产状态。
区块链***402在接收到第四接口报文时，可以先对第四接口报文进行校验；在第四接口报文校验成功的情况下，再根据该数字资产标识查询该数字资产的资产状态；在第四接口报文校验失败的情况下，向资产发行服务器4011返回出错提醒消息，并结束操作，资产发行服务器4011接收到该出错提醒消息时，可以重新调用智能合约资产核销接口来向区块链***402发送第四接口报文。
其中，区块链***402对第四接口报文进行校验的操作与相关技术中某一设备对某一报文进行校验的操作类似，本申请实施例对此不进行详细阐述。
（3）区块链***402在该数字资产的资产状态为已出售的情况下，设置该数字资产的资产状态为已核销，设置该数字资产的资产核销时间为第四接口报文的接收时间，将该数字资产的资产状态和资产核销时间存储到区块链，向资产发行服务器4011返回核销通知消息。
其中，区块链***402将该数字资产的资产状态和资产核销时间存储到区块链的操作与上述区块链***402将该数字资产的属性信息存储到区块链的操作类似，本申请实施例对此不再赘述。
进一步地，区块链***402在该数字资产的资产状态为待出售的情况下，生成告警提醒消息，将该告警提醒消息发送给资产发行服务器4011，资产发行服务器4011接收到该告警提醒消息时，可以重新调用智能合约资产核销接口来向区块链***402发送第四接口报文。
由于资产发行服务器4011已经将该数字资产及其资产密码发送给用户终端，即已将该数字资产出售给用户。若此时区块链***402中记录的该数字资产的资产状态为待出售，则说明数字资产出售存在问题，因而区块链***402可以向资产发行服务器4011发送告警提醒消息，以提醒资产发行服务器4011该数字资产的出售存在问题。
（4）资产发行服务器4011在接收到该核销通知消息时，核销该数字资产。
若资产发行服务器4011接收到该核销通知消息，说明区块链***402中已记录将该数字资产出售给用户，则资产发行服务器4011可以核销该数字资产。
本申请实施例中，通过调用智能合约资产核销接口，可以执行合约逻辑，来实现资产发行服务器4011向区块链***402发送第四接口报文、区块链***402设置数字资产的核销信息并向资产发行服务器4011返回核销通知消息、资产发行服务器4011核销该数字资产的这一系列操作。
值得说明的是，本申请实施例中，该数字资产转移***基于区块链架构，可以实现所有的数字资产转移过程记录到区块链，不可篡改，如此可以提供数字资产转移关系的公信力证明，可以极大提高数字资产权属确认效率。
这种情况下，数字资产权属转移安全可靠。并且，由于每一个数字资产转移环节都通过调用智能合约交易接口来实现，转移信息记录到区块链中，所以数字资产交易结果不容篡改和抵赖，数字资产转移流程全程可追溯。
此外，数字资产在分发过程中，资产分发服务器4012和分销服务器4013均不能取得资产密码，从而可以杜绝密码泄露风险。资产密码在数字资产分发过程中只存在于资产发行服务器4011，只有当数字资产出售给用户时，资产密码才通过资产发行服务器4011发送给用户，从而可以最大程度保证数字资产的安全。如此，可以保证数字资产在转移过程中的安全性和独享性。
进一步地，业务***401中的资产发行服务器4011、资产分发服务器4012、分销服务器4013均可以从区块链***402中查询数字资产的相关信息。
具体地，业务***401可以调用智能合约资产查询接口以向区块链***402发送携带数字资产标识的第五接口报文。区块链***402在接收到第五接口报文时，根据该数字资产标识从区块链中获取该数字资产的所有信息，将该数字资产的所有信息发送给业务***401。
第五接口报文可以是JSON格式的报文。当然，第五接口报文也可以是其他格式的报文，本申请实施例对此不作唯一限定。
区块链***402在接收到第五接口报文时，可以先对第五接口报文进行校验；在第五接口报文校验成功的情况下，再根据该数字资产标识从区块链中获取该数字资产的所有信息；在第五接口报文校验失败的情况下，向业务***401返回出错提醒消息，并结束操作，业务***401接收到该出错提醒消息时，可以重新调用智能合约资产查询接口来向区块链***402发送第五接口报文。
其中，区块链***402对第五接口报文进行校验的操作与相关技术中某一设备对某一报文进行校验的操作类似，本申请实施例对此不进行详细阐述。
本申请实施例中，通过调用智能合约资产查询接口，可以执行合约逻辑，来实现业务***401向区块链***402发送第五接口报文、区块链***402查询数字资产的所有信息并返回给业务***401的这一系列操作。
值得注意的是，业务***401中还可以包括公证服务器，公证服务器作为可选参与方，可以负责数字资产交易中的公证。比如，公证服务器可以用于资产发行服务器4011到资产分发服务器4012的数字资产转移的公证，还可以用于资产分发服务器4012到分销服务器4013的数字资产转移的公证，还可以用于分销服务器4013到用户的数字资产转移的公证。
图8为本申请实施例提供的一种计算机设备的结构示意图。上述数字资产转移***可以通过计算机设备8实现。如图8所示，计算机设备8包括：处理器80、存储器81以及存储在存储器81中并可在处理器80上运行的计算机程序82，处理器80执行计算机程序82时实现上述实施例中的数字资产转移***执行的操作。
计算机设备8可以是一个通用或专用计算机设备。在具体实现中，计算机设备8可以是由多台服务器组成的服务器集群。本领域技术人员可以理解，图8仅仅是计算机设备8的举例，并不构成对计算机设备8的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件，比如还可以包括输入输出设备、网络接入设备等。
处理器80可以是中央处理单元（Central Processing Unit，CPU），处理器80还可以是其他通用处理器、数字信号处理器（Digital Signal Processor，DSP）、专用集成电路（Application Specific Integrated Circuit，ASIC）、现成可编程门阵列（Field-Programmable Gate Array，FPGA）或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者也可以是任何常规的处理器。
存储器81在一些实施例中可以是计算机设备8的内部存储单元，比如计算机设备8的硬盘或内存。存储器81在另一些实施例中也可以是计算机设备8的外部存储设备，比如计算机设备8上配备的插接式硬盘，智能存储卡（Smart Media Card，SMC），安全数字（Secure Digital，SD）卡，闪存卡（Flash Card）等。进一步地，存储器81还可以既包括计算机设备8的内部存储单元也包括外部存储设备。存储器81用于存储操作***、应用程序、引导装载程序（BootLoader）、数据以及其他程序等，比如计算机程序的程序代码等。存储器81还可以用于暂时地存储已经输出或者将要输出的数据。
在一些实施例中，还提供了一种计算机可读存储介质，该存储介质内存储有计算机程序，该计算机程序被处理器执行时实现上述实施例中的数字资产转移***执行的操作。比如，该计算机可读存储介质可以是ROM（Read-Only Memory，只读存储器）、RAM（Random Access Memory，随机存取存储器）、CD-ROM（Compact Disc Read-Only Memory，只读光盘）、磁带、软盘和光数据存储设备等。
值得注意的是，本申请提到的计算机可读存储介质可以为非易失性存储介质，换句话说，可以是非瞬时性存储介质。
应当理解的是，实现上述实施例的全部或部分步骤可以通过软件、硬件、固件或者其任意结合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。该计算机程序产品包括一个或多个计算机指令。该计算机指令可以存储在上述计算机可读存储介质中。
在一些实施例中，还提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述实施例中的数字资产转移***执行的操作。
以上所述为本申请提供的可选实施例，并不用以限制本申请，凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (10)

  1. 一种数字资产转移***，其特征在于，所述数字资产转移***包括业务***和区块链***；
    所述业务***，用于生成数字资产；
    所述区块链***，用于设置所述数字资产的属性信息，将所述数字资产和所述数字资产的属性信息存储到所述区块链***配置的区块链，所述数字资产的属性信息包括资产归属和资产转移时间；
    所述业务***，用于对所述数字资产进行转移；
    所述区块链***，用于根据所述数字资产的转移情况，更新所述数字资产的属性信息，将更新后的属性信息存储到所述区块链。
  2. 如权利要求1所述的数字资产转移***，其特征在于，所述业务***包括资产发行服务器；
    所述资产发行服务器，用于生成所述数字资产，并调用智能合约资产初始化接口以向所述区块链***发送携带有所述数字资产的第一接口报文；
    所述区块链***，用于在接收到所述第一接口报文时，设置所述数字资产的属性信息，将所述数字资产和所述数字资产的属性信息存储到所述区块链。
  3. 如权利要求2所述的数字资产转移***，其特征在于，
    所述资产发行服务器，用于向所述区块链***发送数字证书；
    所述区块链***，用于在接收到所述资产发行服务器发送的所述数字证书时，检验所述数字证书的合法性，在所述数字证书的合法性校验通过的情况下，向所述资产发行服务器返回校验成功通知消息；
    所述资产发行服务器，用于在接收到所述区块链***返回的校验成功通知消息时，调用所述智能合约资产初始化接口以向所述区块链***发送所述第一接口报文。
  4. 如权利要求2所述的数字资产转移***，其特征在于，所述数字资产的属性信息还包括资产状态，所述区块链***用于：
    设置所述数字资产的资产归属为资产分发服务器标识，设置所述数字资产的资产转移时间为所述第一接口报文的接收时间，设置所述数字资产的资产状态为待出售；
    根据所述资产分发服务器标识将所述数字资产发送给资产分发服务器。
  5. 如权利要求1所述的数字资产转移***，其特征在于，所述业务***包括资产分发服务器；
    所述资产分发服务器，用于在检测到针对所述数字资产的分销操作时，调用智能合约资产分销接口以向所述区块链***发送携带有所述数字资产和分销服务器标识的第二接口报文；
    所述区块链***，用于在接收到所述第二接口报文时，根据所述分销服务器标识向分销服务器发送所述数字资产，并在接收到所述分销服务器返回的第一确认响应时，更新所述数字资产的资产归属为所述分销服务器标识，更新所述数字资产的资产转移时间为所述第一确认响应的接收时间，将所述数字资产的资产归属和资产转移时间存储到所述区块链。
  6. 如权利要求2所述的数字资产转移***，其特征在于，所述数字资产的属性信息还包括资产状态，所述业务***包括分销服务器；
    所述分销服务器，用于在检测到针对所述数字资产的出售操作时，调用智能合约资产出售接口以向所述区块链***发送携带有所述数字资产和用户标识的第三接口报文；
    所述区块链***，用于在接收到所述第三接口报文时，更新所述数字资产的属性信息，将更新后的属性信息存储到所述区块链。
  7. 如权利要求6所述的数字资产转移***，其特征在于，
    所述区块链***，用于在接收到所述第三接口报文时，根据资产发行服务器标识向所述资产发行服务器发送携带有所述数字资产和所述用户标识的资产出售通知消息；
    所述资产发行服务器，用于在接收到所述资产出售通知消息时，根据所述用户标识将所述数字资产和所述数字资产的资产密码发送给用户终端，向所述区块链***返回第二确认响应；
    所述区块链***，用于在接收到所述第二确认响应时，更新所述数字资产的资产归属为所述用户标识，更新所述数字资产的资产转移时间为所述第二确认响应的接收时间，更新所述数字资产的资产状态为已出售，将所述数字资产的资产归属、资产转移时间和资产状态存储到所述区块链。
  8. 如权利要求7所述的数字资产转移***，其特征在于，
    所述资产发行服务器，用于在将所述数字资产和所述数字资产的资产密码发送给所述用户终端后，调用智能合约资产核销接口以向所述区块链***发送携带有数字资产标识的第四接口报文；
    所述区块链***，用于在接收到所述第四接口报文时，根据所述数字资产标识查询所述数字资产最新的资产状态，在所述数字资产最新的资产状态为待出售的情况下，生成告警提醒消息，将所述告警提醒消息发送给所述资产发行服务器。
  9. 如权利要求8所述的数字资产转移***，其特征在于，
    所述区块链***，用于在所述数字资产最新的资产状态为已出售的情况下，设置所述数字资产的资产状态为已核销，设置所述数字资产的资产核销时间为所述第四接口报文的接收时间，将所述数字资产的资产状态和资产核销时间存储到所述区块链，向所述资产发行服务器返回核销通知消息；
    所述资产发行服务器，用于在接收到所述核销通知消息时，核销所述数字资产。
  10. 如权利要求1-9任一所述的数字资产转移***，其特征在于，
    所述业务***，用于调用智能合约资产查询接口以向所述区块链***发送携带数字资产标识的第五接口报文；
    所述区块链***，用于在接收到所述第五接口报文时，根据所述数字资产标识从所述区块链中获取所述数字资产的所有信息；将所述数字资产的所有信息发送给所述业务***。
PCT/CN2020/121885 2020-10-19 2020-10-19 数字资产转移*** WO2022082360A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2020/121885 WO2022082360A1 (zh) 2020-10-19 2020-10-19 数字资产转移***
CN202080002607.7A CN112513908A (zh) 2020-10-19 2020-10-19 数字资产转移***

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/121885 WO2022082360A1 (zh) 2020-10-19 2020-10-19 数字资产转移***

Publications (1)

Publication Number Publication Date
WO2022082360A1 true WO2022082360A1 (zh) 2022-04-28

Family

ID=74952797

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/121885 WO2022082360A1 (zh) 2020-10-19 2020-10-19 数字资产转移***

Country Status (2)

Country Link
CN (1) CN112513908A (zh)
WO (1) WO2022082360A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116340897A (zh) * 2021-04-19 2023-06-27 支付宝(杭州)信息技术有限公司 一种基于区块链的数字资产处理方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110178338A (zh) * 2016-08-24 2019-08-27 高阶公司 活动门票的数字证券化、模糊化、策略和商务
CN110633965A (zh) * 2019-09-20 2019-12-31 张嘉荣 点对点的资产映射和数字资产交易的方法及***
CN111177275A (zh) * 2020-01-02 2020-05-19 肖光昱 基于区块链的管理方法、终端、装置及存储介质
CN111222841A (zh) * 2019-11-26 2020-06-02 腾讯科技（深圳）有限公司 一种基于区块链的数据分配方法及其设备、存储介质
CN111724146A (zh) * 2020-05-21 2020-09-29 梁伟 一种基于区块链的数字资产流转的方法及装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109598142B (zh) * 2018-12-05 2022-02-22 腾讯科技（深圳）有限公司 债权凭证生成方法、装置、电子设备及存储介质
CN110503416B (zh) * 2019-08-29 2023-08-22 腾讯科技（深圳）有限公司 数值转移方法、装置、计算机设备及存储介质
CN111213168B (zh) * 2019-09-11 2023-11-03 创新先进技术有限公司 用于数字资产转移的***和方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110178338A (zh) * 2016-08-24 2019-08-27 高阶公司 活动门票的数字证券化、模糊化、策略和商务
CN110633965A (zh) * 2019-09-20 2019-12-31 张嘉荣 点对点的资产映射和数字资产交易的方法及***
CN111222841A (zh) * 2019-11-26 2020-06-02 腾讯科技（深圳）有限公司 一种基于区块链的数据分配方法及其设备、存储介质
CN111177275A (zh) * 2020-01-02 2020-05-19 肖光昱 基于区块链的管理方法、终端、装置及存储介质
CN111724146A (zh) * 2020-05-21 2020-09-29 梁伟 一种基于区块链的数字资产流转的方法及装置

Also Published As

Publication number Publication date
CN112513908A (zh) 2021-03-16

Similar Documents

Publication Publication Date Title
TWI724391B (zh) 基於區塊鏈的節點管理方法和裝置
CN111144881B (zh) 对资产转移数据的选择性访问
CN110620810B (zh) 在区块链上的连续资产转移的非链接所有权
US11720711B2 (en) System and method for interaction object management in a blockchain environment
TWI734088B (zh) 基於區塊鏈的交易處理方法及裝置、電子設備
US10523526B2 (en) System and method for managing services and licenses using a blockchain network
US20220382746A1 (en) Blockchain notification board storing blockchain resources
US20200074470A1 (en) Database configuration for asset transfers
US20200112432A1 (en) Blockchain notification board storing blockchain resources
US10922097B2 (en) Collaborative model execution
US11270017B2 (en) Selective exchange of transaction data
CN111241557B (zh) 基于区块链的服务请求方法及装置
WO2020037927A1 (zh) 可协商的区块链交易方法、装置、设备及存储介质
CN110471982B (zh) 基于区块链的数据处理方法和装置
CN111127021A (zh) 基于区块链的服务请求方法及装置
WO2019142884A1 (ja) ブロック検証装置、ブロック検証方法、及びプログラム
CN113706313A (zh) 基于区块链的融资方法、***及计算机可读存储介质
CN110941840B (zh) 一种数据处理方法、***及终端
WO2021184642A1 (zh) 基于区块链的交易方法、装置、电子设备及可读存储介质
CN114331397B (zh) 信息处理方法、装置、电子设备和存储介质
CN111915308A (zh) 一种区块链网络的交易处理方法及区块链网络
WO2022082360A1 (zh) 数字资产转移***
WO2023185862A1 (zh) 基于区块链***的多方计算方法和***
WO2023019903A1 (zh) 跨链交易***、方法、设备及存储介质
CN113674118A (zh) 基于区块链的捐赠方法、***、介质及电子设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20957949

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20957949

Country of ref document: EP

Kind code of ref document: A1