WO2024117536A1

WO2024117536A1 - System and method for issuing nft

Info

Publication number: WO2024117536A1
Application number: PCT/KR2023/016014
Authority: WO
Inventors: 이준섭; 김현석; 김관래; 박기석; 최은정; 강수영
Original assignee: 주식회사 엔터프라이즈블록체인
Priority date: 2022-12-01
Filing date: 2023-10-17
Publication date: 2024-06-06
Also published as: KR102544012B1

Abstract

Disclosed are an apparatus and method for reissuing an NFT. An apparatus for issuing an NFT, according to an embodiment of the present disclosure, may comprise: a memory for storing at least one instruction; and at least one processor that is electrically connected to the memory and executes the at least one instruction. The at least one processor may receive, from an external device, an NFT issue request signal, set an NFT attribute value, and issue an NFT on the basis of the NFT attribute value. The NFT attribute value may include a higher node including a parent token ID, a lower node including a child token ID, and token data including base data and additional data.

Description

NFT issuance system and method

Embodiments disclosed in this document relate to an NFT issuing device and method, and more specifically, to an NFT issuing device that issues nth NFTs interconnected by a bidirectional linked list and a method of issuing nth NFTs using the same.

NFT (Non-Fungible Token) performs a similar function to cryptocurrency in that it is digital information recorded on a blockchain network. In particular, NFT can be distinguished from general cryptocurrency in that it is non-fungible. In other words, in the case of general cryptocurrencies such as Bitcoin, as long as they can be exchanged for the same amount, individual coin objects do not have characteristics that distinguish them. However, NFTs have scarcity and uniqueness for each individual object, and have unique characteristics that cannot be replaced.

According to these characteristics, NFTs are widely used to facilitate transactions in fields where the scarcity and uniqueness of each object are important, such as the art field.

However, the existing NFT algorithm has a problem in that it cannot protect the original author's copyright on the NFT if a person other than the original author earns unfair profits by creating and selling the NFT without permission.

In addition, the existing NFT algorithm has limitations in that even if you purchase an NFT, you cannot acquire ownership of the work itself, but only obtain proof of the original work, which limits the NFT purchaser's rights and the scope of NFT use.

One purpose of the present invention is to provide an NFT issuance device that can reproduce child NFTs in various scenarios based on the parent NFT and expand the scope of use of the issued NFT.

Another purpose of the present invention is to provide an NFT issuance device that can clarify rights between NFT buyers by storing contractual relationships between a plurality of NFTs derived from the original author's content on the blockchain.

Another object of the present invention is to provide a method of issuing NFT using the NFT issuing device.

However, the problem to be solved by the present invention is not limited to the above-mentioned problem, and may be expanded in various ways without departing from the spirit and scope of the present invention.

An NFT issuing device according to embodiments of the present disclosure may include a memory that stores at least one command and at least one processor that is electrically connected to the memory and executes the at least one command. The at least one processor may receive an NFT issuance request signal from an external device. The at least one processor may set NFT attribute values. The at least one processor may issue an NFT based on the NFT attribute value. The NFT attribute value may include an upper node including a parent token ID, a lower node including a child token ID, and token data including basic data and additional data.

In one embodiment, the at least one processor may receive the NFT issuance request signal including a child NFT creation request signal from the external device. The at least one processor may generate a child NFT that is linked to a previously issued parent NFT based on the child NFT creation request signal.

In one embodiment, the at least one processor may set the basic data of the child NFT based on the child NFT creation request signal. The at least one processor may set the additional data of the child NFT based on the child NFT creation request signal. The at least one processor may generate the child NFT with a smart contract based on the basic data and the additional data. The at least one processor may link the child NFT to the parent NFT.

In one embodiment, the at least one processor may receive an update request signal from an external device. The at least one processor may query owner information of the child NFT. The at least one processor may calculate the contribution to the child NFT based on the owner information. The at least one processor may update the NFT attribute value based on the contribution.

In one embodiment, the owner information includes at least one of a holding NFT history stored in the owner wallet of the child NFT, an off-chain activity record of the owner of the child NFT, and a sales history of a grandchild NFT recreated by the owner of the child NFT. can do.

In one embodiment, the basic data includes at least one of owner information, token ID, token URL, NFT type, NFT expansion amount, expiration date, resale status, NFT expansion order, target value, upper node information, and lower node information. can do.

In one embodiment, the type of NFT may include at least one of dividend NFT, funding NFT, and secondary work NFT.

In one embodiment, when the type of NFT is the dividend NFT, the additional data may include dividend rate, dividend date, and dividend contribution.

In one embodiment, when the type of NFT is the funding NFT, the additional data may include a revenue distribution rate, revenue distribution date, and funding contribution.

In one embodiment, when the type of NFT is the secondary work NFT, the additional data may include a royalty rate, settlement date, and secondary work contribution.

