KR102666287B1 - Method for providing nft service and system thereof - Google Patents

Abstract

A method and system for providing NFT voucher-based services is provided. In the method of providing an NFT ticket-based service according to an embodiment of the present disclosure, the first transaction for issuing an NFT (Non-Fungible Token) indicating a usage ticket owned by a first user with a first wallet is a token management block. A request to record the first transaction is transmitted to the token management blockchain so that it is recorded in the chain, and in response to the first user's request for use of a service based on the right of use accompanied by the address of the first wallet, the right of use information of the NFT is sent. is updated based on the service use request, and a request to record the second transaction is recorded in the history management blockchain so that the second transaction for recording the second hash value of the updated usage rights information is recorded in the history management blockchain. It may include the step of transmitting to . At this time, the history management blockchain may be a separate blockchain from the token management blockchain.

Description

NFT ticket-based service provision method and system {METHOD FOR PROVIDING NFT SERVICE AND SYSTEM THEREOF}

This disclosure relates to a method and system for providing services for use rights by converting use rights into NFTs.

Methods for managing member membership include swiping a plastic card on a terminal, obtaining information by linking the information to the system, and, if an individual wishes to buy or sell the ownership of the membership, uploading it to an online marketplace to conduct a direct transaction. However, there are problems with both acquiring information and transferring ownership. When acquiring information, only fragmented information is stored on magnetic cards, which has security vulnerabilities. Selling ownership takes time, has problems related to crime, and there are legal issues with rights transfer. do.

Japanese Patent No. 6940212

The technical problem to be solved in some embodiments of the present disclosure is that when services are provided by converting usage rights into NFTs, frequently changing usage rights information is stored in a blockchain that does not generate gas fees for recording transactions, It is to provide services.

Another technical problem to be solved in some embodiments of the present disclosure is to set the user terminal to not allow access to the blockchain that does not generate gas fees, so that the service server transmits the hash value only to the user terminal of the license holder. It provides a ticket service.

Another technical problem to be solved in some embodiments of the present disclosure is to provide a service that encrypts and stores off-chain information that is likely to significantly infringe on an individual's privacy.

The technical problems of the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by those skilled in the art from the description below.

In order to solve the above technical problem, a method of providing an NFT usage right-based service according to an embodiment of the present disclosure is to issue an NFT (Non-Fungible Token) indicating a usage right owned by a first user with a first wallet. Sending a request to record the first transaction to the token management blockchain so that the first transaction for is recorded in the token management blockchain, using a service based on the first user's usage rights accompanied by the address of the first wallet. In response to the request, updating the usage rights information of the NFT based on the service usage request and a second transaction for recording a second hash value of the updated usage rights information is recorded in the history management blockchain, 2 It may include the step of transmitting a transaction record request to the history management blockchain. At this time, the history management blockchain may be a separate blockchain from the token management blockchain.

In one embodiment, the step of updating the use right information of the NFT based on the service use request includes receiving the service use request accompanied by a first hash value and a first wallet address from the user terminal of the first user. Step, in the history management blockchain, using the first wallet address, querying the second hash value of the usage rights information of the NFT, and only if the first hash value and the second hash value match , It may include performing processing logic according to the service use request.

In one embodiment, the processing logic according to the service use request may cause an update of the usage right information of the NFT as a result of performing the processing logic according to the service use request.

In one embodiment, updating the usage rights information of the NFT based on the service use request, encrypting the updated usage rights information, and updating the encrypted usage rights so that the encrypted updated usage rights information is stored as metadata of the NFT. It may further include the step of transmitting the used usage information to off-chain storage.

In one embodiment, the step of updating the usage right information of the NFT based on the service use request includes encrypting the encrypted usage right information included in the metadata of the NFT off-chain before encrypting the updated usage right information. It may include the steps of requesting and receiving storage, decrypting the encrypted usage right information, and updating the decrypted usage rights information based on the service use request.

