CN115936707A

CN115936707A - Transaction authentication method and device based on block chain and computer equipment

Info

Publication number: CN115936707A
Application number: CN202211231797.7A
Authority: CN
Inventors: 幸兰欣
Original assignee: Bank of China Ltd
Current assignee: Bank of China Ltd
Priority date: 2022-09-30
Filing date: 2022-09-30
Publication date: 2023-04-07

Abstract

The utility model provides a transaction authentication method, a device and a computer device based on a block chain, which relate to the technical field of the block chain and comprise the steps of receiving an authentication request of a target transaction carrying identity authentication information of an authorized person; initiating a digital wallet query request to query whether an authorized person's digital wallet is established on the blockchain; when a digital wallet is established, initiating a non-homogenization evidence-based inquiry request to inquire whether the digital wallet stores non-homogenization evidence of target transaction; when the non-homogenization general evidence is stored, receiving the non-homogenization general evidence fed back by the block chain; and decrypting the non-homogenization permit by using the private key of the righter and authenticating the target transaction according to a decryption result. The authentication of the transaction is realized through the non-homogenization evidence, so that when a user holds a private key which can decrypt the non-homogenization evidence of the target transaction to obtain a decryption result, the user is judged to be the ownership owner of the target transaction, and the right dispute is favorably avoided.

Description

Transaction authentication method and device based on block chain and computer equipment

Technical Field

The present disclosure relates to the field of blockchain technologies, and in particular, to a method and an apparatus for authenticating a transaction based on a blockchain, and a computer device.

Background

With the migration of more and more banking businesses on line, the original form of signing and confirming the client's intention by the paper application form no longer meets the development requirement, so a method for making the client to sign by hand on an electronic screen and store the signature in an imaging manner at the end of the business is born and used as a corroboration for confirming the client's true intention. The electronic signature method has certain disadvantages: the electronic signature is a retention of an image, and has reproducibility and falsification, so that the electronic signature often cannot have good proof effect when a service dispute really occurs.

In view of the above, the present disclosure is directed to a method, an apparatus, and a computer device for transaction authentication based on a blockchain.

Disclosure of Invention

In view of the above problems in the prior art, an object of the present disclosure is to provide a transaction authentication method, apparatus and computer device based on a block chain, so as to solve the defect in the prior art that when a transaction dispute occurs, the prior electronic signature has insufficient corroborative effectiveness on the transaction.

In order to solve the technical problems, the specific technical scheme is as follows:

in one aspect, provided herein is a method for authentication of transactions based on blockchains, comprising:

receiving an authentication request for target transaction initiated by a first user, wherein the authentication request carries identity authentication information of an authorized person;

initiating a digital wallet inquiry request to a blockchain to inquire whether a digital wallet corresponding to the identity authentication information of the authorized person is established on the blockchain;

when the block chain feeds back the inquiry result of the digital wallet, initiating a non-homogenization certification inquiry request to the block chain so as to inquire whether the non-homogenization certification of the target transaction is stored in the block chain;

when the block chain feedback stores the query result of the non-homogenization evidence, receiving the non-homogenization evidence fed back by the block chain;

and decrypting the non-homogenization permit by using the private key of the obligee, and authenticating the target transaction according to a decryption result.

Specifically, before receiving an authentication request initiated by a first user for a target transaction, the method further comprises:

acquiring a transaction request for the target transaction initiated by a second user, wherein the transaction request carries identity authentication information of the second user;

receiving a transaction credential characterizing a willingness of the second user to confirm the target transaction when the target transaction is completed;

uploading the transaction credentials to a blockchain and invoking a pre-deployed smart contract on the blockchain to cast the transaction credentials as a non-homogenization pass by the smart contract and encrypt and store the non-homogenization pass in a digital wallet corresponding to the second user's identity authentication information.

Further, before encrypting and storing the non-homogenization pass ticket in a digital wallet corresponding to the second user's authentication information, the method further comprises:

initiating a digital wallet inquiry request to a blockchain to inquire whether a digital wallet corresponding to the identity authentication information of the second user is established on the blockchain;

