Method for issuing NFT related to corporate services and server performing the same

Abstract

A method for issuing an NFT linked to a corporate service is provided. A method for issuing an NFT linked to a corporate service according to some embodiments of the present invention is a method for issuing an NFT linked to a corporate service performed on a server, comprising the steps of: receiving a request for issuance of a first NFT related to the first service from a user device of a first user who has received the first service; collecting first user information of the first user and first service information of the first service as metadata; providing the metadata to an NFT contract to issue the first NFT and creating a first ledger corresponding to the first NFT; and delivering the first NFT to the virtual asset wallet of the first user.

Description

Technology Field

[0001] The present invention relates to a method for issuing NFTs and a server for performing the same. Specifically, the present invention relates to a method for issuing NFTs linked to corporate services and a server for performing the same, which can support customers in conveniently issuing and managing NFTs linked to services operated by the company. Background Technology

[0003] The content described in this section merely provides background information regarding the present embodiment and does not constitute prior art.

[0004] Over the past few years, blockchain-based virtual asset technology has been cited as the most promising technology globally as a core technology of the Fourth Industrial Revolution, and the fields in which blockchain-based virtual asset technology is utilized in users' real lives are on the rise.

[0005] Among these, NFTs are garnering attention as a key technology related to virtual assets. An NFT (Non-Fungible Token) is a virtual asset technology authenticated by a blockchain verified by unique bits that permanently record authenticity. Each piece of digital data in an NFT possesses a unique identification value, representing a non-fungible token. Various content and digital documents, ranging from digital art and game items to music, photos, and videos, can be created as NFTs and traded.

[0006] For general users to purchase NFTs or receive them through specific services, multiple steps of preparation were required, which could lead to errors during the process of transferring or purchasing virtual assets.

[0007] Furthermore, when a specific company intends to provide NFTs related to its current services to service users, the data processing for NFT transactions on the blockchain network takes a significant amount of time, and certain costs (gas fees) are continuously incurred. In addition, this conventional NFT issuance procedure suffers from poor interoperability with the company's service platform, resulting in a problem where users cannot conveniently utilize the company's NFT issuance services.

[0008] In other words, conventional NFT issuance procedures have acted as technical or procedural barriers to activating NFTs for general users, and there is a need for methods and technologies to improve this. The problem to be solved

[0010] The objective of the present invention is to provide a method and server for issuing NFTs linked to corporate services that can support customers in easily receiving and managing NFTs linked to corporate services by opening and managing centralized virtual asset wallets for each customer.

[0011] In addition, the objective of the present invention is to provide an NFT issuance method and server linked to an enterprise service that can support the rapid processing of NFT issuance and transactions by managing NFT contracts through a centralized server without registering them on a blockchain network.

[0012] In addition, the objective of the present invention is to provide an NFT issuance method and server linked to an enterprise service that can prevent tampering with NFT contracts managed through a centralized server and prevent tampering with NFT transaction records.

[0013] The objects of the present invention are not limited to those mentioned above, and other unmentioned objects and advantages of the present invention may be understood from the following description and will be more clearly understood by the embodiments of the present invention. Furthermore, it will be readily apparent that the objects and advantages of the present invention can be realized by the means and combinations thereof set forth in the claims. means of solving the problem

[0015] A method for issuing an NFT linked to an enterprise service according to some embodiments of the present invention for solving the above problem is a method for issuing an NFT linked to an enterprise service performed on a server, comprising the steps of: receiving a request to issue a first NFT related to the first service from a user device of a first user who has received the first service; collecting first user information of the first user and first service information of the first service as metadata; providing the metadata to an NFT contract to issue the first NFT and creating a first ledger corresponding to the first NFT; and delivering the first NFT to the virtual asset wallet of the first user.

[0016] Additionally, the step of receiving a request to issue the first NFT may include creating a virtual asset wallet for the first user, providing the first service to the first user, providing a digital document related to the first service, and receiving a request to issue the first NFT for the digital document from the user device.

[0017] Additionally, the request for the first NFT issuance for the digital document includes the first user processing the first NFT issuance cost, the step of creating the first user's virtual asset wallet includes configuring the first user's payment method storage unit, the step of providing the first service to the first user includes providing reward points related to the first service to the payment method storage unit, and the first NFT issuance cost can be processed through the reward points.

[0018] Additionally, the request for the first NFT issuance for the digital document includes issuance method information for issuing the first NFT, and if the issuance method information is an internal process method, the metadata is provided to the NFT contract, and if the issuance method information is an external process method, the metadata may be provided to a blockchain network.

[0019] Additionally, the NFT issuance method according to the present embodiment may further include the step of providing transaction information for the first NFT to the NFT contract, and the step of recording the transaction information of the first NFT processed by the NFT contract in the first ledger.

[0020] In addition, the transaction information of the first NFT can be recorded in the first ledger in the form of a hash chain.

[0021] In addition, the code constituting the NFT contract may be stored on a blockchain network.

[0022] In addition, the NFT issuance method according to the present embodiment may further include a step of verifying the authenticity of the NFT contract based on the code constituting the NFT contract stored in the blockchain network.

[0023] Additionally, the NFT issuance method according to the present embodiment may further include the steps of receiving a bridge request from the user device to move the first NFT to a blockchain network, collecting metadata of the first NFT in response to the bridge request, deleting the first NFT from the first user's virtual asset wallet, and minting a new NFT corresponding to the first NFT to the blockchain network based on the collected metadata of the first NFT.

[0024] A server according to some embodiments of the present invention for solving the above problem comprises a service providing unit that provides a first service to a first user, a customer account management unit including a virtual asset wallet of the first user, and an NFT management unit that receives a request to issue a first NFT related to the first service from a user device of the first user who has received the first service, collects the first user information and the information of the first service as metadata, provides the metadata to an NFT contract to issue the first NFT, generates a first ledger corresponding to the first NFT, and transmits the first NFT to the virtual asset wallet of the first user. Effects of the invention

[0026] A method and server for issuing NFTs linked to corporate services according to some embodiments of the present invention can support customers in easily issuing and managing NFTs linked to corporate services by opening and managing a centralized virtual asset wallet for each customer.

[0027] In addition, the NFT issuance method and server linked to enterprise services according to some embodiments of the present invention can support the rapid processing of NFT issuance and transactions by managing NFT contracts through a centralized server without registering them on a blockchain network.