In one embodiment, the step of encrypting the updated usage right information may include encrypting the updated usage right information only when the updated usage right information satisfies an encryption condition, and the encrypted updated usage right information The step of transmitting the encrypted updated usage rights information to off-chain storage so that the usage rights information is stored as metadata of the NFT is carried out only when the updated usage rights information satisfies the encryption conditions. It may include transmitting the encrypted updated usage rights information to off-chain storage so that it is stored as metadata of the NFT.

In one embodiment, the step of transmitting the request to record the second transaction to the history management blockchain includes transmitting the second hash value to the user's terminal as a response to the request for use of the service based on the usage right. may include.

In one embodiment, the step of updating the use right information of the NFT based on the service use request includes subtracting the remaining number of services included in the use right information of the NFT by a value corresponding to the number of service uses of the service use request. may include.

In one embodiment, the history management blockchain may be a blockchain that does not incur a gas fee for recording transactions.

In one embodiment, the history management blockchain may not be accessible to user terminals.

In another embodiment of the present disclosure to solve the above technical problem, the NFT voucher-based service provision system includes a communication interface connected to the blockchain node of the token management blockchain and the blockchain node of the history management blockchain, and an NFT voucher-based service provision program. It may include a memory that is loaded and a processor that executes the NFT ticket-based service provision program.

At this time, the NFT usage rights-based service provision program ensures that the first transaction for issuance of an NFT (Non-Fungible Token) indicating a usage right owned by the first user with the first wallet is recorded in the token management blockchain. , an instruction for transmitting a request to record the first transaction to the token management blockchain, in response to the user's request for use of the service based on the right of use accompanied by the address of the first wallet, the use right information of the NFT A request for recording the second transaction is recorded in the history management blockchain so that the instruction for updating based on the service use request and the second transaction for recording the second hash value of the updated usage right information are recorded in the history management blockchain. It may include instructions to be transmitted to the management blockchain, and the history management blockchain may be a separate blockchain from the token management blockchain.

Figure 1 is a configuration diagram of a system that provides an NFT voucher service centered on a service server according to an embodiment of the present disclosure.
Figure 2 is an exemplary diagram for explaining an NFT issuing unit according to an embodiment of the present disclosure.
FIG. 3 is a configuration diagram of metadata described with reference to FIG. 2.
Figure 4 is a flow chart showing the NFT usage rights verification process according to an embodiment of the present disclosure.
Figure 5 is a flow chart showing the NFT issuance process explained with reference to Figure 4.
FIG. 6 is a flowchart of a transaction between a user terminal and a service server described with reference to FIG. 4.
Figure 7 is a flow chart specifying the NFT verification method described with reference to Figure 4.
Figure 8 is a flowchart for explaining the usage rights update process, which is referred to in embodiments of the present disclosure.
FIG. 9 is a flowchart specifying the pass update step described with reference to FIG. 8.
Figure 10 is a flowchart showing a process of modifying usage rights information, which is referred to in embodiments of the present disclosure.
FIG. 11 is a flowchart specifying the steps for modifying usage rights information explained with reference to FIG. 10.
FIG. 12 is a flowchart explaining the process of modifying the usage right information explained with reference to FIG. 10 according to FIG. 1.
13 is a hardware configuration diagram of a computing system described in some embodiments of the present disclosure.

Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the attached drawings. The advantages and features of the present invention and methods for achieving them will become clear by referring to the embodiments described in detail below along with the accompanying drawings. However, the technical idea of the present invention is not limited to the following embodiments and may be implemented in various different forms. The following examples are merely intended to complete the technical idea of the present invention and to be used in the technical field to which the present invention pertains. It is provided to fully inform those skilled in the art of the scope of the present invention, and the technical idea of the present invention is only defined by the scope of the claims.

In describing the present disclosure, if it is determined that a detailed description of a related known configuration or function may obscure the gist of the present invention, the detailed description will be omitted. Hereinafter, several embodiments of the present disclosure will be described with reference to the drawings.

