WO2021204273A1 - 资产类型注册、交易记录验证 - Google Patents

资产类型注册、交易记录验证 Download PDF

Info

Publication number
WO2021204273A1
WO2021204273A1 PCT/CN2021/086277 CN2021086277W WO2021204273A1 WO 2021204273 A1 WO2021204273 A1 WO 2021204273A1 CN 2021086277 W CN2021086277 W CN 2021086277W WO 2021204273 A1 WO2021204273 A1 WO 2021204273A1
Authority
WO
WIPO (PCT)
Prior art keywords
ciphertext
list
ring signature
public key
verification
Prior art date
Application number
PCT/CN2021/086277
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 WO2021204273A1 publication Critical patent/WO2021204273A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3829—Payment protocols; Details thereof insuring higher security of transaction involving key management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3825—Use of electronic signatures
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • 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/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
    • H04L9/0819—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s)
    • H04L9/0825—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s) using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates
    • 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
    • H04L9/3255—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 using group based signatures, e.g. ring or threshold signatures

Definitions

  • This manual relates to the field of information technology, and particularly relates to asset type registration and transaction record verification.
  • One of the embodiments of this specification provides an object encryption method, which includes: generating a first ciphertext of the identification information of the object to be encrypted; generating a ring signature for a ring signature message using a public key set and a target private key, wherein the The ring signature message includes the first ciphertext, the public key set is obtained based on the preset object list and the first ciphertext, and when the object to be encrypted belongs to the preset object list, the public key The set includes a public key matching the target private key.
  • One of the embodiments of this specification provides an object encryption system, which includes: a first ciphertext generating module for generating a first ciphertext of identification information of an object to be encrypted; a ring signature generating module for using a public key set Generate a ring signature on a ring signature message with a target private key, wherein the ring signature message includes the first ciphertext, the public key set is obtained based on a preset object list and the first ciphertext, and when the When the object to be encrypted belongs to the preset object list, the public key set includes a public key matching the target private key.
  • One of the embodiments of this specification provides an object encryption device, which includes a processor and a storage device.
  • the storage device is used to store instructions.
  • the processor executes the instructions, the implementation is as described in any embodiment of this specification The object encryption method.
  • One of the embodiments of this specification provides an object verification method, which includes: obtaining a first ciphertext and a ring signature, the first ciphertext being generated based on the identification information of the object to be verified; and using a public key set to verify the ring signature The set of public keys is obtained based on the preset object list and the first ciphertext; if the verification is successful, it is determined that the first ciphertext is an encryption result of an object from the preset object list.
  • One of the embodiments of this specification provides an object verification system, which includes: a first acquisition module for acquiring a first ciphertext and a ring signature, the first ciphertext being generated based on the identification information of the object to be verified; the ring signature
  • the verification module is configured to verify the ring signature using a set of public keys, the set of public keys is obtained based on the preset object list and the first ciphertext; the determining module is configured to: if the verification of the ring signature verification module succeeds, then It is determined that the first ciphertext is an encryption result of an object from a preset object list.
  • One of the embodiments of this specification provides an object verification apparatus, which includes a processor and a storage device.
  • the storage device is used to store instructions.
  • the processor executes the instructions, the implementation is as described in any embodiment of this specification The object verification method.
  • One of the embodiments of this specification provides an asset type registration method, wherein the method is executed by a user terminal of a blockchain member, the blockchain is provided with a list of permitted asset types, and the method includes: obtaining Asset type; based on the object encryption method described in any embodiment of this specification, the asset type to be registered is regarded as the object to be encrypted, and the list of permitted asset types is processed as a preset object list to obtain the first Ciphertext and ring signature; generating transaction records based at least on the first ciphertext and ring signature; uploading the transaction records to the blockchain network.
  • One of the embodiments of this specification provides an asset type registration system, which includes: a second acquisition module for acquiring the asset type to be registered;
  • the object encryption method uses the asset type to be registered as the object to be encrypted, and the list of permitted asset types is processed as a preset object list to obtain the first ciphertext and the ring signature;
  • the transaction record generation module is used for at least A transaction record is generated based on the first ciphertext and the ring signature;
  • the transaction record upload module is used to upload the transaction record to the blockchain network.
  • One of the embodiments of this specification provides an asset type registration device, which includes a processor and a storage device.
  • the storage device is used to store instructions.
  • the processor executes the instructions, the implementation is as described in any embodiment of this specification The asset type registration method described.
  • One of the embodiments of this specification provides a transaction record verification method, which is executed by a blockchain node receiving the transaction record, the blockchain is provided with a list of permitted asset types, and the transaction record includes the first generated based on the asset type.
  • a ciphertext, and a ring signature the method includes: verifying the ring signature based on the object verification method described in any embodiment of this specification using the list of permitted asset types as a preset object type list; if If the verification fails, the first ciphertext is not registered for the record.
  • One of the embodiments of this specification provides a transaction record verification system, which includes: a ring signature verification module, configured to use the permitted asset type list as a preset object based on the object verification method described in any embodiment of this specification The type list is used for verifying the ring signature; the second processing module is used for not registering the first ciphertext if the ring signature verification fails.
  • One of the embodiments of this specification provides a transaction record verification device, which includes a processor and a storage device.
  • the storage device is used to store instructions.
  • the described transaction record verification method is used to verify the transaction record verification method.
  • Fig. 1 is a schematic diagram of an application scenario of a blockchain system according to some embodiments of this specification
  • Fig. 2 is an exemplary flowchart of an asset type registration method according to some embodiments of the present specification
  • Fig. 3 is an exemplary flowchart of an asset type encryption method according to some embodiments of the present specification
  • Fig. 4 is an exemplary flowchart of a transaction record verification method according to some embodiments of the present specification
  • Fig. 5 is an exemplary flowchart of an asset type verification method according to some embodiments of the present specification
  • Fig. 6 is an exemplary block diagram of an object encryption system according to some embodiments of the present specification.
  • Fig. 7 is an exemplary block diagram of an object verification system according to some embodiments of the present specification.
  • Fig. 8 is an exemplary block diagram of an asset type registration system according to some embodiments of the present specification.
  • Fig. 9 is an exemplary block diagram of a transaction record verification system according to some embodiments of the present specification.
  • system is a method for distinguishing different components, elements, parts, parts, or assemblies of different levels.
  • the words can be replaced by other expressions.
  • the embodiments in this specification can be applied to the privacy protection of asset types in electronic transaction scenarios.
  • a list of permitted asset types can be preset, and the list of permitted asset types includes asset types permitted to be used by the entity.
  • entities may include one or more of individuals, groups, organizations, companies, and the like.
  • the list of permitted asset types may be published by an entity playing a regulatory role, for example, by a regulatory agency. It should be noted that this specification does not impose specific restrictions on the definition and classification of assets.
  • asset types can include currencies issued by countries or regions (such as RMB, US dollars, British pounds, euros, etc.), virtual currencies (such as Bitcoin, One or more of Ether, Litecoin, etc.), securities, funds, stocks, real estate, real estate, car products, etc.
  • countries or regions such as RMB, US dollars, British pounds, euros, etc.
  • virtual currencies such as Bitcoin, One or more of Ether, Litecoin, etc.
  • securities funds, stocks, real estate, real estate, car products, etc.
  • the embodiments in this specification provide asset type encryption, verification methods, asset type registration methods, transaction record verification methods and systems.
  • Asset types are concealed by encryption, and a set of public keys is constructed and a ring signature is generated to make it possible to pass The ring signature is verified to determine whether the encrypted asset type is the encryption result of the asset type from the approved asset type list. It is worth noting that although this manual mainly describes electronic transaction scenarios based on blockchain as an example, the principles of this manual can also be applied to other electronic transaction scenarios, and this manual does not impose any restrictions on this.
  • Fig. 1 is a schematic diagram of an application scenario of a blockchain system according to some embodiments of this specification.
  • the blockchain system 100 may include a blockchain client 110 (which can be referred to as a client for short), a blockchain network 120, and a network 130, where the blockchain network 120 includes more than one blockchain node (Can be referred to as "nodes" for short), such as blockchain nodes 120-1, 120-2, 120-3...120-n, etc.
  • the blockchain client 110 can be connected to the blockchain network 120 through the network 130. Entities can access the blockchain network 120 through the blockchain client 110, and entities that join the blockchain network 120 can also be referred to as blockchain members.
  • the blockchain client 110 may upload information and/or data to one or more blockchain nodes in the blockchain network 120, for example, upload transaction records.
  • the transaction record may include transaction information (may be simply referred to as "transaction" written in the block.
  • the blockchain client 110 may initiate a query to one or more blockchain nodes in the blockchain network 120 to obtain the area stored in the blockchain (ie, distributed ledger, which is continuously generated). The data in the block chained), such as transactions.
  • the user terminal may include various types of devices with information receiving and/or sending functions.
  • the user terminal may include a smart phone, a tablet computer, a laptop computer, a desktop computer, etc., or any combination thereof.
  • Each node in the blockchain network 120 needs to verify and confirm the transaction, and then generate a new block (this process can be called "accounting"). At the same time, each node can maintain the data stored in each node through a consensus mechanism. Consistency of distributed ledgers. It is worth noting that the blockchain node can also be regarded as the client terminal of the blockchain network 120. Unlike other client terminals, the blockchain node needs to participate in accounting. In addition, the entity can join the blockchain network 120 through a user terminal that does not participate in accounting, or can join the blockchain network 120 through a blockchain node that participates in accounting.
  • nodes may include various types of computing devices, such as servers.
  • the server may be an independent server or a server group, and the server group may be centralized or distributed.
  • the server may be regional or remote.
  • the server may be executed on a cloud platform.
  • the cloud platform may include one or any combination of private cloud, public cloud, hybrid cloud, community cloud, decentralized cloud, internal cloud, etc.
  • the network 130 connects the various components of the system so that communication between the various components can be carried out.
  • the network between the various parts in the system may include a wired network and/or a wireless network.
  • the network 130 may include a cable network, a wired network, an optical fiber network, a telecommunication network, an internal network, the Internet, a local area network (LAN), a wide area network (WAN), a wireless local area network (WLAN), a metropolitan area network (MAN), public Switched telephone network (PSTN), Bluetooth network, ZigBee network (ZigBee), near field communication (NFC), device bus, device line, cable connection, etc. or any combination thereof.
  • LAN local area network
  • WAN wide area network
  • WLAN wireless local area network
  • MAN metropolitan area network
  • PSTN public Switched telephone network
  • Bluetooth network ZigBee network
  • ZigBee ZigBee network
  • NFC near field communication
  • the network connection between each two parts can be in one of the above-mentioned ways, or in multiple ways. It can be understood that the network 130 and the blockchain network 120 do not have to have a clear boundary. In a more general application scenario, the blockchain node and the ordinary network node can be connected to the same physical network, and the blockchain node is in the logical The above constitutes a blockchain network.
  • Fig. 2 is an exemplary flowchart of an asset type registration method according to some embodiments of the present specification.
  • Asset type registration can refer to the registration and filing of asset types.
  • asset type registration can refer to the registration of encrypted asset types (ie, the first ciphertext) in the accounts of blockchain members.
  • the asset type registration method can be executed by the client of the blockchain member.
  • the process 200 may include:
  • Step 210 Obtain the asset type to be registered.
  • step 210 may be performed by the second acquisition module 810.
  • Step 220 Obtain the first ciphertext and the ring signature.
  • step 220 may be performed by the first processing module 820.
  • the first ciphertext can be obtained by encrypting the identification information of the asset type to be registered, so that the asset type can be concealed, thereby protecting the privacy of the entity.
  • the ring signature is the signature of the first ciphertext as the signature message, and its function can be equivalent to the "identity proof" of the hidden asset type. If the signature verification is successful, it can prove that the first ciphertext is an asset from the permitted asset list. Type of encryption result.
  • Step 230 Generate a transaction record based on at least the first ciphertext and the ring signature.
  • step 230 may be performed by the transaction record generation module 830.
  • the transaction record may include any information related to the transaction, including but not limited to account information, transaction time, amount, transaction contract, and the like.
  • the transaction record may include identification information of the account, the first ciphertext, the ring signature, and the first digital signature.
  • the identification information of the account is used to indicate to which account the encrypted asset type (that is, the first ciphertext) is registered.
  • the first digital signature may be generated by using the private key of the account on the first message to be signed, and the first message to be signed includes the identification information of the account, the first ciphertext, and the ring signature.
  • a digital signature can be used to prove the identification information of the account, the first ciphertext and the source of the ring signature.
  • the public key of the account is used to verify that the first digital signature is successful, it indicates the identification information of the account ,
  • the first ciphertext and the ring signature are from the account and have not been tampered with during the dissemination process.
  • the identification information of the account may include an account address, and the address may correspond to a public key of the account.
  • the transaction record may include more information.
  • the list of permitted asset types can be published by the client of the blockchain administrator, and the blockchain administrator can be responsible for supervising the asset types that blockchain members need to register.
  • the client of the blockchain member can send the asset type to be registered and the first ciphertext to the client of the blockchain administrator.
  • the client of the blockchain administrator After the client of the blockchain administrator receives the asset type to be registered and the first cipher text, it verifies whether the received first cipher text is the encryption result of the identification information of the received asset type.
  • the client of the blockchain member returns the second digital signature.
  • the transaction record generated by the user end of the blockchain member may also include the second digital signature.
  • the second digital signature may be generated by using the private key of the blockchain administrator on the second message to be signed, and the second message to be signed includes the identification information of the account and the first ciphertext.
  • the function of the second digital signature is that if the verification is successful, it indicates that the blockchain administrator has known the asset type to be registered and approved that the encrypted asset type (ie the first ciphertext) can be registered to the On the account.
  • the second digital signature from the client of the blockchain administrator may also be added to the first message to be signed.
  • the transaction record may be expressed as (a, E, R; Sig'; Sig), where a represents the identification information of the account, E represents the first cipher text, and R represents the ring signature , Sig' represents the second digital signature generated by the client of the blockchain administrator, and Sig represents the first digital signature generated by the client of the blockchain member.
  • Step 240 Upload the transaction record to the blockchain network.
  • step 240 may be performed by the transaction record uploading module 840.
  • the client of the blockchain member may broadcast the transaction record to the nodes in the blockchain network 120.
  • the blockchain node in the blockchain network 120 verifies the content in the transaction record. If the verification is successful, it can be written into a new block.
  • verifying transaction records please refer to Figure 4 and its related descriptions.
  • Fig. 3 is an exemplary flowchart of an asset type encryption method according to some embodiments of the present specification.
  • the encryption method can be implemented by the user side of the blockchain member. It should be noted that the encryption method can also be implemented in other electronic transaction scenarios to: conceal the asset type; and make it possible to determine whether the encrypted asset type is the encryption result of the asset type from the permitted asset list by verifying the ring signature.
  • the process 300 may include:
  • Step 310 Generate a first ciphertext of the identification information of the asset type to be encrypted.
  • step 310 may be performed by the first ciphertext generation module 610.
  • the first ciphertext may be in accordance with the Pedersen commitment protocol.
  • E represents the ciphertext
  • G and H are points on the elliptic curve
  • G can be called the first base point
  • H can be called the second base point
  • t 1 And t 2 are both integers.
  • the base point on the elliptic curve involved in this specification can be pre-determined and used globally.
  • the first base point G here can also be used to generate a public-private key pair.
  • E represents the first ciphertext
  • r represents a random number
  • Pk represents the first public key
  • sn_k represents the The identification information (integer, such as number) of the asset type to be verified
  • H represents a point on the elliptic curve.
  • P k P r G
  • P r represents the first private key matching the first public key
  • P r can take an integer. It is worth noting that due to the existence of random numbers, for the same asset type, the first ciphertext generated is different due to different random numbers.
  • the client of the blockchain member can provide the client of the blockchain administrator with a random number r and the asset type to be registered (corresponding to sn_k ) And the first ciphertext E.
  • the user terminal of the blockchain administrator Based on the received random number r, the public key P k of the account, the identification information sn_k of the asset type to be registered, and the second base point H, the user terminal of the blockchain administrator calculates the first A ciphertext. Compare the calculated first ciphertext with the received first ciphertext. If the two are consistent, it means that the random number r provided by the user end of the blockchain member and the asset type to be registered (corresponding sn_k) and the first ciphertext E are reliable.
  • Step 320 Use the public key set and the target private key to generate a ring signature on the ring signature message, where the ring signature message may include the first ciphertext.
  • the ring signature message may also include other information, such as an account identifier. information.
  • the public key set is obtained based on the permitted asset type list and the first ciphertext, and when the asset type to be encrypted belongs to the permitted asset type list, the public key set includes a public key matching the target private key.
  • step 320 may be performed by the ring signature generation module 620.
  • Ring signature is a signature scheme that can realize the unconditional anonymity of the signer. It has the following characteristics: the signature phase requires a public key set and the signer’s private key (ie, the target private key). To generate a correct ring signature (verification) A necessary condition for successful signing), it is necessary to ensure that the public key set includes the public key that matches the target private key; in the verification phase, the verifier cannot infer the private key corresponding to which public key in the public key set is used to generate the ring signature.
  • a public key set is constructed based on the list of permitted asset types and the first ciphertext (ie, the encrypted asset type), where the list of permitted asset types and the first ciphertext are both publicly available, and the public key set is combined with the list of permitted asset types.
  • the relationship between the public key set and the target private key is affected by the ownership relationship of the asset type to be encrypted relative to the list of permitted asset types.
  • the public key set includes the target private key
  • the matching public key can generate the correct ring signature.
  • the public key set since the relationship between the public key set and the target private key is affected by the ownership of the asset type to be encrypted relative to the list of permitted asset types, when the asset type to be encrypted belongs to the list of permitted asset types, the public key set includes those that match the target private key.
  • the public key implies that when the asset type to be encrypted does not belong to the list of permitted asset types, the public key set does not include the public key matching the target private key or the public key set includes the target private key matching
  • the probability of the public key is negligible (then the probability that the correct ring signature cannot be generated or the correct ring signature is generated can be ignored). In this way, when the ring signature verification is successful, the asset type to be encrypted (that is, the asset type to be verified as described later) can be considered to belong to the list of permitted asset types.
  • the public key set is obtained in the following manner: the identification information of the asset types in the permitted asset type list is respectively subjected to the first operation to obtain the permitted asset type ciphertext list; the first ciphertext and the permitted asset are respectively calculated The difference value of each ciphertext in the type ciphertext list, and the public key set includes each difference value.
  • the first operation is such that when the identification information of the asset type to be encrypted belongs to the list of permitted asset types, the public key set includes the public key matching the target private key.
  • the first operation includes calculating according to sn_i*H to obtain each ciphertext in the ciphertext list of permitted asset types, where , Sn_i represents the identification information of the asset type in the permitted asset type list, and H is the second base point used to generate the first ciphertext.
  • Sn_i represents the identification information of the asset type in the permitted asset type list
  • H is the second base point used to generate the first ciphertext.
  • the process shown in Fig. 3 can also be applied to any scene where an object needs to be concealed and proves that the concealed object comes from a preset object list.
  • the preset object list may also be a list of persons, a list of goods, a list of vehicles, a list of addresses, etc., and the objects that need to be hidden are from the list of preset objects. .
  • Fig. 4 is an exemplary flowchart of a transaction record verification method according to some embodiments of the present specification.
  • the transaction record verification method may be executed by a blockchain node that receives the transaction record, the transaction record including the first ciphertext generated based on the asset type, and the ring signature.
  • the process 400 may include:
  • Step 410 Verify the ring signature in the transaction record.
  • step 410 may be performed by the ring signature verification module 910.
  • the purpose of verifying the ring signature in the transaction record is to determine whether the first ciphertext is an encryption result of an asset type from a list of permitted asset types.
  • Step 420 If the ring signature verification fails, the first ciphertext in the transaction record is not registered. In some embodiments, step 420 may be performed by the second processing module 920.
  • the blockchain node may also verify other content in the transaction record.
  • the public key of the account can be used to verify the first digital signature. If the verification is successful, it can be determined whether the signature message corresponding to the first digital signature (ie, the first message to be signed) comes from the blockchain The member’s user terminal has not been tampered with during the propagation process.
  • the public key of the blockchain administrator can be used to verify the second digital signature. If the verification is successful, it means that the blockchain administrator already knows the asset type to be registered and approves the asset type that can be encrypted ( That is, the first ciphertext) is registered on the account. It should be noted that, in the case of any verification failure, the transaction record can not be registered.
  • the blockchain node may register (ie, register) the first ciphertext in the transaction record in the account of the blockchain member.
  • the verification and/or registration related processes can be implemented through smart contracts.
  • a smart contract used to implement verification and/or registration related processes can be pre-deployed in the blockchain.
  • the transaction record can include the address of the smart contract.
  • the smart contract can be invoked according to the address in the transaction record, so as to realize the related process of verification and/or registration.
  • Fig. 5 is an exemplary flowchart of an asset type verification method according to some embodiments of the present specification.
  • the asset type verification method can be implemented by the client of the blockchain node. It should be noted that the asset type verification method can also be implemented in other electronic transaction scenarios to determine whether the encrypted asset type (that is, the first ciphertext) is the encryption result of the asset type from the list of permitted asset types.
  • Step 510 Obtain a first ciphertext and a ring signature.
  • the first ciphertext is generated based on the identification information of the asset type to be verified.
  • step 510 may be performed by the first obtaining module 710.
  • Step 520 Use a public key set to verify the ring signature, which is obtained based on the permitted asset type list and the first ciphertext.
  • step 520 may be performed by the ring signature verification module 720.
  • the set of public keys may be calculated based on the list of permitted asset types and the first ciphertext during verification.
  • the ring signature may include the set of public keys, and the set of public keys is extracted from the ring signature during verification.
  • verification may be performed based on the set of public keys, the ring signature message (eg, the first ciphertext), and the ring signature to verify whether the ring signature is that the ring signature message corresponds to the set of public keys Valid signature.
  • step 530 if the verification is successful, it is determined that the first ciphertext is an encryption result of the asset type from the permitted asset type list. In some embodiments, step 530 may be performed by the determining module 730.
  • successful ring signature verification in the case of successful ring signature verification, it can be considered that the asset type to be verified belongs to the permitted asset type list, that is, the first ciphertext is the encryption result of the asset type from the permitted asset type list.
  • successful ring signature verification will not reveal which public key in the public key set of the signer’s private key (that is, the target private key) corresponds to, and will not reveal that the asset type corresponding to the first ciphertext is in the list of permitted asset types. Which asset type.
  • the process shown in FIG. 5 can also be applied to any scene that verifies whether other hidden objects are from a preset object list.
  • the preset object list may also be a list of personnel, a list of products, a list of vehicles, a list of addresses, and so on.
  • Fig. 6 is an exemplary block diagram of an object encryption system according to some embodiments of the present specification.
  • the object encryption system 600 may include a first ciphertext generation module 610 and a ring signature generation module 620.
  • the first ciphertext generating module 610 may be used to generate the first ciphertext of the identification information of the object to be encrypted.
  • the ring signature generation module 620 may be configured to generate a ring signature on a ring signature message using a public key set and a target private key, where the ring signature message includes the first ciphertext, and the public key set is based on a preset object list and The first ciphertext is obtained, and when the object to be encrypted belongs to the permitted object list, the public key set includes a public key matching the target private key.
  • object encryption system 600 For more details about the object encryption system 600 and its modules, please refer to FIG. 3 and related descriptions.
  • Fig. 7 is an exemplary block diagram of an object verification system according to some embodiments of the present specification.
  • the object verification system 700 may include a first acquisition module 710, a ring signature verification module 720, and a determination module 730.
  • the first obtaining module 710 may be used to obtain the first ciphertext and the ring signature, and the first ciphertext may be generated based on the identification information of the object to be verified.
  • the ring signature verification module 720 may be configured to verify the ring signature using a set of public keys, and the set of public keys may be obtained based on a preset object list and the first ciphertext.
  • the determining module 730 may be configured to determine that the first ciphertext is an encryption result of an object from a preset object list if the verification by the ring signature verification module is successful.
  • object verification system 700 For more details about the object verification system 700 and its modules, please refer to FIG. 5 and related descriptions.
  • Fig. 8 is an exemplary block diagram of an asset type registration system according to some embodiments of the present specification.
  • the asset type registration system 800 may include a second acquisition module 810, a first processing module 820, a transaction record generation module 830, and a transaction record upload module 840.
  • the second obtaining module 810 may be used to obtain the asset type to be registered.
  • the first processing module 820 may be used to obtain the first ciphertext and the ring signature.
  • the specific manner in which the first processing module 820 obtains the first ciphertext and the ring signature reference may be made to FIG. 3 and related descriptions.
  • the transaction record generating module 830 may be configured to generate a transaction record based on at least the first ciphertext and the ring signature.
  • the transaction record uploading module 840 may be used to upload the transaction record to the blockchain network.
  • asset type registration system 800 For more details about the asset type registration system 800 and its modules, please refer to FIG. 2 and related descriptions.
  • Fig. 9 is an exemplary block diagram of a transaction record verification system according to some embodiments of the present specification.
  • the transaction record verification system 900 may include a ring signature verification module 910 and a second processing module 920.
  • the ring signature verification module 910 can be used to verify the ring signature in the transaction record.
  • the ring signature verification module 910 can be used to verify the ring signature in the transaction record.
  • FIG. 5 For the specific manner of verifying the ring signature by the ring signature verification module 910, reference may be made to FIG. 5 and related descriptions.
  • the second processing module 920 may be configured to not register the first ciphertext in the transaction record if the ring signature verification fails.
  • the systems and modules shown in FIGS. 6-9 can be implemented in various ways.
  • the system and its modules can be implemented by hardware, software, or a combination of software and hardware.
  • the hardware part can be implemented using dedicated logic;
  • the software part can be stored in a memory and executed by an appropriate instruction execution system, such as a microprocessor or dedicated design hardware.
  • an appropriate instruction execution system such as a microprocessor or dedicated design hardware.
  • the above-mentioned methods and systems can be implemented using computer-executable instructions and/or included in processor control codes, for example on a carrier medium such as a disk, CD or DVD-ROM, such as a read-only memory (firmware)
  • Such codes are provided on a programmable memory or a data carrier such as an optical or electronic signal carrier.
  • the system and its modules in this specification can not only be implemented by hardware circuits such as very large scale integrated circuits or gate arrays, semiconductors such as logic chips, transistors, etc., or programmable hardware devices such as field programmable gate arrays, programmable logic devices, etc., It can also be implemented by, for example, software executed by various types of processors, and can also be implemented by a combination of the above-mentioned hardware circuit and software (for example, firmware).
  • the above description of the system and its modules is only for convenience of description, and does not limit this specification within the scope of the examples mentioned. It can be understood that for those skilled in the art, after understanding the principle of the system, without departing from this principle, various modules can be combined arbitrarily, or a subsystem can be connected to other modules.
  • the transaction record generating module 830 and the transaction record uploading module 840 disclosed in FIG. 8 may be different modules in the same system, or one module may implement the functions of two or more modules mentioned above.
  • the first processing module 820 may include the object encryption system 600.
  • the ring signature verification module 910 may include the object verification system 700. Such deformations are all within the protection scope of this specification.
  • the possible beneficial effects of the embodiments of this specification include, but are not limited to: (1) The type of asset is concealed by encryption, and the public key set is constructed and the ring signature is generated, so that the ring signature can be verified to confirm that the encrypted asset type is from The encryption result of the asset type in the list of permitted asset types, and the verification of the ring signature will not reveal which asset type in the list of permitted asset types corresponds to the encrypted asset type; (2) Due to the existence of random numbers, for the same asset type, generated The first ciphertext is different due to different random numbers, so it can effectively ensure that it is difficult to infer the asset type from the first ciphertext if the random number does not leak. It should be noted that different embodiments may have different beneficial effects. In different embodiments, the possible beneficial effects may be any one or a combination of the above, or any other beneficial effects that may be obtained.
  • the computer storage medium may contain a propagated data signal containing a computer program code, for example on a baseband or as part of a carrier wave.
  • the propagated signal may have multiple manifestations, including electromagnetic forms, optical forms, etc., or a suitable combination.
  • the computer storage medium may be any computer readable medium other than the computer readable storage medium, and the medium may be connected to an instruction execution system, device, or device to realize communication, propagation, or transmission of the program for use.
  • the program code located on the computer storage medium can be transmitted through any suitable medium, including radio, cable, fiber optic cable, RF, or similar medium, or any combination of the above medium.
  • the computer program codes required for the operations of the various parts of the embodiments of this specification can be written in any one or more programming languages, including object-oriented programming languages such as Java, Scala, Smalltalk, Eiffel, JADE, Emerald, C++, C#, VB.NET , Python, etc., conventional programming languages such as C language, VisualBasic, Fortran2003, Perl, COBOL2002, PHP, ABAP, dynamic programming languages such as Python, Ruby and Groovy, or other programming languages, etc.
  • the program code can run entirely on the user's computer, or run as an independent software package on the user's computer, or partly run on the user's computer and partly run on a remote computer, or run entirely on the remote computer or processing equipment.
  • the remote computer can be connected to the user's computer through any network form, such as a local area network (LAN) or a wide area network (WAN), or connected to an external computer (for example, via the Internet), or in a cloud computing environment, or as a service Use software as a service (SaaS).
  • LAN local area network
  • WAN wide area network
  • SaaS service Use software as a service