[0028] In addition, the NFT issuance method and server associated with enterprise services according to some embodiments of the present invention may perform NFT contract anchoring by registering the code of the NFT contract on a blockchain network to prevent tampering with the NFT contract managed through a centralized server. Accordingly, it may be possible to verify the tampering with the NFT contract and restore it to the original NFT contract.

[0029] In addition, the NFT issuance method and server linked to enterprise services according to some embodiments of the present invention manage a centralized ledger for each NFT, and record NFT transaction history in a hash chain manner to prevent the ledger's records from being falsified or altered.

[0030] In addition to the above, the specific effects of the present invention are described together with the following explanation of specific details for implementing the invention. Brief explanation of the drawing

[0032] FIG. 1 is a block diagram illustrating the main configuration of an enterprise NFT issuance system according to some embodiments of the present invention. FIG. 2 is a block diagram illustrating the functions of a server in an enterprise NFT issuance system according to some embodiments of the present invention. FIG. 3 illustrates, exemplarily, the preliminary process conventionally performed by a user to purchase or receive an NFT. Figure 4 is an example diagram illustrating the data processing process of a blockchain network for processing transactions for conventional NFTs. FIG. 5 is a block diagram illustrating the main functions of a server according to some embodiments of the present invention. FIG. 6 is a flowchart of an NFT issuance method linked to corporate services according to some embodiments of the present invention. FIG. 7 is an illustrative diagram for explaining the process of performing an NFT issuance method linked to a corporate service according to some embodiments of the present invention. Figure 8 is a flowchart showing the detailed steps of receiving a request for the issuance of the first NFT. Figure 9 is an example diagram illustrating how the code of an NFT contract is registered and anchored to a blockchain network. Figure 10 is an example diagram illustrating the steps to verify the authenticity of an NFT contract. Figure 11 is a flowchart illustrating the steps for recording transaction details according to an NFT transaction. FIG. 12 is an example diagram illustrating the process of issuing an NFT according to the type of request for issuance of the first NFT. Figure 13 is an example diagram illustrating the process of handling NFT issuance costs. FIG. 14 is an example diagram illustrating the modification of an NFT ledger based on a transaction between a first user and a second user. FIG. 15 is a flowchart illustrating the process of bridging a first NFT to a blockchain network in response to an NFT bridge request. Specific details for implementing the invention

[0033] Terms and words used in this specification and claims shall not be interpreted as being limited to their general or dictionary meanings. In accordance with the principle that an inventor may define the concept of a term or word to best describe their invention, they shall be interpreted in a meaning and concept consistent with the technical spirit of the invention. Furthermore, since the embodiments described in this specification and the configurations illustrated in the drawings are merely one embodiment of the invention and do not represent the entire technical spirit of the invention, it should be understood that various equivalents, modifications, and applicable examples capable of replacing them may exist at the time of filing this application.

[0034] The terms first, second, A, B, etc., as used in this specification and claims may be used to describe various components, but said components should not be limited by said terms. These terms are used solely for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, the first component may be named the second component, and similarly, the second component may be named the first component. The term "and / or" includes a combination of a plurality of related described items or any of a plurality of related described items.

[0035] The terms used in this specification and claims are used merely to describe specific embodiments and are not intended to limit the invention. The singular expression includes the plural expression unless the context clearly indicates otherwise. In this application, terms such as "comprising" or "having" should be understood as not precluding the existence or addition of the features, numbers, steps, actions, components, parts, or combinations thereof described in the specification.

[0036] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as generally understood by those skilled in the art to which this invention pertains.

[0037] Terms such as those defined in commonly used dictionaries should be interpreted as having meanings consistent with their meanings in the context of the relevant technology, and should not be interpreted in an ideal or overly formal sense unless explicitly defined in this application.

[0038] In the present invention, a Non-Fungible Token (NFT; hereinafter NFT) is a virtual asset technology authenticated by a blockchain authenticated by unique bits that permanently record authenticity. Each piece of digital data possesses a unique recognition value and represents a non-fungible token. An NFT can be viewed as a type of certified copy of a land register that proves the authentication and ownership of digital assets by utilizing blockchain technology, which guarantees transaction transparency and is fundamentally impossible to tamper with.

[0039] Digital assets utilized as NFTs can include a wide range of content, from digital art and game items to music, photos, and videos. Additionally, digital assets utilized as NFTs may include digital documents and data that provide or guarantee information related to products sold by a company or services provided by the company, such as product warranties, product barcodes, product serial numbers, service warranties, and service memberships.

[0040] Furthermore, NFTs are not limited to digital assets but can also provide the function of authenticating and proving ownership of actual assets.

[0041] In the present invention, "minting" refers to the process of creating and exchanging virtual assets or tokens as a process for generating blockchain assets. Additionally, in the present invention, "minting" may refer to the process by which a creator registers and generates their content as an NFT.

[0042] In the present invention, an NFT bridge may mean connecting an existing NFT and a new NFT by minting a new NFT having the same metadata as an NFT minted on a first blockchain network into a second blockchain network that is different from the first blockchain network, and the existing NFT may be modified so as not to be used or discarded, and substantially interpreted as the existing NFT being moved from the first blockchain network to the second blockchain network.

[0043] In addition, each component, process, procedure, or method included in each embodiment of the present invention may be shared within a scope that is not technically contradictory to one another.

[0045] Hereinafter, with reference to FIGS. 1 to 15, a method for issuing an NFT associated with an enterprise service according to some embodiments of the present invention will be described.

[0047] FIG. 1 is a block diagram illustrating the main configuration of an enterprise NFT issuance system according to some embodiments of the present invention. FIG. 2 is a block diagram illustrating the functions of a server in an enterprise NFT issuance system according to some embodiments of the present invention.

[0048] Referring to FIG. 1, an enterprise NFT issuance system (10) includes a user device (100), a server (200), and a blockchain network (300).

[0049] A user device (100), a server (200), and a blockchain network (300) can exchange data through a network. The network may include wired internet technology, wireless internet technology, and a network based on local area communication technology. Wired internet technology may include, for example, at least one of a local area network (LAN) and a wide area network (WAN).

[0050] Wireless internet technology may include, for example, at least one of Wireless LAN (WLAN), DLNA (Digital Living Network Alliance), WiBro (Wireless Broadband), WiMAX (World Interoperability for Microwave Access), HSDPA (High Speed ​​Downlink Packet Access), HSUPA (High Speed ​​Uplink Packet Access), IEEE 802.16, Long Term Evolution (LTE), LTE-A (Long Term Evolution-Advanced), Wireless Mobile Broadband Service (WMBS), and 5G NR (New Radio) technology. However, the present embodiment is not limited thereto.

