TW202409933A - Non-fungible token login verification system and method - Google Patents

Abstract

A non-fungible token login verification system includes: a database; and a server, the server accesses the database and is communicatively connected to a blockchain, the server receives an electronic wallet application instruction from a first user device; wherein the server associates an electronic wallet with a first non-fungible token data based on the electronic wallet application instruction, the server transmits the first non-fungible token data to the blockchain, and the server stores the first non-fungible token data in the database as a second non-fungible token. token data; wherein the electronic wallet is associated with a first wallet address data, the blockchain has the first wallet address data, the server receives a login instruction from a second user device, and the server uses the first wallet address data to obtain the first non-fungible token data from the blockchain based at least on the login instruction; wherein the server provides the electronic wallet usage rights to the second user device based on the second non-fungible token data stored in the database being consistent with the first non-fungible token data.

Description

Non-fungible token login verification system and method

The present invention relates to a non-fungible token login verification system and method thereof, and in particular to a non-fungible token login verification system and method thereof with high security.

Traditional non-homogeneous token login verification systems often only perform password verification (e.g., password matching verification with public and private keys) during the login verification process (during which the user is provided with the corresponding electronic wallet usage rights). However, this login verification mechanism is relatively simple and it is difficult to effectively protect the user's account and the electronic wallet owned by the account. In view of this, a highly secure non-homogeneous token login verification system and method thereof will be required.

In order to solve the above problems, one idea of the present invention is to provide a non-fungible token login verification system and method with high security.

Based on the foregoing concept, the present invention provides a non-fungible token login verification system, including: a database; and a server. The server accesses the database and communicates with a blockchain. The server starts from a first A user device receives an electronic wallet application instruction; wherein the server associates an electronic wallet with a first non-fungible token data based on the electronic wallet application instruction, and the server converts the first non-fungible token The data is transmitted to the blockchain, and the server stores the first non-fungible token data in the database as a second non-fungible token data; wherein the electronic wallet is associated with a first wallet Address data, the blockchain has the first wallet address data, the server receives a login command from a second user device, and the server uses the first wallet address data to log in from the second user device based on at least the login command. The blockchain obtains the first non-fungible token data; wherein the server provides the electronic token based on the second non-fungible token data stored in the database that matches the first non-fungible token data. Wallet usage rights are granted to the second user device.

In a preferred embodiment of the present invention, the server generates the first non-fungible token data based on the electronic wallet application instruction.

In a preferred embodiment of the present invention, the server associates an electronic wallet with the first wallet address data, a first password data and a second password data based on the electronic wallet application instruction, and the server transmits the first wallet address data and the first password data to the blockchain; wherein the login instruction includes the second password data, the server obtains the first password data from the blockchain based on the login instruction, and the server matches the first password data and the second password data to obtain a matching result information; wherein the server uses the first wallet address data to obtain the first non-fungible token data from the blockchain based on the login instruction and the matching result information.

In a preferred embodiment of the present invention, the database stores a third password information, and the login command includes a fourth password information; wherein the server matches the fourth password information based on the third password information, and Obtain the first password data from the blockchain, and match the first password data and the second password data to obtain the matching result information.

In a preferred embodiment of the present invention, the first non-fungible token data includes a first smart contract address data, the first wallet address data, a first issuer wallet address data, and a first transaction time. At least one of data, a first transaction identity data and a first non-fungible token identity data.

In a preferred embodiment of the present invention, the second non-fungible token data stored in the database includes a second smart contract address data, a second wallet address data, and a second issuer wallet address data. , at least one of a second transaction time data, a second transaction identity data and a second non-fungible token identity data; wherein the second non-fungible token data is consistent with the first non-fungible token data. Token data means that the second smart contract address data matches the first smart contract address data, and/or the second wallet address data matches the first wallet address data, and/or the second issuer wallet the address data matches the first issuer wallet address data, and/or the second transaction time data matches the first transaction time data, and/or the second transaction identity data matches the first transaction identity data, and /or the second non-fungible token identity data matches the first non-fungible token identity data.