Unless otherwise defined, terms (including technical and scientific terms) used in the following embodiments may be used with meanings that can be commonly understood by those skilled in the art to which this disclosure pertains. It may vary depending on the intentions or precedents of engineers working in related fields, the emergence of new technologies, etc. The terminology used in this disclosure is for describing embodiments and is not intended to limit the scope of this disclosure.

The singular expressions used in the following embodiments include plural concepts, unless the context clearly specifies singularity. Additionally, plural expressions include singular concepts, unless the context clearly specifies plurality.

In addition, terms such as first, second, A, B, (a), (b) used in the following embodiments are only used to distinguish one component from another component, and the terms The nature, sequence, or order of the relevant components are not limited.

An NFT ticket-based service provision system according to an embodiment of the present disclosure will be described with reference to FIG. 1. The NFT voucher-based service provision system according to an embodiment of the present disclosure may be comprised of one or more computing systems.

As shown in FIG. 1, the NFT voucher-based service provision system according to this embodiment may include a service server 200. And the service server 200 is an NFT issuing department (210, hereinafter abbreviated as 'Issuing Department'). It may include a usage verification unit 220 and a usage processing unit 230. The service server (200) is a history management blockchain (400) and a token management blockchain (500). The information about the usage rights is recorded and stored in the off-chain storage 300, which will be described in detail below.

According to an embodiment of the present disclosure, the issuing unit 210 of FIG. 2 is a module that issues NFT vouchers, and can issue vouchers using an NFT standard interface. The NFT standard interface may include a token method based on ERC-721 or ERC-1155, but the scope of the present disclosure is not limited thereto. Below, for convenience of understanding, the explanation will be continued assuming that NFTs are issued based on ERC-721.

The issuing unit 210 can issue an NFT voucher by executing the smart contract 211. As a result of the execution of the smart contract 211, NFT key data (or basic information) such as owner address information, initial price information, Image URL, etc. may be recorded in the token management blockchain 500. Additionally, the issuing unit 210 may store metadata 212 including NFT information (see 212a in FIG. 3) and usage rights information (see 212b in FIG. 3) in the off-chain storage 300.

In the case of the main data of the NFT voucher token, it can be recorded in the token management blockchain (500). Specifically, the first transaction for issuance of an NFT indicating a usage right owned by the first user with the first wallet may be recorded in the token management blockchain.

In addition, the main data of the voucher may include the user in the smart contract 211, the initial amount, etc., and in the case of the token management blockchain 500, for example, the Ethereum blockchain may be used. However, the scope of the present disclosure is not limited thereto.

The hash value of the usage rights information 212b in the metadata 212 may be recorded in the history management blockchain 400 according to an embodiment of the present disclosure. Specifically, the service server 200 has a Wallet ID (hereinafter, Wallet ID may also mean a wallet address) or Contract ID of the owner of the right to use, and according to the Wallet ID or Contract ID, a history management blockchain ( The hash value of the usage right information 212b can be recorded in 400). Hereinafter, the hash value before the usage rights information 212b is changed will be referred to as the first hash value, and the hash value after the usage rights information 212b has been changed will be referred to as the second hash value.

Additionally, the history management blockchain 400 may refer to a blockchain separate from the token management blockchain 500. For example, the history management blockchain 400 can utilize a blockchain such as Hyperledger that does not incur a gas fee for recording transactions. Since a new hash value must be recorded in the history management blockchain 400 every time the ticket information is updated, the economic effect of saving gas costs can be achieved when the ticket is used and renewed.

Additionally, the history management blockchain 400 may be set to not allow access to the user terminal 100. This is because the user terminal 100 must be able to have only the hash value transmitted by the service server 200 so that the usage rights verification process of the usage verification unit 220 can be safely performed. A detailed explanation of this will be provided later.

Figure 3 illustrates a case where metadata 212 according to an embodiment of the present disclosure consists of NFT information 212a and usage rights information 212b. Additionally, Figure 3 shows as an example that metadata 212 is managed in JSON format.