In one embodiment, the at least one processor may receive the first proceeds for the child NFT sales price from the purchaser of the child NFT and deliver the first proceeds to the previously issued parent NFT.

In one embodiment, the at least one processor receives second proceeds generated based on the child NFT from an external payment device, and provides the second proceeds to the parent NFT and the child NFT based on the NFT attribute value. It can be distributed.

The NFT issuance method according to embodiments of the present disclosure may include the operation of receiving an NFT issuance request signal from an external device, setting an NFT attribute value, and issuing an NFT based on the NFT attribute value. there is. The NFT attribute value may include an upper node including a parent token ID, a lower node including a child token ID, and token data including basic data and additional data.

In one embodiment, the operation of receiving the NFT issuance request signal may include receiving the NFT issuance request signal including a child NFT creation request signal from the external device. The operation of issuing the NFT may generate a child NFT that is linked to a previously issued parent NFT based on the child NFT creation request signal.

In one embodiment, the operation of issuing the NFT sets the basic data of the child NFT based on the child NFT creation request signal, and sets the additional data of the child NFT based on the child NFT creation request signal. And, the child NFT can be created with a smart contract based on the basic data and the additional data, and the child NFT can be linked to the parent NFT.

In one embodiment, the operation of setting the NFT attribute value includes receiving an update request signal from an external device, querying owner information of the child NFT, and calculating a contribution to the child NFT based on the owner information. , the NFT attribute value can be updated based on the contribution.

In one embodiment, the method of issuing the NFT may further include paying the proceeds generated from the NFT to the NFT. The operation of paying the proceeds generated from the NFT to the NFT may include receiving the first proceeds for the child NFT sales price from the purchaser of the child NFT and delivering the first proceeds to the previously issued parent NFT.

In one embodiment, the operation of paying the proceeds generated from the NFT to the NFT includes receiving second proceeds generated based on the child NFT from an external payment device, and based on the NFT attribute value, the parent NFT and the child The second proceeds can be distributed to NFT.

The NFT issuing device and NFT issuing method according to various embodiments disclosed in this document can issue parent NFT and child NFT that are interconnected in a bidirectional linked list to form a tree structure.

Therefore, the NFT issuance device and NFT issuance method can reproduce child NFTs in various scenarios based on the parent NFT and expand the scope of use of the issued NFT.

In addition, the NFT issuing device and NFT issuing method can clarify rights between NFT buyers by storing contractual relationships between multiple NFTs derived from the original author's content on the blockchain.

The effects that can be obtained from the exemplary embodiments of the present disclosure are not limited to the effects mentioned above, and other effects not mentioned are common knowledge in the technical field to which the exemplary embodiments of the present disclosure belong from the following description. It can be clearly derived and understood by those who have it. That is, unintended effects resulting from implementing the exemplary embodiments of the present disclosure may also be derived by those skilled in the art from the exemplary embodiments of the present disclosure.

Figure 1 shows the block configuration of an NFT issuing device according to an embodiment.

Figure 2 shows a detailed block configuration of an NFT issuing device according to an embodiment.

Figure 3 shows the NFT issuance operation flow of the NFT issuance device according to an embodiment.

Figure 4 shows the block configuration of the NFT generator according to one embodiment.

Figure 5 shows the operation flow of creating a child NFT of an NFT issuing device according to an embodiment.

Figure 6 shows the structure of an NFT according to one embodiment.

Figure 7 shows detailed data included in basic data according to an embodiment.

Figure 8 shows detailed data included in additional data according to one embodiment.

Figure 9 shows an NFT tree structure in which parent NFT and child NFT are connected in a bidirectional linked list according to one embodiment.

Figure 10 shows an NFT attribute value update operation flow according to the contribution of an NFT issuing device according to an embodiment.

Figure 11 shows an operation flow of paying the proceeds of an NFT issuing device to NFT according to an embodiment.

Figure 12 shows the delivery process of the proceeds when paying the proceeds to NFT according to one embodiment.

In relation to the description of the drawings, identical or similar reference numerals may be used for identical or similar components.

Hereinafter, with reference to the drawings, embodiments of the present disclosure will be described in detail so that those skilled in the art can easily practice them. However, the present disclosure may be implemented in many different forms and is not limited to the embodiments described herein. In relation to the description of the drawings, identical or similar reference numerals may be used for identical or similar components. Additionally, in the drawings and related descriptions, descriptions of well-known functions and configurations may be omitted for clarity and brevity.

The NFT issuing device 100 according to one embodiment may refer to a server device for managing information about the work performed by a plurality of client devices and providing input/output signals for NFT issuance to the client device.

In one embodiment, the client device may refer to an electronic device used by the seller of the NFT and the buyer of the NFT to request the issuance of the NFT. For example, a client device may mean a service user's portable terminal (e.g., smartphone, personal digital assistant (PDA), tablet PC, wearable device, etc.), laptop, PC, etc.