when the block chain feeds back the inquiry result of the digital wallet which is not established and corresponds to the identity authentication information of the second user, the identity authentication information of the second user is uploaded to the block chain, a digital wallet creating function on the block chain is called to create the digital wallet which corresponds to the identity authentication information of the second user, and a private key in the digital wallet of the second user fed back by the block chain is received to feed back the private key to the second user.

Specifically, casting the transaction credential as a non-homogenous credential by the smart contract, further comprising:

calling a non-homogenization evidence casting function by the intelligent contract, and defining the attribute of the transaction evidence when the transaction evidence is cast to be non-homogenization evidence, wherein the attribute at least comprises a valid period.

Preferably, before decrypting the non-homogenization voucher by using the secret key of the rightful person and authenticating the target transaction according to the decryption result, the method further comprises:

receiving the validity period of the non-homogenization evidence obtained by the intelligent contract through calling a non-homogenization evidence validity period verification function for query, wherein the validity period of the non-homogenization evidence is fed back by the block chain;

verifying whether the non-homogenous general evidence is in a valid period;

if the non-homogenization certification is in the valid period, authenticating the target transaction according to the decryption result of the private key on the non-homogenization certification;

and if the non-homogenization evidence is not in the valid period, feeding back the target transaction authentication failure prompt.

Specifically, authenticating the target transaction according to the decryption result, further comprising:

judging whether the non-homogenization voucher is decrypted according to the private key to obtain the transaction voucher;

if yes, the target transaction is authenticated successfully;

and if not, feeding back the target transaction authentication failure prompt.

Further, the method further comprises:

and when the block chain feeds back the inquiry result without establishing the digital wallet, feeding back the target transaction authentication failure prompt.

Still further, the method further comprises:

and when the block chain feeds back the query result which does not store the non-homogenization evidence, feeding back the target transaction authentication failure prompt.

In a second aspect, an embodiment of the present specification further provides a transaction authentication device based on a blockchain, including:

the first receiving module is used for receiving an authentication request for target transaction initiated by a first user, wherein the authentication request carries identity authentication information of an authorized person;

the system comprises a first query module, a second query module and a third query module, wherein the first query module is used for initiating a digital wallet query request to a blockchain so as to query whether a digital wallet corresponding to the identity authentication information of the authorized person is established on the blockchain;

a second query module, configured to initiate a non-homogeneous voucher query request to the blockchain to query whether the digital wallet stores a non-homogeneous voucher of the target transaction when the blockchain feeds back a query result of the digital wallet;

a second receiving module, configured to receive the non-homogenization evidence returned by the block chain when the block chain returns a query result storing the non-homogenization evidence;

and the authentication module is used for decrypting the non-homogenization voucher by using the private key of the righter and authenticating the target transaction according to a decryption result.

In a third aspect, the present specification further provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor executes the computer program to implement the method for authentication of transaction based on blockchain according to the above technical solution.

In a fourth aspect, the present specification further provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the computer program implements a transaction authentication method based on blockchain according to the above technical solution.

In a fifth aspect, the present specification further provides a computer program product including at least one instruction or at least one program, the at least one instruction or the at least one program being loaded and executed by a processor to implement a method for authentication of transaction based on blockchain as described in the above technical solution.

By adopting the technical scheme, the transaction authentication method, the transaction authentication device and the computer equipment based on the block chain realize the authentication of the transaction through the uniqueness and the authenticity of the non-homogeneous certificate, so that the owner of the target transaction is ensured to be the owner of the target transaction only when the non-homogeneous certificate of the target transaction is stored in the digital wallet of the owner corresponding to the identity authentication information and the user holds the private key capable of decrypting the non-homogeneous certificate to obtain a decryption result, the owner of the target transaction is prevented from being maliciously falsely claimed by other people, the loss of the user who actually owns the ownership of the target transaction is avoided, and the transaction dispute is favorably avoided.

In order to make the aforementioned and other objects, features and advantages of the present invention comprehensible, preferred embodiments accompanied with figures are described in detail below.

Drawings

In order to more clearly illustrate the embodiments or technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 is a schematic diagram illustrating steps of a transaction authentication method based on a blockchain according to an embodiment of the present disclosure;

fig. 2 is a schematic diagram illustrating another step of a transaction authentication method based on a blockchain provided in an embodiment of the present disclosure;

fig. 3 is a schematic diagram illustrating another step of a transaction authentication method based on a blockchain according to an embodiment of the present disclosure;