As shown in FIG. 3, the NFT information 212a of the metadata 212 may be managed in a plain text state, and the usage rights information 212b may be managed in an encrypted state. NFT information 212a includes, for example, image_data (e.g., ticket image), external_url (e.g., URL for storage location of usage ticket information), description (e.g., additional description of usage ticket), name (e.g., name of usage ticket, owner may include information on the name of the service provider, the name of the service provider, etc. In addition, the usage rights information 212b may include information on validity period, level, mileage, total number of uses, number of ownership changes, number of uses, owner, etc. However, the scope of the present disclosure is not limited thereto.

Any method may be used to encrypt the usage right information 213b, and in some cases, only part of the information belonging to the usage right information 213b may be encrypted.

As an example, the remaining number of uses or the expiration date in the usage rights information 212b may be disclosed without the need for encryption, but in the case of highly sensitive information such as the date of use, it may be encrypted to protect the user's privacy. . In this case, encryption conditions for selective encryption may be set in the usage rights information 212b.

The NFT information 212a may refer to information about the NFT itself rather than attribute information about the usage right, and conversely, the usage rights information 212b may mean attribute information about the usage right itself. Therefore, as an embodiment of the present disclosure, when the usage right is used or sold, the NFT information 212a is not changed, and only the usage right information 212b can be changed. Since the usage processing unit 230 of the service server 200 can modify and update only the changed usage rights information 212b, there is an advantage in that usage rights management is easy.

Since blockchain has scalability issues, it is realistically difficult to record all information about usage rights on the blockchain. Therefore, metadata 212 may be stored in off-chain storage 300. Off-chain storage 300 may be implemented, for example, as IPFS (i.e., distributed file system), but the scope of the present disclosure is not limited thereto.

In this case, the usage rights information 212b can be encrypted and stored in the off-chain storage 300, and when encryption conditions are set for the usage rights information 212b, only information that satisfies the above conditions is encrypted and stored in the off-chain storage. It may be stored in storage 300.

Additionally, the issuing unit 210 can store the Wallet ID of the person who originally issued the voucher. In one embodiment of the present disclosure, the user terminal 100 provides the user Wallet ID and hash value to the service server 200 and can request service use, and the service server 200 provides the Wallet ID and hash value. The usage right verification can be performed in the usage verification unit 220 using . In another embodiment, the issuing unit 210 may store not only the Wallet ID but also the Contract ID on a platform such as OpenSea, and the right to use may be verified through the Contract ID. The detailed operation of the usage verification unit 200 will be described below.

Figure 4 schematically illustrates the sequence for the issuing unit 210 and the usage right verification unit 220 to verify usage rights according to an embodiment of the present disclosure. First, when the issuing unit 210 issues an NFT voucher, the issuing unit 210 may transmit the Wallet ID of the ticket issuer and the first hash value of the voucher information to the user terminal 100. Additionally, the issuing unit 210 may record the first hash value (hereinafter abbreviated as 'first hash value') of the usage right information in the history management blockchain 400 (step S100).

Figure 5 is an example showing the process after issuing (issuing) a voucher in the issuing unit 210. First, the issuing unit 210 issues a voucher (S110), and then the issuing unit 210 issues the first hash value. And the user's Wallet ID can be transmitted to the user terminal 100 (step S120). During the process, the issuing unit 210 may internally store the user's Wallet ID for later verification of usage rights.

In step S130, the issuing unit 210 may record the first hash value in the history management blockchain. And in step S140, the usage rights information 213b in the metadata can be encrypted. At this time, there is no particular limitation on the method of encrypting the usage rights information 213b. Step S130 does not have to precede step S140, and the order may be changed if the first hash value does not change after encryption.

In Figure 4, step S200 is a step in which the user terminal 100 transmits the first hash value of the usage right information 213b to the service server. The user terminal 100 may include any device capable of wireless communication, such as a user's smartphone, laptop, or wearable device. Figure 6 schematically illustrates an example of step S200 according to a flowchart.

First, when the user terminal 100 requests the service server 200 to use a service based on a usage right (S210), the usage verification unit 220 of the service server 200 sends the first hash value, Wallet, as data for validating the usage right. You can request ID and/or Contract ID (S220). Then, the user terminal 100 may respond to the request and transmit the first hash value, Wallet ID, and/or Contract ID to the usage verification unit 220 of the service server 200.

When the user terminal 100 transmits the first hash value of the usage right information to the usage verification unit 220 of the service server 200, the usage verification unit 220 stores the received first hash value and the history management blockchain. By comparing the recorded first hash value, the right to use can be verified (S300).

Figure 7 is an embodiment of the present disclosure and specifically illustrates the process of verifying usage rights. First, the usage verification unit 220 can determine whether the first hash value transmitted from the user terminal and the first hash value recorded in the history management blockchain 400 are the same (S310). For example, the usage verification unit 220 may query the hash value (i.e., the first hash value) stored in the history management blockchain 400 using the user's first wallet address. If the first hash value transmitted from the user terminal and the first hash value recorded in the history management blockchain 400 are not the same, the right to use verification fails.

In one embodiment of the present disclosure, the history management blockchain 400 may be set to not allow access to the user terminal 100. If access to the user terminal 100 is allowed, a third party other than the license holder can also know the hash value of the license information, so it may be difficult to prove that the user is a legitimate user of the license using the system of the usage verification unit 220. Because.

Processing according to the user's service use request of the service server 200 only when the first hash value transmitted from the user terminal 100 and the first hash value recorded in the history management blockchain 400 match. The logic can be performed, and as a result of the execution of the processing logic, it is proven that the user is a legitimate user of the right of use, and the right of use information can be updated.

The usage verification unit 220 can obtain encrypted usage rights information stored in the off-chain storage 300 (S320). For example, the usage verification unit 220 may transmit a request to query usage rights information to the off-chain storage 300 and receive encrypted usage rights information from the off-chain storage 300. When the encrypted usage rights information is received, the usage verification unit 220 will decrypt the encrypted usage rights information. There is no particular limitation on the method of encrypting the usage rights information, and similarly, there will be no particular limitation on the method of decryption.

When the usage verification unit 220 decrypts the encrypted usage rights information received from the off-chain storage 300, the next step is to confirm (verify) the validity of the usage rights (S340). The step of confirming the validity of the ticket (S340) may mean, for example, a step of checking the validity of the ticket based on the remaining number of times, validity period, etc. For example, the usage verification unit 220 may determine that the usage right is not valid if there are no remaining usage times or the validity period has expired.

FIG. 8 shows a flowchart showing the step (S400) of updating usage right information in the usage processing unit 230 after completing the usage right verification step (S300) of the usage verification unit 220. The step of updating the usage right information (S400) can be performed immediately following the usage right verification step (S300).

For example, if the pass verification is successful, information such as the user's grade may change even before the pass is used, so it will be necessary to update the pass information immediately after the pass verification. In another embodiment of the present disclosure, the updating step (S400) may include deducting the remaining number of services included in the usage right information by a value corresponding to the number of service uses when the usage right holder uses the usage right.

Referring to FIG. 9, the usage rights information updating step of the usage processing unit 230 according to an embodiment of the present disclosure will be described in detail. First, the usage processing unit 230 may generate a second hash value, which is a new hash value of the updated usage right information (S410).

As an embodiment of the present disclosure, the service server 200 has the Wallet ID of the license holder, and therefore transmits a second hash value, which is a new hash value of the updated license information, to the user terminal (S420). Also, a second transaction for recording the second hash value of the updated usage rights information is recorded in the history management blockchain. A request to record the second transaction will be transmitted to the history management blockchain, and the second hash value is accordingly recorded in the history management blockchain (S430).

The usage processing unit 230 will encrypt the updated usage rights information (S440), and if encryption conditions are set in the usage rights information 212b, it will encrypt only information that satisfies the encryption conditions. There will be no particular limitation on the method of encryption, but if the service server 200 is encrypted using the same method as the method of encrypting the ticket information 212b when the ticket is first issued, the service server 200 will be able to operate effectively.

Next, when the usage processing unit 230 transmits the encrypted updated usage rights information to the off-chain storage, the off-chain storage can store the encrypted updated usage rights information in the off-chain storage (S450). Of course, if encryption conditions are set in the usage rights information 212b, information in the usage rights information 212b that does not meet the above conditions can be stored in off-chain storage in an unencrypted state.

Figure 10 is a flowchart showing the process for the license holder to modify the license information. In order for the user to modify the usage right information, a usage right verification step by the usage verification unit 220 will be required (S300). If it is proven that the user is the rightful owner of the usage right, the usage rights information will be updated by the usage processing unit 230 (S400), and the usage rights information can be modified in the next step (S500).

As an embodiment of the present disclosure, if there is an error in the usage right information 212b, the usage right information 212b may be modified at the user's request. In another embodiment, even if the user sells the ticket and the owner changes, modification of the ticket information will be necessary. but. If the owner of the right has changed due to sale, the service server 200 receives the owner change information from the NFT market platform where the right was traded, rather than a request to modify the right information 212b to the service server 200 of the right owner. , the usage processing unit 230 of the service server 200 modifies the usage right information. The NFT market platform may refer to a platform that provides transaction services for NFT, and transactions for NFT usage rights may be performed in conjunction with the service server 200.

Figure 11 is a flow chart showing the process of modifying the usage right information 212b according to an embodiment of the present disclosure. First, the user terminal 100 whose usage rights have been verified will be able to request the service server 200 to modify the usage rights information (S510). As an example, if the remaining number of passes, mileage, etc. of the pass are incorrectly calculated and stored in the open chain storage 300, the ticket holder may request a correction (S510) from the service server 200. However, if the remaining number of passes, etc. is set to be automatically deducted, the usage processing unit 230 can automatically modify information such as the remaining number of uses without a request from the user terminal 100.

The usage processing unit 230 may modify the usage rights information in response to the user's request to modify the usage rights information (S520). For example, the usage processing unit 230 may modify the usage right information according to the user's modification request only if the user's modification request is determined to be reasonable.

Next, the usage processing unit 230 may generate a second hash value, which is a new hash value, for the modified usage right information (S530). Then, the usage processing unit 23 can transmit the second hash value to the user terminal and record it in the history management blockchain 400.

As another embodiment of the present disclosure, when the user changes the owner in the usage right information 212b (e.g., when the NFT usage right is traded through the NFT market platform), a process such as step S550 is further performed in addition to the above process. It can be. Since the token management blockchain 500 is a space that stores key data of the usage token, owner change information (e.g., current owner information) can be recorded in the token management blockchain 500.

The above owner change information is only an example, and among the information set as key data by the issuing department 210 and recorded in the token management blockchain 500, changed information will also be recorded in the token management blockchain 500. You can.

In step S560, the usage processing unit 230 may re-encrypt the modified usage right information and store it in the off-chain storage 300. At this time, there is no particular limitation on the method of encrypting the usage right information (213b), and when encryption conditions are set, only the part of the usage right information (213b) that satisfies the encryption conditions among the information belonging to the usage right information (213b) is encrypted and used off-chain. It may be stored in storage 300.

Figure 12 shows the user terminal 100, the usage verification unit 220, the usage processing unit 230, the history management blockchain 400, and the token management blockchain ( 500) This is a schematic diagram of the entire flow chart.

The user terminal 100 can transmit the user's Wallet ID (address) and the first hash value to the usage verification unit 220 and request modification of usage rights information (S510a). Of course, the Contract ID may be transmitted in addition to the user's Wallet ID. In some cases, the NFT market platform may request modification of usage rights information.

Next, the usage verification unit 220 determines whether the first hash value of the history management blockchain 400 searched by the user's Wallet ID or Contract ID and the first hash value transmitted by the user are the same to verify usage rights. You can do it (S300). For details on this, please refer to the above description.

Next, when the usage right is verified, a process of updating the usage right can be performed (step S400).

Next, the use verification unit 220 may request the use processing unit 230 to modify the use right information in response to a request to modify the use right information transmitted by the user terminal (S510b). The usage processing unit 230 may modify the usage rights information in response to the request for modifying the usage rights information (S520). And, the usage processing unit 230 may generate a second hash value corresponding to the modified usage right information (S530).

The usage processing unit 230 may record the second hash value in the history management blockchain 400 (S540a) and transmit the second hash value to the user terminal 100 (S540b).

If a request for modification of key data (e.g., owner information, etc.) for NFT usage rights is received, the usage processing unit 230 may record the modified key data in the token management blockchain 500. In the case of key data, there may be information such as the user (owner) of the ticket, the amount of the ticket, etc., but it is not limited to this.

13 is a hardware configuration diagram of a computing system according to some embodiments of the present disclosure. The computing system 1000 of FIG. 13 includes one or more processors 1100, a system bus 1600, a communication interface 1200, and a memory (loading) a computer program 1500 executed by the processor 1100. 1400) and a storage 1300 that stores a computer program 1500. For example, the computing system of FIG. 13 may be the NFT service server 100 described with reference to FIG. 1.