According to the purpose of the present invention, a non-fungible token login verification method is provided, which is applied to a non-fungible token login verification system. The non-fungible token login verification system includes a database and a server. The server accesses the database and is connected to a blockchain. The non-fungible token login verification method includes the following steps: the server receives an electronic wallet application instruction from a first user device; the server associates an electronic wallet with a first non-fungible token data based on the electronic wallet application instruction, wherein the electronic wallet is associated with a first wallet address data, and the blockchain has the first wallet address data; the server transmits the first non-fungible token data to the blockchain and stores the first non-fungible token data in the database as a second non-fungible token data; the server receives a login command from a second user device; the server uses the first wallet address data to obtain the first non-fungible token data from the blockchain based on at least the login command; and the server provides the electronic wallet usage rights to the second user device based on the second non-fungible token data stored in the database being consistent with the first non-fungible token data.

In a preferred embodiment of the present invention, the non-fungible token login verification method further includes the following steps: generating the first non-fungible token data by the server based on the electronic wallet application instruction.

In a preferred embodiment of the present invention, the non-fungible token login verification method further includes the following steps: the server applies an instruction based on the electronic wallet to associate an electronic wallet with the first wallet address information, a first a password information and a second password information; the server transmits the first wallet address information and the first password information to the blockchain; and the server obtains it from the blockchain based on the login command The first password information is matched with the first password information and the second password information to obtain a matching result information, wherein the login instruction includes the second password information; wherein the server is based on the login instruction and the Match the result information and use the first wallet address information to obtain the first non-fungible token information from the blockchain.

In a preferred embodiment of the present invention, the database stores a third password information, and the login command includes a fourth password information; wherein the server matches the fourth password information based on the third password information, The first password data is obtained from the blockchain, and the first password data and the second password data are matched to obtain a matching result information.

In a preferred embodiment of the present invention, the first non-fungible token data includes a first smart contract address data, the first wallet address data, a first issuer wallet address data, and a first transaction time. At least one of data, a first transaction identity data and a first non-fungible token identity data.

In a preferred embodiment of the present invention, the second non-fungible token data stored in the database includes a second smart contract address data, a second wallet address data, and a second issuer wallet address data. , at least one of a second transaction time data, a second transaction identity data and a second non-fungible token identity data; wherein the second non-fungible token data is consistent with the first non-fungible token data. Token data means that the second smart contract address data matches the first smart contract address data, and/or the second wallet address data matches the first wallet address data, and/or the second issuer wallet the address data matches the first issuer wallet address data, and/or the second transaction time data matches the first transaction time data, and/or the second transaction identity data matches the first transaction identity data, and /or the second non-fungible token identity data matches the first non-fungible token identity data.

The foregoing aspects and other aspects of the present invention will become more apparent based on the following detailed description of non-limiting specific embodiments and with reference to the accompanying drawings.

Please refer to the first figure, which illustrates a system architecture diagram of a specific embodiment of a non-fungible token login verification system according to the present invention. As shown in the first embodiment, the non-fungible token login verification system 100 includes a database 110 and a server 120. The server 120 is connected to the database 110 through communication, and the server 120 can access the database 110. In addition, the server 120 communicates with the blockchain 800, the first user device 910, and the second user device 920. In different embodiments, the first user device 910 and/or the second user device 920 may be various devices with network connection functions, such as the first user device 910 and/or the second user device 920 can be a computer, laptop, mobile phone, etc., but is not limited to this. In a specific embodiment, the non-fungible token login verification system 100 of the present invention includes one or more processors, and the non-fungible token login verification system 100 implements a database by cooperating with hardware and software. 110 and/or server 120. For example, the server 120 can transmit, receive, and process various data or instructions in a cooperative manner of hardware and software, and the database 110 can transmit, receive, and store various data or instructions in a cooperative manner of hardware and software.