fig. 4 is a schematic diagram illustrating another step of a transaction authentication method based on a blockchain according to an embodiment of the present disclosure;

FIG. 5 is a diagram illustrating the steps in an embodiment herein for authenticating a target transaction based on the decryption result;

fig. 6 is a schematic structural diagram illustrating a transaction authentication device based on a blockchain according to an embodiment of the present disclosure;

fig. 7 shows a schematic structural diagram of a computer device provided in an embodiment herein.

Description of the symbols of the drawings:

61. a first receiving module;

62. a first query module;

63. a second query module;

64. a second receiving module;

65. an authentication module;

702. a computer device;

704. a processor;

706. a memory;

708. a drive mechanism;

710. an input/output module;

712. an input device;

714. an output device;

716. a presentation device;

718. a graphical user interface;

720. a network interface;

722. a communication link;

724. a communication bus.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the scope of protection given herein.

It should be noted that the terms "first," "second," and the like in the description and claims herein and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments herein described are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, apparatus, article, or device that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or device.

Due to the problems of reproducibility and easy tampering of the existing paper voucher for representing the confirmation intention of the user in transaction, the paper voucher cannot have good proof effectiveness when solving the dispute problem of the transaction. In order to solve the above problem, embodiments herein provide a method, an apparatus, and a computer device for transaction authentication based on a blockchain. It should be noted that the method, the device, and the computer device for transaction authentication based on the blockchain provided in the embodiments of the present specification may be used in the financial field, and may also be used in any field other than the financial field.

Fig. 1 is a schematic diagram of steps of a block chain-based transaction authentication method provided in an embodiment herein, and the present specification provides operation steps of the method as described in the embodiment or the flowchart, but more or less operation steps may be included based on conventional or non-creative labor. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of sequences, and does not represent a unique order of performance. When an actual system or apparatus product executes, it can execute sequentially or in parallel according to the method shown in the embodiment or the figures. Specifically, as shown in fig. 1, the method is applicable to a bank server, and the method may include:

s110: receiving an authentication request for target transaction initiated by a first user, wherein the authentication request carries identity authentication information of an obligee.

For example, the target transaction may be a deposit transaction, and the authentication request of the first user for the target transaction may be a confirmation of ownership of the funds involved in the deposit transaction, an authentication request.

It should be noted that, in the embodiment of the present specification, the identity authentication information is in a one-to-one correspondence with the user, and the identity authentication information is information authorized and agreed by the user in the past. And the technical scheme described in the embodiment of the present specification conforms to the relevant regulations of national laws and regulations in terms of data acquisition, storage, use, processing, and the like.

The righter may be the first user himself, i.e. the first user initiates an authentication request which is itself the righter (or ownership owner) of the target transaction. The obliquest may also be another user, that is, the right is a principal of the first user, for example, if the first user is a child and the obliquest is a parent, the child carries identity authentication information of the parent to initiate an authentication request for the target transaction instead of the parent.

S120: and initiating a digital wallet inquiry request to the blockchain to inquire whether a digital wallet corresponding to the identity authentication information of the authorized person is established on the blockchain.

Namely, the bank server initiates a digital wallet inquiry request to the server where the blockchain is located, and receives an inquiry result fed back by the server where the blockchain is located.

S130: when the block chain is fed back and established with the inquiry structure of the digital wallet, initiating a non-homogenization evidence inquiry request to the block chain so as to inquire whether the digital wallet stores the non-homogenization evidence of the target transaction.

In the embodiment of the present specification, the Non-homogeneous token (NFT) is a digital asset ownership with irreplaceable and inseparable characteristics based on block chains. A non-homogenous pass corresponds to a transaction.

S140: and when the block chain feedback stores the query result of the non-homogenization evidence, receiving the non-homogenization evidence fed back by the block chain.

That is, when the server where the block chain is located inquires that the digital wallet corresponding to the identity authentication information of the authorized person has the non-homogeneous certificate corresponding to the target transaction, the non-homogeneous certificate can be directly fed back to the bank server, and the bank server does not need to initiate a request for obtaining the non-homogeneous certificate.

S150: and decrypting the non-homogenization permit by using the private key of the obligee, and authenticating the target transaction according to a decryption result.