Referring to Figure 1, the NFT issuing device 100 according to one embodiment may include a memory 110, a processor 120, and a communication unit 130. The configuration shown in FIG. 1 illustrates a configuration related to the description of an embodiment according to the present disclosure, and in addition to the configuration shown, other configurations for performing the function of the NFT issuing device 100 may be added, and the configurations shown are It may be omitted.

The memory 110 according to one embodiment is a storage medium used by the NFT issuing device 100, and can store data such as at least one command or setting information corresponding to at least one program. The program may include an operating system (OS) program and various application programs.

In one embodiment, the memory 110 is a flash memory type, a hard disk type, a multimedia card micro type, or a card type of memory (e.g., SD or memory, etc.), random access memory (RAM), static random access memory (SRAM), read only memory (ROM), electrically erasable programmable ROM (EEPROM), programmable ROM (PROM), magnetic memory, magnetic disk, It may include at least one type of storage medium, such as an optical disk.

The communication unit 130 according to one embodiment includes an NFT issuing device 100 and an external electronic device (e.g., a client device (not shown), an IAM server (not shown), a billing server (not shown), and a cloud server (not shown). , IPFS (not shown)) can be used to perform direct (e.g. wired) communication. For example, the communication unit 130 may receive an NFT creation request signal transmitted from a client device. Additionally, for example, the communication unit 130 may transmit the unique NFT attribute value of the generated NFT to a cloud server (not shown) and IPFS (not shown).

In one embodiment, the communication unit 130 may include a wireless communication unit (eg, a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication unit. Among these communication units, the corresponding communication units communicate with external electronic devices (e.g., clients) through networks (e.g., legacy cellular networks, 5G networks, next-generation communication networks, the Internet, or telecommunication networks such as computer networks (e.g., LAN or WAN)). It can communicate with devices, IAM servers, billing servers, cloud servers, and IPFS).

In one embodiment, the communication unit 130 may support a 5G network after the 4G network and next-generation communication technology, for example, NR access technology (new radio access technology). NR access technology provides high-speed transmission of high-capacity data (enhanced mobile broadband (eMBB)), minimization of terminal power and access to multiple terminals (massive machine type communications (mMTC)), or ultra-reliable and low-latency (URLLC). -latency communications)) can be supported. For example, the communication unit 130 may support a high frequency band (eg, mmWave band) to achieve a high data transmission rate. The communication unit 130 uses various technologies to secure performance in the high frequency band, for example, beamforming, massive MIMO (multiple-input and multiple-output), and full-dimensional multiple input/output ( It can support technologies such as FD-MIMO (full dimensional MIMO), array antenna, analog beam-forming, or large scale antenna.

In one embodiment, the communication unit 130 includes an NFT issuing device 100, an external electronic device (e.g., a client device (not shown), an IAM server (not shown), a billing server (not shown), and a cloud server (not shown). , IPFS (not shown)) or a variety of requirements specified in network systems can be supported.

The processor 120 according to one embodiment, for example, executes software (e.g., a program) to execute at least one other component (e.g., hardware or software configuration) of the NFT issuing device 100 connected to the processor 120. elements) can be controlled and various data processing or operations can be performed.

In one embodiment, the processor 120 stores commands or data received from another component (e.g., communication unit 130) in volatile memory, as at least part of data processing or calculation, and stores the commands or data stored in the volatile memory. can be processed, and the resulting data can be stored in non-volatile memory.

In one embodiment, the processor 120 may be a main processor (e.g., a central processing unit or an application processor) or an auxiliary processor that can operate independently or together (e.g., a graphics processing unit, a neural processing unit (NPU), or a communication processor).

As shown in Figure 1, the NFT issuing device 100 according to embodiments of the present disclosure can operate in conjunction with a blockchain network. A blockchain network may be a decentralized network with multiple nodes, including a specific node.

The NFT issuing device 100 according to embodiments of the present disclosure may be configured to support a user accessing a specific node of a blockchain network. For example, the NFT issuing device 100 may serve as an intermediary for connection to the node by transmitting a front-end code to the user. For another example, the NFT issuing device 100 may serve to directly connect a user and a specific node.

Meanwhile, since different implementations of the NFT issuing device 100 of the present disclosure can be appropriately selected by a person skilled in the art depending on the situation, it is not considered to affect the scope of rights of the present invention. For example, hereinafter, for convenience of explanation, the NFT issuing device 100 is described as managing both the issuance of the n-th NFT and the payment of profits for the NFT. Revenue payment may be performed by different servers.

In one embodiment, the processor 120 may issue at least one NFT that is connected to other NFTs in a bidirectional linked list to form a tree structure. For example, the processor 120 may receive an NFT issuance request signal from an external device. For example, the processor 120 may set the NFT attribute value based on the NFT issuance request signal. For example, the processor 120 may issue an NFT based on the NFT attribute value.

The processor 120 according to one embodiment may perform the operation of the NFT issuing device 100 described through the drawings below.