[0051] Short-range communication technology may include, for example, at least one of Bluetooth, RFID (Radio Frequency Identification), Infrared Data Association (IrDA), Ultra-Wideband (UWB), ZigBee, Near Field Communication (NFC), Ultra Sound Communication (USC), Visible Light Communication (VLC), Wi-Fi, Wi-Fi Direct, and 5G NR (New Radio). However, the present embodiment is not limited thereto.

[0052] The server (200) may be a service server operated by an entity (hereinafter, “Company”) that sells products or provides services to customers. The Company may provide to customers through a user environment in which customers purchase products or receive intangible services via the server (200).

[0053] The customer can use the user environment provided by the server (200) through the user device (100). That is, the user device (100) refers to the customer's device that can access the user environment. The user device (100) may refer to a personal computer (PC), a laptop, a personal digital assistant (PDA), a portable computer, a web tablet, a wireless phone, a mobile phone, a digital music player, a memory card, a cold wallet, a hot wallet, or any electronic product capable of transmitting and / or receiving information over a network.

[0054] The server (200) and the user device (100) may be implemented as a server-client system. In an embodiment, the server (200) may provide a user environment to the user through a service application installed on the user device (100). Here, the service application may be a dedicated application for providing a user environment or a web browsing application for providing a web page.

[0055] The server (200) may be implemented as at least one of a workstation, a data center, an internet data center (IDC), a direct attached storage (DAS) system, a storage area network (SAN) system, a network attached storage (NAS) system, and a redundant array of inexpensive disks, or a redundant array of independent disks (RAID) system, but the present embodiment is not limited thereto. Additionally, the server (200) may be implemented through cloud computing, distributed computing, or client-server computing technology to efficiently provide a user environment to the user device (100).

[0056] The blockchain network (300) may be a peer-to-peer network comprising nodes that are multiple computing devices. The blockchain network (300) can prevent forgery and alteration by storing transaction records of various coins, tokens, and NFTs in corresponding nodes.

[0057] Referring to FIG. 2, the server (200) can provide a user environment for a customer to use the company's services online. Through the user environment, the customer can purchase the company's products or use the services provided by the company. Through the user environment provided by the server (200), the customer can view information related to the services they have used or receive digital documents related thereto.

[0058] In addition, the company can provide services to offline customers. That is, customers can purchase the company's products at offline stores or use the services provided by the company. Through the user environment provided by the server (200), customers can register information related to the services they have used, look up related information, or receive digital documents related thereto.

[0059] The server (200) may provide the customer with a digital document related to a product or service that is sold or provided to the customer. Such a digital document may be a certificate indicating at least one of the authenticity, condition, and grade of a specific product. For example, the server (200) may provide a digital document along with a certificate certifying that the bag is genuine to a customer who has purchased a bag. Additionally, the digital document may be a document proving the membership of a user receiving a specific service. For example, the server (200) may provide a digital document with a VIP membership certificate indicating the user's VIP grade.

[0060] In an embodiment of the present invention, a digital document may be minted and registered as an NFT and provided to a customer. An NFT can represent a non-fungible token, as each piece of digital data possesses a unique recognition value. Therefore, when a digital document is minted and registered as an NFT and provided, the originality of the digital document is further guaranteed, and forgery and alteration are fundamentally blocked, thereby further enhancing the reliability of the document.

[0061] FIG. 3 illustrates, in an exemplary manner, the preliminary process conventionally performed by a user to purchase or receive an NFT. FIG. 4 is an exemplary diagram illustrating the data processing process of a blockchain network for processing transactions for a conventional NFT.

[0062] Referring to Fig. 3, a general user (consumer) must carry out multiple preliminary procedures to purchase an NFT. First,

[0063] A general user (consumer) must sign up for a virtual asset exchange (S11) and proceed with the procedure of issuing a real-name account (S12). Additionally, the general user can purchase virtual assets from the virtual asset exchange (S13). In step (S13), the purchase of virtual assets can be performed using a wallet from the virtual asset exchange. However, since the general user must use their own virtual asset wallet to purchase NFTs with virtual assets, in the next step (S14), the process of the general user creating a separate personal virtual asset wallet is carried out. Next, the general user proceeds with a preliminary procedure to transfer the virtual assets purchased from the exchange to their personal virtual asset wallet (S15). After carrying out the above-described process, the general user can use the virtual assets transferred to their personal wallet to purchase the desired NFT or proceed with the process of receiving NFTs from a specific entity (S16). This complex preliminary process may cause errors by the consumer.

[0064] In particular, general consumers may make mistakes during the process of transferring or purchasing virtual assets, such as sending assets to the wrong wallet address or purchasing unwanted NFTs. Currently, virtual asset exchanges are unable to immediately correct or rectify such purchases and transfers by general consumers, and regulations to protect these consumers remain inadequate. Consequently, the conventional preliminary procedures required to obtain and purchase NFTs act as technical and procedural barriers for general consumers, serving as a factor hindering the popularization of NFTs.

[0065] Referring to Fig. 4, when a company or consumer performs a transaction such as issuing or trading an NFT, they must wait for the data processing process on the blockchain network. That is, for an NFT minted on a blockchain network, the approval and processing of the transaction related to the NFT is completed only after the consensus process of the participants in the blockchain network is completed.

[0066] If data processing (consensus and sharing) on ​​such a blockchain network is required for each transaction of an issued NFT, rapid processing of NFT transactions becomes impossible, and maintenance costs become significant. In other words, the burden on companies to maintain NFT issuance services can increase proportionally to the number of NFTs issued, and these technical limitations act as a factor hindering the popularization of NFTs.

[0068] In an embodiment of the present invention, the server (200) may be configured to provide and manage an NFT associated with a digital document to a customer without performing the complex preliminary process that a customer must perform to receive the NFT. Additionally, the server (200) can save time and costs associated with NFT issuance by minimizing data exchange with a blockchain network that was previously performed to issue NFTs.

[0069] FIG. 5 is a block diagram illustrating the main functions of a server according to some embodiments of the present invention.

[0070] Referring to FIG. 5, the server (200) may include a service provision unit (210), a customer account management unit (220), and an NFT management unit (230).