The private key of the obligee is provided to the bank server by the first user, and particularly can be actively provided when the first user initiates an authentication request; or the first user may provide the first user with the bank server after the bank server initiates a request for obtaining the private key to the first user after performing the above steps S110 to S140.

In the transaction authentication method based on the block chain provided in the embodiment of the present specification, if and only if the rightful person establishes the digital wallet corresponding to the identity authentication information of the rightful person on the block chain, and the digital wallet corresponding to the identity authentication information of the rightful person holds the non-homogenization permit of the target transaction, and the private key held by the rightful person can decrypt the non-homogenization permit to obtain a decryption result, the rightful person can be ensured to be the ownership owner of the target transaction, which is beneficial to avoiding the ownership of the target transaction from being maliciously impersonated by other people, and avoiding dispute of the transaction.

Further, as shown in fig. 2, in the embodiment of the present specification, in step S110: before receiving an authentication request initiated by a first user for a target transaction, the method further comprises:

s210: and acquiring a transaction request for the target transaction initiated by a second user, wherein the transaction request carries identity authentication information of the second user.

It should be noted that, in this embodiment of the present specification, the first user is a user who initiates an authentication request for the target transaction, and the second user is a user who initiates the target transaction (for example, the deposit transaction described above). The first user and the second user can be the same user, namely the same user initiates an authentication request of the authorized person who is the target transaction after finishing the target transaction; the first user may also be a different user, for example, the second user is a parent completing the target transaction, the first user is a child, and the first user initiates an authentication request whose parent is the rightful person for the target transaction.

S220: receiving a transaction credential characterizing a willingness of the second user to confirm the target transaction when the target transaction is completed.

The transaction certificate can be an electronic signature image of the second user after the target transaction is completed; the second user may also be a video recording of the target transaction, where the video recording may include voice information, limb information (including a head-nodding confirmation action), and the like, of the second user, where the second user has a confirmation intention for the target transaction.

S230: uploading the transaction credentials to a blockchain and invoking a pre-deployed smart contract on the blockchain to cast the transaction credentials as a non-homogenization pass by the smart contract and encrypt and store the non-homogenization pass in a digital wallet corresponding to the second user's identity authentication information.

In the embodiment of the specification, the intelligent contract is a section of code written on a block chain, and once a certain event triggers a term in the intelligent contract, the code automatically executes casting non-homogeneity evidence.

Before invoking the intelligent contract, the method also comprises the steps of deploying and initializing the intelligent contract: the intelligent contract for casting the non-homogenization evidence is deployed on the block chain, so that the intelligent contract can inherit contract interfaces of protocols such as ERC (Ethernet Request for Comments) -721 protocol, ERC-875 protocol and ERC-1155 protocol according to different protocol standards, and therefore functions of non-homogenization evidence casting, verification, transfer, destruction and the like are achieved.

In this embodiment of the present specification, the encryption processing on the non-homogeneous certificate may adopt an asymmetric encryption manner, the smart contract may invoke a public key in a digital wallet corresponding to the identity authentication information of the second user to encrypt the non-homogeneous certificate, and during decryption, the public key in the digital wallet is used to perform encryption. In other possible embodiments, the encryption of the non-homogenous certificate may also adopt a symmetric encryption manner, that is, the non-homogenous certificate is encrypted and decrypted by using a private key.

When the bank server performs the target transaction with the second user, the bank server may further perform a step of screening the qualification of the second user, for example:

comparing the identity authentication information of the second user with a preset information data table of the credit loser and a preset data table of a bad credit loan officer;

refusing to process the target transaction for the second user when the identity authentication information of the second user is listed in the deceased person information data table and/or the bad loan person data table;

and when the identity authentication information of the second user is not listed in the deceased person information data table and the bad loan person data table, agreeing to process the target transaction for the second user and receiving the transaction certificate.

The said information data sheet of the lost credit can be linked with the related department of justice, the said bad credit person data sheet can be linked with the credit record of the bank, help the bank to know the qualification of the user, reduce the bad business and happen the rate.

And further, after acquiring the transaction request for the target transaction initiated by the second user in step S210, the method may further include:

linking the target transaction;

