WO2018157788A1 - 区块链中账户信息的处理方法和装置、存储介质和电子装置 - Google Patents

区块链中账户信息的处理方法和装置、存储介质和电子装置 Download PDF

Info

Publication number
WO2018157788A1
WO2018157788A1 PCT/CN2018/077412 CN2018077412W WO2018157788A1 WO 2018157788 A1 WO2018157788 A1 WO 2018157788A1 CN 2018077412 W CN2018077412 W CN 2018077412W WO 2018157788 A1 WO2018157788 A1 WO 2018157788A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
account
blockchain
identity information
transfer
Prior art date
Application number
PCT/CN2018/077412
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 腾讯科技（深圳）有限公司
Publication of WO2018157788A1 publication Critical patent/WO2018157788A1/zh
Priority to US16/371,480 priority Critical patent/US10785038B2/en
Priority to US16/993,985 priority patent/US11477034B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • G06F21/6245—Protecting personal data, e.g. for financial or medical purposes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/30—Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
    • H04L9/3239—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3263—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements

Definitions

  • the present application relates to the field of blockchain, and in particular to a method and apparatus for processing account information in a blockchain, a storage medium, and an electronic device.
  • An account in a blockchain usually consisting of a pair of public and private keys (asymmetric keys).
  • the address of the account is usually obtained by a hash transformation of the public key, and the private key is used to prove and authorize the transaction of the resources in the account.
  • the user proves his identity with the account private key and trades the resources in his account. Once the private key is lost, there is no way to transfer or trade the resources in the account.
  • Option 1 Use an intermediary to help users host the user's private key.
  • Option 2 Host the account's permissions to a third party, and when the account's private key is lost, trade or transfer the resource. For example, using smart contract technology or similar technology for hosting.
  • the embodiment of the present application provides a method and a device for processing account information in a blockchain, a storage medium, and an electronic device, which can solve the technical problem of account uneasiness caused by the loss of the private key of the account in the blockchain.
  • a method for processing account information in a blockchain is provided.
  • the processing method is performed by a computer device, where the processing method includes: the computer device receives a user to send a transfer request and identity information, where The transfer request is for requesting transfer of resources in the lost account to the target account, the target account being generated by the certificate center; the computer device acquiring all of the lost accounts from the certificate center according to the transfer request Comparing the identity information with the owner information by the computer device; the computer device submits an authentication request to the blockchain when the identity information and the owner information are aligned, so that the The blockchain records a transfer event in the blockchain according to the authentication request, wherein the transfer event is used to indicate that resources in the lost account are transferred to the target account.
  • a processing device for account information in a blockchain the processing device being disposed in a computer device, the processing device comprising: a first receiving unit, configured to receive a user Transmitting a transfer request and an identity information, wherein the transfer request is for requesting transfer of a resource in the lost account to a target account, the target account being generated by a certificate center; and an obtaining unit, configured to The certificate center obtains the owner information of the lost account; the first comparison unit is configured to compare the identity information with the owner information; and the first submitting unit is configured to compare the And when the identity information is consistent with the owner information, submitting an authentication request to the blockchain, so that the blockchain records a transfer event in the blockchain according to the authentication request, wherein the transfer event is used for Instructing to transfer resources in the lost account to the target account.
  • a storage medium having stored therein a computer program, wherein the computer program is configured to execute the method described above at runtime.
  • an electronic device comprising a memory and a processor, wherein the memory stores a computer program, the processor being arranged to perform the method described above by the computer program.
  • the receiving user sends the transfer request and the identity information, wherein the transfer request is used to request to transfer the resources in the lost account to the target account, and the target account is generated by the certificate center; Obtaining the owner information of the lost account; comparing the identity information with the owner information; and submitting the authentication request to the blockchain when the identity information and the owner information are aligned, so that the blockchain is based on the authentication request
  • a transfer event is recorded in the blockchain, wherein the transfer event is used to indicate that the resource in the lost account is transferred to the target account, and whether the identity information provided by the comparison user and the lost account owner information are consistent, and compared
  • the authentication request is submitted to the blockchain, and the purpose of transferring the resources in the lost account to the target account in the blockchain is achieved, thereby realizing the transfer of the resources in the lost account to the target account.
  • Figure 1 is a schematic illustration of a blockchain in accordance with the prior art
  • FIG. 2 is a schematic diagram of a hardware environment of a method for processing account information in a blockchain according to an embodiment of the present application
  • FIG. 3 is a flowchart of a method for processing account information in an optional blockchain according to an embodiment of the present application
  • FIG. 4 is a schematic diagram of a field list of first data according to an embodiment of the present application.
  • FIG. 5 is a flowchart of a method for processing account information in an optional blockchain according to an embodiment of the present application.
  • FIG. 6 is a schematic diagram of an apparatus for processing account information in an optional blockchain according to an embodiment of the present application.
  • FIG. 7 is a structural block diagram of a terminal according to an embodiment of the present application.
  • Blockchain As shown in Figure 1, the blockchain organizes data in blocks. All transaction records on the entire network can be stored in the blockchain in the form of a transaction order. Among them, the first block in the blockchain is the initial block, also known as the creation block. Each time a transaction is formed, it is recorded in a block, and the information recorded in the block is transparent to the whole network, and the plurality of blocks are connected together in a certain order to form a blockchain.
  • An account in a blockchain usually consisting of a pair of public and private keys (asymmetric keys).
  • the address of the account is usually obtained by hashing the public key, and the private key is used to prove and authorize the transaction of the assets in the account. Once the private key is lost, it is generally impossible to conduct regular transactions.
  • the account concept in this article is similar to the Bitcoin address concept of Bitcoin. The lost accounts and target accounts in this article are all accounts in the blockchain.
  • Certificate Center is used to create a blockchain account that records the account's public key, address, and account owner's identity information.
  • Loss of private key In this article, the loss of private key and account loss can be understood as synonyms.
  • the "old account” is the lost account.
  • Special Transaction A transaction in which a user loses a private key and transfers the assets in the lost account to a new account through a super account is called a special transaction.
  • First account refers to the super account in the blockchain.
  • the super account can be an untrusted account that is recognized in the blockchain network. It can be used for special transactions. It may also be used for other purposes, such as creating assets in a blockchain, etc.
  • the public key of the first account is recorded in the certificate block and the initial block of the blockchain.
  • the asset gateway is a type of user with special permissions in the blockchain, and the super account is its account.
  • the asset gateway can send requests for issuing assets and assets to the blockchain service in the blockchain.
  • the gateway can be another system, such as an electronic counter system, that handles user and business requests, and then sends these requests to the blockchain through the blockchain interface (via the super account).
  • the gateway can be set in a terminal or a server, and the terminal or the server implements the function of the gateway.
  • a method embodiment of a method for processing account information in a blockchain is provided.
  • the method for processing account information in the above blockchain may be applied to a hardware environment composed of the server 202 and the terminal 204 as shown in FIG. 2.
  • the server 202 is connected to the terminal 204 through a network.
  • the network includes but is not limited to a wide area network, a metropolitan area network, or a local area network.
  • the terminal 204 is not limited to a PC, a mobile phone, a tablet, or the like.
  • the method for processing the account information in the blockchain of the embodiment of the present application may be executed by the server 202, may be performed by the terminal 204, or may be jointly performed by the server 202 and the terminal 204.
  • the method for processing the account information in the blockchain of the embodiment of the present application may also be performed by a client installed on the terminal.
  • the hardware environment formed by the server 202 and the terminal 204 shown in FIG. 2 is mainly for performing the processing method of the account information in the blockchain of the embodiment, and the blockchain in the processing method of the account information in the blockchain may be set in In a different server than the one shown in Figure 2. That is to say, the hardware environment formed by the server 202 and the terminal 204 of the embodiment is used to implement the environment of the gateway, and the blockchain may be two different systems.
  • the server 202 shown in FIG. 2 may be a server cluster. Some servers in the server cluster may be used to implement the function of the gateway, and another part of the server may implement the function of the blockchain. Alternatively, implement gateway and blockchain functionality on a single server.
  • the device in the blockchain of this embodiment can be understood as a computer device, such as a terminal or a server.
  • the device in the block can be used as a node of the blockchain, and the nodes of the plurality of blockchains form a blockchain, and at least one device corresponding to the plurality of nodes implements the function of the blockchain.
  • the method steps or processes performed by the blockchain are performed by nodes in the blockchain.
  • FIG. 3 is a flowchart of a method for processing account information in an optional blockchain according to an embodiment of the present application.
  • the processing method is performed by a computer device, where the computer device includes a terminal and a server, and the computer device can implement a gateway. Function, the gateway is used to execute the processing method of the account information in the blockchain. As shown in FIG. 3, the method may include the following steps:
  • Step S302 the computer device receives the user sends a transfer request and identity information, where the transfer request is used to request to transfer the resources in the lost account to the target account, and the target account is generated by the certificate center;
  • Step S304 the computer device acquires owner information of the lost account from the certificate center according to the transfer request
  • Step S306 the computer device compares the identity information with the owner information.
  • Step S308 the computer device submits an authentication request to the blockchain when the identity information and the owner information are matched, so that the blockchain records the transfer event in the blockchain according to the authentication request, wherein the transfer event is used to indicate Transfer the resources from the lost account to the target account.
  • step S302 when the user loses the private key of the blockchain account, the user may send the identity information and the transfer request to the gateway to transfer the resources in the lost account to the target account, specifically, the user.
  • the gateway When the private key of the account is lost, a new account is generated through the certificate center, and the newly generated account is used as the target account.
  • the certificate center is used to create an account, and all the accounts are recorded in the certificate center. Key, address, and account owner information.
  • the user sends a transfer request to the gateway according to the lost account and the target account, and the transfer request is used to request the gateway to transfer the resources in the lost account to the target account, and the user also needs to provide the identity information to the gateway to pass the This identity information proves that it is the owner of the lost account.
  • the gateway may be, but is not limited to, a server or an electronic platform or a counter service set by an authority in the blockchain network, and the gateway is configured to receive the transfer request and identity information submitted by the user on behalf of the authority.
  • the identity information submitted by the user may be a scanned copy of the paper or paper material of the identity document or other formats that can prove the identity of the user and its wishes, such as: face image, pupil scan, depending on the specific regulations. Information, etc.
  • the gateway has the right to acquire the account information recorded therein from the certificate center.
  • the gateway obtains the information of the owner of the lost account from the certificate center according to the transfer request submitted by the user, and the information of the lost account owner is the identity information of the lost account owner.
  • the certificate center records the ID card number of the lost account owner or a scanned copy of the ID card, the user is required to provide a copy of the corresponding ID card and other identification materials.
  • the certificate center records the voiceprint information of the lost account owner, and the user is required to provide the corresponding voiceprint material.
  • the gateway compares the identity information submitted by the user with the information of the lost account owner obtained from the certificate center to determine whether the identity information submitted by the user is consistent with the owner information of the lost account. And then verify that the user is the owner of the lost account.
  • step S308 if the identity information submitted by the user is inconsistent with the information of the owner of the lost account, the identity information verification of the user fails, that is, the user is not the owner of the lost account, the user
  • the transfer request submitted to the gateway is invalid, the gateway will not respond to the transfer request; if the identity information submitted by the user is consistent with the owner information of the lost account, the user's identity information is verified successfully, and the user is lost.
  • the owner of the account the gateway responds to the transfer request submitted by the user. Specifically, the gateway submits an authentication request to the blockchain according to the transfer request submitted by the user, so that the blockchain records a transfer event, indicating that the resource of the lost account is transferred to the target account. For example, a block is added to the blockchain to record the transfer event, thereby completing the transfer of the resource of the lost account to the target account.
  • the method provided by the embodiment of the present application can be applied to a digital payment scenario in various blockchain modes, such as a bank transaction in a blockchain mode, an account transaction in a gold transaction, or a blockchain.
  • the trading scenario of the virtual resource in the mode such as the transaction of the virtual resource of the game account in the online game.
  • the gateway submitting the authentication request to the blockchain includes: signing the initial data by using the private key of the first account to obtain the first data, where the initial data includes the information of the lost account, the information of the target account, and the identity information. a transfer request and a resource list, the resource list being a list of all resources waiting to be transferred in the lost account; generating an authentication request according to the first data; and submitting an authentication request carrying the initial data to the blockchain.
  • the gateway when the gateway submits the authentication request to the blockchain, the gateway first obtains initial data according to the received transfer request, and then signs the initial data to obtain the first data, as shown in FIG.
  • the initial data and the signature of the initial data by the gateway are included in the initial data, and the information of the lost account, the information of the target account, the identity information submitted by the user, the transfer request, and the need to withdraw from the lost account are included in the initial data.
  • the gateway generates an authentication request according to the first data and the initial data, and finally submits the authentication request to the blockchain.
  • the first account may be a super account in the blockchain
  • the first account may be a unique and unforgeable account in the blockchain
  • the gateway is the first account. Owner, with the private key of the first account.
  • the gateway may use the first account private key to sign the initial data to obtain the first data.
  • the authentication request submitted by the gateway to the blockchain is generated according to the first data, and the first data is obtained by signing the initial data by using the private key of the first account, and the gateway is the owner of the first account and has the first account.
  • the private key is responsible for the above authentication request, that is, the authenticity of the information in the initial data. Therefore, the blockchain only needs to verify whether the gateway uses the private key to sign the initial data, and confirms the authentication and records the transfer event under legal circumstances.
  • the computer device uses the private key of the first account to sign the initial data
  • the obtaining the first data includes: the computer device encrypts the identity information and the transfer request by using the public key of the first account to obtain the second data; the computer device The first account is obtained by signing the information of the lost account, the information of the target account, the resource list, and the second data by using the private key of the first account.
  • the identity information and the transfer request submitted by the user may be encrypted.
  • the gateway uses the private key of the first account to sign the initial data to obtain the first data
  • the gateway first obtains the public key of the first account from the certificate center, and uses the public key of the first account to submit the identity information submitted by the user. Encrypting with the transfer request to obtain the second data; and reusing the information of the lost account, the information of the target account, the resource list, and the second data by using the private key of the first account to obtain the first data.
  • the gateway After the gateway generates an authentication request according to the first data, and submits the authentication request to the blockchain, since the identity information and the transfer request submitted by the user are encrypted by the public key of the first account, other people can only obtain the blockchain.
  • the present application further provides an optional embodiment.
  • the computer device signs the initial data by using the private key of the first account, and obtaining the first data includes: using the private key pair of the first account by the computer device The identity information and the transfer request are signed to obtain the third data; the computer device uses the private key of the first account to sign the information of the lost account, the information of the target account, the resource list, and the third data to obtain the first data.
  • the gateway uses the private key of the first account to sign the initial data to obtain the first data
  • the gateway first uses the private key of the first account to sign the identity information and the transfer request submitted by the user to obtain the third data;
  • the private key of the account signs the information of the lost account, the information of the target account, the resource list, and the third data to obtain the first data. Since the gateway uses the private key of the first account to sign the identity information and the transfer request submitted by the user, the identity information and the transfer request submitted by the user are hash-transformed, and then encrypted to obtain the third data.
  • the process of hash transformation is irreversible.
  • the gateway After the gateway generates an authentication request according to the first data and submits the authentication request to the blockchain, even if other people can decrypt, the obtained hash-transformed identity information and The transfer request, the user's identity information and the original text of the transfer request cannot be obtained, and the privacy of the user can be protected from being leaked.
  • the authentication request is submitted to the blockchain, so that the block chain records the transfer event in the blockchain according to the authentication request, including: the device according to the device in the blockchain.
  • the authentication request acquires the first data; the device in the blockchain verifies the first data; after the verification is passed, the device in the blockchain records the transfer event according to the initial data.
  • the gateway when the gateway submits the authentication request to the blockchain, so that the blockchain records the transfer event according to the authentication request, the blockchain obtains the first data from the authentication request submitted by the gateway. And verifying the first data. After the verification succeeds, the blockchain trusts the initial data carried in the authentication request, and records the transfer event according to the initial data in the authentication request.
  • the blockchain verifies the first data
  • the public key of the first account is obtained from the certificate center, and the first data is verified by using the public key of the first account. If the verification is successful, the blockchain trusts the authentication. Requesting, and obtaining initial data carried in the authentication request, and recording a transfer event according to the initial data.
  • the blockchain in the process of authenticating the first data by the blockchain, the blockchain only verifies the signature of the fifth column in FIG. 4, and does not need to verify the initial data of the first four columns.
  • the signature of the column is that the gateway uses the private key of the first account to sign the initial data of the first four columns. After the signature verification of the fifth column is successful, the initial data of the first four columns is selected, and the first four columns of initial data are selected.
  • the authenticity of the gateway is responsible for verification, that is, the gateway assumes responsibility for verifying the initial data.
  • the blockchain since the verification of the identity information and the transfer request is completed by the gateway, the blockchain trusts the check result of the gateway. Therefore, the blockchain only needs to verify whether the signature of the initial data by the gateway is true, without Verify the user's identity information and transfer request. As long as the signature of the initial data is true by the blockchain verification gateway, the received authentication request is acknowledged and the transfer event is recorded, thereby transferring the resources in the lost account to the target account.
  • the determining, by the blockchain, the first data includes: the multiple devices of the blockchain obtain the public key of the first account from the initial block of the certificate center or the blockchain; and the multiple devices of the blockchain utilize The first account's public key verifies the first data.
  • the blockchain includes a plurality of devices. It should be noted that the blockchain in this embodiment includes multiple block nodes, and multiple devices included in the blockchain correspond to multiple block nodes, that is, one block node may correspond to one device.
  • each device in the plurality of blocks of the blockchain acquires the public key of the first account from the certificate block or the initial block in the blockchain, and utilizes the first The public key of an account verifies the first data. If most of the plurality of devices are successfully verified, the blockchain successfully verifies the first data, and the block selects the initial data in the first data.
  • each device In the process of verifying the first data by each device, each device only needs to verify whether the signature of the initial data by the gateway is true, and does not need to verify the identity information and the transfer request submitted by the user in the initial data.
  • the gateway assumes responsibility for verifying the authenticity of the identity information and transfer requests submitted by the user.
  • the method further includes: the device in the blockchain sets a freeze period for the target account, where During the freeze period, the resources in the target account are in a state where transfer is not allowed.
  • the blockchain pair sets a freeze period during which resources in the target account cannot be transferred. If the owner of the lost account raises an objection during the freezing period set by the blockchain to the target account, for example, the owner of the lost account does not actually initiate the transfer request, or the resource in the lost account is transferred. In the process of an error, or the owner of the lost account believes that the gateway or other people are fraudulent, etc., the blockchain can return the lost account to the target account and return it to the lost account to protect the owner of the lost account. Rights.
  • the process of re-entering the resources in the target account to the lost account is the same as the process of transferring the resources of the lost account to the target account, and the owner of the lost account provides the identity information and the resource return request to the gateway.
  • the gateway verifies the identity information and the resource return request, and after the verification is passed, submits an authentication request to the blockchain according to the user identity information and the resource return request, and the blockchain records the transfer event according to the authentication request, thereby returning the resources in the target account. Has been lost in the account.
  • the computer device submits the authentication request to the blockchain, so that the block chain records the transfer event in the blockchain according to the authentication request
  • the method further includes: the computer device extracts the initial data from the blockchain, where The initial data includes second data obtained by the gateway encrypting the identity information and the transfer request by using the public key of the first account; the computer device decrypts the second data by using the private key of the first account to obtain the first decrypted data; the computer device Comparing whether the first decrypted data is consistent with the data stored locally by the gateway; if the computer device compares the first decrypted data with the locally stored data, it determines that the locally stored data is tampered with.
  • the initial data recorded by the blockchain may also be verified. For example, after transferring the resources in the lost account to the target account, the owner of the lost account proposes that the gateway or other person has fraud, requests to return the transferred resource, or the target account freeze period has ended, and the transfer to the target account The resources have been transferred again, so that they cannot be returned to the lost account.
  • the gateway When the owner of the lost account needs to be compensated by judicial means, the gateway needs to provide the local identity information and transfer request as evidence, and can It is verified that the identity information and the transfer request provided by the gateway are the identity information and the transfer request submitted by the gateway to the blockchain without being tampered with. Specifically, if the identity information and the transfer data included in the authentication request submitted by the gateway to the blockchain are encrypted by using the public key of the first account, the gateway extracts initial data from the blockchain, and in the initial data, The second data obtained by the gateway encrypting the identity information and the transfer request submitted by the user by using the public key of the first account is used, and the gateway decrypts the second data by using the private key of the first account to obtain the identity information submitted by the user.
  • the gateway compares the first decrypted data with the data stored locally by the gateway. If the first decrypted data is consistent with the data stored locally by the gateway, the locally stored data of the gateway is not tampered with, if the first decrypted data and the data stored locally by the gateway Inconsistent, the data stored locally by the gateway has been tampered with.
  • the computer device submits the authentication request to the blockchain, so that the block chain records the transfer event in the blockchain according to the authentication request
  • the method further includes: the computer device extracts the initial data from the blockchain, where The initial data includes third data obtained by signing the identity information and the transfer request by using the private key of the first account; the computer device decrypts the third data by using the public key of the first account to obtain the second decrypted data;
  • the locally stored data is hash-transformed to obtain hash-converted data; the computer device compares the second decrypted data with the hash-transformed data; if the second decrypted data and the hash-converted data are compared
  • the computer device determines that the locally stored data has been tampered with.
  • the identity information and the transfer request provided by the verification gateway are consistent with the identity information and the transfer request submitted by the gateway to the blockchain
  • the identity of the authentication request submitted by the gateway to the blockchain is included
  • the information and the transfer data are signed by using the private key of the first account, and the gateway extracts the initial data from the blockchain, and the initial data includes the identity information submitted by the gateway to the user by using the private key of the first account.
  • the third data obtained by the transfer request is signed, and the gateway decrypts the third data by using the public key of the first account to obtain the second decrypted data, which is obtained after the identity information and the transfer request are hash-converted.
  • the gateway performs hash transformation on the locally stored identity information and the transfer request to obtain hash-converted data, and compares the second decrypted data with the hash-converted data, if the second decrypted data and the hash are transformed
  • the data is consistent, the data stored locally by the gateway is consistent with the data recorded by the blockchain, and the data stored locally by the gateway has not been tampered with. If the second decrypted data is inconsistent with the hashed data, the data and area stored locally by the gateway are The data recorded on the blockchain is inconsistent, and the data stored locally by the gateway has been tampered with.
  • the method further includes: the computer device extracting the initial from the blockchain according to the verification instruction sent by the user.
  • Data wherein the initial data includes second data obtained by encrypting the identity information and the transfer request using the public key of the first account, the verification command is used to instruct verification of the second data; and the computer device utilizes the public key pair of the first account
  • the transfer request and the identity information sent by the user are encrypted to obtain the fourth data; the computer device compares the second data with the fourth data to obtain a comparison result, wherein if the comparison result is consistent, the transfer request sent by the user And the identity information has not been tampered with, if the comparison result is inconsistent, the transfer request and identity information sent by the user are tampered with.
  • the method further includes: the computer device extracting the initial from the blockchain according to the verification instruction sent by the user.
  • Data wherein the initial data includes third data obtained by signing the identity information and the transfer request using the private key of the first account, the verification instruction is used to indicate verification of the third data; the transfer request and identity sent by the computer device to the user
  • the information is hash-transformed to obtain the fifth data; the computer device decrypts the third data by using the public key of the first account to obtain the third decrypted data; and the computer device compares the fifth data with the third decrypted data to obtain a ratio. For the result, if the comparison result is consistent, the transfer request and the identity information sent by the user are not tampered with, and if the comparison result is inconsistent, the transfer request and the identity information sent by the user are tampered with.
  • the user can check the identity information and transfer request recorded by the client block block to ensure that the initial information recorded by the blockchain is true and has not been tampered with.
  • the computer device for verification may be a verification client issued by the gateway, and the client may emulate the gateway to encrypt or sign the identity information of the user and the transfer request of the user, and obtain encrypted or signed data.
  • the user sends a verification instruction to the client, where the verification instruction includes the identity information submitted by the user to the gateway and the original text of the transfer request.
  • the client After receiving the verification instruction of the user, the client obtains the identity information and the transfer request of the user according to the verification instruction, extracts the user identity information and the transfer request of the blockchain record, and verifies the identity information and the transfer request and the area of the user through verification. Whether the user identity information of the blockchain record and the transfer request are consistent.
  • the client encrypts the identity information and the transfer request of the user by using the public key of the first account to obtain the fourth data, and compares the fourth data with the user identity information and the transfer request recorded on the blockchain to obtain a comparison result. . If the comparison result is consistent, the initial data recorded on the blockchain is the initial data actually submitted by the user to the gateway; if the comparison result is inconsistent, the initial data recorded on the blockchain is actually submitted to the gateway by the user.
  • the client decrypts the third data by using the public key of the first account to obtain the third decrypted data, and performs hash transformation on the identity information and the transfer request of the user to obtain the fifth data, and then the fifth data.
  • the third decrypted data is compared to obtain a comparison result. If the comparison result is consistent, the initial data recorded on the blockchain is the initial data actually submitted by the user to the gateway; if the comparison result is inconsistent, the initial data recorded on the blockchain is actually submitted to the gateway by the user. The initial data is inconsistent and the user can appeal to the gateway.
  • the user is required to appeal to the gateway, or the sue of the gateway requesting the gateway to provide evidence may be, but is not limited to, the following situations: a situation: the transfer request received by the gateway is an error or a false request initiated by another user, and the gateway is The negligence in the verification process causes the blockchain to record the transfer event according to the error or the false request.
  • the gateway re-checks the material, the user can transfer the request according to the user's return request. The resource is returned to the original account of the resource, that is, the lost account in the transfer request.
  • the gateway when the user discovers that the target account has been frozen, and the transferred resource cannot be returned, the user can sue the gateway to the arbitration institution, and the arbitration institution requests the gateway to provide the received user identity information and transfer request. And use it as evidence. If the evidence can prove that the gateway error caused the user's loss, the gateway is responsible for the responsibility and compensation for the user. It should be noted that the evidence provided by the gateway to the arbitration institution cannot be tampered with. If the evidence is tampered with by the gateway, the arbitration institution will encrypt or sign the evidence again and compare it with the initial data recorded on the blockchain. The comparison result will be Inconsistent.
  • the gateway itself falsifies and fakes the real user dividend and transfer request into false initial data. When the user discovers, he can sue the gateway to the arbitration institution. The gateway can only provide the arbitrator with its fake false initial data as evidence. Otherwise, the evidence provided by the gateway will be inconsistent with the initial data recorded by the blockchain after being encrypted or signed.
  • the above method embodiment according to the present application provides a method of transferring resources of a lost account in a blockchain to a target account in the event that a user's account private key is lost, and after a resource transfer, when a dispute or fraud occurs At the time, it is possible to provide complete evidence that cannot be tampered with to retrieve resources or to identify responsibilities, thereby safeguarding the interests of all parties in the blockchain.
  • FIG. 5 is a flowchart of a method for processing account information in an optional blockchain according to an embodiment of the present application. As shown in FIG. 5, the method includes the following steps:
  • Step S501 the user generates a target account from the certificate center, and submits the transfer request and the identity information to the gateway.
  • the user loses the private key of the account, first generate a new account through the certificate center, and the newly generated account is used as the target account, wherein the certificate center is used to create the account, and the public key of all accounts is recorded in the user center. , address and account owner information.
  • the user sends a transfer request to the gateway according to the lost account and the target account, and the transfer request is used to request the gateway to transfer the resources in the lost account to the target account, and the user also needs to provide the identity information to the gateway to pass the This identity information proves that it is the owner of the lost account.
  • Step S502 the gateway receives the transfer request and the identity information submitted by the user, and obtains the owner information of the lost account from the certificate center according to the transfer request.
  • the gateway has the right to obtain the account information recorded therein from the certificate center, and the gateway obtains the identity information of the owner of the lost account from the certificate center according to the transfer request submitted by the user, to verify the identity information submitted by the user. For example, if the certificate center records the ID card number of the lost account owner or a scanned copy of the ID card, the user is required to provide a copy of the corresponding ID card and other identification materials. Alternatively, the certificate center records the voiceprint information of the lost account owner, and the user is required to provide the corresponding voiceprint material.
  • Step S503 the gateway compares the identity information submitted by the user with the owner information of the lost account.
  • the gateway compares the identity information submitted by the user with the information of the lost account owner obtained from the certificate center to determine whether the identity information submitted by the user is consistent with the owner information of the lost account, thereby verifying whether the user is already The owner of the lost account.
  • Step S504 When the identity information submitted by the user and the owner information of the lost account are consistent, the gateway encrypts the identity information and the transfer request submitted by the user by using the public key of the first account to obtain the second data.
  • the gateway In order to protect the privacy of the user and prevent the leakage of the user's personal data, the gateway first obtains the public key of the first account from the certificate center, and encrypts the identity information and the transfer request submitted by the user by using the public key of the first account to obtain the second data.
  • Step S505 the gateway uses the private key of the first account to sign the information of the lost account, the information of the target account, the resource list, and the second data, obtains the first data, generates an authentication request according to the first data, and submits the authentication request. Give the blockchain.
  • Step S506 the blockchain acquires the first data according to the received authentication request, and the plurality of devices in the blockchain use the public key of the first account to verify the first data, and the initial data is obtained after the verification succeeds.
  • the blockchain obtains the first data from the authentication request submitted by the gateway, and the first data is verified by multiple devices in the blockchain by using the public key of the first account. If the verification succeeds, the blockchain can be from the first The initial data is obtained in one data.
  • the blockchain since the verification of the identity information and the transfer request is completed by the gateway, the blockchain trusts the check result of the gateway. Therefore, the blockchain only needs to verify whether the signature of the initial data by the gateway is true, without Verify the user's identity information and transfer request.
  • step S507 the blockchain records the transfer event according to the initial data to transfer the resources in the lost account to the target account.
  • the blockchain can add a block to record the above transfer event, thereby completing the transfer of the above lost account resources to the target account.
  • Step S508 the blockchain sets a freeze period for the target account.
  • the blockchain sets a freeze period for the target account. During the freeze period, resources in the target account cannot be transferred. If the owner of the lost account raises an objection during the freezing period set by the blockchain to the target account, for example, the owner of the lost account does not actually initiate the transfer request, or the resource in the lost account is transferred.
  • the blockchain can return the lost account to the target account and return it to the lost account to protect the owner of the lost account. Rights.
  • the process of re-entering the resources in the target account to the lost account is the same as the process of transferring the resources of the lost account to the target account, and the owner of the lost account provides the identity information and the resource return request to the gateway.
  • the gateway verifies the identity information and the resource return request, and after the verification is passed, submits an authentication request to the blockchain according to the user identity information and the resource return request, and the blockchain records the transfer event according to the authentication request, thereby returning the resources in the target account. Has been lost in the account.
  • Step S509 when a dispute occurs, the gateway extracts initial data from the blockchain, and obtains second data encrypted by the public key of the first account from the initial data, and performs the second data by using the private key of the first account. Decrypt, get the decrypted data.
  • the decrypted data can be used as evidence to determine the above dispute to decide on the dispute that occurred.
  • Step S510 the gateway re-encrypts the decrypted data by using the public key of the first account to prove that the decrypted data has not been tampered with.
  • the gateway may re-encrypt the user identity information and the transfer request as evidence using the public key of the first account, and encrypt the encrypted data with the slave block.
  • the second data acquired on the chain is compared. If the encrypted data is inconsistent with the second data obtained from the blockchain, the user information and the transfer request used as evidence are tampered with instead of being true. .
  • the gateway may further obtain, from the database, the user-submitted identity information and the backup file of the original text of the transfer request, and the backup file may also be re-encrypted by the gateway using the public key of the first account and in the blockchain.
  • the second data is compared to prove the authenticity of the backup file.
  • the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation.
  • the technical solution of the present application which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present application.
  • FIG. 6 is a schematic diagram of an apparatus for processing account information in an optional blockchain according to an embodiment of the present application.
  • the apparatus may include: a first receiving unit 610, an obtaining unit 620, and a first ratio.
  • the unit 630 and the first submitting unit 640 may include: a first receiving unit 610, an obtaining unit 620, and a first ratio.
  • the first receiving unit 610 is configured to receive, by the user, a transfer request and an identity information, where the transfer request is used to request to transfer the resource in the lost account to the target account, where the target account is generated by the certificate center; 620, configured to acquire owner information of the lost account from the certificate center according to the transfer request; a first comparison unit 630, configured to compare the identity information with the owner information; a submitting unit 640, configured to submit an authentication request to the blockchain when the identity information and the owner information are aligned, so that the blockchain is in the blockchain according to the authentication request The transfer event is recorded, wherein the transfer event is used to indicate that the resource in the lost account is transferred to the target account.
  • the first receiving unit 610 in this embodiment may be used to perform step S302 in the foregoing embodiment of the present application.
  • the obtaining unit 620 in this embodiment may be used to perform step S304 in the foregoing embodiment of the present application.
  • the first comparison unit 630 in this embodiment may be used to perform step S306 in the foregoing embodiment of the present application.
  • the first submitting unit 640 in this embodiment may be used to perform step S308 in the foregoing embodiment of the present application.
  • the foregoing units are the same as the examples and application scenarios implemented by the corresponding steps, but are not limited to the contents disclosed in the foregoing embodiments. It should be noted that the above-mentioned unit can be operated as a part of the device in the hardware environment as shown in FIG. 2, and can be implemented by software or by hardware.
  • the first submitting unit includes: a signing module, configured to sign initial data by using a private key of the first account, to obtain first data, where the initial data includes information of the lost account, information of the target account, and identity Information, transfer request, and resource list, the resource list is a list of all resources waiting to be transferred in the lost account; a generating module is configured to generate an authentication request according to the first data; and a submitting module is configured to submit the initial data to the blockchain Authentication request.
  • a signing module configured to sign initial data by using a private key of the first account, to obtain first data, where the initial data includes information of the lost account, information of the target account, and identity Information, transfer request, and resource list, the resource list is a list of all resources waiting to be transferred in the lost account
  • a generating module is configured to generate an authentication request according to the first data
  • a submitting module is configured to submit the initial data to the blockchain Authentication request.
  • the signing module includes: an encryption submodule, configured to encrypt the identity information and the transfer request by using the public key of the first account to obtain the second data; and the first signature submodule, configured to utilize the private key of the first account
  • an encryption submodule configured to encrypt the identity information and the transfer request by using the public key of the first account to obtain the second data
  • the first signature submodule configured to utilize the private key of the first account
  • the signature module includes: a second signature sub-module, configured to use the private key of the first account to sign the identity information and the transfer request to obtain a third
  • the third signature sub-module is configured to use the private key of the first account to sign the information of the lost account, the information of the target account, the resource list, and the third data to obtain the first data.
  • the first submitting unit includes: an obtaining module, configured to acquire first data by using a blockchain; a verification module, configured to verify the first data by using a blockchain; and a recording module, after the verification is passed, The transfer event is recorded according to the initial data through the blockchain.
  • the verification module includes: an obtaining submodule, configured to obtain, by using multiple devices of the blockchain, a public key of the first account from the initial block of the certificate center or the blockchain; and the verification submodule is used for the pass zone
  • the plurality of devices of the block chain authenticate the first data using the public key of the first account.
  • the apparatus further includes: a setting unit, configured to submit an authentication request to the blockchain, so that the blockchain sets a freeze period for the target account through the blockchain after the transfer event is recorded in the blockchain according to the authentication request , wherein the resources in the target account are in a state where the transfer is not allowed during the freeze period.
  • a setting unit configured to submit an authentication request to the blockchain, so that the blockchain sets a freeze period for the target account through the blockchain after the transfer event is recorded in the blockchain according to the authentication request , wherein the resources in the target account are in a state where the transfer is not allowed during the freeze period.
  • the apparatus further includes: a first extracting unit, configured to, after submitting the authentication request to the blockchain, to cause the blockchain to extract the initial data from the blockchain after recording the transfer event in the blockchain according to the authentication request
  • the initial data includes the second data obtained by encrypting the identity information and the transfer request by using the public key of the first account;
  • the first decrypting unit is configured to decrypt the second data by using the private key of the first account,
  • a first decryption unit configured to compare whether the first decrypted data is consistent with the locally stored data
  • the first determining unit is configured to: when comparing the first decrypted data with the locally stored data, Make sure that the locally stored data has been tampered with.
  • the apparatus further includes: a second extracting unit, configured to, after submitting the authentication request to the blockchain, to cause the blockchain to extract the initial data from the blockchain after recording the transfer event in the blockchain according to the authentication request
  • the initial data includes third data obtained by signing the identity information and the transfer request by using a private key of the first account; and the second decrypting unit is configured to use the public key of the first account to the third data Decrypting to obtain second decrypted data; a first transforming unit, configured to perform hash transform on the locally stored data to obtain hash-converted data; and a third comparing unit, configured to compare the second decrypted data with the Whether the data after the transformation is consistent; the second determining unit is configured to determine that the locally stored data is tampered when the second decrypted data is compared with the data after the hash transformation.
  • the apparatus further includes: a third extracting unit, configured to extract initial data from the blockchain according to the verification instruction sent by the user, wherein the initial data comprises encrypting the identity information and the transfer request by using the public key of the first account
  • the second data obtained, the verification instruction is used to instruct to check the second data
  • the encryption unit is configured to encrypt the transfer request and the identity information sent by the user by using the public key of the first account to obtain the fourth data
  • the comparison unit is configured to compare whether the second data and the fourth data are consistent, and obtain a comparison result, wherein if the comparison result is consistent, the transfer request and the identity information sent by the user are not tampered, if the comparison result is Inconsistent, the transfer request and identity information sent by the user are tampered with.
  • the apparatus further includes: a fourth extracting unit, configured to submit an authentication request to the blockchain, so that the blockchain records the transfer event in the blockchain according to the authentication request, and the slave unit sends the verification command according to the verification command sent by the user.
  • Initial data is extracted from the blockchain, wherein the initial data includes third data obtained by signing the identity information and the transfer request by using the private key of the first account, and the verification instruction is used to instruct to check the third data;
  • the second transform unit And performing a hash transformation on the transfer request and the identity information sent by the user to obtain the fifth data;
  • the third decryption unit is configured to decrypt the third data by using the public key of the first account to obtain the third decrypted data;
  • the comparison unit is configured to compare whether the fifth data and the third decrypted data are consistent, and obtain a comparison result, wherein if the comparison result is consistent, the transfer request and the identity information sent by the user are not tampered, if the comparison result Inconsistent, the transfer request and identity information sent by the
  • the foregoing modules are the same as the examples and application scenarios implemented by the corresponding steps, but are not limited to the contents disclosed in the foregoing embodiments. It should be noted that the foregoing module may be implemented in a hardware environment as shown in FIG. 2 as part of the device, and may be implemented by software or by hardware, where the hardware environment includes a network environment.
  • a storage medium wherein a computer program is stored in the storage medium, wherein the computer program is configured to execute the method described above at runtime.
  • an electronic device comprising a memory and a processor, wherein the memory stores a computer program, the processor being arranged to perform the method described above by the computer program.
  • a server for implementing a method for processing account information in the above blockchain.
  • the server can function as the above electronic device.
  • FIG. 7 is a structural block diagram of a server according to an embodiment of the present application.
  • the server may include: one or more (only one shown in the figure) processor 701, memory 703, and transmission device 705. (As in the transmitting apparatus in the above embodiment), as shown in FIG. 7, the terminal may further include an input/output device 707.
  • the memory 703 can be used to store the software program and the module, such as the processing method of the account information in the blockchain and the program instruction/module corresponding to the device in the embodiment of the present application, and the processor 701 runs the software program stored in the memory 703. And a module to perform various functional applications and data processing, that is, to implement the processing method of the account information in the above blockchain.
  • Memory 703 can include high speed random access memory, and can also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory.
  • memory 703 can further include memory remotely located relative to processor 701, which can be connected to the terminal over a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • the above described transmission device 705 is used to receive or transmit data via a network, and can also be used for data transmission between the processor and the memory.
  • Specific examples of the above network may include a wired network and a wireless network.
  • the transmission device 705 includes a Network Interface Controller (NIC) that can be connected to other network devices and routers via a network cable to communicate with the Internet or a local area network.
  • the transmission device 705 is a Radio Frequency (RF) module for communicating with the Internet wirelessly.
  • NIC Network Interface Controller
  • RF Radio Frequency
  • the memory 703 is used to store an application.
  • the processor 701 can call the application stored in the memory 703 through the transmission device 705 to perform the following steps:
  • the processor 701 is configured to: receive a user to send a transfer request and identity information, where the transfer request is used to request to transfer resources in the lost account to the target account, where the target account is generated by the certificate center; Obtaining owner information of the lost account from the certificate center according to the transfer request; comparing the identity information with the owner information; comparing the identity information and the owner information When consistent, submit an authentication request to the blockchain to cause the blockchain to record a transfer event in the blockchain according to the authentication request, wherein the transfer event is used to indicate that the lost account is to be The resources are transferred to the target account.
  • the processor 701 can also perform other method steps in the foregoing embodiments.
  • a scheme for processing account information in a blockchain is provided.
  • the resources in the lost account will be transferred to the blockchain.
  • the purpose in the target account thereby realizing the technical effect of not verifying the private key signature of the lost account when transferring the resources in the lost account to the target account, thereby solving the loss of the private key of the account in the blockchain.
  • the technical problem of the account is uneasy.
  • the terminal may be a smart phone (such as an Android mobile phone, an iOS mobile phone, etc.), a tablet computer, a palmtop computer, and a mobile Internet device (MID). Terminal equipment such as PAD.
  • FIG. 7 does not limit the structure of the above electronic device.
  • the terminal may also include more or fewer components (such as a network interface, display device, etc.) than shown in FIG. 7, or have a different configuration than that shown in FIG.
  • Embodiments of the present application also provide a storage medium.
  • the foregoing storage medium may be used to store program code for executing a processing method of account information in a blockchain.
  • the foregoing storage medium may be located on at least one of the plurality of network devices in the network shown in the foregoing embodiment.
  • the storage medium is arranged to store program code for performing the following steps:
  • the receiving user sends a transfer request and identity information, where the transfer request is used to request that the resources in the lost account be transferred to the target account, and the target account is generated by the certificate center;
  • the storage medium of the embodiment is used to store the program instructions for implementing the processing method steps of the foregoing embodiment.
  • the embodiment is no longer used. Narration.
  • the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • a mobile hard disk e.g., a hard disk
  • magnetic memory e.g., a hard disk
  • the integrated unit in the above embodiment if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in the above-described computer readable storage medium.
  • the technical solution of the present application in essence or the contribution to the prior art, or all or part of the technical solution may be embodied in the form of a software product, which is stored in a storage medium.
  • a number of instructions are included to cause one or more computer devices (which may be a personal computer, server or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the disclosed client may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • multiple units or components may be combined or may be Integrate into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, unit or module, and may be electrical or otherwise.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Theoretical Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Bioethics (AREA)
  • General Health & Medical Sciences (AREA)
  • Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Computer Hardware Design (AREA)
  • Databases & Information Systems (AREA)
  • Computing Systems (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Computer And Data Communications (AREA)
  • Storage Device Security (AREA)

Abstract

一种区块链中账户信息的处理方法和装置、存储介质和电子装置。其中，该方法包括：计算机设备接收用户发送转移请求和身份信息(S302)，其中，转移请求用于请求将已丢失账户中的资源转移到目标账户中，目标账户由证书中心生成；计算机设备根据转移请求从证书中心获取已丢失账户的所有者信息(S304)；计算机设备对身份信息和所有者信息进行比对(S306)；计算机设备在比对出身份信息和所有者信息一致时，向区块链提交认证请求，以使区块链根据认证请求在区块链中记录转移事件(S308)，其中，转移事件用于指示将已丢失账户中的资源转移到目标账户中。该方法可以解决由于区块链中账户的私钥丢失造成的账户不安全的技术问题。

Description

区块链中账户信息的处理方法和装置、存储介质和电子装置
本申请要求于2017年02月28日提交中国专利局、申请号为201710120699.9、发明名称为“区块链中账户信息的处理方法和装置、存储介质和电子装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及区块链领域，具体而言，涉及一种区块链中账户信息的处理方法和装置、存储介质和电子装置。
背景技术
区块链中的账户，通常由一对公私钥组成(非对称密钥)。账户的地址通常由公钥通过哈希变换得到，而私钥用于对账户中资源的交易进行证明和授权。用户以账户私钥证明其身份，交易其账户中的资源。一旦私钥丢失，账户中的资源便没有办法转移或者交易。
为了避免在私钥丢失的情况下无法对账户中的资源进行转移或者交易，现有技术通常采用以下两种方案：
方案1：采用中介机构帮助用户托管用户的私钥。
方案2：将账户的权限托管给第三方，在账户私钥丢失时，代为交易或转移资源。例如利用智能合约技术或类似技术进行托管。
然而，上述方案必须要求在私钥丢失前进行托管，如果用户在在账户丢失前未托管，则这些方案无效。另外，当把私钥或者权限托管给第三方时，无法完全保证资源的安全，如果资源丢失，也可能无法证明是用户本人还是托管方造成的，导致账户不安全。
针对上述的问题，目前尚未提出有效的解决方案。
发明内容
本申请实施例提供了一种区块链中账户信息的处理方法和装置、存储介质和电子装置，可以解决于区块链中账户的私钥丢失造成的账户不安的技术问题。
根据本申请实施例的一个方面，提供了一种区块链中账户信息的处理方法，所述处理方法通过计算机设备执行，所述处理方法包括：计算机设备接收用户发送转移请求和身份信息，其中，所述转移请求用于请求将已丢失账户中的资源转移到目标账户中，所述目标账户由证书中心生成；计算机设备根据所述转移请求从所述证书中心获取所述已丢失账户的所有者信息；计算机设备对所述身份信息和所述所有者信息进行比对；计算机设备在比对出所述身份信息和所述所有者信息一致时，向区块链提交认证请求，以使所述区块链根据所述认证请求在所述区块链中记录转移事件，其中，所述转移事件用于指示将所述已丢失账户中的资源转移到所述目标账户中。
根据本申请实施例的一方面，还提供了一种区块链中账户信息的处理装置，所述处理装置被设置在计算机设备中，所述处理装置包括：第一接收单元，用于接收用户发送转移请求和身份信息，其中，所述转移请求用于请求将已丢失账户中的资源转移到目标账户中，所述目标账户由证书中心生成；获取单元，用于根据所述转移请求从所述证书中心获取所述已丢失账户的所有者信息；第一比对单元，用于对所述身份信息和所述所有者信息进行比对；第一提交单元，用于在比对出所述身份信息和所述所有者信息一致时，向区块链提交认证请求，以使所述区块链根据所述认证请求在所述区块链中记录转移事件，其中，所述转移事件用于指示将所述已丢失账户中的资源转移到所述目标账户中。
根据本申请实施例的一方面，还提供了一种存储介质，所述存储介质 中存储有计算机程序，其中，所述计算机程序被设置为运行时执行上述的方法。
根据本申请实施例的一方面，还提供了一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为通过所述计算机程序执行上述的方法。
在本申请实施例中，采用接收用户发送转移请求和身份信息，其中，转移请求用于请求将已丢失账户中的资源转移到目标账户中，目标账户由证书中心生成；根据转移请求从证书中心获取已丢失账户的所有者信息；对身份信息和所有者信息进行比对；在比对出身份信息和所有者信息一致时，向区块链提交认证请求，以使区块链根据认证请求在区块链中记录转移事件，其中，转移事件用于指示将已丢失账户中的资源转移到目标账户中，通过比对用户提供的身份信息和已丢失账户所有者信息是否一致，并在比对一致时，向区块链提交认证请求，达到了在区块链中将已丢失账户中的资源转移到目标账户中的目的，从而实现了在将已丢失账户中的资源转移到目标账户中时，无需验证丢失账户的私钥签名的技术效果，进而解决了于区块链中账户的私钥丢失造成的账户不安的技术问题。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1是根据现有技术的区块链的示意图；
图2是根据本申请实施例的区块链中账户信息的处理方法的硬件环境的示意图；
图3是根据本申请实施例的一种可选的区块链中账户信息的处理方法的流程图；
图4是根据本申请实施例的第一数据的字段列表的示意图；
图5是根据本申请实施例的一种可选的区块链中账户信息的处理方法的流程图；
图6是根据本申请实施例的一种可选的区块链中账户信息的处理装置的示意图；以及
图7是根据本申请实施例的一种终端的结构框图。
具体实施方式
为了使本技术领域的人员更好地理解本申请方案，下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分的实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都应当属于本申请保护的范围。
需要说明的是，本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
名词解释：
区块链：如图1所示，区块链以区块为单位组织数据。全网所有的交易记录都可以以交易单的形式存储在区块链中。其中，区块链中的第一个区块为初始区块，也称创世区块。每形成一次交易，就记录在一个区块中，且区块中记录的信息对全网透明，多个区块按照一定的顺序连在一起形成 区块链。
账户：区块链中的账户，通常由一对公私钥组成(非对称密钥)。账户的地址通常由公钥通过哈希变换得到，而私钥用于证明和授权对账户中资产的交易，一旦私钥丢失，一般无法进行常规的交易了。本文的账户概念类似于比特币的比特币地址概念。本文中的已丢失账户以及目标账户均为区块链中的账户。
证书中心：证书中心用于创建区块链账户，其记录了账户的公钥、地址和账户所有者的身份信息。
私钥丢失：本文中，私钥丢失、账户丢失可理解为同义词。“旧账户”即为已丢失的账户。
特殊交易：在用户丢失私钥情况下，通过超级账户，把丢失的账户中的资产转移到一个新账户的交易，称为特殊交易。
第一账户：指区块链中的超级账户，超级账户可以是在区块链网络中被认可的，不可伪造的账户。其可以用于特殊交易。也可能用于其他用途，比如在区块链中创造资产等，第一账户的公钥记录在证书中心和区块链的初始区块中。
网关：即资产网关，资产网关是区块链的一种有特殊权限的用户，超级账户即其帐号。资产网关在区块链中能够，将发行资产、资产找回等请求发送给区块链业务。网关可以是另外一套系统，例如可以是电子柜台系统，负责处理用户和业务请求，再把这些请求通过区块链接口(通过超级账户)发送给区块链。代表资产网关机构，是第一账户(超级账户)的所有者，通常为区块链网络中的权威机构。本文中其负责受理用户找回资源的请求。该网关可以设置在终端或者服务器中，由终端或者服务器来实现网关的功能。
根据本申请实施例，提供了一种区块链中账户信息的处理方法的方法实施例。
可选地，在本实施例中，上述区块链中账户信息的处理方法可以应用于如图2所示的由服务器202和终端204所构成的硬件环境中。如图2所示，服务器202通过网络与终端204进行连接，上述网络包括但不限于：广域网、城域网或局域网，终端204并不限定于PC、手机、平板电脑等。本申请实施例的区块链中账户信息的处理方法可以由服务器202来执行，也可以由终端204来执行，还可以是由服务器202和终端204共同执行。其中，终端204执行本申请实施例的区块链中账户信息的处理方法也可以是由安装在其上的客户端来执行。
图2所示的服务器202和终端204所构成的硬件环境主要为了执行本实施例的区块链中账户信息的处理方法，该区块链中账户信息的处理方法中的区块链可以设置在与图2所示的硬件环境中不同的服务器中。也就是说，本实施例的服务器202和终端204所构成的硬件环境用来实现网关的环境，与区块链可以是不同的两个系统。可选地，图2所示的服务器202可以是一个服务器集群，该服务器集群中的部分服务器可以用于实现网关的功能，另外一部分服务器可以实现区块链的功能。或者，在一个服务器上同时实现网关和区块链的功能。
需要说明的是，本实施例的区块链中的设备可以理解为一种计算机设备，如终端或者服务器。该区块中的设备可以作为区块链的一个节点，多个区块链的节点构成区块链，多个节点对应的至少一个设备实现区块链的功能。区块链执行的方法步骤或者流程即是由区块链中的节点执行的。
图3是根据本申请实施例的一种可选的区块链中账户信息的处理方法的流程图，该处理方法通过计算机设备执行，该计算机设备包括终端和服务器，该计算机设备可以实现网关的功能，网关用来执行该区块链中账户信息的处理方法。如图3所示，该方法可以包括以下步骤：
步骤S302，计算机设备接收用户发送转移请求和身份信息，其中，转移请求用于请求将已丢失账户中的资源转移到目标账户中，目标账户由证书中心生成；
步骤S304，计算机设备根据转移请求从证书中心获取已丢失账户的所有者信息；
步骤S306，计算机设备对身份信息和所有者信息进行比对；
步骤S308，计算机设备在比对出身份信息和所有者信息一致时，向区块链提交认证请求，以使区块链根据认证请求在区块链中记录转移事件，其中，转移事件用于指示将已丢失账户中的资源转移到目标账户中。
通过上述步骤S302至步骤S308，通过比对用户提供的身份信息和已丢失账户所有者信息是否一致，并在比对一致时，向区块链提交认证请求，以在区块链中将已丢失账户中的资源转移到目标账户，可以解决于区块链中账户的私钥丢失造成的账户不安的技术问题，无需验证丢失账户的私钥签名即可将已丢失账户中的资源转移到目标账户，进而达到了提高账户安全性的技术效果。
在步骤S302提供的技术方案中，用户在丢失区块链账户的私钥时，可以向网关发送身份信息和转移请求，以将已丢失账户中的资源转移到目标账户中，具体地，在用户丢失账户的私钥时，先通过证书中心生成一个新的账户，将新生成的账户作为目标账户，其中，可选的，证书中心用于创建账户，并且在证书中心中记录了所有账户的公钥、地址和账户所有者的信息。用户根据已丢失的账户和目标账户，向网关发送转移请求，该转移请求用于向网关请求将已丢失账户中的资源转移到目标账户中，同时，用户还需要向网关提供身份信息，以通过该身份信息证明自己是已丢失账户的所有者。上述网关可以但不限定是由区块链网络中的权威机构所设置的服务器或者电子平台或者柜台服务，网关用于代表该权威机构接收用户提交的转移请求和身份信息。用户提交的身份信息视具体规定，可以是其身份证件的纸质材料或者纸质材料的扫描件，也或者是能够证明用户身份及其意愿的其它格式的文件，例如：人脸图像、瞳孔扫描信息等。
在步骤S304提供的技术方案中，网关具有从证书中心获取其中记录的账户信息的权限。为了对用户提交的身份信息进行验证，网关根据用户 提交的转移请求，从证书中心获取已丢失账户的所有者的信息，已丢失账户所有者的信息为已丢失账户所有者的身份信息。例如，证书中心记录了已丢失账户所有者的身份证号码或者身份证复印件的扫描件，则需要用户提供相应的身份证复印件等证明身份的材料。或者，证书中心记录了已丢失账户所有者的声纹信息，则需要用户提供相应的声纹材料。
在步骤S306提供的技术方案中，网关将用户提交的身份信息与从证书中心获取到的已丢失账户所有者的信息进行比对，以确定用户提交的身份信息与丢失账户的所有者信息是否一致，进而验证出该用户是否是已丢失账户的所有者。
在步骤S308提供的技术方案中，如果经过验证，用户提交的身份信息与已丢失账户的所有者的信息不一致，则该用户的身份信息验证失败，即该用户不是已丢失账户的所有者，用户向网关提交的转移请求不合法，网关不会对该转移请求作出响应；如果用户提交的身份信息与已丢失账户的所有者信息一致，则用户的身份信息验证成功，该用户即为已丢失的账户的所有者，网关对该用户提交的转移请求作出响应。具体地，网关根据用户提交的转移请求，向区块链提交认证请求，以使区块链记录一个转移事件，指示将上述已丢失账户的资源转移到目标账户中。例如，在区块链中新增一个区块，用来记录上述转移事件，从而完成了将上述已丢失账户的资源转移到目标账户中。
本申请实施例所提供的方法可以应用于各种区块链模式下的数字支付场景中，如：区块链模式下的银行、有价证券、黄金交易的账户交易，也可以是区块链模式下的虚拟资源的交易场景中，如：网络游戏中游戏账户的虚拟资源的交易等。
可选地，网关向区块链提交认证请求包括：利用第一账户的私钥对初始数据进行签名，得到第一数据，其中，初始数据包括已丢失账户的信息、目标账户的信息、身份信息、转移请求和资源列表，资源列表为已丢失账户中等待转移的所有资源的列表；根据第一数据生成认证请求；向区块链 提交携带有初始数据的认证请求。
作为一种可选的实施例，网关在向区块链提交认证请求时，先根据接收到的转移请求获取初始数据，再对初始数据进行签名得到第一数据，如图4所示，可选地，在认证请求中包括有初始数据和网关对初始数据的签名，在初始数据中包含了已丢失账户的信息、目标账户的信息、用户提交的身份信息、转移请求以及需要从已丢失账户中转移到目标账户的所有资源的列表。网关根据上述第一数据及初始数据生成认证请求，最后将认证请求提交给区块链。
区块链中存在第一账户，可选地，第一账户可以是区块链中的超级账号，第一账户在区块链中可以是唯一的并且不可伪造的账户，而网关是第一账户的所有者，具有第一账户的私钥。网关可以利用第一账户私钥对初始数据进行签名从而得到第一数据。网关向区块链提交的认证请求是根据第一数据生成的，而第一数据是利用第一账户的私钥对初始数据进行签名得到的，网关作为第一账户的所有者且拥有第一账户私钥，要对上述认证请求，也即初始数据中信息的真实性承担责任。因此，区块链只需要验证网关利用私钥对初始数据进行签名是否合法，并在合法的情况下确认认证通过，记录转移事件。
可选地，计算机设备利用第一账户的私钥对初始数据进行签名，得到第一数据包括：计算机设备利用第一账户的公钥对身份信息和转移请求进行加密，得到第二数据；计算机设备利用第一账户的私钥对已丢失账户的信息、目标账户的信息、资源列表和第二数据进行签名，得到第一数据。
作为一种可选的实施例，为了保护用户的隐私，防止用户的个人资料泄漏，可以对用户提交的身份信息和转移请求进行加密。具体地，网关在利用上述第一账户的私钥对初始数据进行签名得到第一数据时，先从证书中心获取第一账户的公钥，并利用第一账户的公钥对用户提交的身份信息和转移请求进行加密得到第二数据；再利用第一账户的私钥对已丢失账户的信息、目标账户的信息、资源列表及上述第二数据进行签名，得到第一 数据。网关根据第一数据生成认证请求，并将认证请求提交到区块链之后，由于用户提交的身份信息和转移请求被第一账户的公钥加密过，其他人仅可以从区块链上获取到加密后的用户的身份信息和转移请求，而无法获取到用户的身份信息和转移请求的原文。
本申请还提供了一种可选实施例，该可选实施例中，计算机设备利用第一账户的私钥对初始数据进行签名，得到第一数据包括：计算机设备利用第一账户的私钥对身份信息和转移请求进行签名，得到第三数据；计算机设备利用第一账户的私钥对已丢失账户的信息、目标账户的信息、资源列表和第三数据进行签名，得到第一数据。
网关在利用上述第一账户的私钥对初始数据进行签名得到第一数据时，先利用第一账户的私钥对用户提交的身份信息和转移请求进行签名，得到第三数据；再利用第一账户的私钥对已丢失账户的信息、目标账户的信息、资源列表及上述第三数据进行签名，得到第一数据。由于网关利用第一账户的私钥对用户提交的身份信息和转移请求进行签名的过程是先对用户提交的身份信息和转移请求进行哈希变换，再对其进行加密从而得到第三数据，而哈希变换的过程是不可逆的，因此，在网关根据第一数据生成认证请求，并将认证请求提交到区块链之后，即使其他人能够解密，得到的也是经过哈希变换后的身份信息和转移请求，无法获得用户的身份信息和转移请求的原文，可以保护用户的隐私不被泄露。
可选地，在比对出身份信息和所有者信息一致时，向区块链提交认证请求，以使区块链根据认证请求在区块链中记录转移事件包括：区块链中的设备根据认证请求获取第一数据；区块链中的设备对第一数据进行验证；在验证通过后，区块链中的设备根据初始数据记录转移事件。
作为一种可选的实施例，在网关将认证请求提交给区块链，以使区块链根据认证请求记录转移事件的过程中，区块链从网关提交的认证请求中获取第一数据，并对第一数据进行验证，在验证成功之后，区块链信任该认证请求中携带的初始数据，并根据认证请求中的初始数据记录转移事件。
区块链对第一数据进行验证时，只需从证书中心获取第一账户的公钥，并利用第一账户的公钥对第一数据进行验证，如果验证成功，则区块链信任该认证请求，并获取该认证请求中携带的初始数据，以及根据该初始数据记录转移事件。如图4所示，在区块链对第一数据的认证过程中，区块链仅对图4中第五列的签名进行验证，而不需要对前4列的初始数据进行验证，第五列的签名是网关利用第一账户的私钥对前面四列初始数据的签名，当区块对第五列的签名验证成功之后，即选择信任前四列的初始数据，而前面四列初始数据的真实性由网关来负责验证，即由网关承担对初始数据的验证责任。
在上述验证过程中，由于身份信息和转移请求的核对是由网关完成的，区块链信任网关的核对结果，因此，区块链只需验证网关对初始数据的签名是否是真的，而无需对用户的身份信息和转移请求进行验证。只要区块链验证网关对初始数据的签名为真，则认可接收到的认证请求，并记录转移事件，从而将已丢失账户中的资源转移到目标账户中。
可选地，区块链对第一数据进行验证包括：区块链的多个设备从证书中心或者区块链的初始区块中获取第一账户的公钥；区块链的多个设备利用第一账户的公钥对第一数据进行验证。
作为一种可选的实施例，区块链包括多个设备。需要说明的是，本实施例中的区块链包括多个区块节点，区块链包括的多个设备对应多个区块节点，即一个区块节点可以对应一个设备。在区块链对第一数据进行验证的过程中，区块链的多个区块中每一个设备从证书中心或者区块链中的初始区块中获取第一账户的公钥，并利用第一账户的公钥对第一数据进行验证，如果多个设备中的多数设备都验证成功，则区块链对第一数据的验证成功，区块选择信任该第一数据中的初始数据。在每个设备对第一数据进行验证的过程中，每个设备仅需验证网关对初始数据的签名是否为真，而不需要对初始数据中用户提交的身份信息和转移请求进行验证。由网关承担对用户提交的身份信息和转移申请的真实性的进行验证的责任。
可选地，在向区块链提交认证请求，以使区块链根据认证请求在区块链中记录转移事件之后，方法还包括：区块链中的设备对目标账户设置冻结期，其中，在冻结期内目标账户中的资源处于不允许转移的状态。
作为一种可选的实施例，为了解决错误地将已丢失账户中的资源转移到目标账户造成已丢失账号的损失，在区块链根据网关提交的认证请求记录转移事件之后，区块链对目标账户设置一个冻结期，在该冻结期内，目标账户中的资源无法被转移。如果在区块链对目标账户设置的冻结期内，已丢失账户的所有者提出异议，例如：已丢失账户的所有者实际并未发起转移请求，或者在对已丢失账户中的资源进行转移的过程中发生错误，或者已丢失账户的所有者认为网关或者其他人存在欺诈等，区块链可以将已丢失账户转移到目标账户的资源重新退回给已丢失账户，以保护已丢失账户的所有者的权益。具体地，将目标账户中的资源重新退回给已丢失账户的过程与将已丢失账户的资源转移到目标账户的过程相同，由已丢失账户的所有者向网关提供身份信息和资源退回请求，由网关验证身份信息和资源退回请求，并在验证通过后根据用户的身份信息和资源退回请求向区块链提交认证请求，区块链根据认证请求记录转移事件，从而将目标账户中的资源退回到已丢失账户中。
可选地，计算机设备在向区块链提交认证请求，以使区块链根据认证请求在区块链中记录转移事件之后，方法还包括：计算机设备从区块链中提取初始数据，其中，初始数据包括网关利用第一账户的公钥对身份信息和转移请求进行加密后得到的第二数据；计算机设备利用第一账户的私钥对第二数据进行解密，得到第一解密数据；计算机设备比对第一解密数据与网关本地存储的数据是否一致；计算机设备如果比对出第一解密数据与本地存储的数据不一致，则确定本地存储的数据被篡改。
作为一种可选的实施例，为了避免用户发送给网关的初始数据在被提交给区块链的过程中被篡改，还可以对区块链所记录的初始数据进行验证。例如：在将已丢失账户中的资源转移到目标账户中之后，已丢失账户的所 有者提出网关或者他人存在欺诈，要求退回被转移的资源，或者目标账户的冻结期已经结束，转移到目标账户的资源已经被再次转移，从而无法将其退回到已丢失的账户，需要通过司法手段对已丢失账户的所有者进行赔偿时，需要网关提供存储在本地的身份信息和转移请求作为证据，并可以通过验证的方式证实网关提供的身份信息和转移请求即是网关提交给区块链的身份信息和转移请求，而未被篡改过。具体地，如果网关提交给区块链的认证请求中包含的身份信息和转移数据是利用第一账户的公钥进行加密的，则网关从区块链中提取初始数据，在该初始数据中即包括了网关利用第一账户的公钥对用户提交的身份信息和转移请求进行加密得到的第二数据，网关利用第一账户的私钥对第二数据进行解密即可得到用户提交的身份信息和转移请求的原文，即第一解密数据。网关对第一解密数据与网关本地存储的数据进行比对，如果第一解密数据与网关本地存储的数据一致，则网关本地存储的数据未被篡改，如果第一解密数据与网关本地存储的数据不一致，则网关本地存储的数据被篡改过。
可选地，计算机设备在向区块链提交认证请求，以使区块链根据认证请求在区块链中记录转移事件之后，方法还包括：计算机设备从区块链中提取初始数据，其中，初始数据包括利用第一账户的私钥对身份信息和转移请求进行签名后得到的第三数据；计算机设备利用第一账户的公钥对第三数据进行解密，得到第二解密数据；计算机设备对本地存储的数据进行哈希变换，得到哈希变换后的数据；计算机设备比对第二解密数据与哈希变换后的数据是否一致；如果比对出第二解密数据与哈希变换后的数据不一致，则计算机设备确定本地存储的数据被篡改。
作为一种可选的实施例，在验证网关提供的身份信息和转移请求是否与网关提交给区块链的身份信息和转移请求一致时，如果网关提交给区块链的认证请求中包含的身份信息和转移数据是利用第一账户的私钥进行签名的，则网关从区块链中提取初始数据，在该初始数据中即包括了网关利用第一账户的私钥对用户提交的身份信息和转移请求进行签名得到的第三数据，网关利用第一账户的公钥对第三数据进行解密即可得到第二解 密数据，该数据是身份信息和转移请求经过哈希转换后得到的。网关对本地存储的身份信息和转移请求进行哈希变换，得到哈希变换后的数据，将第二解密数据与上述哈希变换后的数据进行比对，如果第二解密数据与哈希变换后的数据一致，则网关本地存储的数据与区块链记录的数据一致，网关本地存储的数据未被篡改，如果第二解密数据与哈希变换后的数据不一致，则网关本地存储的数据与区块链上记录的数据不一致，网关本地存储的数据被篡改过。
可选地，在向区块链提交认证请求，以使区块链根据认证请求在区块链中记录转移事件之后，方法还包括：计算机设备根据用户发送的核查指令从区块链中提取初始数据，其中初始数据包括利用第一账户的公钥对身份信息和转移请求进行加密后得到的第二数据，核查指令用于指示对第二数据进行核查；计算机设备利用第一账户的公钥对用户发送的转移请求和身份信息进行加密，得到第四数据；计算机设备比对第二数据与第四数据是否一致，得到比对结果，其中，如果比对结果为一致，则用户发送的转移请求和身份信息未被篡改，如果比对结果为不一致，则用户发送的转移请求和身份信息被篡改。
可选地，在向区块链提交认证请求，以使区块链根据认证请求在区块链中记录转移事件之后，方法还包括：计算机设备根据用户发送的核查指令从区块链中提取初始数据，其中初始数据包括利用第一账户的私钥对身份信息和转移请求进行签名后得到的第三数据，核查指令用于指示对第三数据进行核查；计算机设备对用户发送的转移请求和身份信息进行哈希变换，得到第五数据；计算机设备利用第一账户的公钥对第三数据进行解密，得到第三解密数据；计算机设备比对第五数据与第三解密数据是否一致，得到比对结果，其中，如果比对结果为一致，则用户发送的转移请求和身份信息未被篡改，如果比对结果为不一致，则用户发送的转移请求和身份信息被篡改。
作为一种可选的实施例，用户可以通过客户端对区块链记录的身份信 息和转移请求进行核查，以确保区块链记录的初始信息为真实的未被篡改过的。可选的，用于核查的计算机设备可以是由网关发布的核查客户端，该客户端可以模仿网关对用户的身份信息和用户的转移请求进行加密或者签名，并得到加密或者签名后的数据。具体地，在区块链已经根据网关提交的认证请求记录转移事件之后，用户向客户端发送核查指令，该核查指令中包括用户向网关提交的身份信息和转移请求的原文。客户端接收到用户的核查指令后，根据该核查指令获取用户的身份信息和转移请求，再提取区块链记录的用户身份信息和转移请求，通过验证来证实用户的身份信息和转移请求与区块链记录的用户身份信息和转移请求是否一致。具体地，如果网关提交给区块链的认证请求中包含的身份信息和转移数据是经过加密的，即利用第一账户的公钥对身份信息和转移数据进行加密得到的第二数据，则客户端利用第一账户的公钥对用户的身份信息和转移请求进行加密，得到第四数据，再将第四数据与区块链上记录的用户身份信息和转移请求进行比对，得到比对结果。如果比对结果为一致，说明区块链上记录的初始数据即是用户实际提交给网关的初始数据；如果比对结果为不一致，说明区块链上记录的初始数据与用户实际提交给网关的初始数据不一致，用户需要向网关申诉；如果网关提交给区块链的认证请求中包含的身份信息和转移数据是经过签名的，即利用第一账户的私钥对身份信息和转移数据进行签名得到的第三数据，则客户端利用第一账户的公钥对第三数据进行解密得到第三解密数据，同时对用户的身份信息和转移请求进行哈希变换得到第五数据，再将第五数据与第三解密数据进行比对，得到比对结果。如果比对结果为一致，说明区块链上记录的初始数据即是用户实际提交给网关的初始数据；如果比对结果为不一致，说明区块链上记录的初始数据与用户实际提交给网关的初始数据不一致，用户可以向网关申诉。
可选地，需要用户向网关申诉，或者起诉网关要求网关提供证据可能但不限定于存在以下几种情况：一种情况：网关接收到的转移请求为其他用户发起的错误或者虚假请求，网关在验证进程中疏忽导致区块链根据该错误或者虚假请求记录了转移事件，用户发现时，尚处于目标账户的冻结 期，在网关对材料进行重新核对之后，可以根据用户的退回请求将已转移的资源重新退回到该资源的原账户中，也即转移请求中的已丢失账户。另一种情况：在用户发现时，已超过了目标账户的冻结期，已转移的资源无法退回，则用户可以向仲裁机构起诉网关，由仲裁机构要求网关提供接收到的用户身份信息和转移请求，并将其作为证据，如果该证据能够证明网关失误造成了用户的损失，则由网关负责承担责任并对用户进行赔偿。需要说明的是，网关提供给仲裁机构的证据无法篡改，如果该证据被网关篡改，仲裁机构通过将证据再次加密或者签名，并与区块链上记录的初始数据进行比对，比对结果将不一致。第三种情况：网关自身弄虚作假，将真实的用户份息和转移请求伪造成虚假的初始数据。当用户发现后可以向仲裁机构起诉网关。网关只能向仲裁机构提供其伪造的虚假初始数据作为证据，否则网关提供的证据经过加密或者签名之后，将与区块链记录的初始数据不一致。
上述根据本申请的方法实施例提供了在用户的账户私钥丢失的情况下，将区块链中已丢失账户的资源转移到目标账户的方法，并且在资源转移之后，当发生纠纷或者欺诈行为时，能够提供完整的无法篡改的证据来找回资源或者鉴定责任，从而保障区块链中各方的利益。
图5是根据本申请实施例的一种可选的区块链中账户信息的处理方法的流程图，如图5所示，该方法包括以下步骤：
步骤S501，用户从证书中心中生成目标账户,并向网关提交转移请求和身份信息。在用户丢失账户的私钥时，先在通过证书中心生成一个新的账户，将新生成的账户作为目标账户，其中，证书中心用于创建账户，并且在用户中心中记录了所有账户的公钥、地址和账户所有者的信息。用户根据已丢失的账户和目标账户，向网关发送转移请求，该转移请求用于向网关请求将已丢失账户中的资源转移到目标账户中，同时，用户还需要向网关提供身份信息，以通过该身份信息证明自己是已丢失账户的所有者。
步骤S502，网关接收用户提交的转移请求和身份信息，并根据转移 请求从证书中心中获取已丢失账户的所有者信息。网关具有从证书中心获取其中记录的账户信息的权限，网关根据用户提交的转移请求，从证书中心获取已丢失账户的所有者的身份信息，以对用户提交的身份信息进行验证。例如，证书中心记录了已丢失账户所有者的身份证号码或者身份证复印件的扫描件，则需要用户提供相应的身份证复印件等证明身份的材料。或者，证书中心记录了已丢失账户所有者的声纹信息，则需要用户提供相应的声纹材料。
步骤S503，网关对用户提交的身份信息和已丢失账户的所有者信息进行比对。网关将用户提交的身份信息与从证书中心获取到的已丢失账户所有者的信息进行比对，以确定用户提交的身份信息与丢失账户的所有者信息是否一致，进而验证出该用户是否是已丢失账户的所有者。
步骤S504，在用户提交的身份信息和已丢失账户的所有者信息一致时，网关利用第一账户的公钥对用户提交的身份信息和转移请求进行加密，得到第二数据。为了保护用户的隐私，防止用户的个人资料泄漏，网关先从证书中心获取第一账户的公钥，并利用第一账户的公钥对用户提交的身份信息和转移请求进行加密得到第二数据。
步骤S505，网关利用第一账户的私钥对已丢失账户的信息、目标账户的信息、资源列表和第二数据进行签名，得到第一数据,根据第一数据生成认证请求，并将认证请求提交给区块链。
步骤S506，区块链根据接收到的认证请求获取第一数据,由区块链的多个设备利用第一账户的公钥对第一数据进行验证，验证成功后得到初始数据。区块链从网关提交的认证请求中获取第一数据，并由区块链中的多个设备利用第一账户的公钥对第一数据进行验证，如果验证成功，则区块链可以从第一数据中获取初始数据。在上述验证过程中，由于身份信息和转移请求的核对是由网关完成的，区块链信任网关的核对结果，因此，区块链只需验证网关对初始数据的签名是否是真的，而无需对用户的身份信息和转移请求进行验证。
步骤S507，区块链根据初始数据记录转移事件，以将已丢失账户中的资源转移到目标账户中。区块链可以新增一个区块，用来记录上述转移事件，从而完成了将上述已丢失账户的资源转移到目标账户中。
步骤S508，区块链对目标账户设置冻结期。为了解决错误的将已丢失账户中的资源转移到目标账户造成已丢失账号的损失，在区块链根据网关提交的认证请求记录转移事件之后，区块链对目标账户设置一个冻结期，在该冻结期内，目标账户中的资源无法被转移。如果在区块链对目标账户设置的冻结期内，已丢失账户的所有者提出异议，例如：已丢失账户的所有者实际并未发起转移请求，或者在对已丢失账户中的资源进行转移的过程中发生错误，或者已丢失账户的所有者认为网关或者其他人存在欺诈等，区块链可以将已丢失账户转移到目标账户的资源重新退回给已丢失账户，以保护已丢失账户的所有者的权益。具体地，将目标账户中的资源重新退回给已丢失账户的过程与将已丢失账户的资源转移到目标账户的过程相同，由已丢失账户的所有者向网关提供身份信息和资源退回请求，由网关验证身份信息和资源退回请求，并在验证通过后根据用户的身份信息和资源退回请求向区块链提交认证请求，区块链根据认证请求记录转移事件，从而将目标账户中的资源退回到已丢失账户中。
步骤S509，在发生纠纷时，网关从区块链中提取初始数据，并从初始数据中获取由第一账户的公钥加密过的第二数据，利用第一账户的私钥对第二数据进行解密，得到解密后的数据。解密后的数据可以用作裁决上述纠纷的证据，以对发生的纠纷进行裁决。
步骤S510，网关利用第一账户的公钥对解密后的数据进行重新加密，以证明解密后的数据未被篡改。为了证明用作裁决上述纠纷的证据是真实的而未被篡改过，网关可以利用第一账户的公钥对作为证据的用户身份信息和转移请求重新加密，并将加密后的数据与从区块链上获取的第二数据进行比对，如果经过比对，加密后数据与从区块链上获取的第二数据不一致，则证明用作证据的用户信息和转移请求被篡改过而非真实的。可选地， 网关还可以从数据库中获取用户提交的身份信息和转移请求的原文的备份文件，该备份文件同样可以由网关利用第一账户的公钥对其进行重新加密并与区块链中的第二数据进行比对，以证明该备份文件的真实性。
需要说明的是，对于前述的各方法实施例，为了简单描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本申请并不受所描述的动作顺序的限制，因为依据本申请，某些步骤可以采用其他顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作和模块并不一定是本申请所必须的。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本申请各个实施例所述的方法。
根据本申请实施例，还提供了一种用于实施上述区块链中账户信息的处理方法的区块链中账户信息的处理装置，所述处理装置被设置在计算机设备中。图6是根据本申请实施例的一种可选的区块链中账户信息的处理装置的示意图，如图6所示，该装置可以包括：第一接收单元610、获取单元620、第一比对单元630和第一提交单元640。
第一接收单元610，用于接收用户发送转移请求和身份信息，其中，所述转移请求用于请求将已丢失账户中的资源转移到目标账户中，所述目标账户由证书中心生成；获取单元620，用于根据所述转移请求从所述证书中心获取所述已丢失账户的所有者信息；第一比对单元630，用于对所述身份信息和所述所有者信息进行比对；第一提交单元640，用于在比对出所述身份信息和所述所有者信息一致时，向区块链提交认证请求，以使 所述区块链根据所述认证请求在所述区块链中记录转移事件，其中，所述转移事件用于指示将所述已丢失账户中的资源转移到所述目标账户中。
需要说明的是，该实施例中的第一接收单元610可以用于执行本申请上述实施例中的步骤S302，该实施例中的获取单元620可以用于执行本申请上述实施例中的步骤S304，该实施例中的第一比对单元630可以用于执行本申请上述实施例中的步骤S306，该实施例中的第一提交单元640可以用于执行本申请上述实施例中的步骤S308。
此处需要说明的是，上述单元与对应的步骤所实现的示例和应用场景相同，但不限于上述实施例所公开的内容。需要说明的是，上述单元作为装置的一部分可以运行在如图2所示的硬件环境中，可以通过软件实现，也可以通过硬件实现。
通过上述单元，可以解决了于区块链中账户的私钥丢失造成的账户不安的技术问题，进而达到提高账户安全性的技术效果。
可选地，第一提交单元包括：签名模块，用于利用第一账户的私钥对初始数据进行签名，得到第一数据，其中，初始数据包括已丢失账户的信息、目标账户的信息、身份信息、转移请求和资源列表，资源列表为已丢失账户中等待转移的所有资源的列表；生成模块，用于根据第一数据生成认证请求；提交模块，用于向区块链提交携带有初始数据的认证请求。
可选地，签名模块包括：加密子模块，用于利用第一账户的公钥对身份信息和转移请求进行加密，得到第二数据；第一签名子模块，用于利用第一账户的私钥对已丢失账户的信息、目标账户的信息、资源列表和第二数据进行签名，得到第一数据。
本发明还提供了一种可选实施例，该可选实施例中，签名模块包括：第二签名子模块，用于利用第一账户的私钥对身份信息和转移请求进行签名，得到第三数据；第三签名子模块，用于利用第一账户的私钥对已丢失账户的信息、目标账户的信息、资源列表和第三数据进行签名，得到第一 数据。
可选地，第一提交单元包括：获取模块，用于通过区块链获取第一数据；验证模块，用于通过区块链对第一数据进行验证；记录模块，用于在验证通过后，通过区块链根据初始数据记录转移事件。
可选地，验证模块包括：获取子模块，用于通过区块链的多个设备从证书中心或者区块链的初始区块中获取第一账户的公钥；验证子模块，用于通过区块链的多个设备利用第一账户的公钥对第一数据进行验证。
可选地，装置还包括：设置单元，用于在向区块链提交认证请求，以使区块链根据认证请求在区块链中记录转移事件之后，通过区块链对目标账户设置冻结期，其中，在冻结期内目标账户中的资源处于不允许转移的状态。
可选地，装置还包括：第一提取单元，用于在向区块链提交认证请求，以使区块链根据认证请求在区块链中记录转移事件之后，从区块链中提取初始数据，其中，初始数据包括利用第一账户的公钥对身份信息和转移请求进行加密后得到的第二数据；第一解密单元，用于利用第一账户的私钥对第二数据进行解密，得到第一解密数据；第二比对单元，用于比对第一解密数据与本地存储的数据是否一致；第一确定单元，用于在比对出第一解密数据与本地存储的数据不一致时，确定本地存储的数据被篡改。
可选地，装置还包括：第二提取单元，用于在向区块链提交认证请求，以使区块链根据认证请求在区块链中记录转移事件之后，从区块链中提取初始数据，其中，初始数据包括利用第一账户的私钥对所述身份信息和所述转移请求进行签名后得到的第三数据；第二解密单元，用于利用第一账户的公钥对第三数据进行解密，得到第二解密数据；第一变换单元，用于对本地存储的数据进行哈希变换，得到哈希变换后的数据；第三比对单元，用于比对第二解密数据与哈希变换后的数据是否一致；第二确定单元，用于在比对出第二解密数据与哈希变换后的数据不一致时，确定本地存储的数据被篡改。
可选地，装置还包括：第三提取单元，用于根据用户发送的核查指令从区块链中提取初始数据，其中，初始数据包括利用第一账户的公钥对身份信息和转移请求进行加密后得到的第二数据，核查指令用于指示对第二数据进行核查；加密单元，用于利用第一账户的公钥对用户发送的转移请求和身份信息进行加密，得到第四数据；第四比对单元，用于比对第二数据与第四数据是否一致，得到比对结果，其中，如果比对结果为一致，则用户发送的转移请求和身份信息未被篡改，如果比对结果为不一致，则用户发送的转移请求和身份信息被篡改。
可选地，装置还包括：第四提取单元，用于在向区块链提交认证请求，以使区块链根据认证请求在区块链中记录转移事件之后，根据用户发送的核查指令从区块链中提取初始数据，其中初始数据包括利用第一账户的私钥对身份信息和转移请求进行签名后得到的第三数据，核查指令用于指示对第三数据进行核查；第二变换单元，用于对用户发送的转移请求和身份信息进行哈希变换，得到第五数据；第三解密单元，用于利用第一账户的公钥对第三数据进行解密，得到第三解密数据；第五比对单元，用于比对第五数据与第三解密数据是否一致，得到比对结果，其中，如果比对结果为一致，则用户发送的转移请求和身份信息未被篡改，如果比对结果为不一致，则用户发送的转移请求和身份信息被篡改。
此处需要说明的是，上述模块与对应的步骤所实现的示例和应用场景相同，但不限于上述实施例所公开的内容。需要说明的是，上述模块作为装置的一部分可以运行在如图2所示的硬件环境中，可以通过软件实现，也可以通过硬件实现，其中，硬件环境包括网络环境。
根据本申请实施例，还提供了一种存储介质，其中，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行上述的方法。
根据本申请实施例，还提供了一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为通过所述计算机程 序执行上述的方法。
根据本申请实施例，还提供了一种用于实施上述区块链中账户信息的处理方法的服务器。该服务器可以作为上述电子装置。
图7是根据本申请实施例的一种服务器的结构框图，如图7所示，该服务器可以包括：一个或多个(图中仅示出一个)处理器701、存储器703、以及传输装置705(如上述实施例中的发送装置)，如图7所示，该终端还可以包括输入输出设备707。
其中，存储器703可用于存储软件程序以及模块，如本申请实施例中的区块链中账户信息的处理方法和装置对应的程序指令/模块，处理器701通过运行存储在存储器703内的软件程序以及模块，从而执行各种功能应用以及数据处理，即实现上述的区块链中账户信息的处理方法。存储器703可包括高速随机存储器，还可以包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中，存储器703可进一步包括相对于处理器701远程设置的存储器，这些远程存储器可以通过网络连接至终端。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
上述的传输装置705用于经由一个网络接收或者发送数据，还可以用于处理器与存储器之间的数据传输。上述的网络具体实例可包括有线网络及无线网络。在一个实例中，传输装置705包括一个网络适配器(Network Interface Controller，NIC)，其可通过网线与其他网络设备与路由器相连从而可与互联网或局域网进行通讯。在一个实例中，传输装置705为射频(Radio Frequency，RF)模块，其用于通过无线方式与互联网进行通讯。
其中，具体地，存储器703用于存储应用程序。
处理器701可以通过传输装置705调用存储器703存储的应用程序，以执行下述步骤：
处理器701用于执行下述步骤：接收用户发送转移请求和身份信息， 其中，所述转移请求用于请求将已丢失账户中的资源转移到目标账户中，所述目标账户由证书中心生成；根据所述转移请求从所述证书中心获取所述已丢失账户的所有者信息；对所述身份信息和所述所有者信息进行比对；在比对出所述身份信息和所述所有者信息一致时，向区块链提交认证请求，以使所述区块链根据所述认证请求在所述区块链中记录转移事件，其中，所述转移事件用于指示将所述已丢失账户中的资源转移到所述目标账户中。
可选的，处理器701还可以执行上述实施例中的其他方法步骤。
采用本申请实施例，提供了一种区块链中账户信息的处理的方案。通过比对用户提供的身份信息和已丢失账户所有者信息是否一致，并在比对一致时，向区块链提交认证请求，达到了在区块链中将将已丢失账户中的资源转移到目标账户中的目的，从而实现了在将已丢失账户中的资源转移到目标账户中时，无需验证丢失账户的私钥签名的技术效果，进而解决了于区块链中账户的私钥丢失造成的账户不安的技术问题。
可选地，本实施例中的具体示例可以参考上述实施例中所描述的示例，本实施例在此不再赘述。
本领域普通技术人员可以理解，图7所示的结构仅为示意，终端可以是智能手机(如Android手机、iOS手机等)、平板电脑、掌上电脑以及移动互联网设备(Mobile Internet Devices，MID)、PAD等终端设备。图7其并不对上述电子装置的结构造成限定。例如，终端还可包括比图7中所示更多或者更少的组件(如网络接口、显示装置等)，或者具有与图7所示不同的配置。
本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分步骤是可以通过程序来指令终端设备相关的硬件来完成，该程序可以存储于一计算机可读存储介质中，存储介质可以包括：闪存盘、只读存储器(Read-Only Memory，ROM)、随机存取器(Random Access Memory，RAM)、磁盘或光盘等。
本申请的实施例还提供了一种存储介质。可选地，在本实施例中，上述存储介质可以用于存储执行区块链中账户信息的处理方法的程序代码。
可选地，在本实施例中，上述存储介质可以位于上述实施例所示的网络中的多个网络设备中的至少一个网络设备上。
可选地，在本实施例中，存储介质被设置为存储用于执行以下步骤的程序代码：
S1，接收用户发送转移请求和身份信息，其中，转移请求用于请求将已丢失账户中的资源转移到目标账户中，目标账户由证书中心生成；
S2，根据转移请求从证书中心获取已丢失账户的所有者信息；
S3，对身份信息和所有者信息进行比对；
S4，在比对出身份信息和所有者信息一致时，向区块链提交认证请求，以使区块链根据认证请求在区块链中记录转移事件，其中，转移事件用于指示将已丢失账户中的资源转移到目标账户中。
可选地，本实施例的存储介质用于存储实现上述实施例的处理方法步骤的程序指令，该实施例的具体示例可以参考上述方法实施例中所描述的示例，本实施例在此不再赘述。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
上述实施例中的集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在上述计算机可读取的存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在存储介质中，包括若干指令用以使得一台或多台计算 机设备(可为个人计算机、服务器或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。
在本申请的上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。
在本申请所提供的几个实施例中，应该理解到，所揭露的客户端，可通过其它的方式实现。其中，以上所描述的装置实施例仅仅是示意性的，例如所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，单元或模块的间接耦合或通信连接，可以是电性或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
以上所述仅是本申请的可选实施方式，应当指出，对于本技术领域的普通技术人员来说，在不脱离本申请原理的前提下，还可以做出若干改进和润饰，这些改进和润饰也应视为本申请的保护范围。

Claims (24)

  1. 一种区块链中账户信息的处理方法，所述处理方法通过计算机设备执行，所述处理方法包括：
    所述计算机设备接收用户发送转移请求和身份信息，其中，所述转移请求用于请求将已丢失账户中的资源转移到目标账户中，所述目标账户由证书中心生成；
    所述计算机设备根据所述转移请求从所述证书中心获取所述已丢失账户的所有者信息；
    所述计算机设备对所述身份信息和所述所有者信息进行比对；
    所述计算机设备在比对出所述身份信息和所述所有者信息一致时，向区块链提交认证请求，以使所述区块链根据所述认证请求在所述区块链中记录转移事件，其中，所述转移事件用于指示将所述已丢失账户中的资源转移到所述目标账户中。
  2. 根据权利要求1所述的方法，其中，所述计算机设备向区块链提交认证请求包括：
    利用第一账户的私钥对初始数据进行签名，得到第一数据，其中，所述初始数据包括所述已丢失账户的信息、所述目标账户的信息、所述身份信息、所述转移请求和资源列表，所述资源列表为所述已丢失账户中等待转移的所有资源的列表；
    根据所述第一数据生成所述认证请求；
    向所述区块链提交携带有所述初始数据的所述认证请求。
  3. 根据权利要求2所述的方法，其中，所述计算机设备利用第一账户的私钥对初始数据进行签名，得到第一数据包括：
    利用所述第一账户的公钥对所述身份信息和所述转移请求进行加密，得到第二数据；
    利用所述第一账户的私钥对所述已丢失账户的信息、所述目标账 户的信息、所述资源列表和所述第二数据进行签名，得到所述第一数据。
  4. 根据权利要求2所述的方法，其中，所述计算机设备利用第一账户的私钥对初始数据进行签名，得到第一数据包括：
    利用所述第一账户的私钥对所述身份信息和所述转移请求进行签名，得到第三数据；
    利用所述第一账户的私钥对所述已丢失账户的信息、所述目标账户的信息、所述资源列表和所述第三数据进行签名，得到所述第一数据。
  5. 根据权利要求2至4中任一项所述的方法，其中，所述计算机设备在比对出所述身份信息和所述所有者信息一致时，向区块链提交认证请求，以使所述区块链根据所述认证请求在所述区块链中记录转移事件包括：
    所述区块链的设备根据所述认证请求获取所述第一数据；
    所述区块链的设备对所述第一数据进行验证；
    在验证通过后，所述区块链的设备根据所述初始数据记录所述转移事件。
  6. 根据权利要求5所述的方法，其中，所述区块链的设备对所述第一数据进行验证包括：
    所述区块链的多个设备从所述证书中心或者所述区块链的初始区块中获取所述第一账户的公钥；
    所述区块链的所述多个设备利用所述第一账户的公钥对所述第一数据进行验证。
  7. 根据权利要求1所述的方法，其中，所述计算机设备在向区块链提交认证请求，以使所述区块链根据所述认证请求在所述区块链中记录转移事件之后，所述方法还包括：
    所述区块链中设备对所述目标账户设置冻结期，其中，在所述冻结期内所述目标账户中的资源处于不允许转移的状态。
  8. 根据权利要求3所述的方法，其中，所述计算机设备在向区块链提交认证请求，以使所述区块链根据所述认证请求在所述区块链中记录转移事件之后，所述方法还包括：
    所述计算机设备从所述区块链中提取初始数据，其中，所述初始数据包括所述利用所述第一账户的公钥对所述身份信息和所述转移请求进行加密后得到的第二数据；
    所述计算机设备利用所述第一账户的私钥对所述第二数据进行解密，得到第一解密数据；
    所述计算机设备比对所述第一解密数据与本地存储的数据是否一致；
    如果比对出所述第一解密数据与本地存储的数据不一致，则所述计算机设备确定所述本地存储的数据被篡改。
  9. 根据权利要求4所述的方法，其中，所述计算机设备在向区块链提交认证请求，以使所述区块链根据所述认证请求在所述区块链中记录转移事件之后，所述方法还包括：
    所述计算机设备从所述区块链中提取初始数据，其中，所述初始数据包括所述利用所述第一账户的私钥对所述身份信息和所述转移请求进行签名后得到的第三数据；
    所述计算机设备利用第一账户的公钥对所述第三数据进行解密，得到第二解密数据；
    所述计算机设备对本地存储的数据进行哈希变换，得到哈希变换后的数据；
    所述计算机设备比对所述第二解密数据与所述哈希变换后的数据是否一致；
    所述计算机设备如果比对出所述第二解密数据与所述哈希变换 后的数据不一致，则确定所述本地存储的数据被篡改。
  10. 根据权利要求3所述的方法，其中，所述计算机设备在向区块链提交认证请求，以使所述区块链根据所述认证请求在所述区块链中记录转移事件之后，所述方法还包括：
    所述计算机设备根据所述用户发送的核查指令从所述区块链中提取初始数据，其中，所述初始数据包括利用所述第一账户的公钥对所述身份信息和转移请求进行加密后得到的第二数据，所述核查指令用于指示对所述第二数据进行核查；
    所述计算机设备利用所述第一账户的公钥对所述用户发送的所述转移请求和身份信息进行加密，得到第四数据；
    所述计算机设备比对所述第二数据与所述第四数据是否一致，得到比对结果，其中，如果所述比对结果为一致，则所述用户发送的所述转移请求和身份信息未被篡改，如果所述比对结果为不一致，则所述用户发送的所述转移请求和身份信息被篡改。
  11. 根据权利要求4所述的方法，其中，所述计算机设备在向区块链提交认证请求，以使所述区块链根据所述认证请求在所述区块链中记录转移事件之后，所述方法还包括：
    所述计算机设备根据所述用户发送的核查指令从所述区块链中提取初始数据，其中所述初始数据包括利用所述第一账户的私钥对所述身份信息和转移请求进行签名后得到的第三数据，所述核查指令用于指示对所述第三数据进行核查；
    所述计算机设备对所述用户发送的所述转移请求和身份信息进行哈希变换，得到第五数据；
    所述计算机设备利用所述第一账户的公钥对所述第三数据进行解密，得到第三解密数据；
    所述计算机设备比对所述第五数据与所述第三解密数据是否一 致，得到比对结果，其中，如果所述比对结果为一致，则所述用户发送的所述转移请求和身份信息未被篡改，如果所述比对结果为不一致，则所述用户发送的所述转移请求和身份信息被篡改。
  12. 一种区块链中账户信息的处理装置，所述处理装置被设置在计算机设备中，所述处理装置包括：
    第一接收单元，用于接收用户发送转移请求和身份信息，其中，所述转移请求用于请求将已丢失账户中的资源转移到目标账户中，所述目标账户由证书中心生成；
    获取单元，用于根据所述转移请求从所述证书中心获取所述已丢失账户的所有者信息；
    第一比对单元，用于对所述身份信息和所述所有者信息进行比对；
    第一提交单元，用于在比对出所述身份信息和所述所有者信息一致时，向区块链提交认证请求，以使所述区块链根据所述认证请求在所述区块链中记录转移事件，其中，所述转移事件用于指示将所述已丢失账户中的资源转移到所述目标账户中。
  13. 根据权利要求12所述的装置，其中，所述第一提交单元包括：
    签名模块，用于利用第一账户的私钥对初始数据进行签名，得到第一数据，其中，所述初始数据包括所述已丢失账户的信息、所述目标账户的信息、所述身份信息、所述转移请求和资源列表，所述资源列表为所述已丢失账户中等待转移的所有资源的列表；
    生成模块，用于根据所述第一数据生成所述认证请求；
    提交模块，用于向所述区块链提交携带有所述初始数据的所述认证请求。
  14. 根据权利要求13所述的装置，其中，所述签名模块包括：
    加密子模块，用于利用所述第一账户的公钥对所述身份信息和所述转移请求进行加密，得到第二数据；
    第一签名子模块，用于利用所述第一账户的私钥对所述已丢失账 户的信息、所述目标账户的信息、所述资源列表和所述第二数据进行签名，得到所述第一数据。
  15. 根据权利要求13所述的装置，其中，所述签名模块包括：
    第二签名子模块，用于利用所述第一账户的私钥对所述身份信息和所述转移请求进行签名，得到第三数据；
    第三签名子模块，用于利用所述第一账户的私钥对所述已丢失账户的信息、所述目标账户的信息、所述资源列表和所述第三数据进行签名，得到所述第一数据。
  16. 根据权利要求13至15中任一项所述的装置，其中，所述第一提交单元包括：
    获取模块，用于通过所述区块链获取所述第一数据；
    验证模块，用于通过所述区块链对所述第一数据进行验证；
    记录模块，用于在验证通过后，通过所述区块链根据所述初始数据记录所述转移事件。
  17. 根据权利要求16所述的装置，其中，所述验证模块包括：
    获取子模块，用于通过所述区块链的多个设备从所述证书中心或者所述区块链的初始区块中获取所述第一账户的公钥；
    验证子模块，用于通过所述区块链的所述多个设备利用所述第一账户的公钥对所述第一数据进行验证。
  18. 根据权利要求12所述的装置，其中，所述装置还包括：
    设置单元，用于在向区块链提交认证请求，以使所述区块链根据所述认证请求在所述区块链中记录转移事件之后，通过所述区块链对所述目标账户设置冻结期，其中，在所述冻结期内所述目标账户中的资源处于不允许转移的状态。
  19. 根据权利要求14所述的装置，其中，所述装置还包括：
    第一提取单元，用于在向区块链提交认证请求，以使所述区块链 根据所述认证请求在所述区块链中记录转移事件之后，从所述区块链中提取初始数据，其中，所述初始数据包括利用所述第一账户的公钥对所述身份信息和所述转移请求进行加密后得到的第二数据；
    第一解密单元，用于利用所述第一账户的私钥对所述第二数据进行解密，得到第一解密数据；
    第二比对单元，用于比对所述第一解密数据与本地存储的数据是否一致；
    第一确定单元，用于在比对出所述第一解密数据与本地存储的数据不一致时，确定所述本地存储的数据被篡改。
  20. 根据权利要求15所述的装置，其中，所述装置还包括：
    第二提取单元，用于在向区块链提交认证请求，以使所述区块链根据所述认证请求在所述区块链中记录转移事件之后，从所述区块链中提取初始数据，其中，所述初始数据包括所述利用所述第一账户的私钥对所述身份信息和所述转移请求进行签名后得到的第三数据；
    第二解密单元，用于利用第一账户的公钥对所述第三数据进行解密，得到第二解密数据；
    第一变换单元，用于对本地存储的数据进行哈希变换，得到哈希变换后的数据；
    第三比对单元，用于比对所述第二解密数据与所述哈希变换后的数据是否一致；
    第二确定单元，用于在比对出所述第二解密数据与所述哈希变换后的数据不一致时，确定所述本地存储的数据被篡改。
  21. 根据权利要求14所述的装置，其中，所述装置还包括：
    第三提取单元，用于根据所述用户发送的核查指令从所述区块链中提取初始数据，其中，所述初始数据包括所述利用所述第一账户的公钥对所述身份信息和转移请求进行加密后得到的第二数据，所述核查指令用于指示对所述第二数据进行核查；
    加密单元，用于利用所述第一账户的公钥对所述用户发送的所述转移请求和身份信息进行加密，得到第四数据；
    第四比对单元，用于比对所述第二数据与所述第四数据是否一致，得到比对结果，其中，如果所述比对结果为一致，则所述用户发送的所述转移请求和身份信息未被篡改，如果所述比对结果为不一致，则所述用户发送的所述转移请求和身份信息被篡改。
  22. 根据权利要求15所述的装置，其中，所述装置还包括：
    第四提取单元，用于在所述向区块链提交认证请求，以使所述区块链根据所述认证请求在所述区块链中记录转移事件之后，根据所述用户发送的核查指令从所述区块链中提取初始数据，其中所述初始数据包括利用所述第一账户的私钥对所述身份信息和转移请求进行签名后得到的第三数据，所述核查指令用于指示对所述第三数据进行核查；
    第二变换单元，用于对所述用户发送的所述转移请求和身份信息进行哈希变换，得到第五数据；
    第三解密单元，用于利用所述第一账户的公钥对所述第三数据进行解密，得到第三解密数据；
    第五比对单元，用于比对所述第五数据与所述第三解密数据是否一致，得到比对结果，其中，如果所述比对结果为一致，则所述用户发送的所述转移请求和身份信息未被篡改，如果所述比对结果为不一致，则所述用户发送的所述转移请求和身份信息被篡改。
  23. 一种存储介质，所述存储介质中存储有计算机程序，所述计算机程序被设置为运行时执行所述权利要求1至11任一项中所述的方法。
  24. 一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为通过所述计算机程序执行所述权利要求1至11任一项中所述的方法。
PCT/CN2018/077412 2017-02-28 2018-02-27 区块链中账户信息的处理方法和装置、存储介质和电子装置 WO2018157788A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US16/371,480 US10785038B2 (en) 2017-02-28 2019-04-01 Method and apparatus for processing account information in block chain, storage medium, and electronic apparatus
US16/993,985 US11477034B2 (en) 2017-02-28 2020-08-14 Method and apparatus for processing account information in block chain, storage medium, and electronic apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710120699.9 2017-02-28
CN201710120699.9A CN107066893B (zh) 2017-02-28 2017-02-28 区块链中账户信息的处理方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/371,480 Continuation US10785038B2 (en) 2017-02-28 2019-04-01 Method and apparatus for processing account information in block chain, storage medium, and electronic apparatus

Publications (1)

Publication Number Publication Date
WO2018157788A1 true WO2018157788A1 (zh) 2018-09-07

Family

ID=59622806

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/077412 WO2018157788A1 (zh) 2017-02-28 2018-02-27 区块链中账户信息的处理方法和装置、存储介质和电子装置

Country Status (3)

Country Link
US (2) US10785038B2 (zh)
CN (1) CN107066893B (zh)
WO (1) WO2018157788A1 (zh)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111369259A (zh) * 2020-03-10 2020-07-03 北京意锐新创科技有限公司 适用于区块链支持的支付方法和装置
ES2774397A1 (es) * 2019-01-18 2020-07-20 Telefonica Digital Espana Slu Metodo y sistema para recuperacion de claves criptograficas de una red de cadena de bloques
CN111461721A (zh) * 2020-04-16 2020-07-28 北京俩撇科技有限公司 一种基于区块链的保护账户、验证交易的方法及装置
US10885207B2 (en) 2018-10-31 2021-01-05 Advanced New Technologies Co., Ltd. Method, apparatus, and electronic device for blockchain-based recordkeeping
CN113435888A (zh) * 2020-04-13 2021-09-24 腾讯科技（深圳）有限公司 一种账户数据处理方法、装置、设备及存储介质
CN115941364A (zh) * 2023-03-13 2023-04-07 广东电网有限责任公司 基于智能电网的资产数据管理方法及其系统

Families Citing this family (61)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107066893B (zh) 2017-02-28 2018-11-09 腾讯科技（深圳）有限公司 区块链中账户信息的处理方法和装置
CN106952094B (zh) * 2017-03-10 2018-09-04 腾讯科技（深圳）有限公司 电子票据管理方法及装置
CN107682378A (zh) * 2017-11-22 2018-02-09 国民认证科技（北京）有限公司 一种基于区块链的实名认证方法及系统
CN108009441B (zh) 2017-11-23 2023-05-30 创新先进技术有限公司 资源转移和资金转移的方法和装置
CN108288158A (zh) * 2018-01-29 2018-07-17 张天 一种基于区块链技术的存储方法、计算机可读存储介质
CN108280358B (zh) * 2018-02-12 2020-10-30 北京金山安全软件有限公司 一种信息提醒方法、装置及电子设备
US11038689B2 (en) * 2018-03-01 2021-06-15 FinancialForce.com, Inc. Efficient block chain generation
US11003777B2 (en) * 2018-04-16 2021-05-11 International Business Machines Corporation Determining a frequency at which to execute trap code in an execution path of a process executing a program to generate a trap address range to detect potential malicious code
WO2019221651A1 (en) 2018-05-18 2019-11-21 Telefonaktiebolaget Lm Ericsson (Publ) Method and network node for managing access to a blockchain
CN108776892B (zh) * 2018-05-21 2022-05-31 北京橙鑫数据科技有限公司 存储系统、设备以及存储系统的恢复方法
CN108809630A (zh) * 2018-06-19 2018-11-13 中钞信用卡产业发展有限公司杭州区块链技术研究院 一种遗嘱保存方法、系统、设备及计算机可读存储介质
CN109377358A (zh) * 2018-08-09 2019-02-22 杭州复杂美科技有限公司 一种资产找回方法、设备和存储介质
US20200059363A1 (en) * 2018-08-17 2020-02-20 Walmart Apollo, Llc Systems and methods of authenticating items
CN109246208B (zh) * 2018-08-29 2020-12-29 杭州秘猿科技有限公司 一种去中心化应用账户恢复方法、装置及系统
CN110428307A (zh) * 2018-08-30 2019-11-08 腾讯科技（深圳）有限公司 虚拟宠物商品的交易方法、系统、设备及存储介质
CN108875398B (zh) * 2018-09-06 2023-06-09 山西特信环宇信息技术有限公司 基于证件链技术的加解密系统及其使用方法
CN109492424B (zh) * 2018-09-29 2023-05-26 平安科技（深圳）有限公司 数据资产管理方法、数据资产管理装置及计算机可读介质
CN109395393B (zh) * 2018-09-29 2022-03-04 杭州复杂美科技有限公司 基于平行链的游戏部署方法和游戏方法、设备及存储介质
CN109617861B (zh) * 2018-11-20 2021-07-23 北京小米移动软件有限公司 一种基于区块链的业务账号管理方法及系统
CN109523385A (zh) * 2018-12-07 2019-03-26 深圳市智税链科技有限公司 在区块链网络中查询交易信息的方法、记账节点和介质
CN109670801B (zh) * 2018-12-10 2021-02-12 华中科技大学 一种针对区块链的数字加密货币转移方法
CN109741070B (zh) * 2018-12-28 2024-01-05 深圳市元征科技股份有限公司 一种基于网证的账户管理方法及装置
CN109639421B (zh) * 2019-01-09 2021-09-21 山东浪潮质量链科技有限公司 一种私钥找回的方法及服务器
CN109660346B (zh) * 2019-01-16 2021-09-17 中钞信用卡产业发展有限公司杭州区块链技术研究院 信息托管方法、装置、设备及计算机存储介质
CN109767221B (zh) * 2019-01-16 2021-05-11 杭州趣链科技有限公司 一种面向区块链安全的移动跨平台签名方法
US11734655B2 (en) * 2019-01-17 2023-08-22 Mastercard International Incorporated Method and system for a failsafe mechanism for blockchain wallets
CN110070363B (zh) * 2019-03-13 2021-08-06 咪咕文化科技有限公司 区块链网络中的账户管理方法、验证方法及终端设备
CN110163604B (zh) * 2019-04-29 2021-02-09 华中科技大学 一种基于多方验证的区块链资产转移方法
CN110381075B (zh) * 2019-07-26 2021-10-29 烨链（上海）科技有限公司 基于区块链的设备身份认证方法和装置
CN110505217B (zh) * 2019-08-05 2021-11-02 河北科技大学 一种基于博弈论与区块链融合的位置隐私保护方法
CN110597837B (zh) * 2019-09-19 2024-05-03 腾讯科技（深圳）有限公司 业务数据处理方法、装置、存储介质和计算机设备
CN110601858B (zh) * 2019-09-27 2021-05-28 腾讯科技（深圳）有限公司 证书管理方法及装置
CN110928677B (zh) * 2019-09-30 2022-09-06 咪咕文化科技有限公司 基于区块链的虚拟资源计算方法及装置、电子设备及存储介质
CN112749959B (zh) * 2019-10-29 2023-09-19 腾讯科技（深圳）有限公司 资源转移方法、系统、装置、设备及存储介质
CN111061558B (zh) * 2019-10-30 2023-09-01 京东科技信息技术有限公司 处理虚拟资源数据的方法、装置、计算机设备和存储介质
CN110958223B (zh) * 2019-10-31 2023-03-24 百度在线网络技术（北京）有限公司 基于区块链的委托授权方法、装置、设备和介质
CN112950198A (zh) * 2019-12-03 2021-06-11 微观(天津)科技发展有限公司 基于区块链的跨境贸易监管方法、装置以及存储介质
CN111010379B (zh) * 2019-12-04 2022-08-09 腾讯科技（深圳）有限公司 一种基于区块链网络的数据登录方法和装置
CN111210224A (zh) * 2019-12-23 2020-05-29 中思博安科技（北京）有限公司 区块链网络中访问控制方法和装置
CN111275417B (zh) * 2020-01-16 2024-03-12 平安科技（深圳）有限公司 交易背书处理方法、服务器及计算机可读存储介质
CN111260488B (zh) * 2020-01-23 2021-11-26 腾讯科技（深圳）有限公司 一种数据处理方法、装置及可读存储介质
CN111160997A (zh) * 2020-04-02 2020-05-15 支付宝(杭州)信息技术有限公司 基于区块链的广告监管方法、装置及广告投放系统
CN111476572B (zh) * 2020-04-09 2024-03-19 财付通支付科技有限公司 基于区块链的数据处理方法、装置、存储介质及设备
CN111507881B (zh) * 2020-04-20 2022-04-29 支付宝实验室(新加坡)有限公司 一种资源需求信息处理方法、装置及设备
CN111815321A (zh) * 2020-05-21 2020-10-23 北京金山云网络技术有限公司 交易提案的处理方法、装置、系统、存储介质和电子装置
CN111738734B (zh) * 2020-06-22 2021-08-24 微晶(北京)科技有限公司 一种区块链中账户信息转移与合并的方法
CN112035892A (zh) * 2020-07-20 2020-12-04 江苏傲为控股有限公司 一种去中心化电子合同存证平台账号管理方法
CN111882273A (zh) * 2020-07-20 2020-11-03 上海东普信息科技有限公司 基于区块链的业务费用结算方法、装置、设备及存储介质
CN111835783B (zh) * 2020-07-22 2022-09-02 东莞盟大集团有限公司 数据调阅方法、装置和计算机设备
CN112087497B (zh) * 2020-08-17 2021-04-27 成都质数斯达克科技有限公司 数据同步方法、装置、电子设备及可读存储介质
CN112202734B (zh) * 2020-09-14 2023-04-07 成都质数斯达克科技有限公司 业务处理方法、电子设备及可读存储介质
CN112235109B (zh) * 2020-12-14 2021-03-09 布比（北京）网络技术有限公司 一种基于区块链的账户恢复方法及系统
CN112508578B (zh) * 2021-02-04 2021-06-04 支付宝(杭州)信息技术有限公司 基于区块链的资源转移请求验证、发送方法及装置
CN112990903B (zh) * 2021-03-10 2023-06-09 中国联合网络通信集团有限公司 基于区块链的话费转账方法、可转账节点和需求节点
CN113114465B (zh) * 2021-03-19 2022-10-11 青岛海尔科技有限公司 归属权限的处理方法及装置、存储介质、电子装置
CN113572599B (zh) * 2021-06-21 2023-11-28 深圳供电局有限公司 电力数据的传输方法、数据源设备及数据访问设备
CN114172660B (zh) * 2021-12-03 2024-03-26 浙商银行股份有限公司 联盟链的账户管理方法、装置、设备以及存储介质
CN114969808B (zh) * 2022-05-07 2023-09-19 中移互联网有限公司 一种账号的管理方法、装置、电子设备及存储介质
CN115208956B (zh) * 2022-06-23 2023-06-02 北京链道科技有限公司 区块链网关的实现方法
CN115659313B (zh) * 2022-12-08 2023-04-07 广州简悦信息科技有限公司 账号数据处理方法、设备、存储介质及程序产品
CN117032998B (zh) * 2023-10-09 2024-01-19 腾讯科技（深圳）有限公司 一种基于区块链的数据处理方法、装置以及可读存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101567780A (zh) * 2009-03-20 2009-10-28 武汉理工大学 一种针对加密数字证书的密钥管理与恢复方法
CN105468994A (zh) * 2015-11-26 2016-04-06 布比（北京）网络技术有限公司 一种对象转移方法、装置及系统
WO2016118359A1 (en) * 2015-01-22 2016-07-28 Alibaba Group Holding Limited Method, apparatus, and system for quantum key distribution
CN106022917A (zh) * 2016-05-08 2016-10-12 杭州复杂美科技有限公司 区块链撮合交易所方案
CN107066893A (zh) * 2017-02-28 2017-08-18 腾讯科技（深圳）有限公司 区块链中账户信息的处理方法和装置

Family Cites Families (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
ATE506797T1 (de) * 2004-05-07 2011-05-15 Alcatel Lucent Datenauthentifizierungsverfahren und agent basiertes system
US7797413B2 (en) * 2004-10-29 2010-09-14 The Go Daddy Group, Inc. Digital identity registration
US20070074027A1 (en) * 2005-09-26 2007-03-29 Tien-Chun Tung Methods of verifying, signing, encrypting, and decrypting data and file
US8374354B2 (en) * 2007-09-27 2013-02-12 Verizon Data Services Llc System and method to pass a private encryption key
US9094379B1 (en) * 2010-12-29 2015-07-28 Amazon Technologies, Inc. Transparent client-side cryptography for network applications
US9876775B2 (en) * 2012-11-09 2018-01-23 Ent Technologies, Inc. Generalized entity network translation (GENT)
US9015858B2 (en) * 2012-11-30 2015-04-21 nCrypted Cloud LLC Graphical user interface for seamless secure private collaboration
US10068228B1 (en) * 2013-06-28 2018-09-04 Winklevoss Ip, Llc Systems and methods for storing digital math-based assets using a secure portal
US11282139B1 (en) * 2013-06-28 2022-03-22 Gemini Ip, Llc Systems, methods, and program products for verifying digital assets held in a custodial digital asset wallet
CN104348822B (zh) * 2013-08-09 2019-01-29 深圳市腾讯计算机系统有限公司 一种互联网账号身份验证的方法、装置及服务器
WO2015024129A1 (en) * 2013-08-21 2015-02-26 Trent Lorne Mcconaghy Method to securely establish, affirm, and transfer ownership of artworks
WO2015183497A1 (en) * 2014-05-06 2015-12-03 Case Wallet, Inc. Cryptocurrency virtual wallet system and method
US10970684B1 (en) * 2014-05-20 2021-04-06 Wells Fargo Bank, N.A. Systems and methods for maintaining deposits of math-based currency
US10579974B1 (en) * 2015-02-16 2020-03-03 AI Coin Inc. Systems, methods, and program products for a distributed digital asset network with rapid transaction settlements
US10664923B2 (en) * 2015-03-13 2020-05-26 Gyft, Inc. System and method for establishing a public ledger for gift card transactions
US10158480B1 (en) * 2015-03-16 2018-12-18 Winklevoss Ip, Llc Autonomous devices
US20160300234A1 (en) * 2015-04-06 2016-10-13 Bitmark, Inc. System and method for decentralized title recordation and authentication
US10740732B2 (en) * 2015-05-20 2020-08-11 Ripple Luxembourg S.A. Resource transfer system
US20160359633A1 (en) * 2015-06-02 2016-12-08 Crater Dog Technologies, LLC System and method for publicly certifying data
US20170048234A1 (en) * 2015-07-14 2017-02-16 Fmr Llc Social Aggregating, Fractionally Efficient Transfer Guidance, Conditional Triggered Transaction, Datastructures, Apparatuses, Methods and Systems
US10402792B2 (en) * 2015-08-13 2019-09-03 The Toronto-Dominion Bank Systems and method for tracking enterprise events using hybrid public-private blockchain ledgers
JP6951329B2 (ja) * 2015-10-14 2021-10-20 ケンブリッジ ブロックチェーン，エルエルシー デジタルアイデンティティを管理するためのシステム及び方法
US20170147808A1 (en) * 2015-11-19 2017-05-25 International Business Machines Corporation Tokens for multi-tenant transaction database identity, attribute and reputation management
US10116667B2 (en) * 2016-01-26 2018-10-30 Bank Of America Corporation System for conversion of an instrument from a non-secured instrument to a secured instrument in a process data network
US11164165B1 (en) * 2016-04-08 2021-11-02 Greenberg & Lieberman, Llc Multi-asset blockchain network platform
KR101780636B1 (ko) * 2016-05-16 2017-09-21 주식회사 코인플러그 인증 정보의 발급 방법 및 이를 지원하는 블록체인기반 인증 정보 관리 서버
US20170344983A1 (en) * 2016-05-30 2017-11-30 Business Information Exchange System Corp. BIXCoin: A Secure Peer-to-Peer Payment System Based on the Public Payments Ledger
US10375177B1 (en) * 2016-06-21 2019-08-06 Amazon Technologies, Inc. Identity mapping for federated user authentication
AU2017315345B2 (en) * 2016-08-23 2022-01-06 BBM Health LLC Blockchain-based mechanisms for secure health information resource exchange
CN106357644B (zh) * 2016-09-21 2019-07-12 江苏通付盾科技有限公司 基于区块链网络的身份认证方法、系统及服务器
US10296764B1 (en) * 2016-11-18 2019-05-21 Amazon Technologies, Inc. Verifiable cryptographically secured ledgers for human resource systems

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101567780A (zh) * 2009-03-20 2009-10-28 武汉理工大学 一种针对加密数字证书的密钥管理与恢复方法
WO2016118359A1 (en) * 2015-01-22 2016-07-28 Alibaba Group Holding Limited Method, apparatus, and system for quantum key distribution
CN105468994A (zh) * 2015-11-26 2016-04-06 布比（北京）网络技术有限公司 一种对象转移方法、装置及系统
CN106022917A (zh) * 2016-05-08 2016-10-12 杭州复杂美科技有限公司 区块链撮合交易所方案
CN107066893A (zh) * 2017-02-28 2017-08-18 腾讯科技（深圳）有限公司 区块链中账户信息的处理方法和装置

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10885207B2 (en) 2018-10-31 2021-01-05 Advanced New Technologies Co., Ltd. Method, apparatus, and electronic device for blockchain-based recordkeeping
US11361089B2 (en) 2018-10-31 2022-06-14 Advanced New Technologies Co., Ltd. Method, apparatus, and electronic device for blockchain-based recordkeeping
US11550935B2 (en) 2018-10-31 2023-01-10 Advanced New Technologies Co., Ltd. Method, apparatus, and electronic device for blockchain-based recordkeeping
ES2774397A1 (es) * 2019-01-18 2020-07-20 Telefonica Digital Espana Slu Metodo y sistema para recuperacion de claves criptograficas de una red de cadena de bloques
CN111369259A (zh) * 2020-03-10 2020-07-03 北京意锐新创科技有限公司 适用于区块链支持的支付方法和装置
CN113435888A (zh) * 2020-04-13 2021-09-24 腾讯科技（深圳）有限公司 一种账户数据处理方法、装置、设备及存储介质
CN113435888B (zh) * 2020-04-13 2022-05-31 腾讯科技（深圳）有限公司 一种账户数据处理方法、装置、设备及存储介质
CN111461721A (zh) * 2020-04-16 2020-07-28 北京俩撇科技有限公司 一种基于区块链的保护账户、验证交易的方法及装置
CN115941364A (zh) * 2023-03-13 2023-04-07 广东电网有限责任公司 基于智能电网的资产数据管理方法及其系统

Also Published As

Publication number Publication date
CN107066893A (zh) 2017-08-18
CN107066893B (zh) 2018-11-09
US20190229927A1 (en) 2019-07-25
US10785038B2 (en) 2020-09-22
US11477034B2 (en) 2022-10-18
US20200374134A1 (en) 2020-11-26

Similar Documents

Publication Publication Date Title
WO2018157788A1 (zh) 区块链中账户信息的处理方法和装置、存储介质和电子装置
EP3685334B1 (en) Improving integrity of communications between blockchain networks and external data sources
US11777726B2 (en) Methods and systems for recovering data using dynamic passwords
US10673632B2 (en) Method for managing a trusted identity
CN109951489B (zh) 一种数字身份认证方法、设备、装置、系统及存储介质
US11082221B2 (en) Methods and systems for creating and recovering accounts using dynamic passwords
CN111062716B (zh) 生成区块链签名数据的方法及装置、区块链交易发起系统
US11341466B2 (en) Transferring digital tickets based on blockchain networks
US20160162897A1 (en) System and method for user authentication using crypto-currency transactions as access tokens
CN109845220A (zh) 用于提供区块链参与者身份绑定的方法和装置
KR20190075793A (ko) 블록체인을 이용한 일회성 접근 권한 부여 시스템
JP2023502346A (ja) 量子安全ネットワーキング
TWI728587B (zh) 用於安全地執行加密操作的電腦實施的方法、系統及裝置
EP4092984A1 (en) Data processing method and apparatus, device and medium
CN110365472B (zh) 基于非对称密钥池对的量子通信服务站数字签名方法、系统
US11729159B2 (en) System security infrastructure facilitating protecting against fraudulent use of individual identity credentials
TWI778319B (zh) 跨平台授權存取資源方法及授權存取系統
TWI818679B (zh) 非同質化代幣登入驗證系統及其方法
WO2024014017A1 (ja) メッセージ提示システム、提示用装置、及びメッセージ提示方法

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: 18761660

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: 18761660

Country of ref document: EP

Kind code of ref document: A1