[0071] Here, each component of the server (200) is not intended to refer to a physically distinct component. In FIG. 5, each component is depicted as a distinct block, but this is merely functionally distinguished by the operation being performed. Depending on the embodiment, some or all of the components may be integrated within the same device, one or more may be implemented as separate devices physically distinct from other parts, or they may be components connected to communicate with each other in a distributed computing environment.

[0072] The service provider (210) can provide the company's services to customers. The service provider (210) can configure a user environment for customers to use the company's services online and provide it to the customer's user device (100). Additionally, the service provider (210) can provide a user environment that allows customers to register and manage the history of using the company's services offline. That is, the service provider (210) can provide a user environment that can manage both online and offline customers.

[0073] The customer account management unit (220) can manage information on customers using the company's services on an account-by-account basis. Additionally, the customer account management unit (220) may include a virtual asset wallet (220A) configured for each account using the company's services.

[0074] A virtual asset wallet (220A) can provide the function of storing a customer's virtual assets and tokens. In particular, the virtual asset wallet (220A) may be configured to store and keep NFTs issued through the process described below. The virtual asset wallet (220A) may be protected by an encryption method consisting of a private key that is a random number and a corresponding wallet address (hash value of the public key). In some embodiments, the encryption method may apply cryptographic security technologies such as multi-signature, Shamir secret sharing, threshold signature (TSS), or secure MPC, but is not limited thereto.

[0075] A server (200) according to an embodiment of the present invention can issue and manage a customer's public key and private key in a centralized manner. A virtual asset wallet (220A) can be created in response to a customer's request or a procedure for signing up to use the service environment provided by the server (200). The server (200) can provide a private key to each customer, generate a public key corresponding to the provided private key, and construct a wallet address for storing NFTs based on the generated public key. As the server (200) provides a virtual asset wallet (220A), customers do not have to individually perform the process of creating a virtual asset wallet for issuing or purchasing NFTs, and can proceed with NFT issuance through the virtual asset wallet (220A).

[0076] Additionally, in some embodiments, the customer account management unit (220) may include a payment method storage unit (220B) that stores information related to digital goods or payment methods for using the company's services. For example, the payment method storage unit (220B) may include prepaid points provided through prepayment or the customer's credit card information. Additionally, the service provider (210) may provide points to the customer as a reward for the customer's use of the service, and such points provided as a reward may be stored in the payment method storage unit (220B). The customer may use the company's services by utilizing the points or credit card information stored in the payment method storage unit (220B).

[0077] The NFT management unit (230) may be configured to issue NFTs related to the service used by the customer. Here, the subject to be issued as an NFT may be a digital document related to the service, but is not limited thereto. When a digital document is minted, registered, and provided as an NFT, the authenticity and reliability of the digital document may be enhanced. Additionally, the NFT management unit (230) may manage NFTs issued by the customer by recording changes resulting from transactions regarding the NFT in the NFT ledger.

[0078] Specifically, the NFT management unit (230) may include an NFT issuance unit (230A), an NFT contract unit (230B), an NFT management unit (230C), and an NFT ledger (230D).

[0079] The NFT issuance unit (230A) can issue a new NFT in response to a customer's request for NFT issuance. The NFT contract unit (230B) can manage and control a smart contract (hereinafter referred to as “NFT contract”) required for NFT issuance or NFT transactions. In an embodiment of the present invention, an NFT contract may refer to a script or command for executing a contract for issuing an NFT according to input conditions or a contract for generating an NFT transaction according to input conditions.

[0080] The NFT management unit (230C) can manage previously issued NFTs. A transaction request for an issued NFT can be provided to the NFT management unit (230C). The NFT management unit (230C) provides transaction information corresponding to the provided transaction request to the NFT contract unit (230B) so that a transaction for the NFT is processed in the NFT contract. Additionally, the details of changes processed by the NFT contract can be recorded in the NFT ledger. Here, the NFT transaction details can be recorded in the corresponding ledger in the form of a hash chain.

[0081] The NFT ledger (230D) may store information related to previously issued NFTs. Each NFT may have its own unique ledger, and information related to the NFT may be recorded in the corresponding ledger.

[0082] Here, the NFT issuing unit (230A) may request the issuance of an NFT to the NFT contract, and the NFT contract may issue the NFT without performing data exchange (e.g., unnecessary consensus and sharing processes) on the blockchain network (300).

[0083] Additionally, the NFT management unit (230C) can transmit NFT transactions performed by customers to the NFT contract, and the NFT contract can record changes related to the NFT in response to the NFT transaction in the NFT ledger without performing data exchange (e.g., unnecessary consensus and sharing processes) in the blockchain network (300).

[0084] That is, in an embodiment of the present invention, the server (200) can use a centralized NFT contract through the NFT management unit (230) without using an NFT contract configured in the blockchain network (300). Accordingly, when an NFT is issued or traded, the issuance history and transaction history can be recorded immediately in the ledger without waiting for the data processing process in the blockchain network (300). In an embodiment of the present invention, the server (200) can provide technical features that enable the issuance and management of NFTs quickly, efficiently, and economically.

[0086] Hereinafter, the characteristics of the main components of the server (200) and the method of issuing and managing NFTs in the server (200) will be explained in more detail with reference to FIGS. 6 to 11.

[0087] FIG. 6 is a flowchart of a method for issuing an NFT linked to a corporate service according to some embodiment of the present invention. FIG. 7 is an illustrative diagram explaining the process of performing a method for issuing an NFT linked to a corporate service according to some embodiment of the present invention. FIG. 8 is a flowchart showing detailed steps of the step of receiving a request for the issuance of a first NFT. FIG. 9 is an illustrative diagram explaining that the code of an NFT contract is registered and anchored to a blockchain network. FIG. 10 is an illustrative diagram explaining the step of verifying the authenticity of an NFT contract. FIG. 11 is a flowchart explaining the step of recording transaction details according to an NFT transaction.

[0089] A method for issuing an NFT linked to a corporate service according to some embodiments of the present invention corresponds to a method for issuing an NFT linked to a corporate service performed on a server (200).

[0090] Referring to FIG. 6, a method for issuing an NFT associated with an enterprise service according to some embodiments of the present invention includes the steps of: receiving a request to issue a first NFT associated with the first service from a user device of a first user who has received the first service (S110); collecting first user information of the first user and first service information of the first service as metadata (S120); providing the metadata to an NFT contract to issue the first NFT and creating a first ledger corresponding to the first NFT (S130); and delivering the first NFT to the virtual asset wallet of the first user (S140).