and entering relevant information of the target transaction in a blockchain, wherein the relevant information comprises but is not limited to the initiation time of the transaction request of the target transaction, the identity authentication information of the user of the target transaction initiator (namely the identity authentication information of the second user), the type of the target transaction, the transaction serial number of the target transaction and the like.

And receiving the uplink result of the target transaction fed back by the server of the block chain.

Further, as shown in fig. 3, before encrypting and storing the non-homogenization certificate in the digital wallet corresponding to the identity authentication information of the second user in step S230, the method further includes:

s310: and initiating a digital wallet inquiry request to the blockchain to inquire whether a digital wallet corresponding to the identity authentication information of the second user is established on the blockchain.

S320: when the query result of the digital wallet corresponding to the identity authentication information of the second user is not established in the blockchain feedback, uploading the identity authentication information of the second user to the blockchain, calling a digital wallet creating function on the blockchain to create a digital wallet corresponding to the identity authentication information of the second user, and receiving a private key in the digital wallet of the second user fed back by the blockchain to feed back the private key to the second user.

When a user transacts for the first time, a related function on a block chain is called to establish a digital wallet corresponding to identity authentication information of the user for realizing registration, wherein the digital wallet comprises a private key, a public key and a wallet address; and feeds back the private key to the user. And storing the non-homogenization pass-certificate to the digital wallet corresponding to the second user identity authentication information, namely storing the non-homogenization pass-certificate to the storage space of the wallet address.

And

if a digital wallet corresponding to the identity authentication information of the second user is established on the blockchain, the smart contract on the blockchain can directly call the digital wallet so as to store the non-homogenization certificate in the digital wallet.

In some possible embodiments, the casting of the transaction credential as a homogenous document by the smart contract in step S230 may further include:

and the intelligent contract takes the transaction certificate as metadata of the non-homogenization evidence and calls a casting function of the non-homogenization evidence to define the attribute of the transaction certificate in casting into the non-homogenization evidence, wherein the attribute at least comprises a validity period.

The non-homogenous evidence casting function may include a validity period function for defining validity period attributes of the non-homogenous evidence. The casting functions may include, among other things, a name function for defining a non-homogenous certification name attribute, a quantity function for defining a non-homogenous certification quantity attribute, a monetary function for defining a non-homogenous certification monetary attribute, and so on.

Further, as shown in fig. 4, in step S150: before decrypting the non-homogenization voucher by using the private key of the obligee and authenticating the target transaction according to a decryption result, the method further comprises the following steps:

s410: and receiving the validity period of the non-homogenization certification, which is fed back by the block chain and is obtained by the intelligent contract through calling a non-homogenization certification validity period verification function for query.

Since the attribute defined by the non-homogenization certification at the time of casting includes the validity period, in the embodiment of the present specification, the intelligent contract further includes a step of calling a non-homogenization certification validity period verification function to query the validity period of the non-homogenization certification, and feeding back the query result to the bank server.

S420: verifying whether the non-homogenization general evidence is in a valid period.

Namely, the validity time of the non-homogenization evidence is compared with the current time node.

S430: and if the non-homogenization evidence is in the valid period, the target transaction is authenticated by using the decryption result of the non-homogenization evidence of the private key.

S440: and if the non-homogeneous certificate is not in the valid period, feeding back the target transaction authentication failure prompt to the first user.

The transaction authentication method based on the block chain provided by the embodiment of the specification can improve the accuracy of target transaction authentication by checking whether the non-homogeneous certificate is valid or not; and when the non-homogenization general certificate is not in the validity period, the right holder corresponding to the identity authentication information carried in the authentication request can be directly judged to not have the ownership of the target transaction, and the prompt of authentication failure is directly fed back at the moment, so that the follow-up step of authenticating the target transaction according to the decryption result is not required, and the response rate of the authentication result is favorably improved.

Further, as shown in fig. 5, the authenticating the target transaction according to the decryption result in step S150 may further include:

s510: and judging whether to decrypt the non-homogenization voucher according to the private key to obtain the transaction voucher.

Namely, whether the electronic signature image of the user after the target transaction is finished or the video recording of the user during the target transaction can be obtained by decrypting the non-homogenization pass according to the private key is judged.

S520: if yes, the target transaction is authenticated successfully.