The processor 1100 controls the overall operation of each component of the computing system 1000. The processor 1100 may perform operations on at least one application or program to execute methods/operations according to various embodiments of the present disclosure. The memory 1400 stores various data, commands and/or information. The memory 1400 may load one or more computer programs 1500 from the storage 1300 to execute methods/operations according to various embodiments of the present disclosure. Storage 1300 may non-temporarily store one or more computer programs 1500. The computer program 1500 may include one or more instructions implementing methods/operations according to various embodiments of the present disclosure. When the computer program 1500 is loaded into the memory 1400, the processor 1100 can perform methods/operations according to various embodiments of the present disclosure by executing the one or more instructions.

The computer program 1500 may be an NFT ticket service program.

In some embodiments, the computer program 1500 records a first transaction for issuance of a non-fungible token (NFT) indicating a usage right owned by a first user having a first wallet in the token management blockchain. Preferably, instructions for transmitting a request to record the first transaction to the token management blockchain, in response to a request for use of the service based on the right of the user accompanied by the address of the first wallet, use right information of the NFT Instructions for updating based on the service use request, requesting a record of the second transaction so that the second transaction for recording the second hash value of the updated usage rights information is recorded in the history management blockchain. It may include instructions sent to the history management blockchain. In this case, the history management blockchain is a separate blockchain from the token management blockchain.