In the embodiment shown in the first figure, the server 120 may receive an electronic wallet application instruction from the first user device 910. Based on the electronic wallet application instruction, the server 120 may associate an electronic wallet with a first non-fungible token data (this step may be regarded as the server 120 providing or trading a specific non-fungible token to the electronic wallet. The specific non-fungible token is associated with the first non-fungible token data). The electronic wallet is associated with a first wallet address data, and the blockchain 800 has the first wallet address data. The server 120 may transmit the first non-fungible token data to the blockchain 800, and the server 120 may store the first non-fungible token data in the database 110 as a second non-fungible token data (preferably, the second non-fungible token data has the same data content as the first non-fungible token data). The server 120 may receive a login instruction from the second user device 920, and the server 120 may use the first wallet address data to obtain the first non-fungible token data from the blockchain 800 based at least on the login instruction. Then, the server 120 can provide the second user device 920 with the electronic wallet usage rights based on the second non-fungible token data stored in the database 110 being consistent with the first non-fungible token data (the first non-fungible token data is obtained by the server 120 from the blockchain 800). In this way, after obtaining the electronic wallet usage rights, the second user device 920 can use the electronic wallet. Preferably, the first non-fungible token data is associated with a smart contract data, and the smart contract data indicates that the specific non-fungible token associated with the first non-fungible token data is a non-tradable non-fungible token. That is, the smart contract data indicates that a specific non-fungible token is exclusive to the electronic wallet, and the electronic wallet cannot trade (e.g., sell or give away) the specific non-fungible token to other parties (e.g., other electronic wallets).

Preferably, the first non-fungible token data is generated by the server 120 based on the electronic wallet application instruction, and the server 120 associates the electronic wallet with the first non-fungible token data. In a specific embodiment, the server 120 may be based on the fact that the second non-fungible token data stored in the database 110 does not match the first non-fungible token data (the first non-fungible token data is obtained by the server). The device 120 obtains from the blockchain 800) and decides not to provide the electronic wallet usage rights to the second user device 920. At this time, the second user device 920 cannot use the electronic wallet. Preferably, the second non-fungible token data is consistent with the first non-fungible token data, which refers to the content recorded in the second non-fungible token data and the first non-fungible token data. The content recorded in is the same. Preferably, the second non-fungible token information is not consistent with the first non-fungible token information, which means that the content recorded in the second non-fungible token information is different from the first non-fungible token information. The content recorded in the data is different. In different embodiments, the first user device 910 and the second user device 920 may be the same user device as required, or may be different user devices as required.

Preferably, the first non-fungible token information may include the first smart contract address information, the first wallet address information, the first issuer wallet address information, the first transaction time information, the first transaction identity information and the first non-fungible token information. At least one of the homogeneous token identity data. Preferably, the second non-fungible token data stored in the database 110 may include second smart contract address data, second wallet address data, second issuer wallet address data, second transaction time data, and second transaction data. At least one of the identity data and the second non-fungible token identity data.

Preferably, the second non-fungible token data is consistent with the first non-fungible token data, which means that the second smart contract address data is consistent with the first smart contract address data, and/or the second wallet address data is consistent with the first wallet address data, and/or the second issuer wallet address data is consistent with the first issuer wallet address data, and/or the second transaction time data is consistent with the first transaction time data, and/or the second transaction identity data is consistent with the first transaction identity data, and/or the second non-fungible token identity data is consistent with the first non-fungible token identity data. Preferably, the second non-fungible token data is consistent with the first non-fungible token data, which means that each data included in the second non-fungible token data is respectively consistent with the corresponding data included in the first non-fungible token data. Preferably, the second smart contract address data is consistent with the first smart contract address data, which means that the data content of the second smart contract address data is the same as the data content of the first smart contract address data. And the second wallet address data is consistent with the first wallet address data, which means that the data content of the second wallet address data is the same as the data content of the first wallet address data, and so on.

Preferably, the second non-fungible token data does not match the first non-fungible token data, which means that the second smart contract address data does not match the first smart contract address data, and/or the second wallet address data does not match the first wallet address data, and/or the second issuer wallet address data does not match the first issuer wallet address data, and/or the second transaction time data does not match the first transaction time data, and/or the second transaction identity data does not match the first transaction identity data, and/or the second non-fungible token identity data does not match the first non-fungible token identity data.