[0091] The NFT issuance method of the present embodiment described below is explained based on a first user, but this is merely an example and the method according to the embodiment of the present invention is not limited thereto.

[0092] First, a request to issue a first NFT related to the first service is received from a user device (S110).

[0093] In step (S110), the server (200) may receive a request for the issuance of the first NFT from the user device (100). Referring to FIG. 7, the user device (100) may be the user device of a first user who has received the first service provided by the company, and the first user may request the issuance of the first NFT related to the first service from the NFT issuance unit (230A) of the server (200) through the user device (100).

[0094] Referring to FIG. 8, step (S110) includes the step of creating a virtual asset wallet for the first user (S111), the step of providing the first service to the first user (S112), the step of providing a digital document related to the first service (S113), and the step of receiving a request for the issuance of the first NFT for the digital document from the user device (S114).

[0095] In step (S111), a virtual asset wallet for the first user may be created at the request of the first user or during the first user's membership registration process. The server (200) may provide a private key to the first user. The first user may generate a public key corresponding to the provided private key and configure a wallet address for storing NFTs based on the generated public key. The configured virtual asset wallet of the first user may be stored in the virtual asset wallet (220A) of the customer account management department (220).

[0096] In step (S112), the service provider (210) may configure a user environment for the first user to use the company's services online and provide it to the customer's user device (100). Additionally, the service provider (210) may provide a user environment that allows the customer to register and manage the history of using the company's services offline. That is, in step (S112), the first service provided to the first user may refer to an online service or an offline service provided by the company. If the first user uses the online service, the first user's service usage history may be automatically recorded and managed through the server (200). Additionally, if the first user uses the offline service, the first user's service usage history may be managed through the server (200) as the company registers it on the server (200) in accordance with the first user or the first user's request.

[0097] In step (S113), the service provider (210) provides a digital document related to the first service to the first user. Such digital document may be provided in response to a request from the first user. The first user may request the server (200) to provide the digital document related to the received first service, and the server (200) may provide the digital document to the first user's user device (100) in response to the request. However, this is not limited thereto, and in some embodiments, the digital document may be provided in step (S113) in response to the provision of the first service in step (S112). The digital document may be a certificate indicating at least one of the authenticity, status, and grade of a specific product. Additionally, the digital document may be a document proving the membership of a user receiving a specific service.

[0098] In step (S114), a request for the issuance of a first NFT for a digital document is received from the user device (100). The NFT issuance unit (230A) of the NFT management unit (200) receives this request for the issuance of a first NFT and proceeds with subsequent operations for the issuance of a first NFT.

[0100] Next, the first user information and the first service information are collected as metadata (S120).

[0101] In step (S120), metadata for the issuance of the first NFT may be collected. Metadata refers to data that can verify key information of the first NFT. In this embodiment, the metadata may be configured based on first user information regarding the first user who is the owner of the first NFT and first service information regarding the first service that is the target of the issuance of the first NFT.

[0102] The first service information refers to information related to the subject issued as an NFT in relation to the first service. As illustrated in FIG. 7, the NFT issuing unit (230A) can collect the first service information from the service providing unit (210) (S120A).

[0103] The first service information may refer to information constituting a digital document corresponding to the issuance target of the NFT. For example, if the digital document includes information related to the purchase of a product, the purchased product, the date of purchase, and product authenticity verification information may be collected as service information. For example, if the digital document is a certificate representing the first user's membership, the user's membership level information, the membership level maintenance period, and information on benefits associated with the membership level may be collected as service information.

[0104] Additionally, referring to FIG. 7, the NFT issuing unit (230A) can collect first user information from the customer account management unit (220) (S120B). The first user information may include information that can verify the identity of the first user, such as the first user's name and ID. The NFT issuing unit (230A) can construct metadata based on the collected service information and user information.

[0105] Next, metadata is provided to the NFT contract to issue the first NFT, and a first ledger corresponding to the first NFT is created (S130).

[0106] In step (S130), the process of issuing a first NFT through the collected metadata and creating a first ledger corresponding to the issued first NFT can be performed. The NFT issuing unit (230A) can provide the collected metadata to the NFT contract unit (230B) so that the issuance of the first NFT proceeds (S130A).

[0107] The NFT contract unit (230B) can issue an NFT based on metadata entered through a pre-configured NFT contract. The NFT contract may refer to a script or command for executing a contract for issuing an NFT based on entered conditions or a contract for generating an NFT transaction based on entered conditions. In an embodiment, the NFT contract may be managed on a centralized server (200) rather than on a blockchain network (300). Therefore, rapid issuance of the NFT and processing of transactions can proceed through the NFT contract without waiting for data processing on the blockchain network (300).

[0108] In an embodiment, the NFT contract may be programmed to comply with the ERC721 standard. In some embodiments, the NFT contract may be configured to be distributed by distributed nodes. Additionally, the NFT contract may be included in an NFT contract unit (230B), but embodiments of the invention are not limited thereto.

[0109] The NFT contract unit (230B) can perform data exchange with the NFT contract. The NFT contract unit (230B) can operate the NFT contract in a separate distributed computing environment different from the server environment where the configurations of other NFT issuing servers (200) operate, and can manage the operation of the NFT contract. This distributed computing environment may refer to an environment where data processing is performed without a consensus or agreement process among participants, such as in a conventional blockchain network (300). In some embodiments, the NFT contract may be contained in at least one cloud server (not shown) separated from the server (200) and may be controlled by the NFT contract unit (230B). As the NFT contract is configured in at least one cloud server (not shown), the independent operation of the NFT contract can be further guaranteed.

[0110] In some embodiments, considering that the conventional blockchain network (300) is an open environment in which multiple users can participate publicly, if it is defined as a “public blockchain network,” the computing environment in which the NFT contract operates through the NFT contract unit (230B) can be defined as a “closed blockchain network” or a “private blockchain network.” Additionally, when issuing an NFT through a public blockchain network is defined as “external issuance,” issuing an NFT through a private blockchain network can be defined as “internal issuance.”

[0111] Here, the code constituting the NFT contract can be registered on the blockchain network (300). In an embodiment of the present invention, the process of registering the code constituting the NFT contract on the blockchain network (300) is defined as “NFT contract anchoring.”

[0112] Referring to FIG. 9, the NFT contract unit (230B) can register the code that constitutes the NFT contract to the blockchain network (300) after the NFT contract is configured.