In some embodiments, the computing system described with reference to FIG. 13 may be configured using one or more physical servers included in a server farm based on cloud technology, such as a virtual machine. In this case, at least some of the processor 1100, memory 1400, and storage 1300 among the components shown in FIG. 13 may be virtual hardware, and the communication interface 1200 may also be a virtual switch. It may be composed of virtualized networking elements such as switches.

Although operations are shown in the drawings in a specific order, it should not be understood that the operations must be performed in the specific order shown or sequential order or that all illustrated operations must be performed to obtain the desired results. In certain situations, multitasking and parallel processing may be advantageous. Although embodiments of the present disclosure have been described above with reference to the attached drawings, those skilled in the art will understand that the present invention can be implemented in other specific forms without changing the technical idea or essential features. I can understand that there is. Therefore, the embodiments described above should be understood in all respects as illustrative and not restrictive. The scope of protection of the present invention should be interpreted in accordance with the claims below, and all technical ideas within the equivalent scope should be construed as being included in the scope of rights of the technical ideas defined by this disclosure.

Claims (11)

In a method performed by a computing system,
A request to record the first transaction is sent to the token so that the first transaction for the issuance of a non-fungible token (NFT) indicating a usage right owned by the first user with the first wallet is recorded in the token management blockchain. transmitting to the management blockchain;
In response to a service use request based on the service right of the first user accompanied by the address of the first wallet, updating the use right information of the NFT based on the service use request;
Transmitting a request to record the second transaction to the history management blockchain so that the second transaction for recording the second hash value of the updated usage rights information is recorded in the history management blockchain,
The history management blockchain is a separate blockchain from the token management blockchain,
A method of providing services based on NFT usage rights. According to claim 1,
The step of updating the NFT usage rights information based on the service use request,
Receiving, from the user terminal of the first user, the service use request accompanied by a first hash value and a first wallet address;
In the history management blockchain, using the first wallet address, searching for a second hash value of the usage rights information of the NFT; and
Comprising the step of performing processing logic according to the service use request only when the first hash value and the second hash value match,
A method of providing services based on NFT usage rights. According to clause 2,
The processing logic according to the above service use request is,
As a result of performing the processing logic according to the service use request, the NFT usage rights information is updated,
A method of providing services based on NFT usage rights. According to claim 1,
The step of updating the NFT usage rights information based on the service use request,
Encrypting the updated usage rights information; and
Further comprising transmitting the encrypted updated usage rights information to off-chain storage so that the encrypted updated usage rights information is stored as metadata of the NFT,
A method of providing services based on NFT usage rights. According to clause 4,
The step of updating the NFT usage rights information based on the service use request,
Before the step of encrypting the updated usage rights information, the encrypted usage rights information included in the metadata of the NFT is requested and received from off-chain storage, the encrypted usage rights information is decrypted, and the decrypted usage rights information is stored in the Including the step of updating based on service use requests,
A method of providing services based on NFT usage rights. According to clause 4,
The step of encrypting the updated usage rights information is,
Comprising the step of encrypting the updated usage right information only when the updated usage right information satisfies encryption conditions,
The step of transmitting the encrypted updated usage rights information to off-chain storage so that the encrypted updated usage rights information is stored as metadata of the NFT,
Only when the updated usage rights information satisfies the encryption conditions, it includes transmitting the encrypted updated usage rights information to off-chain storage so that the encrypted updated usage rights information is stored as metadata of the NFT. doing,
A method of providing services based on NFT usage rights. According to claim 1,
The step of transmitting a request to record the second transaction to the history management blockchain is,
Including transmitting the second hash value to the user's terminal as a response to the request for use of the service based on the usage right,
A method of providing services based on NFT usage rights. According to claim 1,
The step of updating the NFT usage rights information based on the service use request,
Including the step of subtracting the remaining number of services included in the usage rights information of the NFT by a value corresponding to the number of service uses of the service use request,
A method of providing services based on NFT usage rights. According to claim 1,
The history management blockchain is a blockchain that does not incur gas fees for recording transactions.
A method of providing services based on NFT usage rights. According to claim 1,
The history management blockchain is one in which user terminal access is not permitted,
A method of providing services based on NFT usage rights. In computing systems,
A communication interface connected to the blockchain node of the token management blockchain and the blockchain node of the history management blockchain;
Memory into which the NFT ticket-based service provision program is loaded;
Including a processor that executes the NFT usage rights-based service provision program,
The NFT ticket-based service provision program is,
A request to record the first transaction is sent to the token so that the first transaction for the issuance of a non-fungible token (NFT) indicating a usage right owned by the first user with the first wallet is recorded in the token management blockchain. Instructions to send to the management blockchain;
In response to a request for use of a service based on the service right of a user carrying the address of the first wallet, instructions for updating the use right information of the NFT based on the service use request;
Includes instructions for transmitting a request to record the second transaction to the history management blockchain so that the second transaction for recording the second hash value of the updated usage rights information is recorded in the history management blockchain,
The history management blockchain is a separate blockchain from the token management blockchain,
NFT ticket-based service provision system.

Images