Figure 2 shows a detailed block configuration of an NFT issuing device according to an embodiment, and Figure 3 shows an NFT issuing operation flow of an NFT issuing device according to an embodiment.

Referring to Figures 2 and 3, the NFT issuing device 200 according to the present disclosure includes an API gateway 210 (or API Gateway), an NFT generation unit 220 (or NFT Generator), and a payment management unit 230 (or Payment Manager) may be included. The API gateway 210, NFT creation unit 220, and payment management unit 230 may be operated by the processor 120.

API gateway 210 may provide at least one API for NFT issuance. For example, the API gateway 210 may provide an API for receiving an NFT issuance request signal. For example, the API gateway 210 may provide an API for querying NFT contract terms. For example, the API gateway 210 may provide an API to query owner information of an NFT. For example, the API gateway 210 may provide input/output signals for payment of profits for the NFT.

The NFT generator 220 may set the NFT attribute value based on the NFT creation request signal. For example, the NFT generator 220 may set token data including basic data and additional data. The NFT generator 220 may generate an NFT based on token data. The NFT generator 220 may link the generated NFT to at least one other NFT.

The payment management unit 230 may pay profits derived from the issued NFT to the NFT. For example, the payment management unit 230 may receive proceeds from NFT sales and deliver the proceeds to the NFT. For example, the payment management unit 230 may receive proceeds generated based on a plurality of NFTs and distribute the proceeds to the plurality of NFTs based on a smart contract.

According to one example, in operation 310, the NFT issuing device 200 may receive an NFT issuance request signal. For example, the API gateway 210 may provide an API for receiving an NFT issuance request signal from an external device. The external device may be an electronic device owned by at least one of the original content creator, the NFT seller, and the NFT buyer.

According to one example, in operation 320, the NFT issuing device 200 may set the NFT attribute value. The NFT attribute value may include an upper node including a parent token ID, a lower node including a child token ID, and token data including basic data and additional data. For example, the NFT generator 220 may be a smart contract that sets the NFT attribute value based on contract conditions.

According to one example, in operation 330, the NFT issuing device 200 may issue an NFT. The NFT generator 220 may generate an NFT with a smart contract based on the NFT attribute value. The NFT generator 220 may link the generated NFT to at least one other NFT. The NFT generator 220 may update the NFT attribute value based on the contribution. For example, the NFT generator 220 may calculate a contribution based on owner information and update additional data based on the contribution.

The NFT issuing device 200 of the present disclosure may receive the NFT issuance request signal including a child NFT creation request signal from the external device. The NFT issuing device 200 may generate a child NFT that is linked to a previously issued parent NFT based on the child NFT creation request signal. For example, the NFT issuing device 200 may issue a parent NFT and a child NFT that are interconnected in a doubly linked list to form a tree structure.

Figure 4 shows the block configuration of the NFT generator according to one embodiment. For example, the NFT generator 400 of FIG. 4 may have the same configuration as the NFT generator 220 of FIG. 2.

Referring to Figure 4, the NFT generation unit 400 includes a contract management unit 410 (or Contract Handler), a token generation unit 420 (or Token Generator), an update management unit 430 (or Update Handler), and a contribution management unit. (440) (or Contribution Handler) may be included. For example, the contract management unit 410, token generation unit 420, update management unit 430, and contribution management unit 440 may be operated by the processor 120.

According to one example, the NFT generator 400 may set NFT attribute values for generating an NFT. Additionally, the NFT generator 400 can update the attribute values of the NFT. The NFT generator 400 may generate an NFT based on the NFT attribute value. For example, the NFT generator 400 may generate a child NFT that is linked to a previously issued parent NFT based on a child NFT creation request signal.

Specifically, the contract management unit 410 can check the contract terms of the NFT. The NFT attribute value may be determined according to the contract conditions. For example, the contract management unit 410 can query the contract terms of the parent NFT and the contract terms of the child NFT. The contract terms of a child NFT may include the type of NFT. The contract management unit 410 can set NFT attribute values to reflect the contract conditions. The contract management unit 410 can check whether the contract conditions have changed. If the contract conditions change, the NFT attribute value may be updated.

The token generator 420 may generate an NFT based on the NFT attribute value. For example, the token generator 420 may generate a child NFT derived from a previously issued parent NFT. The token generator 420 may interconnect the parent NFT and the created child NFT through a bidirectional linked list.

The update management unit 430 may receive an update request signal from an external device. The update management unit 430 may update the NFT attribute value based on contribution. For example, the update management unit 430 may transmit a contribution calculation request signal to the contribution management unit 440 and receive the contribution from the contribution management unit 440 .

The contribution management unit 440 can query the owner information of the NFT. For example, the contribution management unit 440 can query the owner information of the parent NFT and the owner information of the child NFT. The contribution management unit 440 may calculate the contribution to the NFT based on owner information. The contribution management unit 440 may transmit the calculated contribution to the update management unit 430.