Abstract

本说明书中的实施例提供了资产类型注册、交易记录验证的方法及系统。通过加密隐匿资产类型，且通过构造公钥集合并生成环签名，使得可通过验证环签名来确定加密的资产类型是否为来自准许资产类型列表的资产类型的加密结果。

Description

资产类型注册、交易记录验证 技术领域
本说明书涉及信息技术领域，特别涉及一种资产类型注册、交易记录验证。
背景技术
依托互联网，电子交易极大便利了人们的生活和工作，但其中的隐私问题仍不容忽视。例如，在一些电子交易的场景中，实体(如，机构、公司等)开展业务使用的资产类型(如，人民币、美元、证券等)，可能是该实体的商业机密，需要针对其做隐私保护，避免对外(如竞争对手)泄露。另外，资产类型的泄露可能导致该实体的更多私密信息被获取。比如，在跨境汇款或者在供应链中，通过资产类型有可能推断出实体所在的地区，进而推断出该实体的身份信息。
因此，目前希望提供一种电子交易场景中针对资产类型的隐私保护方案。
发明内容
本说明书实施例之一提供一种对象加密方法，其中，包括：生成待加密对象的标识信息的第一密文；利用公钥集合和目标私钥对环签名消息生成环签名，其中，所述环签名消息包括所述第一密文，所述公钥集合基于预设对象列表和所述第一密文得到，且当所述待加密对象属于所述预设对象列表时，所述公钥集合包括与所述目标私钥匹配的公钥。
本说明书实施例之一提供一种对象加密系统，其中，包括：第一密文生成模块，用于生成待加密对象的标识信息的第一密文；环签名生成模块，用于利用公钥集合和目标私钥对环签名消息生成环签名，其中，所述环签名消息包括所述第一密文，所述公钥集合基于预设对象列表和所述第一密文得到，且当所述待加密对象属于所述预设对象列表时，所述公钥集合包括与所述目标私钥匹配的公钥。
本说明书实施例之一提供一种对象加密装置，其中，包括处理器和存储设备，所述存储设备用于存储指令，当所述处理器执行指令时，实现如本说明书任一实施例所述的对象加密方法。
本说明书实施例之一提供一种对象验证方法，其中，包括：获取第一密文以及环签 名，所述第一密文基于待验证对象的标识信息生成；使用公钥集合验证所述环签名，所述公钥集合基于预设对象列表和所述第一密文得到；若验证成功，则确定所述第一密文为来自预设对象列表的对象的加密结果。
本说明书实施例之一提供一种对象验证系统，其中，包括：第一获取模块，用于获取第一密文以及环签名，所述第一密文基于待验证对象的标识信息生成；环签名验证模块，用于使用公钥集合验证所述环签名，所述公钥集合基于预设对象列表和所述第一密文得到；确定模块，用于若所述环签名验证模块验证成功，则确定所述第一密文为来自预设对象列表的对象的加密结果。
本说明书实施例之一提供一种对象验证装置，其中，包括处理器和存储设备，所述存储设备用于存储指令，当所述处理器执行指令时，实现如本说明书任一实施例所述的对象验证方法。
本说明书实施例之一提供一种资产类型注册方法，其中，所述方法由区块链成员的用户端执行，所述区块链设置有准许资产类型列表，所述方法包括：获取待注册的资产类型；基于如本说明书任一实施例所述的对象加密方法将所述待注册的资产类型作为待加密对象，以及将所述准许资产类型列表作为预设对象列表进行处理，以获得第一密文以及环签名；至少基于所述第一密文以及环签名生成交易记录；将所述交易记录上传至区块链网络。
本说明书实施例之一提供一种资产类型注册系统，其中，包括：第二获取模块，用于获取待注册的资产类型；第一处理模块，用于基于如本说明书任一实施例所述的对象加密方法将所述待注册的资产类型作为待加密对象，以及将所述准许资产类型列表作为预设对象列表进行处理，以获得第一密文以及环签名；交易记录生成模块，用于至少基于所述第一密文以及环签名生成交易记录；交易记录上传模块，用于将所述交易记录上传至区块链网络。
本说明书实施例之一提供一种资产类型注册装置，其中，包括处理器和存储设备，所述存储设备用于存储指令，当所述处理器执行指令时，实现如本说明书任一实施例所述的资产类型注册方法。
本说明书实施例之一提供一种交易记录验证方法，其中，由接收交易记录的区块链节点执行，所述区块链设置有准许资产类型列表，所述交易记录包括基于资产类型生成的第一密文，以及环签名；所述方法包括：基于如本说明书任一实施例所述的对象验证 方法将所述准许资产类型列表作为预设对象类型列表，对所述环签名进行验证；若验证失败，则不对所述第一密文进行登记备案。
本说明书实施例之一提供一种交易记录验证系统，其中，包括：环签名验证模块，用于基于如本说明书任一实施例所述的对象验证方法将所述准许资产类型列表作为预设对象类型列表，对所述环签名进行验证；第二处理模块，用于若所述环签名验证失败，则不对所述第一密文进行登记备案。
本说明书实施例之一提供一种交易记录验证装置，其中，包括处理器和存储设备，所述存储设备用于存储指令，当所述处理器执行指令时，实现如本说明书任一实施例所述的交易记录验证方法。
附图说明
本说明书将以示例性实施例的方式进一步说明，这些示例性实施例将通过附图进行详细描述。这些实施例并非限制性的，在这些实施例中，相同的编号表示相同的结构。
图1是根据本说明书一些实施例所示的区块链系统的应用场景示意图；
图2是根据本说明书一些实施例所示的资产类型注册方法的示例性流程图；
图3是根据本说明书一些实施例所示的资产类型加密方法的示例性流程图；
图4是根据本说明书一些实施例所示的交易记录验证方法的示例性流程图；
图5是根据本说明书一些实施例所示的资产类型验证方法的示例性流程图；
图6是根据本说明书一些实施例所示的对象加密系统的示例性框图；
图7是根据本说明书一些实施例所示的对象验证系统的示例性框图；
图8是根据本说明书一些实施例所示的资产类型注册系统的示例性框图；
图9是根据本说明书一些实施例所示的交易记录验证系统的示例性框图。
具体实施方式
为了更清楚地说明本说明书实施例的技术方案，下面将对实施例描述中所需要使用的附图作简单的介绍。显而易见地，下面描述中的附图仅仅是本说明书的一些示例或实施例，对于本领域的普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图将本说明书应用于其它类似情景。除非从语言环境中显而易见或另做说明，图中 相同标号代表相同结构或操作。
应当理解，本文使用的“系统”、“装置”、“单元”和/或“模块”是用于区分不同级别的不同组件、元件、部件、部分或装配的一种方法。然而，如果其他词语可实现相同的目的，则可通过其他表达来替换所述词语。
如本说明书和权利要求书中所示，除非上下文明确提示例外情形，“一”、“一个”、“一种”和/或“该”等词并非特指单数，也可包括复数。一般说来，术语“包括”与“包含”仅提示包括已明确标识的步骤和元素，而这些步骤和元素不构成一个排它性的罗列，方法或者设备也可能包含其它的步骤或元素。
本说明书中使用了流程图用来说明根据本说明书的实施例的系统所执行的操作。应当理解的是，前面或后面操作不一定按照顺序来精确地执行。相反，可以按照倒序或同时处理各个步骤。同时，也可以将其他操作添加到这些过程中，或从这些过程移除某一步或数步操作。
本说明书中的实施例可应用于电子交易场景中针对资产类型的隐私保护。在一些电子交易的场景中，需要限制实体使用的资产类型，为此可以预设准许资产类型列表，准许资产类型列表包括准许实体使用的资产类型。在一些实施例中，实体可以包括个人、团体、机构、公司等中的一种或多种。在一些实施例中，准许资产类型列表可以由扮演监管角色的实体发布，例如，由监管机构发布。需要说明的是，本说明书对资产的定义和分类不作具体限制，例如，资产类型可以包括国家或地区发行的货币(如，人民币、美元、英镑、欧元等)、虚拟货币(如，比特币、以太币、莱特币等)、证券、基金、股票、地产、房产、车产等中的一种或多种。实体上传涉及资产类型的信息时，一方面不希望暴露该信息涉及的资产类型，另一方面要证明该信息涉及的资产类型属于准许资产类型列表。为此，本说明书中的实施例提供了资产类型加密、验证方法、资产类型注册方法、交易记录验证方法及系统，通过加密隐匿资产类型，且通过构造公钥集合并生成环签名，使得可通过验证环签名来确定加密的资产类型是否为来自准许资产类型列表的资产类型的加密结果。值得说明的是，虽然本说明书主要以基于区块链的电子交易场景为例进行了描述，但本说明书的原理同样可以应用到其他电子交易场景，本说明书对此不做任何限制。
图1是根据本说明书一些实施例所示的区块链系统的应用场景示意图。如图1所示，区块链系统100可以包括区块链用户端110(可简称为用户端)、区块链网络120及网络130，其中，区块链网络120包括一个以上区块链节点(可简称为“节点”)，如区 块链节点120-1、120-2、120-3…120-n等。
区块链用户端110可通过网络130连接于区块链网络120。实体可以通过区块链用户端110访问区块链网络120，加入区块链网络120的实体也可称为区块链成员。在一些实施例中，区块链用户端110可以上传信息和/或数据至区块链网络120中的一个或多个区块链节点，例如上传交易记录。在一些实施例中，交易记录可以包括写入区块中的交易信息(可简称为“交易”)。在一些实施例中，区块链用户端110可以向区块链网络120中的一个或多个区块链节点发起查询，以获得存储在区块链(即分布式账本，由持续生成的区块链接而成)中的数据，如交易。
在一些实施例中，用户端可以包括各类具有信息接收和/或发送功能的设备。在一些实施例中，用户端可以包括智能电话、平板计算机、膝上型计算机、台式计算机等或其任意组合。
区块链网络120中的各个节点需要对交易进行验证和确认，进而生成新的区块(此过程可称为“记账”)，同时，各节点可通过共识机制来维持存储在各节点的分布式账本的一致性。值得说明的是，区块链节点也可视为区块链网络120的用户端，不同于其他用户端，区块链节点需要参与记账。另外，实体可以通过不参与记账的用户端加入区块链网络120，也可以通过参与记账的区块链节点加入区块链网络120。
在一些实施例中，节点可以包括各类计算设备，如服务器。在一些实施例中，服务器可以是独立的服务器或者服务器组，该服务器组可以是集中式的或者分布式的。在一些实施例中，服务器可以是区域的或者远程的。在一些实施例中，服务器可在云平台上执行。例如，该云平台可包括私有云、公共云、混合云、社区云、分散式云、内部云等中的一种或其任意组合。
网络130连接系统的各组成部分，使得各部分之间可以进行通讯。在系统中各部分之间的网络可以包括有线网络和/或无线网络。例如，网络130可以包括电缆网络、有线网络、光纤网络、电信网络、内部网络、互联网、局域网络(LAN)、广域网络(WAN)、无线局域网络(WLAN)、城域网(MAN)、公共交换电话网络(PSTN)、蓝牙网络、紫蜂网络(ZigBee)、近场通信(NFC)、设备内总线、设备内线路、线缆连接等或其任意组合。每两个部分之间的网络连接可以是采用上述一种方式，也可以是采取多种方式。可以理解，网络130与区块链网络120不必具有明显的分界，在更一般的应用场景中，区块链节点与普通网络节点可以共同接入同一物理网络中，其中的区块链节点在逻辑上构成区块链网络。
图2是根据本说明书一些实施例所示的资产类型注册方法的示例性流程图。资产类型注册可以指将资产类型登记备案，在基于账户模型的区块链场景下，资产类型注册可以指将加密的资产类型(即第一密文)登记到区块链成员的账户中。在一些实施例中，该资产类型注册方法可由区块链成员的用户端执行。流程200可以包括：
步骤210，获取待注册的资产类型。在一些实施例中，步骤210可以由第二获取模块810执行。
步骤220，获得第一密文以及环签名。在一些实施例中，步骤220可以由第一处理模块820执行。
所述第一密文可通过加密待注册的资产类型的标识信息得到，如此可以隐匿资产类型，从而保护实体的隐私。所述环签名是以第一密文的为签名消息的签名，其作用可等同于被隐匿资产类型的“身份证明”，若验签成功则可证明第一密文为来自准许资产列表的资产类型的加密结果。
关于获得第一密文以及环签名的具体方式，可以参考以下图3及其相关描述。
步骤230，至少基于所述第一密文以及环签名生成交易记录。在一些实施例中，步骤230可以由交易记录生成模块830执行。
在一些实施例中，所述交易记录可以包括与交易相关的任何信息，包括但不限于账户信息、交易时间、金额、交易合同等。在一些实施例中，所述交易记录可以包括所述账户的标识信息、所述第一密文、所述环签名和第一数字签名。其中，所述账户的标识信息用于指示将加密的资产类型(即所述第一密文)注册到哪个账户。第一数字签名可以是利用所述账户的私钥对第一待签名消息生成的，所述第一待签名消息包括所述账户的标识信息、所述第一密文和所述环签名，第一数字签名可用于证明所述账户的标识信息、所述第一密文和所述环签名的来源，若利用所述账户的公钥验证第一数字签名成功，则说明所述账户的标识信息、所述第一密文和所述环签名来自所述账户且传播过程中未经篡改。在一些实施例中，所述账户的标识信息可以包括账户地址，该地址可对应于所述账户的公钥。
在一些实施例中，所述交易记录可以包括更多信息。例如，在区块链场景中，准许资产类型列表可以由区块链管理员的用户端发布，区块链管理员可以负责监管区块链成员要注册的资产类型。基于此，区块链成员的用户端可以将待注册的资产类型和所述第一密文发送给区块链管理员的用户端。区块链管理员的用户端接收到待注册的资产类型 和第一密文后，验证接收到的第一密文是否为接收到的资产类型的标识信息的加密结果，若通过验证，则向区块链成员的用户端返回第二数字签名。相应地，区块链成员的用户端生成的交易记录还可以包括所述第二数字签名。其中，所述第二数字签名可以是利用区块链管理员的私钥对第二待签名消息生成的，所述第二待签名消息包括所述账户的标识信息和所述第一密文。所述第二数字签名的作用在于，若验签成功，则表明区块链管理员已知晓待注册的资产类型并批准可将加密的资产类型(即所述第一密文)注册到所述账户上。在一些实施例中，区块链成员的用户端在生成第一数字签名时，可以将来自区块链管理员用户端的第二数字签名也加入到第一待签名消息中。
仅作为示例，所述交易记录可表示为(a,E,R；Sig'；Sig)，其中，a表示所述账户的标识信息，E表示所述第一密文，R表示所述环签名，Sig'表示由区块链管理员的用户端生成的第二数字签名，Sig表示由区块链成员的用户端生成的第一数字签名。
步骤240，将所述交易记录上传至区块链网络。在一些实施例中，步骤240可以由交易记录上传模块840执行。
在一些实施例中，所述区块链成员的用户端可以向区块链网络120中的节点广播所述交易记录。区块链网络120中的区块链节点接收到交易记录后对交易记录中的内容进行验证，若验证成功，可以将其写入新的区块。关于验证交易记录的更多细节，可以参考图4及其相关描述。
图3是根据本说明书一些实施例所示的资产类型加密方法的示例性流程图。在区块链场景下，该加密方法可以由区块链成员的用户端实现。需要说明的是，该加密方法也可以在其他电子交易场景下实现，以：隐匿资产类型；并使得通过验证环签名可以确定加密的资产类型是否为来自准许资产列表的资产类型的加密结果。如图3所示，流程300可以包括：
步骤310，生成待加密资产类型的标识信息的第一密文。在一些实施例中，步骤310可以由第一密文生成模块610执行。
在一些实施例中，第一密文可以按Pedersen承诺协议。Pedersen承诺的密文满足E＝t 1G+t 2H，其中E表示密文，G、H均为椭圆曲线上一点，G可称为第一基点，H可称为第二基点，t 1和t 2均为整数。需要说明的是，本说明书涉及的椭圆曲线上的基点可以预先确定好后全局统一使用，例如，此处的第一基点G还可以用于生成公私钥对。
在一些实施例中，第一密文可以按E＝r*P k+sn_k*H计算，其中，E表示第一密文，r 表示随机数，P k表示第一公钥，sn_k表示所述待验证资产类型的标识信息(整数，如编号)，H表示椭圆曲线上的一点。应当理解，第一公钥P k满足P k＝P rG，其中P r表示与第一公钥匹配的第一私钥，P r可以取整数。值得注意的是，由于随机数的存在，对于同一资产类型，生成的第一密文因随机数的不同而不同，因此在该随机数不发生泄露的情况下能有效保证难以由第一密文推测出资产类型。另外，按E＝r*P k+sn_k*H计算第一密文时，区块链成员的用户端可以向区块链管理员的用户端提供随机数r、待注册的资产类型(对应sn_k)以及第一密文E，区块链管理员的用户端基于接收到的随机数r、所述账户的公钥P k、待注册的资产类型的标识信息sn_k和第二基点H，计算第一密文，将计算出的第一密文与接收到的第一密文比对，若两者一致，则说明区块链成员的用户端提供的随机数r、待注册的资产类型(对应sn_k)以及第一密文E是可靠的。
步骤320，利用公钥集合和目标私钥对环签名消息生成环签名，其中，环签名消息可以包括第一密文，在其他实施例中，环签名消息还可以包括其他信息，如账户的标识信息。公钥集合基于准许资产类型列表和第一密文得到，且当待加密资产类型属于准许资产类型列表时，公钥集合包括与目标私钥匹配的公钥。在一些实施例中，步骤320可以由环签名生成模块620执行。
环签名是一种可以实现签名者无条件匿名的签名方案，其具备以下特性：签名阶段需要用到公钥集合和签名者的私钥(即目标私钥)，若要生成正确的环签名(验签成功的必要条件)，需要保证公钥集合包括与目标私钥匹配的公钥；验签阶段验签者无法推测出环签名是利用公钥集合中哪一个公钥对应的私钥生成的。由此，基于准许资产类型列表和第一密文(即加密的资产类型)构建公钥集合，其中准许资产类型列表和第一密文都是可公开的，将公钥集合与准许资产类型列表和待加密资产类型建立联系。进而，使得公钥集合与目标私钥的关系受待加密资产类型相对准许资产类型列表的归属关系影响，具体地，当待加密资产类型属于准许资产类型列表时，公钥集合包括与目标私钥匹配的公钥，从而可生成正确的环签名。应当理解，鉴于公钥集合与目标私钥的关系受待加密资产类型相对准许资产类型列表的归属关系影响，当待加密资产类型属于准许资产类型列表时，公钥集合包括与目标私钥匹配的公钥(进而生成正确的环签名)，暗含了当待加密资产类型不属于准许资产类型列表时，公钥集合不包括与目标私钥匹配的公钥或公钥集合包括与目标私钥匹配的公钥的概率可忽略(进而无法生成正确的环签名或生成正确环签名的概率可忽略)。如此，在环签名验证成功的情况下，可以认为待加密资产类型(即后文所述待验证资产类型)属于准许资产类型列表。
在一些实施例中，公钥集合通过以下方式获得：将准许资产类型列表中的资产类型的标识信息分别进行第一运算，以获得准许资产类型密文列表；分别计算第一密文与准许资产类型密文列表中各密文的差值，公钥集合中包括各差值。其中，所述第一运算使得，当待加密资产类型的标识信息属于准许资产类型列表时，公钥集合包括与目标私钥匹配的公钥。仅作为示例，当第一密文按E＝r*P k+sn_k*H计算时，所述第一运算包括按sn_i*H计算，以获得准许资产类型密文列表中的各密文，其中，sn_i表示准许资产类型列表中的资产类型的标识信息，H即用于生成第一密文的第二基点。可以得出，当待验证资产类型属于准许资产类型列表，即存在sn_i＝sn_k时，公钥集合包括r*P k，此时目标私钥取r*P r，即使得公钥集合包括目标私钥。
不难理解，图3所示的流程还可以应用于其他需要隐匿某对象，并证明被隐匿的对象来自预设对象列表的任意场景。例如，所述预设对象列表除可以是前述的准许资产类型列表以外，还可以是人员名单、商品列表、车辆列表、地址列表等等，相应地需要隐匿的对象来自于所述预设对象列表。
图4是根据本说明书一些实施例所示的交易记录验证方法的示例性流程图。在一些实施例中，该交易记录验证方法可由接收交易记录的区块链节点执行，所述交易记录包括基于资产类型生成的第一密文，以及环签名。如图4所示，流程400可以包括：
步骤410，对交易记录中的环签名进行验证。在一些实施例中，步骤410可以由环签名验证模块910执行。
对交易记录中的环签名进行验证，其目的在于确定所述第一密文是否为来自准许资产类型列表的资产类型的加密结果。
关于环签名验证的更多细节，可以参考图5及其相关描述。
步骤420，若环签名验证失败，则不对交易记录中的第一密文进行登记备案。在一些实施例中，步骤420可以由第二处理模块920执行。
在一些实施例中，除了第一密文外，区块链节点还可以对交易记录中的其他内容进行验证。例如，可以利用所述账户的公钥对所述第一数字签名进行验证，若验签成功则可确定第一数字签名对应的签名消息(即第一待签名消息)是否来自所述区块链成员的用户端且传播过程中未经篡改。又如，可以利用区块链管理员的公钥对所述第二数字签名进行验证，若验签成功则表明区块链管理员已知晓待注册的资产类型并批准可将加密的资产类型(即所述第一密文)注册到所述账户上。需要注意的是，任一项验证失败的 情况下都可以不对交易记录进行登记备案。
在一些实施例中，若交易记录验证成功，区块链节点可以将交易记录中的第一密文登记(即注册)到区块链成员的账户中。
在一些实施例中，验证和/或注册的相关流程可以通过智能合约实现。例如，可以将用于实现验证和/或注册的相关流程的智能合约预先部署到区块链中，相应地，所述交易记录中可以包括该智能合约的地址，当区块链节点接收到所述交易记录后，可以根据所述交易记录中的地址调用智能合约，从而实现验证和/或注册的相关流程。
图5是根据本说明书一些实施例所示的资产类型验证方法的示例性流程图。在区块链场景下，该资产类型验证方法可以由区块链节点的用户端实现。需要说明的是，该资产类型验证方法也可以在其他电子交易场景下实现，以确定加密的资产类型(即第一密文)是否为来自准许资产类型列表的资产类型的加密结果。
步骤510，获取第一密文以及环签名，所述第一密文基于待验证资产类型的标识信息生成。在一些实施例中，步骤510可以由第一获取模块710执行。
步骤520，使用公钥集合验证所述环签名，所述公钥集合基于准许资产类型列表和所述第一密文得到。在一些实施例中，步骤520可以由环签名验证模块720执行。
在一些实施例中，由于准许资产类型列表和所述第一密文是公开的，可以在验证时基于准许资产类型列表和所述第一密文计算所述公钥集合。在一些实施例中，所述环签名可以包括所述公钥集合，在验证时从所述环签名中提取所述公钥集合。关于公钥集合的构造过程可以参见图3中的相关说明。在一些实施例中，可以基于所述公钥集合、环签名消息(如，第一密文)以及环签名进行验证，检验所述环签名是否为所述环签名消息对应于所述公钥集合的有效签名。
步骤530，若验证成功，则确定所述第一密文为来自准许资产类型列表的资产类型的加密结果。在一些实施例中，步骤530可以由确定模块730执行。
根据前述内容，在环签名验证成功的情况下，可以认为待验证资产类型属于准许资产类型列表，即所述第一密文为来自准许资产类型列表的资产类型的加密结果。同时，环签名验证成功不会暴露签名者的私钥(即目标私钥)对应公钥集合中的哪个公钥，也就不会暴露第一密文对应的资产类型为准许资产类型列表中的哪个资产类型。
不难理解，图5所示的流程还可以应用到验证其他的隐匿对象是否来自预设对象列表的任意场景。例如，所述预设对象列表除可以是前述的准许资产类型列表以外，还可 以是人员名单、商品列表、车辆列表、地址列表等等。
应当注意的是，上述有关流程的描述仅仅是为了示例和说明，而不限定本说明书的适用范围。对于本领域技术人员来说，在本说明书的指导下可以对流程进行各种修正和改变。然而，这些修正和改变仍在本说明书的范围之内。
图6是根据本说明书一些实施例所示的对象加密系统的示例性框图。如图6所示，对象加密系统600可以包括第一密文生成模块610和环签名生成模块620。
第一密文生成模块610可以用于生成待加密对象的标识信息的第一密文。
环签名生成模块620可以用于利用公钥集合和目标私钥对环签名消息生成环签名，其中，所述环签名消息包括所述第一密文，所述公钥集合基于预设对象列表和所述第一密文得到，且当所述待加密对象属于所述准许对象列表时，所述公钥集合包括与所述目标私钥匹配的公钥。
关于对象加密系统600及其模块的更多细节，可以参考图3及其相关描述。
图7是根据本说明书一些实施例所示的对象验证系统的示例性框图。如图7所示，对象验证系统700可以包括第一获取模块710、环签名验证模块720和确定模块730。
第一获取模块710可以用于获取第一密文以及环签名，所述第一密文可基于待验证对象的标识信息生成。
环签名验证模块720可以用于使用公钥集合验证所述环签名，所述公钥集合可基于预设对象列表和所述第一密文得到。
确定模块730可以用于若所述环签名验证模块验证成功，则确定所述第一密文为来自预设对象列表的对象的加密结果。
关于对象验证系统700及其模块的更多细节，可以参考图5及其相关描述。
图8是根据本说明书一些实施例所示的资产类型注册系统的示例性框图。如图8所示，资产类型注册系统800可以包括第二获取模块810、第一处理模块820、交易记录生成模块830和交易记录上传模块840。
第二获取模块810可以用于获取待注册的资产类型。
第一处理模块820可以用于获得第一密文以及环签名。关于第一处理模块820获得第一密文以及环签名的具体方式，可以参考图3及其相关描述。
交易记录生成模块830可以用于至少基于所述第一密文以及环签名生成交易记录。
交易记录上传模块840可以用于将所述交易记录上传至区块链网络。
关于资产类型注册系统800及其模块的更多细节，可以参考图2及其相关描述。
图9是根据本说明书一些实施例所示的交易记录验证系统的示例性框图。如图9所示，交易记录验证系统900可以包括环签名验证模块910和第二处理模块920。
环签名验证模块910可以用于对交易记录中的环签名进行验证。关于环签名验证模块910的验证环签名的具体方式，可以参考图5及其相关描述。
第二处理模块920可以用于若环签名验证失败，则不对交易记录中的第一密文进行登记备案。
关于交易记录验证系统900及其模块的更多细节，可以参考图4及其相关描述。
应当理解，图6至图9所示的系统及其模块可利用各种方式来实现。例如，在一些实施例中，系统及其模块可通过硬件、软件或者软件和硬件的结合来实现。其中，硬件部分可利用专用逻辑来实现；软件部分则可存储在存储器中，由适当的指令执行系统，例如微处理器或者专用设计硬件来执行。本领域技术人员可理解上述的方法和系统可使用计算机可执行指令和/或包含在处理器控制代码中来实现，例如在诸如磁盘、CD或DVD-ROM的载体介质、诸如只读存储器(固件)的可编程的存储器或者诸如光学或电子信号载体的数据载体上提供了这样的代码。本说明书的系统及其模块不仅可由诸如超大规模集成电路或门阵列、诸如逻辑芯片、晶体管等的半导体、或者诸如现场可编程门阵列、可编程逻辑设备等的可编程硬件设备的硬件电路实现，也可用例如由各种类型的处理器所执行的软件实现，还可由上述硬件电路和软件的结合(例如，固件)来实现。
需要注意的是，以上对于系统及其模块的描述，仅为描述方便，并不能把本说明书限制在所举实施例范围之内。可以理解，对于本领域的技术人员来说，在了解该系统的原理后，可在不背离这一原理的情况下，对各个模块进行任意组合，或者构成子系统与其他模块连接。例如，图8中披露的交易记录生成模块830和交易记录上传模块840可以是一个系统中的不同模块，也可以是一个模块实现上述的两个或两个以上模块的功能。又如，第一处理模块820可以包括对象加密系统600。又如，环签名验证模块910可以包括对象验证系统700。诸如此类的变形，均在本说明书的保护范围之内。
本说明书实施例可能带来的有益效果包括但不限于：(1)通过加密隐匿资产类型，且通过构造公钥集合并生成环签名，使得可通过验证环签名来确定证明加密的资产类型 为来自准许资产类型列表的资产类型的加密结果，环签名的验证也不会暴露加密的资产类型对应准许资产类型列表中的哪个资产类型；(2)由于随机数的存在，对于同一资产类型，生成的第一密文因随机数的不同而不同，因此在该随机数不发生泄露的情况下能有效保证难以由第一密文推测出资产类型。需要说明的是，不同实施例可能产生的有益效果不同，在不同的实施例里，可能产生的有益效果可以是以上任意一种或几种的组合，也可以是其他任何可能获得的有益效果。
上文已对基本概念做了描述，显然，对于本领域技术人员来说，上述详细披露仅仅作为示例，并不构成对本说明书实施例的限定。虽然此处并没有明确说明，本领域技术人员可能会对本说明书实施例进行各种修改、改进和修正。该类修改、改进和修正在本说明书实施例中被建议，仍属于本说明书示范实施例的精神和范围。
同时，本说明书使用了特定词语来描述本说明书的实施例。如“一个实施例”、“一实施例”、和/或“一些实施例”意指与本说明书至少一个实施例相关的某一特征、结构或特点。因此，应强调并注意的是，本说明书中在不同位置两次或多次提及的“一实施例”或“一个实施例”或“一个替代性实施例”并不一定是指同一实施例。此外，本说明书的一个或多个实施例中的某些特征、结构或特点可以进行适当的组合。
此外，本领域技术人员可以理解，本说明书实施例的各方面可以通过若干具有可专利性的种类或情况进行说明和描述，包括任何新的和有用的工序、机器、产品或物质的组合，或对他们的任何新的和有用的改进。相应地，本说明书实施例的各个方面可以完全由硬件执行、可以完全由软件(包括固件、常驻软件、微码等)执行、也可以由硬件和软件组合执行。以上硬件或软件均可被称为“数据块”、“模块”、“引擎”、“单元”、“组件”或“系统”。此外，本说明书实施例的各方面可能表现为位于一个或多个计算机可读介质中的计算机产品，该产品包括计算机可读程序编码。
计算机存储介质可能包含一个内含有计算机程序编码的传播数据信号，例如在基带上或作为载波的一部分。该传播信号可能有多种表现形式，包括电磁形式、光形式等，或合适的组合形式。计算机存储介质可以是除计算机可读存储介质之外的任何计算机可读介质，该介质可以通过连接至一个指令执行系统、装置或设备以实现通讯、传播或传输供使用的程序。位于计算机存储介质上的程序编码可以通过任何合适的介质进行传播，包括无线电、电缆、光纤电缆、RF、或类似介质，或任何上述介质的组合。
本说明书实施例各部分操作所需的计算机程序编码可以用任意一种或多种程序语言编写，包括面向对象编程语言如Java、Scala、Smalltalk、Eiffel、JADE、Emerald、C++、 C#、VB.NET、Python等，常规程序化编程语言如C语言、VisualBasic、Fortran2003、Perl、COBOL2002、PHP、ABAP，动态编程语言如Python、Ruby和Groovy，或其他编程语言等。该程序编码可以完全在用户计算机上运行、或作为独立的软件包在用户计算机上运行、或部分在用户计算机上运行部分在远程计算机运行、或完全在远程计算机或处理设备上运行。在后种情况下，远程计算机可以通过任何网络形式与用户计算机连接，比如局域网(LAN)或广域网(WAN)，或连接至外部计算机(例如通过因特网)，或在云计算环境中，或作为服务使用如软件即服务(SaaS)。
此外，除非权利要求中明确说明，本说明书实施例所述处理元素和序列的顺序、数字字母的使用、或其他名称的使用，并非用于限定本说明书实施例流程和方法的顺序。尽管上述披露中通过各种示例讨论了一些目前认为有用的发明实施例，但应当理解的是，该类细节仅起到说明的目的，附加的权利要求并不仅限于披露的实施例，相反，权利要求旨在覆盖所有符合本说明书实施例实质和范围的修正和等价组合。例如，虽然以上所描述的系统组件可以通过硬件设备实现，但是也可以只通过软件的解决方案得以实现，如在现有的处理设备或移动设备上安装所描述的系统。
同理，应当注意的是，为了简化本说明书实施例披露的表述，从而帮助对一个或多个发明实施例的理解，前文对本说明书实施例的描述中，有时会将多种特征归并至一个实施例、附图或对其的描述中。但是，这种披露方法并不意味着本说明书实施例对象所需要的特征比权利要求中提及的特征多。实际上，实施例的特征要少于上述披露的单个实施例的全部特征。
针对本说明书引用的每个专利、专利申请、专利申请公开物和其他材料，如文章、书籍、说明书、出版物、文档等，特此将其全部内容并入本说明书作为参考。与本说明书内容不一致或产生冲突的申请历史文件除外，对本说明书权利要求最广范围有限制的文件(当前或之后附加于本说明书中的)也除外。需要说明的是，如果本说明书附属材料中的描述、定义、和/或术语的使用与本说明书所述内容有不一致或冲突的地方，以本说明书的描述、定义和/或术语的使用为准。
最后，应当理解的是，本说明书中所述实施例仅用以说明本说明书实施例的原则。其他的变形也可能属于本说明书实施例的范围。因此，作为示例而非限制，本说明书实施例的替代配置可视为与本说明书的教导一致。相应地，本说明书的实施例不仅限于本说明书明确介绍和描述的实施例。

Claims (26)

  1. 一种对象加密方法，包括：
    生成待加密对象的标识信息的第一密文；
    利用公钥集合和目标私钥对环签名消息生成环签名，其中，所述环签名消息包括所述第一密文，所述公钥集合基于预设对象列表和所述第一密文得到，且当所述待加密对象属于所述预设对象列表时，所述公钥集合包括与所述目标私钥匹配的公钥。
  2. 如权利要求1所述的方法，其中，所述公钥集合通过以下方式获得：
    将所述预设对象列表中的对象的标识信息分别进行第一运算，以获得预设对象密文列表；
    计算第一密文与所述预设对象密文列表中各密文的差值，所述公钥集合中包括各差值；
    其中，所述第一运算使得，当所述待加密对象属于所述预设对象列表时，所述公钥集合包括所述目标私钥对应的公钥。
  3. 如权利要求2所述的方法，其中，所述第一密文按Pedersen承诺协议生成。
  4. 如权利要求3所述的方法，其中，所述生成待加密对象的标识信息的第一密文，包括：
    获取与第一私钥匹配的第一公钥，所述第一私钥与目标私钥相关；
    基于所述第一公钥以及所述待加密对象的标识信息，按Pedersen承诺协议生成所述第一密文。
  5. 如权利要求4所述的方法，其中，所述第一密文按E＝r*P k+sn_k*H计算，其中，E表示所述第一密文，r表示随机数，P k表示所述第一公钥，sn_k表示所述待加密对象的标识信息，H表示椭圆曲线上的一点；
    所述目标私钥为所述第一私钥与所述随机数r的乘积。
  6. 如权利要求5所述的方法，其中，所述第一运算包括按sn_i*H计算，以获得预设对象密文列表中的各密文，其中，sn_i表示所述预设对象列表中的对象的标识信息。
  7. 一种对象加密系统，包括：
    第一密文生成模块，用于生成待加密对象的标识信息的第一密文；
    环签名生成模块，用于利用公钥集合和目标私钥对环签名消息生成环签名，其中，所述环签名消息包括所述第一密文，所述公钥集合基于预设对象列表和所述第一密文得到，且当所述待加密对象属于所述预设对象列表时，所述公钥集合包括与所述目标私钥匹配的公钥。
  8. 一种对象加密装置，包括处理器和存储设备，
    所述存储设备用于存储指令，
    当所述处理器执行指令时，实现如权利要求1～6中任一项所述的对象加密方法。
  9. 一种对象验证方法，包括：
    获取第一密文以及环签名，所述第一密文基于待验证对象的标识信息生成；
    使用公钥集合验证所述环签名，所述公钥集合基于预设对象列表和所述第一密文得到；
    若验证成功，则确定所述第一密文为来自预设对象列表的对象的加密结果。
  10. 如权利要求9所述的方法，其中，所述公钥集合通过以下方式获得：
    将预设对象列表中的对象的标识信息分别进行第一运算，以获得预设对象密文列表；
    分别计算第一密文与所述预设对象密文列表中各密文的差值，所述公钥集合中包括各差值；
    其中，所述第一运算使得，当所述待验证对象属于所述预设对象列表时，所述公钥集合包括与所述环签名对应的目标私钥匹配的公钥。
  11. 如权利要求10所述的方法，其中，所述第一密文按Pedersen承诺协议生成。
  12. 如权利要求11所述的方法，其中，所述第一密文按E＝r*P k+sn_k*H计算，其中，E表示所述第一密文，r表示随机数，P k表示所述第一公钥，sn_k表示所述待验证对象的标识信息，H表示椭圆曲线上的一点。
  13. 如权利要求12所述的方法，其中，
    所述第一运算包括按sn_i*H计算，以获得预设对象密文列表中的各密文，
    sn_i表示所述预设对象列表中的对象的标识信息，H表示椭圆曲线上的一点且来自用于生成第一密文的参数。
  14. 一种对象验证系统，包括：
    第一获取模块，用于获取第一密文以及环签名，所述第一密文基于待验证对象的标识信息生成；
    环签名验证模块，用于使用公钥集合验证所述环签名，所述公钥集合基于预设对象列表和所述第一密文得到；
    确定模块，用于若所述环签名验证模块验证成功，则确定所述第一密文为来自预设对象列表的对象的加密结果。
  15. 一种对象验证装置，包括处理器和存储设备，
    所述存储设备用于存储指令，
    当所述处理器执行指令时，实现如权利要求9～13中任一项所述的对象验证方法。
  16. 一种资产类型注册方法，所述方法由区块链成员的用户端执行，所述区块链设置有准许资产类型列表，所述方法包括：
    获取待注册的资产类型；
    基于如权利要求1～6中任一项所述的方法将所述待注册的资产类型作为待加密对象，以及将所述准许资产类型列表作为预设对象列表进行处理，以获得第一密文以及环签名；
    至少基于所述第一密文以及环签名生成交易记录；
    将所述交易记录上传至区块链网络。
  17. 如权利要求16所述的方法，其中，所述至少基于所述第一密文以及环签名生成交易记录，包括：
    利用所述账户的私钥对第一待签名消息生成第一数字签名，所述第一待签名消息包括所述账户的标识信息、所述第一密文和所述环签名；
    所述交易记录包括所述账户的标识信息、所述第一密文、所述环签名和所述第一数字签名。
  18. 如权利要求17所述的方法，还包括：
    将所述资产类型和所述第一密文发送给区块链管理员的用户端；
    接收区块链管理员的用户端返回的第二数字签名，所述第二数字签名为所述区块链管理员的用户端在通过对所述第一密文的验证后，利用所述账户的私钥对第二待签名消息生成的，所述第二待签名消息包括所述账户的标识信息和所述第一密文；
    并且，所述交易记录还包括所述第二数字签名。
  19. 如权利要求18所述的方法，其中，所述第一待签名消息还包括所述第二数字签名。
  20. 一种资产类型注册系统，包括：
    第二获取模块，用于获取待注册的资产类型；
    第一处理模块，用于基于如权利要求1～6中任一项所述的方法将所述待注册的资产类型作为待加密对象，以及将所述准许资产类型列表作为预设对象列表进行处理，以获得第一密文以及环签名；
    交易记录生成模块，用于至少基于所述第一密文以及环签名生成交易记录；
    交易记录上传模块，用于将所述交易记录上传至区块链网络。
  21. 一种资产类型注册装置，包括处理器和存储设备，
    所述存储设备用于存储指令，
    当所述处理器执行指令时，实现如权利要求16～19中任一项所述的资产类型注册方法。
  22. 一种交易记录验证方法，由接收交易记录的区块链节点执行，所述区块链设置有准许资产类型列表，所述交易记录包括基于资产类型生成的第一密文，以及环签名；所述方法包括：
    基于如权利要求9～13中任一项所述的方法将所述准许资产类型列表作为预设对象类型列表，对所述环签名进行验证；
    若验证失败，则不对所述第一密文进行登记备案。
  23. 如权利要求22所述的方法，其中，所述对交易记录进行登记备案，包括：
    将所述交易记录中的第一密文登记到区块链成员的账户中。
  24. 如权利要求23所述的交易记录验证方法，其中，所述交易记录通过如权利要求16～19中任一项所述的资产类型注册方法得到。
  25. 一种交易记录验证系统，包括：
    环签名验证模块，用于基于如权利要求9～13中任一项所述的对象验证方法将所述准许资产类型列表作为预设对象类型列表，对所述环签名进行验证；
    第二处理模块，用于若所述环签名验证失败，则不对所述第一密文进行登记备案。
  26. 一种交易记录验证装置，包括处理器和存储设备，
    所述存储设备用于存储指令，
    当所述处理器执行指令时，实现如权利要求22～24中任一项所述的交易记录验证方法。
PCT/CN2021/086277 2020-04-10 2021-04-09 资产类型注册、交易记录验证 WO2021204273A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010276662.7 2020-04-10
CN202010276662.7A CN111178894B (zh) 2020-04-10 2020-04-10 资产类型注册、交易记录验证方法及系统

Publications (1)

Publication Number Publication Date
WO2021204273A1 true WO2021204273A1 (zh) 2021-10-14

Family

ID=70647280

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/086277 WO2021204273A1 (zh) 2020-04-10 2021-04-09 资产类型注册、交易记录验证

Country Status (2)

Country Link
CN (1) CN111178894B (zh)
WO (1) WO2021204273A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113743833A (zh) * 2021-11-05 2021-12-03 中国信息通信研究院 基于标识解析的生产控制方法和系统
CN114726645A (zh) * 2022-05-06 2022-07-08 电子科技大学 一种基于用户信息安全的可链接环签名方法
CN116260659A (zh) * 2023-05-15 2023-06-13 典基网络科技(上海)有限公司 一种ipsec数据包丢包处理方法
CN117237124A (zh) * 2023-11-15 2023-12-15 国网浙江省电力有限公司 基于多端交互的数字资产管理方法及装置

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111178894B (zh) * 2020-04-10 2020-09-11 支付宝(杭州)信息技术有限公司 资产类型注册、交易记录验证方法及系统
CN116760528B (zh) * 2023-08-21 2023-10-27 成都乐超人科技有限公司 一种基于多密钥同态共享下的多方资产交付方法和装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103581175A (zh) * 2013-10-17 2014-02-12 江苏科技大学 一种安全的数据聚合方法
CN110189184A (zh) * 2019-04-26 2019-08-30 深圳市智税链科技有限公司 一种电子发票存储方法和装置
CN110473105A (zh) * 2019-08-20 2019-11-19 深圳市网心科技有限公司 一种区块链交易结算方法、系统及相关设备
US20190356481A1 (en) * 2018-05-18 2019-11-21 Qredo Ltd. System and method for securing digital assets
US20200052903A1 (en) * 2018-08-07 2020-02-13 The Toronto-Dominion Bank Dynamically managing exchanges of data using a distributed ledger and homomorphic commitments
CN111178894A (zh) * 2020-04-10 2020-05-19 支付宝(杭州)信息技术有限公司 资产类型注册、交易记录验证方法及系统

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2566098A1 (en) * 2011-08-29 2013-03-06 Thomson Licensing Signcryption method and device and corresponding signcryption verification method and device
CN106038143A (zh) * 2016-07-08 2016-10-26 王宗梅 一种心内科多功能护理架
CN108335106A (zh) * 2018-01-24 2018-07-27 深圳壹账通智能科技有限公司 基于区块链的零知识多账本兑换转账方法、装置及存储介质
CN110012126B (zh) * 2019-04-02 2022-01-21 哈尔滨工业大学（深圳） 一种基于区块链技术的dns系统
CN110572267B (zh) * 2019-09-09 2022-01-28 北京工业大学 一种基于联盟区块链的匿名电子投票方法

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103581175A (zh) * 2013-10-17 2014-02-12 江苏科技大学 一种安全的数据聚合方法
US20190356481A1 (en) * 2018-05-18 2019-11-21 Qredo Ltd. System and method for securing digital assets
US20200052903A1 (en) * 2018-08-07 2020-02-13 The Toronto-Dominion Bank Dynamically managing exchanges of data using a distributed ledger and homomorphic commitments
CN110189184A (zh) * 2019-04-26 2019-08-30 深圳市智税链科技有限公司 一种电子发票存储方法和装置
CN110473105A (zh) * 2019-08-20 2019-11-19 深圳市网心科技有限公司 一种区块链交易结算方法、系统及相关设备
CN111178894A (zh) * 2020-04-10 2020-05-19 支付宝(杭州)信息技术有限公司 资产类型注册、交易记录验证方法及系统

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113743833A (zh) * 2021-11-05 2021-12-03 中国信息通信研究院 基于标识解析的生产控制方法和系统
CN114726645A (zh) * 2022-05-06 2022-07-08 电子科技大学 一种基于用户信息安全的可链接环签名方法
CN114726645B (zh) * 2022-05-06 2023-01-24 电子科技大学 一种基于用户信息安全的可链接环签名方法
CN116260659A (zh) * 2023-05-15 2023-06-13 典基网络科技(上海)有限公司 一种ipsec数据包丢包处理方法
CN116260659B (zh) * 2023-05-15 2023-07-11 典基网络科技(上海)有限公司 一种ipsec数据包丢包处理方法
CN117237124A (zh) * 2023-11-15 2023-12-15 国网浙江省电力有限公司 基于多端交互的数字资产管理方法及装置
CN117237124B (zh) * 2023-11-15 2024-02-02 国网浙江省电力有限公司 基于多端交互的数字资产管理方法及装置

Also Published As

Publication number Publication date
CN111178894A (zh) 2020-05-19
CN111178894B (zh) 2020-09-11

Similar Documents

Publication Publication Date Title
WO2021204273A1 (zh) 资产类型注册、交易记录验证
US20240144280A1 (en) Blockchain architecture with record security
US11461773B2 (en) Blockchain-based node management methods and apparatuses
US20210150521A1 (en) Blockchain-based privacy transaction and blockchain-based privacy transaction application methods and apparatuses
US11870769B2 (en) System and method for identifying a browser instance in a browser session with a server
US10614456B2 (en) Dynamic cryptocurrency aliasing
US10230710B2 (en) Token based network service among IoT applications
WO2021228239A1 (zh) 资产类型一致性证据生成、交易、交易验证方法及系统
US11526955B2 (en) Protocol-based system and method for establishing a multi-party contract
US11258771B2 (en) Systems and methods for sending user data from a trusted party to a third party using a distributed registry
WO2020258858A1 (zh) 块链式账本中的授权方法、系统、装置及设备
KR20220093198A (ko) 전용 및 개방형 블록체인을 이용한 거래의 수행
CN110674531B (zh) 基于区块链的居住信息管理方法、装置、服务器及介质
US20210314139A1 (en) Noisy transaction for protection of data
US11856107B2 (en) Methods and systems for exchanging confidential information via a blockchain
WO2018105038A1 (ja) 通信装置及び分散型元帳システム
CN112446050B (zh) 应用于区块链系统的业务数据处理方法及装置
US20220278845A1 (en) Honest behavior enforcement via blockchain
WO2023185862A1 (zh) 基于区块链系统的多方计算方法和系统
CN110276693B (zh) 保险理赔方法及系统
US20230245112A1 (en) Non-interactive token certification and verification
CN115412256A (zh) 基于区块链的身份认证方法及装置、存储介质、终端设备
CN116091063A (zh) 交易处理方法、电子设备及可读存储介质
KR20210086437A (ko) 블록체인 네트워크 기반의 가상 공통 아이디 서비스 방법 및 이를 이용한 서비스 제공 서버
CN116028981A (zh) 基于区块链的数据处理方法和相关设备

Legal Events

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

Ref document number: 21785698

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

Country of ref document: EP

Kind code of ref document: A1