In a specific embodiment, the first non-fungible token data includes first smart contract address data, first wallet address data, first issuer wallet address data, first transaction time data, first transaction identity data, and first non-fungible token identity data. The second non-fungible token data stored in the database 110 includes second smart contract address data, second wallet address data, second issuer wallet address data, second transaction time data, second transaction identity data, and second non-fungible token identity data. The second non-fungible token data is consistent with the first non-fungible token data, which means that the second smart contract address data is consistent with the first smart contract address data, and the second wallet address data is consistent with the first wallet address data, and the second issuer wallet address data is consistent with the first issuer wallet address data, and the second transaction time data is consistent with the first transaction time data, and the second transaction identity data is consistent with the first transaction identity data, and the second non-fungible token identity data is consistent with the first non-fungible token identity data.

In a specific embodiment, when the server 120 receives an electronic wallet application instruction from the first user device 910, the server 120 may associate the electronic wallet with the first wallet address data, the first password data, and the second password data based on the electronic wallet application instruction. The first password data may be, for example, a public key described in the blockchain field, and the second password data may be, for example, a private key described in the blockchain field. The server 120 may transmit the first wallet address data and the first password data to the blockchain 800. When the server 120 receives a login instruction from the second user device 920, the login instruction includes the second password data. In this way, the server 120 can obtain the first password data from the blockchain 800 based on the login command, and match the first password data with the second password data in the login command to obtain matching result information.

In a specific embodiment, the database 110 may store third password information, and the login command may include fourth password information. The server 120 may obtain the first password data from the blockchain 800 based on the third password data matching the fourth password data, and match the first password data and the second password data to obtain matching result information. Preferably, the server 120 may receive a password import command based on the third password data matching the fourth password data. The server 120 may also cause the login command to include the second password data based on the password import command.

In a specific embodiment, the matching result information indicates that the first password data and the second password data can match each other. At this time, the server 120 can use the first wallet address data (preferably, the first wallet address data is obtained by the server 120 from the blockchain 800 based on the login instruction and the matching result information) to obtain the first non-fungible token data from the blockchain 800, and the server 120 can provide the electronic wallet usage rights to the second user device 920 based on the second non-fungible token data stored in the database 110 matching the first non-fungible token data. Preferably, if the matching result information indicates that the first password data and the second password data cannot match each other, the server 120 may decide not to provide the electronic wallet usage permission to the second user device 920 based on the matching result information. Preferably, the first password data and the second password data in the login instruction are matched to obtain the matching result information in a manner such as matching a public key with a private key in the blockchain field to obtain the matching result information.

Please refer to the second figure, which illustrates a flow chart of a specific embodiment of the non-fungible token login verification method according to the present invention. As shown in the second embodiment, the non-fungible token login verification method 200 can be applied to a non-fungible token login verification system. The non-fungible token login verification system includes a database and a server. The server accesses the database, and the server communicates with the blockchain, the first user device, and the second user device. The non-fungible token login verification method 200 begins in step 210, with the server receiving an electronic wallet application instruction from the first user device. Next, step 220 is executed, and the server applies an instruction based on the electronic wallet to associate the electronic wallet with the first non-fungible token data. Wherein, the electronic wallet is associated with the first wallet address data, and the blockchain has the first wallet address data. Next, step 230 is executed, the server transmits the first non-fungible token data to the blockchain, and stores the first non-fungible token data in the database as the second non-fungible token data. Next, step 240 is executed, and the server receives the login command from the second user device. Next, step 250 is executed, and the server uses the first wallet address data to obtain the first non-fungible token data from the blockchain based on at least the login command. Next, step 260 is executed, and the server provides the electronic wallet usage rights to the second user device based on the second non-fungible token data stored in the database matching the first non-fungible token data.