Figure 5 shows the operation flow of creating a child NFT of an NFT issuing device according to an embodiment, Figure 6 shows the structure of an NFT according to an embodiment, and Figure 7 shows details included in basic data according to an embodiment. Data is shown, Figure 8 shows detailed data included in the additional data according to an embodiment, and Figure 9 shows an NFT tree structure in which a parent NFT and a child NFT are connected in a bidirectional linked list according to an embodiment.

Referring to FIGS. 5 to 9, the NFT issuing device 200 may generate a child NFT that is linked to a previously issued parent NFT based on an NFT creation request signal.

According to one example, in operation 510, the NFT issuing device 200 may receive a child NFT creation request signal from an external device. The external device may be an electronic device owned by at least one of the original content creator, the child NFT seller, and the child NFT buyer.

As shown in Figure 6, the NFT issuing device 200 can issue an NFT based on the NFT attribute value. In other words, NFT may have an NFT structure that includes NFT attribute values. For example, the NFT structure may include a parent node (Prev) containing the parent token ID, a child node (next) containing the child token ID, and token data (data) containing NFT information based on contract conditions. there is. Token data may include basic data and additional data.

According to one example, in operation 520, the NFT issuing device 200 may set basic data of the child NFT based on the child NFT creation request signal. For example, the NFT issuing device 200 may set basic data (Basic params) among the NFT attribute values to reflect contract conditions.

As shown in Figure 7, the basic data (Basic params) include owner information (address), token ID (tokenId), token URL (tokenUrl), NFT type (Type), NFT expansion quantity (quantity), and validity period (period). , whether to resell (Resale), NFT expansion degree (Child_depth), target value (Goal_price), upper node information (prev), and lower node information (next[]). It will be understood by those skilled in the art that the basic data is not limited to a specific data type.

According to one example, in operation 530, the NFT issuing device 200 may set additional data of the child NFT based on the child NFT creation request signal. For example, the NFT issuing device 200 may set additional data (Additional params) based on the NFT type (Type) included in the basic data (Basic params).

As shown in Figure 8, the NFT type may include at least one of Dividend NFT, Crowdfunding NFT, and Adaptation NFT.

For example, if the NFT type is the dividend NFT, the additional data (Additional params) may include at least one of Dividend rate, Dividend Payday, and Dividend contribution. .

For example, if the NFT type is the funding NFT, the additional data (Additional params) may include at least one of Income rate, Income Payday, and Funding contribution. You can.

For example, if the type of NFT is the secondary work NFT, the additional data (Additional params) is at least one of a royalty rate, settlement day, and secondary work contribution (Adaptation contribution). may include.

According to one example, in operation 540, the NFT issuing device 200 may generate a child NFT with a smart contract based on basic data and additional data. For example, the NFT issuing device 200 may generate a child NFT corresponding to at least one of a dividend NFT, a funding NFT, and a secondary work NFT based on basic data and additional data.

According to one example, in operation 550, the NFT issuing device 200 may link the child NFT to the parent NFT. For example, the parent node (Prev) of at least one child NFT may be linked to the parent NFT. For example, a child node (Next) of a parent NFT may be linked to at least one child NFT.

According to one example, at least one child NFT may be linked with a previously issued parent NFT. For example, parent NFTs and child NFTs can be interconnected in a doubly linked list to form a tree structure.

As shown in Figure 9, the root NFT (Root Token) may be the first NFT created. For example, a root NFT may be an NFT created by the original author (e.g., creator) to pay dividends. For example, a root NFT may be an NFT created by the original author for crowdfunding. For example, a root NFT may be an NFT created by the original author to sell the rights to a secondary work. The root NFT may be the parent NFT of at least one child NFT. For example, a child node (Next) of the root NFT (eg, first NFT) may be linked to at least one child NFT (eg, second to fifth NFTs).

Buyers who purchase child NFTs or fans of the original author can acquire child NFTs for the root NFT. For example, a buyer or fan can own child NFTs for the root NFT in an NFT wallet. That is, the buyer or fan can become the owner of a child NFT (eg, the second to fifth NFT). A child NFT may be the parent NFT of at least one other child NFT. For example, the lower node (Next) of the child NFT (eg, second to fifth NFT) may be linked to at least one child NFT (eg, sixth to ninth NFT).

It can be determined based on the NFT type (Type), NFT expansion quantity (quantity), and NFT expansion degree (Child_depth) included in the basic data (Basic params) of the tree structure formed by parent NFT and child NFT. For example, NFT expansion quantity may mean the maximum number of child NFTs that can be created. For example, NFT expansion depth (Child_depth) may mean the depth of a child NFT that can be created.

Referring to FIG. 9, the second NFT to the ninth NFT may each be a child NFT of the first NFT. For example, the NFT expansion quantity of the first NFT may be 8. For example, the NFT expansion depth (Child_depth) of the first NFT may be 2.