[0113] An NFT contract can be composed of a specific blockchain network family language as well as various languages ​​that are conventionally used, and can be written in a language that can be easily applied on an NFT issuance server (200). For example, an NFT contract can be written based on a specific blockchain network family language such as Solidity, as well as languages ​​that are conventionally used such as Python, Java, C#, C / C++, PHP, R, Kotlin, etc.

[0114] The code registered on the blockchain network (300) may include at least one of the source code of the NFT contract and the byte code of the source code compiled from the source code.

[0115] In some embodiments, the server (200) receives the written NFT contract code and compiles the NFT contract code to generate byte code. Using the generated byte code as data, the server (200) can generate a transaction with an empty destination address (to). The administrator of the server (200) may be the deployer of the NFT contract and may be a signer who performs a signature related to the delivery of the transaction. Along with the administrator's signature, the transaction may be transmitted to a node of the blockchain network (300). The transmission of the transaction may be performed through a process such as a Remote Procedure Call (RPC). At the node of the transmitted blockchain network (300), the process of distributing the provided byte code is performed. Here, the node may generate a new contract address using the transaction serial number and the signature address. The byte code is executed on the EVM for error checking, and a contract associated with the byte code may be generated. That is, the contract associated with the byte code is distributed and registered on the blockchain network (300).

[0116] Through the process described above, the code of the NFT contract can be distributed and registered on the blockchain network (300), and the code anchored to the blockchain network (300) can be preserved in a state where arbitrary changes to it are impossible.

[0117] Code anchored to the blockchain network (300) can be preserved in a state where arbitrary changes to it are impossible. When an NFT contract is managed centrally by a server (200), the likelihood of modifications to the NFT contract—such as arbitrary changes by specific individuals or hacking by outsiders—may be higher than when managed through the blockchain network (300). The anchored code corresponds to data that can verify the originality of the NFT contract. Therefore, even if modifications or changes occur to the NFT contract, the modifications or changes can be tracked through the anchored code, and restoration to the original state can be carried out. In other words, through NFT contract anchoring, arbitrary changes to the NFT contract that may occur as the NFT contract is managed by a centralized server (200) can be verified, and restoration to the original state can be supported.

[0118] In some embodiments, the method for issuing an NFT associated with a corporate service according to some embodiments of the present invention may further include a step (S150) of verifying the authenticity of said NFT contract based on code constituting an NFT contract stored on a blockchain network.

[0119] Referring to FIG. 10, the NFT contract unit (230B) can verify the authenticity of the currently operating NFT contract by comparing the code of the currently operating NFT contract with the anchored code (S150). Additionally, step (S150) may include deleting the current NFT contract and restoring the NFT contract based on the code if it is confirmed that the current NFT contract and the NFT contract based on the code are different.

[0120] The step (S150) of verifying the authenticity of the NFT contract and performing restoration can be performed according to a preset period or at the request of the administrator of the server (200). Since the step (S150) is performed periodically or at the request of the administrator of the server (200), the authenticity of the NFT contract can be guaranteed even if the NFT contract is not operated on the blockchain network (300), thereby ensuring stable NFT issuance and management.

[0121] Referring again to FIG. 7, the NFT contract unit (230B) can provide metadata to the NFT contract to issue a first NFT and create a first ledger. The first ledger can be provided to the NFT ledger (230D) (S130B), and the issued first NFT can be provided to the first user's customer account management unit (220) (S140). The first NFT is stored and managed in the first user's virtual asset wallet (220A). When a transaction regarding the first NFT occurs, the details are recorded in this first ledger.

[0123] Referring to FIG. 11, an NFT issuance method linked to an enterprise service according to some embodiments of the present invention may further include the step of providing transaction information for a first NFT to an NFT contract (S160) and the step of recording transaction information of the first NFT processed by the NFT contract in a first ledger (S170).

[0124] In step (S160), a transaction request for the first NFT may be provided to the NFT management unit (230C). In some embodiments, the first user may generate a transaction request for the first NFT to change information related to the first NFT through the user device (100) and transmit it to the NFT management unit (230C). Additionally, in some embodiments, the server (200) may generate a transaction request for the first NFT if an update to the first service provided to the first user or the state of the first user is required, and may have the NFT management unit (230C) process it.

[0125] The NFT management unit (230C) can generate transaction information in response to a transaction request for the provided first NFT and can provide the generated transaction information to the NFT contract.

[0126] In step (S170), the NFT contract can process the transaction of the first NFT according to the provided transaction information, and the processed transaction history can be recorded in the first ledger. In step (S170), the recording in the first ledger can be performed according to a hash chain method. A hash chain method refers to a technology that manages transaction history in a way that makes tampering impossible by utilizing a hash function.

[0127] Step (S170) may include generating a hash value of a history previously stored in the first ledger through a hash function, and storing the generated hash value of the previously stored history and the currently processed transaction history together in the first ledger. The previously stored history may be stored together with the current transaction history as a hash value when storing the current transaction history. That is, data related to the first NFT may only be added to the first ledger without alteration or deletion. Here, if the transaction history is arbitrarily changed, the hash value changes. That is, by continuously accumulating and storing the previously stored history in a chain form, it becomes possible to determine whether the history recorded in the ledger has been tampered with or forged.

[0128] That is, in step (S170), as the record data of the first ledger is stored connected by a hash chain, the record data of the first ledger can be managed so that it is practically impossible to tamper with.

[0130] A method and server for issuing NFTs linked to corporate services according to some embodiments of the present invention can support customers in easily issuing and managing NFTs linked to corporate services by opening and managing a centralized virtual asset wallet for each customer.

[0131] In addition, the NFT issuance method and server linked to enterprise services according to some embodiments of the present invention can support the rapid processing of NFT issuance and transactions by managing NFT contracts through a centralized server without registering them on a blockchain network.

[0132] In addition, the NFT issuance method and server associated with enterprise services according to some embodiments of the present invention may perform NFT contract anchoring by registering the code of the NFT contract on a blockchain network to prevent tampering with the NFT contract managed through a centralized server. Accordingly, it may be possible to verify the tampering with the NFT contract and restore it to the original NFT contract.

[0133] In addition, the NFT issuance method and server linked to enterprise services according to some embodiments of the present invention manage a centralized ledger for each NFT, and record NFT transaction history in a hash chain manner to prevent the ledger's records from being falsified or altered.

[0135] In addition, the NFT issuance method and server linked to the enterprise service according to some embodiments of the present invention can support not only the method of issuing NFTs internally as described above, but also the method of issuing NFTs to the blockchain network (300), that is, the method of issuing NFTs externally.