Preferably, the first non-fungible token data includes the first smart contract address data, the first wallet address data, the first issuer wallet address data, the first transaction time data, the first transaction identity data and the first non-fungible token data. At least one of the token identity data. Preferably, the second non-fungible token data stored in the database includes second smart contract address data, second wallet address data, second issuer wallet address data, second transaction time data, and second transaction identity data. and at least one of the second non-fungible token identity data. Preferably, the second non-fungible token data is consistent with the first non-fungible token data, which means that the second smart contract address data is consistent with the first smart contract address data, and/or the second wallet address data Match the first wallet address data, and/or the second issuer wallet address data match the first issuer wallet address data, and/or the second transaction time data match the first transaction time data, and/or the second transaction The identity data is consistent with the first transaction identity data, and/or the second non-fungible token identity data is consistent with the first non-fungible token identity data.

In a specific embodiment, the login instruction includes the second password data. The non-fungible token login verification method 200 may further include: the server associates the electronic wallet with the first wallet address data, the first password data, and the second password data based on the electronic wallet application instruction; the server transmits the first wallet address data and the first password data to the blockchain; and the server obtains the first password data from the blockchain based on the login instruction, and matches the first password data and the second password data to obtain a matching result information. Wherein, the server uses the first wallet address data to obtain the first non-fungible token data from the blockchain based on the login instruction and the matching result information.

In a specific embodiment, the non-fungible token login verification method 200 may further include: the server generates first non-fungible token data based on the electronic wallet application instruction. In a specific embodiment, the database stores third password data, and the login instruction includes a fourth password data. The server obtains the first password data from the blockchain based on the third password data matching the fourth password data, and matches the first password data and the second password data to obtain matching result information. Preferably, the server may receive a password import instruction based on the third password data matching the fourth password data. The server may also cause the login instruction to include the second password data based on the password import instruction.

So far, the non-homogeneous token login verification system and method of the present invention have been described by the above description and drawings. However, it should be understood that the specific embodiments of the present invention are only for illustrative purposes, and various changes can be made without departing from the scope and spirit of the patent application of the present invention, and all should be included in the patent scope of the present invention. Therefore, the specific embodiments described in this specification are not used to limit the present invention, and the true scope and spirit of the present invention are disclosed in the following patent application scope.

100: Non-fungible token login verification system 110: Database 120: Server 200: Non-fungible token login verification method 210~230: Steps 800: Blockchain 910: First user device 920: Second user device

The first figure is a system architecture diagram of a specific embodiment of the non-fungible token login verification system of the present invention.

The second figure is a flow chart of a specific embodiment of the non-fungible token login verification method of the present invention.

without

100: Non-fungible token login verification system

110:Database

120: Server

800:Blockchain

910: First user device

920: Second user device

Claims (12)