Additionally, the 6th NFT and 7th NFT may each be child NFTs of the 3rd NFT. For example, the NFT expansion quantity of the third NFT may be 2. For example, the NFT expansion depth (Child_depth) of the third NFT may be 1. Likewise, the 8th NFT and 9th NFT may each be child NFTs of the 5th NFT. For example, the NFT expansion quantity of the fifth NFT may be 2. For example, the NFT expansion depth (Child_depth) of the fifth NFT may be 1.

The parent NFT and child NFT form a tree structure interconnected by a doubly linked list, so when an event occurs according to the contract conditions, the smart contract is interconnected by a doubly linked list. It can be implemented by traversing the tree structure.

According to one example, the NFT issuing device 200 may set contract dependency (Dependency) when issuing a child NFT. Contract dependency may be data that quantifies the degree to which the contract terms of a child NFT are dependent on the contract terms of the parent NFT. For example, if contract dependence is 100%, if a change occurs in the contract terms of the parent NFT, the change may be 100% applied to the contract terms of the child NFT.

Specifically, if a change occurs in the contract terms of the first NFT, the changed contract terms are transferred to the second to fifth NFTs, and the contract terms of the second to fifth NFTs may be changed. For example, in the case of a dividend NFT, if the dividend rate (dividend rate) of the first NFT is changed, the changed dividend date is transmitted to the second to fifth NFTs, and the dividend date of the second to fifth NFTs may be changed. You can. For example, in the case of a funding NFT, the profit distribution rate of the first NFT and the changed profit distribution rate are delivered to the 2nd to 5th NFTs, and the profits are distributed to the 2nd to 5th NFTs according to the changed profit distribution rate. can be distributed.

Referring to Figure 10, the NFT issuing device 200 of the present disclosure can calculate the contribution and update the NFT attribute value based on the contribution.

According to one example, in operation 1010, the NFT issuing device 200 may receive an update request signal from an external device. For example, the update request signal may be an update request signal due to a change in contract conditions. For example, the update request signal may be an update request signal based on the sale of a child NFT.

According to one example, in operation 1020, the NFT issuing device 200 may query owner information of the child NFT. For example, the NFT issuing device 200 may receive an update request signal according to a change in contract conditions and inquire whether the owner of the child NFT has changed. For example, the NFT issuing device 200 may receive an update request signal according to the sale of a child NFT and query owner information of the buyer who purchased the child NFT.

The owner information may include at least one of a holding NFT history stored in the owner's wallet of the child NFT, an off-chain activity record of the owner of the child NFT, and a sales history of a grandchild NFT recreated by the owner of the child NFT.

According to one example, in operation 1030, the NFT issuing device 200 may calculate the contribution to the child NFT based on the owner information. Contribution may be data that quantifies the extent to which a child NFT owner has contributed to content according to the contract terms and NFT type of the parent NFT. For example, a factor that increases contribution may be at least one of the child NFT owner's NFT purchase volume, the child NFT owner's number of advertisements, and the child NFT owner's resale rate.

In the case of a dividend NFT, the NFT issuing device 200 can check the details of the NFT stored in the owner's wallet of the child NFT. The NFT issuing device 200 can calculate the dividend contribution based on the child NFT owner's child NFT purchase amount. For example, the more child NFTs for the parent NFT held in the owner's wallet of the child NFT, the dividend contribution to the dividend NFT of the owner of the child NFT may increase.

In the case of a funding NFT, the NFT issuing device 200 can check the off-chain activity record of the owner of the child NFT. The NFT issuing device 200 can calculate the funding contribution based on the number of advertisements of the child NFT owner on the off-chain. For example, the greater the number of times the owner of a child NFT writes promotional posts about funding, the number of answers to funding-related questions, and the number of shares on SNS, the more the owner of the child NFT's funding contribution to the funding NFT may increase.

In the case of a secondary work NFT, the NFT issuing device 200 can check the sales history of the grandchild NFT recreated by the owner of the child NFT. The NFT issuing device 200 may calculate secondary authoring contribution based on the sales rate of a grandchild NFT (eg, a child NFT of the child NFT) created by the owner of the child NFT. For example, the higher the sales rate of a grandchild NFT for content created by the owner of a child NFT through secondary work, the owner of the child NFT's secondary work contribution to the secondary work NFT may increase.

According to one example, in operation 1040, the NFT issuing device 200 may update the NFT attribute value based on the contribution. For example, the NFT issuing device 200 may update the NFT attribute value with contract conditions that are more advantageous to the owner of the child NFT as the contribution level increases.

For example, in the case of a dividend NFT, the NFT issuing device 200 can increase the dividend rate of the child NFT as the dividend contribution increases and change the dividend date to be advantageous to the owner of the child NFT. For example, in the case of a funding NFT, the NFT issuing device 200 can increase the profit distribution rate of the child NFT as the funding contribution increases and change the profit distribution date to be advantageous to the owner of the child NFT. For example, in the case of a secondary work NFT, the NFT issuing device 200 may lower the royalty rate for the parent NFT as the contribution to the secondary work increases and change the settlement date to favor the owner of the child NFT.