That is, when the electronic signature image or the video recording is obtained through decryption, the user can be determined to be successfully authenticated for the target transaction according to the electronic signature image or the video recording (including voice information and limb information which can represent the willingness of the second user to confirm the target transaction).

At this time, if the obligee corresponding to the identity authentication information carried in the authentication request is indeed the ownership owner of the target transaction, the result of successful authentication can be fed back to the first user. For example, the target transaction may be a deposit transaction, and when the authentication is successful, the first user may initiate a further transaction request, such as a withdrawal transaction, based on the target transaction.

S530: and if not, feeding back the target transaction authentication failure prompt.

That is, when the rightful person corresponding to the identity authentication information carried in the authentication request does not hold the private key capable of decrypting the non-homogenous certificate, it can be determined that the rightful person does not have ownership over the target transaction, which is beneficial to preventing the ownership over the target transaction from being maliciously falsely claimed by others, avoiding the loss of users who actually have ownership over the target transaction, and being beneficial to avoiding disputes of transactions.

Further, the method further comprises:

That is, when the licensee corresponding to the identity authentication information carried in the authentication request is not registered and does not create a digital wallet on the blockchain, the licensee cannot be the licensee of the target transaction. At the moment, the subsequent step of authenticating the target transaction according to the decryption result is also not required to be executed, so that the response rate of feeding the authentication result back to the first user is improved.

Further, the transaction authentication method based on the blockchain provided by the embodiment of the present specification may further include:

and when the block chain feedback does not store the inquiry result of the non-homogenization evidence, feeding back the target transaction authentication failure prompt.

For example, when the target transaction is unsuccessful, the target transaction cannot generate a corresponding transaction certificate, and thus a non-homogeneous certificate of the target transaction cannot be cast and stored in a digital wallet of a user; for another example, if the rightee corresponding to the identity authentication information carried in the authentication request is not the initiator of the transaction request of the target transaction, the digital wallet of the rightee does not store the non-homogeneous certificate, and at this time, it can be determined that the rightee does not have ownership of the target transaction, thereby avoiding right dispute of the target transaction.

As shown in fig. 6, an embodiment of the present specification further provides a transaction authentication device based on a blockchain, including:

a first receiving module 61, configured to receive an authentication request for a target transaction initiated by a first user, where the authentication request carries identity authentication information of an authorized person;

a first query module 62, configured to initiate a digital wallet query request to a blockchain to query whether a digital wallet corresponding to the identity authentication information of the rightful person is established on the blockchain;

a second query module 63, configured to, when the block chain feeds back a query result of the digital wallet, initiate a non-homogeneous voucher query request to the block chain to query whether the digital wallet stores a non-homogeneous voucher of the target transaction;

a second receiving module 64, configured to receive the non-homogenization certification-evidence fed back by the blockchain when the query result of the non-homogenization certification-evidence is stored in the blockchain feedback;

and the authentication module 65 is configured to decrypt the non-homogenization voucher by using the private key of the authorized person, and authenticate the target transaction according to a decryption result.

The advantages achieved by the device provided by the embodiment of the specification are consistent with those achieved by the method, and are not described in detail herein.

As shown in fig. 7, for a computer device provided in the embodiments herein, a blockchain-based transaction authentication apparatus in the present specification may be a computer device in the embodiments herein, and perform the above method herein. The computer device 702 may include one or more processors 704, such as one or more Central Processing Units (CPUs), each of which may implement one or more hardware threads. The computer device 702 may also include any memory 706 for storing any kind of information, such as code, settings, data, etc. For example, and without limitation, the memory 706 can include any one or more of the following in combination: any type of RAM, any type of ROM, flash memory devices, hard disks, optical disks, etc. More generally, any memory may use any technology to store information. Further, any memory may provide volatile or non-volatile retention of information. Further, any memory may represent fixed or removable components of computer device 702. In one case, when the processor 704 executes associated instructions that are stored in any memory or combination of memories, the computer device 702 can perform any of the operations of the associated instructions. The computer device 702 also includes one or more drive mechanisms 708, such as a hard disk drive mechanism, an optical disk drive mechanism, or the like, for interacting with any memory.