[0136] FIG. 12 is an example diagram illustrating the process of issuing an NFT according to the type of request for issuance of the first NFT.

[0137] Referring to FIG. 12, in step (S114), the request for issuing an NFT for a digital document may further include information on the method of issuing the NFT. Here, the information on the method of issuing the NFT may refer to information requested by the user, determining whether to issue the NFT internally or to issue the NFT externally.

[0138] In step (S115), the NFT issuance unit (230A) of the server (200) can analyze NFT issuance method information and determine the issuance method of the user's NFT according to the NFT issuance method information. That is, the server (200) can determine whether to issue the NFT internally or externally in response to the user's request included in the NFT issuance method information.

[0139] Here, internal issuance of an NFT refers to a process performed on a server (200) according to the embodiment described above. If the NFT issuance method information is internal issuance, the collected metadata may be provided to a centralized NFT contract of an NFT contract unit (230B). An NFT is issued through the NFT contract, and the issued NFT is provided to a customer-specific virtual asset wallet that is centrally managed, and the NFT may be managed through the issued ledger.

[0140] Here, external issuance of an NFT may mean issuing an NFT using a smart contract registered on a blockchain network, as in conventional methods, and delivering the issued NFT to a wallet on the blockchain network or to a customer's personal wallet. Therefore, if the NFT issuance method information is external issuance, the collected metadata may be provided to the blockchain network.

[0141] That is, the NFT issuance method and server linked to enterprise services according to some embodiments of the present invention support not only the process of internally processing NFTs but also the process of externally processing NFTs, thereby supporting the use of NFTs in various ways without restricting the customer's NFT minting to a specific method.

[0143] In some embodiments, costs for issuing NFTs may be incurred. An NFT issuance method and server associated with enterprise services according to some embodiments of the present invention may process NFT issuance costs through reward points provided per customer account or financial payment methods.

[0144] Figure 13 is an example diagram illustrating the process of handling NFT issuance costs.

[0145] Referring to FIG. 13, the request for issuing an NFT for a digital document in step (S114) may include the user processing the NFT issuance cost. That is, step (S114) may include the step of the user processing the NFT issuance cost (S114A) and the step of confirming the cost processing and transmitting the NFT issuance request to the NFT issuance unit (230A) of the server (200) (S114B).

[0146] In step (S114), the NFT issuance cost may be processed based on information stored in the customer's payment method storage unit (220B). That is, the NFT issuance cost may be processed through digital goods or payment methods stored in the payment method storage unit (220B). In some embodiments, the payment method storage unit (220B) may include reward points provided as a reward for the customer's use of the service, and the NFT issuance cost may be processed through the reward points.

[0147] That is, the NFT issuance method and server linked to enterprise services according to some embodiments of the present invention support processing NFT issuance costs through digital goods or payment methods stored in a payment method storage unit (220B), thereby supporting customers to conveniently issue and use NFTs. In addition, by supporting payment with reward points provided per customer account, it supports customers to issue NFTs at a low cost.

[0149] In addition, the NFT issuance method and server linked to enterprise services according to some embodiments of the present invention can mediate the trading of services between users and can record changes in NFT information resulting from service trading in a corresponding ledger.

[0150] FIG. 14 is an example diagram illustrating the modification of an NFT ledger based on a transaction between a first user and a second user.

[0151] Referring to FIG. 14, a server (200) according to some embodiments of the present invention may include a transaction brokerage unit (240) that mediates service transactions between a plurality of users. The transaction brokerage unit (240) may provide a brokerage service that supports the execution of service transactions between a plurality of users.

[0152] The first user and the second user can use the brokerage service through the first user device (110A) and the second user device (110B) and can conduct service transactions with each other. For example, in FIG. 14, the first service transaction may mean that the first user resells a product purchased through the first service to the second user. In the embodiment, the first user may have issued a first NFT related to the product purchased through the first service. The transaction brokerage unit (240) can broker such transactions between the first user and the second user.

[0153] Here, as the owner of the product changes to a second user through such a transaction, it may be necessary to change the information regarding the first NFT. If the transaction brokerage unit (240) needs to change the information regarding the first NFT according to the first service transaction, it may generate a first NFT transaction request and provide it to the NFT management unit (230C). Here, the change in information regarding the first NFT may include a change in the owner of the target product of the first NFT and the owner of the first NFT.

[0154] The NFT management unit (230C) transmits NFT transaction information to the NFT contract in response to the first NFT transaction request so that the NFT transaction is processed, and accordingly, the transaction details can be recorded in the first NFT ledger.

[0155] In addition, the NFT issuance method and server linked to enterprise services according to some embodiments of the present invention can mediate the trading of services between users and support recording changes to NFT information resulting from service trading in a corresponding ledger, thereby supporting the active trading of goods and services related to NFTs among various users.

[0157] In addition, the NFT issuance method and server associated with enterprise services according to some embodiments of the present invention may support moving an NFT issued through the server (200) to an external, i.e., blockchain network.

[0158] FIG. 15 is a flowchart illustrating the process of bridging a first NFT to a blockchain network in response to an NFT bridge request.

[0159] Referring to FIG. 15, a method for issuing an NFT associated with an enterprise service according to some embodiments of the present invention includes the steps of receiving a bridge request from a user device to move a first NFT to a blockchain network (S210), collecting metadata of the first NFT in response to the bridge request (S220), deleting the first NFT from the first user's virtual asset wallet (S230), and minting a new NFT corresponding to the first NFT to the blockchain network based on the collected metadata of the first NFT (S240).

[0160] In the present invention, an NFT bridge may mean connecting an existing NFT and a new NFT by minting a new NFT having the same metadata as an NFT minted on a first blockchain network into a second blockchain network that is different from the first blockchain network, and the existing NFT may be modified so as not to be used or discarded, and substantially interpreted as the existing NFT being moved from the first blockchain network to the second blockchain network.

[0161] In step (S210), the first NFT may be in a state of being issued through a centralized NFT contract provided by the current server (200). A bridge request to move the first NFT to a blockchain network means moving this first NFT to a blockchain network (300) selected by the user. That is, a bridge request to move the first NFT to a blockchain network may be a request to change the first NFT, which was internally issued through the server (200), into an externally issued state.

[0162] In step (S220), the server (200) can collect metadata related to the first NFT. The server (200) can compose metadata by collecting information related to the first NFT from the first ledger.