Figure 11 shows an operation flow of paying the proceeds of an NFT issuing device to NFT according to an embodiment, and Figure 12 shows the delivery process of the proceeds when paying the proceeds to NFT according to an embodiment.

Referring to Figures 11 and 12, the NFT issuing device 200 may pay revenue derived from the issued NFT to the NFT. For example, the NFT issuing device 200 may receive proceeds from the sale of a child's NFT and transfer the proceeds to the parent NFT. For example, the NFT issuing device 200 may receive profits generated based on a child NFT and pay the profits to the parent NFT and child NFT.

According to one example, in operation 1110, the NFT issuing device 200 may receive the first proceeds for the child NFT sales price from the purchaser of the child NFT. For example, when a child NFT is sold, the NFT issuing device 200 may receive the first proceeds for the child NFT sale price from the purchaser who purchased the child NFT and store the first proceeds.

According to one example, in operation 1120, the NFT issuing device 200 may deliver the first proceeds to the previously issued parent NFT. For example, a parent NFT may receive the first proceeds for the sale of a child NFT. In other words, the parent NFT can generate a child NFT and generate profit (e.g., first profit) by selling the child NFT.

According to one example, in operation 1130, the NFT issuing device 200 may receive second profits generated based on the child NFT from an external payment device. For example, the NFT issuing device 200 may receive at least one of dividends, funding proceeds, and secondary work sales proceeds generated based on the child NFT from an external payment device.

According to one example, in operation 1140, the NFT issuing device 200 may distribute the second proceeds to the parent NFT and the child NFT based on the NFT attribute value. For example, in the case of a dividend NFT, the NFT issuing device 200 may distribute the dividend to the parent NFT and the child NFT based on the dividend rate. For example, in the case of a funding NFT, the NFT issuing device 200 may distribute the funding proceeds to the parent NFT and the child NFT based on a profit distribution ratio. For example, in the case of a secondary work NFT, the NFT issuing device 200 may distribute the proceeds from the sale of the secondary work to the parent NFT and the child NFT based on a royalty rate.

In this way, the NFT issuing device 200 of the present disclosure can reproduce child NFTs in various scenarios based on the parent NFT and expand the scope of use of the issued child NFT.

In addition, the NFT issuing device 200 can clarify the rights between NFT buyers by storing the contractual relationship between a plurality of NFTs derived from the original author's content in a tree structure on the blockchain.

Electronic devices according to various embodiments disclosed in this document may be of various types. Electronic devices may include, for example, display devices, portable communication devices (e.g., smartphones), computer devices, portable multimedia devices, portable medical devices, cameras, wearable devices, or home appliances. Electronic devices according to embodiments of this document are not limited to the above-described devices.

The various embodiments of this document and the terms used herein are not intended to limit the technical features described in this document to specific embodiments, but should be understood to include various changes, equivalents, or replacements of the embodiments. For example, a component expressed in the singular should be understood as a concept that includes plural components unless the context clearly indicates only the singular. It should be understood that the term 'and/or' used in this document encompasses any and all possible combinations of one or more of the listed items. Terms such as 'include', 'have', 'consist', etc. used in this disclosure are only intended to designate the presence of features, components, parts, or combinations thereof described in this disclosure, and the use of such terms It is not intended to exclude the presence or addition of one or more other features, components, parts, or combinations thereof. As used herein, “A or B”, “at least one of A and B”, “at least one of A or B”, “A, B or C”, “at least one of A, B and C”, and “A Each of phrases such as “at least one of , B, or C” may include any one of the items listed together in the corresponding phrase, or any possible combination thereof. Terms such as "first", "second", or "first" or "second" may be used simply to distinguish one element from another, and may be used to distinguish such elements in other respects, such as importance or order) is not limited.

The term “unit” or “module” used in various embodiments of this document may include a unit implemented with hardware, software, or firmware, for example, logic, logic block, component, or circuit. Can be used interchangeably with the same term. The “~part” or “~module” may be an integral part or a minimum unit of the part or a part thereof that performs one or more functions. For example, according to one embodiment, “~unit” or “~module” may be implemented in the form of an application-specific integrated circuit (ASIC).

The term “when” used in various embodiments of this document means “when” or “when” or “in response to determining” or “in response to detecting,” depending on the context. It can be interpreted as doing so. Similarly, “when it is determined that” or “when it is detected” means “when determining” or “in response to determining,” or “when detecting” or “in response to detecting,” depending on the context. It can be interpreted as doing so.

A program executed by an electronic device described in this document may be implemented with hardware components, software components, and/or a combination of hardware components and software components. A program can be executed by any system that can execute computer-readable instructions.