Computer device 702 can also include an input/output module 710 (I/O) for receiving various inputs (via input device 712) and for providing various outputs (via output device 714). One particular output mechanism may include a presentation device 716 and an associated Graphical User Interface (GUI) 718. In other embodiments, input/output module 710 (I/O), input device 712, and output device 714 may also not be included, as only one computer device in a network. Computer device 702 can also include one or more network interfaces 720 for exchanging data with other devices via one or more communication links 722. One or more communication buses 724 couple the above-described components together.

Communication link 722 may be implemented in any manner, such as over a local area network, a wide area network (e.g., the Internet), a point-to-point connection, etc., or any combination thereof. Communication link 722 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc., governed by any protocol or combination of protocols.

Corresponding to the methods as shown in fig. 1 to 5, the embodiments herein also provide a computer-readable storage medium having stored thereon a computer program, which when executed by a processor performs the steps of the above-mentioned method.

Embodiments herein also provide computer readable instructions, wherein when executed by a processor, a program thereof causes the processor to perform the method as shown in fig. 1-5.

Embodiments herein also provide a computer program product comprising at least one instruction or at least one program, which is loaded and executed by a processor to implement the method as shown in fig. 1 to 5.

It should be understood that, in various embodiments herein, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments herein.

It should also be understood that, in the embodiments herein, the term "and/or" is only one kind of association relation describing an associated object, meaning that three kinds of relations may exist. For example, a and/or B, may represent: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter associated objects are in an "or" relationship.

Those of ordinary skill in the art will appreciate that the various illustrative components and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the components and steps of the various examples have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the technical solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided herein, it should be understood that the disclosed system, apparatus, and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may also be an electric, mechanical or other form of connection.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the elements may be selected according to actual needs to achieve the objectives of the embodiments herein.

In addition, functional units in the embodiments herein may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions in the present invention substantially or partially contribute to the prior art, or all or part of the technical solutions may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods described in the embodiments herein. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

The principles and embodiments of this document are explained herein using specific examples, which are presented only to aid in understanding the methods and their core concepts; meanwhile, for the general technical personnel in the field, according to the idea of this document, there may be changes in the concrete implementation and the application scope, in summary, this description should not be understood as the limitation of this document.

Claims

1. A transaction authentication method based on a block chain is characterized by comprising the following steps:

receiving an authentication request for target transaction initiated by a first user, wherein the authentication request carries identity authentication information of an obligee;

when the block chain feeds back the inquiry result of the digital wallet, initiating a non-homogenization evidence inquiry request to the block chain so as to inquire whether the digital wallet stores the non-homogenization evidence of the target transaction;

when the block chain feeds back and stores the query result of the non-homogenization evidence, receiving the non-homogenization evidence fed back by the block chain;

2. The method of claim 1, wherein prior to receiving the first user-initiated request for authentication of the target transaction, the method further comprises:

acquiring a transaction request initiated by a second user for the target transaction, wherein the transaction request carries identity authentication information of the second user;

3. The method of claim 2, wherein prior to encrypting and storing the non-homogenization pass certificate in a digital wallet corresponding to the second user's authentication information, the method further comprises:

4. The method of claim 2, wherein casting the transaction credential as a non-homogenous credential by the smart contract further comprises:

5. The method of claim 4, wherein prior to decrypting the non-homogenization voucher with the obligee's private key and authenticating the target transaction based on the decryption result, the method further comprises:

receiving the validity period of the non-homogenization certification, which is fed back by the block chain and is obtained by the intelligent contract through calling a non-homogenization certification validity period verification function for query;

verifying whether the non-homogenization voucher is within a validity period;

if the non-homogenization evidence is in the valid period, the target transaction is authenticated by using the decryption result of the non-homogenization evidence of the private key;

and if the non-homogenization certification is not in the valid period, feeding back the target transaction authentication failure prompt.

6. The method of claim 2, wherein authenticating the target transaction based on the decryption result further comprises:

if yes, the target transaction is authenticated successfully;

and if not, feeding back the target transaction authentication failure prompt.

7. The method of claim 1, further comprising:

8. The method of claim 1, further comprising:

9. A blockchain based transaction authentication device, comprising:

10. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method according to any of claims 1 to 8 when executing the computer program.

11. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program which, when executed by a processor, implements the method of any one of claims 1 to 8.

12. A computer program product comprising at least one instruction or at least one program which is loaded and executed by a processor to implement the method of any one of claims 1 to 8.