[0163] In step (S230), the server (200) can delete the first NFT for which the collection of metadata is complete.

[0164] In step (S240), the server (200) transmits metadata to the blockchain network (300) so that an NFT corresponding to the metadata is minted.

[0165] In the embodiments, steps (S230) and (S240) are described and explained in order for convenience of explanation, but there is no chronological order between the two steps. In some embodiments, step (S240) may be executed prior to step (S230).

[0166] In step (S240), the blockchain network (300) can issue an NFT based on metadata. The blockchain network (300) can provide metadata to an NFT contract configured for NFT issuance, and a new NFT is issued based on the metadata. The newly issued NFT can be transferred to the first user's wallet address created on the blockchain network (300) or to the first user's individual wallet address.

[0167] An NFT issuance method and server linked to an enterprise service according to some embodiments of the present invention support moving internally issued NFTs to an external blockchain network, thereby enabling customers to utilize NFTs in various ways.

[0169] The method for issuing an NFT linked to an enterprise service according to an embodiment may also be implemented in the form of a computer-readable medium that stores instructions and data executable by a computer. In this case, the instructions and data may be stored in the form of program code, and when executed by a processor, may generate a specific program module to perform a specific operation. Furthermore, the computer-readable medium may be any available medium accessible by a computer and includes both volatile and non-volatile media, as well as removable and inseparable media. Additionally, the computer-readable medium may be a computer recording medium, which may include both volatile and non-volatile, removable and inseparable media implemented by any method or technique for storing information such as computer-readable instructions, data structures, program modules, or other data. For example, the computer recording medium may be a magnetic storage medium such as an HDD or SSD, an optical recording medium such as a CD, DVD, or Blu-ray disc, or a memory included in a server accessible via a network.

[0170] In addition, the NFT issuance method associated with enterprise services according to the embodiment may be implemented as a computer program (or computer program product) comprising instructions executable by a computer. The computer program includes programmable machine instructions processed by a processor and may be implemented in a high-level programming language, an object-oriented programming language, assembly language, or machine language, etc. Additionally, the computer program may be recorded on a tangible computer-readable recording medium (e.g., memory, hard disk, magnetic / optical medium, or SSD (Solid-State Drive), etc.).

[0171] The above description is merely an illustrative explanation of the technical concept of the present embodiment, and a person skilled in the art to which the present embodiment belongs would be able to make various modifications and variations within the scope of the essential characteristics of the present embodiment. Accordingly, the present embodiments are intended to explain, not limit, the technical concept of the present embodiment, and the scope of the technical concept of the present embodiment is not limited by these embodiments. The scope of protection of the present embodiment shall be interpreted by the claims below, and all technical concepts within an equivalent scope shall be interpreted as being included within the scope of rights of the present embodiment.

Claims

Claim 1 A method for issuing an NFT linked to an enterprise service performed on a server, comprising: receiving a request to issue a first NFT related to the first service from a user device of a first user who has received the first service; collecting first user information of the first user and first service information of the first service as metadata; providing the metadata to an NFT contract to issue the first NFT and creating a first ledger corresponding to the first NFT; and delivering the first NFT to the first user's virtual asset wallet, wherein the step of receiving the request to issue the first NFT comprises: creating the first user's virtual asset wallet; providing the first service to the first user; and providing a digital document related to the first service. A method for issuing an NFT linked to an enterprise service, comprising the step of receiving a request for the issuance of a first NFT for the digital document from the user device, wherein the request for the issuance of a first NFT for the digital document includes processing the cost of the first NFT issuance by the first user, and the step of creating a virtual asset wallet of the first user includes configuring a payment means storage unit of the first user, wherein the payment means storage unit is configured to store information related to digital goods or payment means for using the service, and the step of providing the first service to the first user includes providing reward points related to the first service to the payment means storage unit, wherein the cost of the first NFT issuance can be processed through the reward points. Claim 2 delete Claim 3 delete Claim 4 A method for issuing an NFT linked to an enterprise service according to claim 1, wherein a request for the issuance of a first NFT for the digital document includes issuance method information for issuing the first NFT, wherein if the issuance method information is an internal process method, the metadata is provided to the NFT contract, and if the issuance method information is an external process method, the metadata is provided to a blockchain network. Claim 5 A method for issuing an NFT associated with an enterprise service, further comprising: a step of providing transaction information for the first NFT to the NFT contract; and a step of recording transaction information of the first NFT processed by the NFT contract in the first ledger. Claim 6 A method for issuing an NFT linked to a corporate service, wherein, in claim 5, the transaction information of the first NFT is recorded in the first ledger in the form of a hash chain. Claim 7 In claim 1, the NFT contract is a method for issuing an NFT linked to a corporate service, wherein the code constituting the NFT contract is stored on a blockchain network. Claim 8 A method for issuing an NFT linked to an enterprise service, wherein, in claim 7, the method further comprises the step of verifying the authenticity of the NFT contract based on the code constituting the NFT contract stored in the blockchain network. Claim 9 A method for issuing an NFT linked to an enterprise service according to claim 1, further comprising: receiving a bridge request from a user device to move the first NFT to a blockchain network; collecting metadata of the first NFT in response to the bridge request; deleting the first NFT from the first user's virtual asset wallet; and minting a new NFT corresponding to the first NFT to the blockchain network based on the collected metadata of the first NFT. Claim 10 A service providing unit that provides a first service to a first user; a customer account management unit including a virtual asset wallet of the first user; The system includes an NFT management unit that receives a request for the issuance of a first NFT related to the first service from a user device of a first user who has received the first service, collects the first user's information and the information of the first service as metadata, provides the metadata to an NFT contract to issue the first NFT, creates a first ledger corresponding to the first NFT, and delivers the first NFT to the first user's virtual asset wallet. The NFT management unit receiving the request for the issuance of the first NFT includes creating the first user's virtual asset wallet, providing the first service to the first user, providing a digital document related to the first service, and receiving a request for the issuance of the first NFT regarding the digital document from the user device. The request for the issuance of the first NFT regarding the digital document includes the first user processing the cost of issuing the first NFT. The NFT management unit creating the first user's virtual asset wallet includes configuring the first user's payment method storage unit, and the payment method storage unit stores information related to digital goods or payment methods for using the service. A server configured to provide the first service to the first user, wherein providing the first service includes providing reward points related to the first service to the payment method storage unit, and wherein the first NFT issuance cost is capable of being processed through the reward points.

Images