Software may include a computer program, code, instructions, or a combination of one or more of these, which may configure a processing unit to operate as desired, or may be processed independently or collectively. You can command the device. Software may be implemented as a computer program including instructions stored on computer-readable storage media. Computer-readable storage media include, for example, magnetic storage media (e.g., ROM (Read-Only Memory), RAM (Random-Access Memory), floppy disk, hard disk, etc.) and optical read media (e.g., CD-ROM). (CD-ROM), DVD (Digital Versatile Disc), etc. The computer-readable storage medium is distributed across networked computer systems, so that computer-readable code can be stored and executed in a distributed manner. Computer programs may be distributed (e.g., downloaded or uploaded) online, through an application store (e.g., Play Store™) or directly between two user devices (e.g., smart phones). In the case of online distribution, at least a portion of the computer program product may be at least temporarily stored or temporarily created in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store server, or a relay server.

According to various embodiments, each component (e.g., module or program) of the above-described components may include a single or plural entity, and some of the plurality of entities may be separately placed in other components. there is. According to various embodiments, one or more of the components or operations described above may be omitted, or one or more other components or operations may be added. Alternatively or additionally, multiple components (eg, modules or programs) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each component of the plurality of components identically or similarly to those performed by the corresponding component of the plurality of components prior to the integration. . According to various embodiments, operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, or omitted. Alternatively, one or more other operations may be added.

Claims

In the NFT issuing device,

a memory storing at least one instruction; and

At least one processor electrically connected to the memory and executing the at least one instruction,

The at least one processor,

Receive an NFT issuance request signal from an external device,

Set NFT property values,

Issue an NFT based on the NFT attribute value,

The NFT attribute value is,

Parent node containing parent token ID;

Child nodes containing child token IDs; and

Containing token data, including basic data and additional data,

Device.
According to paragraph 1,

The at least one processor,

Receiving the NFT issuance request signal including a child NFT creation request signal from the external device,

Based on the child NFT creation request signal, generating a child NFT that is linked to the previously issued parent NFT,

Device.
According to paragraph 2,

The at least one processor,

Setting the basic data of the child NFT based on the child NFT creation request signal,

Setting the additional data of the child NFT based on the child NFT creation request signal,

Generate the child NFT with a smart contract based on the basic data and the additional data,

Linking the child NFT to the parent NFT,

Device.
According to paragraph 3,

The at least one processor,

Receives an update request signal from an external device,

Check the owner information of the child NFT,

Calculate the contribution to the child NFT based on the owner information,

Updating the NFT attribute value based on the contribution,

Device.
According to paragraph 4,

The above owner information is,

Containing at least one of a holding NFT history stored in the owner wallet of the child NFT, an off-chain activity record of the owner of the child NFT, and a sales history of a grandchild NFT recreated by the owner of the child NFT,

Device.
According to paragraph 1,

The basic data is,

Containing at least one of owner information, token ID, token URL, NFT type, NFT expansion amount, expiration date, resale status, NFT expansion order, target value, upper node information, and lower node information,

Device.
According to clause 6,

The types of NFTs are,

Containing at least one of dividend NFT, funding NFT, and secondary work NFT,

Device.
In clause 7,

If the NFT type is the dividend NFT, the additional data is,

Containing at least one of dividend rate, dividend date, and dividend contribution,

Device.
In clause 7,

If the NFT type is the funding NFT, the additional data is,

Containing at least one of the profit sharing rate, profit distribution date, and funding contribution,

Device.
In clause 7,

If the NFT type is the secondary work NFT, the additional data is,

Containing at least one of the following: royalty rate, settlement date, and derivative work contribution,

Device.
According to paragraph 1,

The at least one processor,

Receive the first proceeds for the child NFT sales proceeds from the purchaser of the child NFT,

Delivering the first proceeds to the previously issued parent NFT,

Device.
According to clause 11,

The at least one processor,

Receive the second profit generated based on the child NFT from an external payment device,

Distributing the second proceeds to the parent NFT and the child NFT based on the NFT attribute value,

Device.
In the NFT issuance method,

An operation of receiving an NFT issuance request signal from an external device;

An operation to set NFT property values; and

Including the operation of issuing an NFT based on the NFT attribute value,

The NFT attribute value is,

Parent node containing parent token ID;

Child nodes containing child token IDs; and

Containing token data, including basic data and additional data,

method.
According to clause 13,

The operation of receiving the NFT issuance request signal is,

Receiving the NFT issuance request signal including a child NFT creation request signal from the external device,

The operation of issuing the NFT is,

Based on the child NFT creation request signal, generating a child NFT that is linked to the previously issued parent NFT,

method.
According to clause 14,

The operation of issuing the NFT is,

Setting the basic data of the child NFT based on the child NFT creation request signal,

Setting the additional data of the child NFT based on the child NFT creation request signal,

Generate the child NFT with a smart contract based on the basic data and the additional data,

Linking the child NFT to the parent NFT,

method.