A non-fungible token login verification system, including: a database; and A server that accesses the database and communicates with a blockchain. The server receives an electronic wallet application instruction from a first user device; wherein the server associates an electronic wallet with a first non-fungible token data based on the electronic wallet application instruction, the server transmits the first non-fungible token data to the blockchain, and the server The server stores the first non-fungible token data into the database as a second non-fungible token data; wherein the electronic wallet is associated with a first wallet address information, the blockchain has the first wallet address information, the server receives a login instruction from a second user device, the server is at least based on the login instruction, and Use the first wallet address information to obtain the first non-fungible token information from the blockchain; The server provides the electronic wallet usage rights to the second user device based on the second non-fungible token data stored in the database being consistent with the first non-fungible token data. A non-fungible token login verification system as claimed in claim 1, wherein the server generates the first non-fungible token data based on the electronic wallet application instruction. If the non-fungible token login verification system of item 1 is requested, the server associates an electronic wallet with the first wallet address information, a first password information and a second password information based on the electronic wallet application instruction, The server transmits the first wallet address information and the first password information to the blockchain; The login command includes the second password data, the server obtains the first password data from the blockchain based on the login command, and the server matches the first password data and the second password data to obtain 1. Matching result information; The server uses the first wallet address data to obtain the first non-fungible token data from the blockchain based on the login command and the matching result information. As in claim 3, the non-fungible token login verification system, wherein the database stores a third password data, and the login instruction includes a fourth password data; wherein the server obtains the first password data from the blockchain based on the third password data being consistent with the fourth password data, and matches the first password data and the second password data to obtain the matching result information. For example, request the non-fungible token login verification system of item 1, wherein the first non-fungible token data includes a first smart contract address data, the first wallet address data, a first issuer wallet address data, a first issuer wallet address data, At least one of first transaction time information, a first transaction identity information, and a first non-fungible token identity information. As in claim 5, the non-fungible token login verification system, wherein the second non-fungible token data stored in the database includes at least one of a second smart contract address data, a second wallet address data, a second issuer wallet address data, a second transaction time data, a second transaction identity data, and a second non-fungible token identity data; The second non-fungible token data is consistent with the first non-fungible token data, which means that the second smart contract address data is consistent with the first smart contract address data, and/or the second wallet address data is consistent with the first wallet address data, and/or the second issuer wallet address data is consistent with the first issuer wallet address data, and/or the second transaction time data is consistent with the first transaction time data, and/or the second transaction identity data is consistent with the first transaction identity data, and/or the second non-fungible token identity data is consistent with the first non-fungible token identity data. A non-fungible token login verification method, applied to a non-fungible token login verification system. The non-fungible token login verification system includes a database and a server. The server accesses the database and communicates with it. Connect to a blockchain; the non-fungible token login verification method includes the following steps: Receive an electronic wallet application instruction from a first user device by the server; The server applies an instruction based on the electronic wallet to associate an electronic wallet with a first non-fungible token data, wherein the electronic wallet is associated with a first wallet address data, and the blockchain has the first wallet address material; The server transmits the first non-fungible token data to the blockchain, and stores the first non-fungible token data in the database as a second non-fungible token data; receiving a login command from a second user device by the server; using the first wallet address information to obtain the first non-fungible token information from the blockchain based on at least the login command by the server; and The server provides the electronic wallet usage rights to the second user device based on the second non-fungible token data stored in the database matching the first non-fungible token data. For example, the non-fungible token login verification method of request item 7 further includes the following steps: the server generates the first non-fungible token data based on the electronic wallet application instruction. For example, the non-fungible token login verification method in request item 7 further includes the following steps: The server associates an electronic wallet with the first wallet address information, a first password information and a second password information based on the electronic wallet application instruction; The server transmits the first wallet address information and the first password information to the blockchain; and The server obtains the first password data from the blockchain based on the login command, and matches the first password data and the second password data to obtain a matching result information, wherein the login command includes the third password data. 2. Password information; The server uses the first wallet address data to obtain the first non-fungible token data from the blockchain based on the login command and the matching result information. If the non-fungible token login verification method of item 9 is requested, the database stores a third password information, and the login command includes a fourth password information; and the server is based on the third password information that complies with the third password information. Four password data are obtained, and the first password data is obtained from the blockchain, and the first password data and the second password data are matched to obtain a matching result information. For example, request the non-fungible token login verification method of item 7, wherein the first non-fungible token information includes a first smart contract address information, the first wallet address information, a first issuer wallet address information, a first issuer wallet address information, At least one of first transaction time information, a first transaction identity information, and a first non-fungible token identity information. As in claim 11, the non-fungible token login verification method, wherein the second non-fungible token data stored in the database includes at least one of a second smart contract address data, a second wallet address data, a second issuer wallet address data, a second transaction time data, a second transaction identity data, and a second non-fungible token identity data; The second non-fungible token data is consistent with the first non-fungible token data, which means that the second smart contract address data is consistent with the first smart contract address data, and/or the second wallet address data is consistent with the first wallet address data, and/or the second issuer wallet address data is consistent with the first issuer wallet address data, and/or the second transaction time data is consistent with the first transaction time data, and/or the second transaction identity data is consistent with the first transaction identity data, and/or the second non-fungible token identity data is consistent with the first non-fungible token identity data.