KR20230132344A - Apparatus and method of managing non-fungible tokens based on blockchain - Google Patents

Abstract

An electronic device according to an aspect of the present disclosure includes a communication interface for communicating with at least one node of a blockchain network and an external device, one or more processors, and one or more memories that store at least one command executed by the one or more processors. The one or more processors may be configured to receive a registration request for a specific token on a specific date from the external device, and register the specific token to correspond to the specific date based on the registration request. The registration request may include date indication information indicating the specific date and token identification information identifying the specific token.

Description

Apparatus and method for managing non-fungible tokens based on blockchain {APPARATUS AND METHOD OF MANAGING NON-FUNGIBLE TOKENS BASED ON BLOCKCHAIN}

The content disclosed in this specification relates to technology for managing non-fungible tokens based on blockchain.

Recently, with the emergence of various media outlets, various types of celebrities or famous people such as idols, actors, influencers, YouTubers, etc. are appearing. In the entertainment business related to celebrities or celebrities, there is an increasing number of cases where fans who like a specific celebrity record the schedule of their favorite celebrity or promote the celebrity to others.

Additionally, recently, there has been an increase in the number of cases where fans promote their favorite celebrities to others by directly posting the celebrity's photos in areas that are exposed to an unspecified number of people (for example, advertising panels at subway platforms or bus stops, or outdoor billboards). I'm doing it.

The content disclosed in this specification provides a technology for preventing the problem of an area for a specific date on a calendar screen displayed on a user terminal being excessively filled with a specific object corresponding to a token.

The content disclosed in this specification provides a technology for preventing a user who has purchased a token that can be registered to correspond to one specific date from registering tokens on multiple specific dates.

The content disclosed in this specification provides technology for allowing users to easily determine history information about a specific object.

The content disclosed in this specification provides a technology that allows a user who has registered a token to correspond to a specific date to arbitrarily change the registered token to another token.

An electronic device according to an aspect of the present disclosure includes a communication interface for communicating with at least one node of a blockchain network and an external device, one or more processors, and one or more memories that store at least one command executed by the one or more processors. The one or more processors may be configured to receive a registration request for a specific token on a specific date from the external device, and register the specific token to correspond to the specific date based on the registration request. The registration request may include date indication information indicating the specific date and token identification information identifying the specific token.

In one embodiment, the one or more processors may be configured to transmit the date indication information and the token identification information to at least one node of the blockchain network to register the specific token to correspond to the specific date. You can.

In one embodiment, the specific token includes a first date attribute group comprising at least one date attribute, and the one or more processors, from at least one node of the blockchain network, select the first date attribute group. Obtaining, determining whether the specific date indicated by the date indication information matches one of the at least one date attribute, and based on the determination that it matches, storing the date indication information and the token identification information in the blockchain It may be configured to transmit to at least one node of the network.

In one embodiment, the one or more memories additionally store a first date attribute group including at least one date attribute corresponding to the specific token, and the one or more processors store the first date attribute group from the one or more memories. 1 Obtain a date attribute group, determine whether the specific date indicated by the date indication information matches one of the at least one date attribute, and according to the determination of the match, the date indication information and the token identification information; It may be configured to transmit to at least one node of the blockchain network.

In one embodiment, the one or more processors receive a replacement request from the external device to replace the specific token registered to correspond to the specific date with another token, and based on the replacement request, exchange the specific token and deregister the token and register the other token to correspond to the specific date, and the replacement request may include information about the specific token and information about the other token.

In one embodiment, the one or more processors are configured to de-register the specific token depending on whether a lock-up release condition for the specific token is satisfied, and the lock-up release condition is: It may be a condition that is satisfied only after a certain period of time has elapsed from the start of registration.

In one embodiment, the specific token may be a non-fungible token.

In one embodiment, the specific token may include information for accessing a specific image.

In one embodiment, the one or more processors receive a transmission request for posting information for the specific date from the external device, generate token list information regarding tokens registered to correspond to the specific date, and It is configured to generate posting information based on token list information and transmit the posting information to the external device, and the posting information may include information about each of the tokens.

In one embodiment, the one or more processors receive, from at least one node of the blockchain network, information about at least one of the tokens registered to correspond to the specific date, and the at least one It may be configured to generate the token list information based on information about the token.

In one embodiment, the publishing information includes a publishing priority between the tokens, and the one or more processors determine the publishing priority based on a time of receipt of a registration request for each of the tokens, so as to correspond to the specific date. It can be configured to determine .

In one embodiment, the token list information includes token group information, the token group information indicates one or more token groups to which each of the tokens belongs, and the publishing information includes publishing priorities between the tokens. , the one or more processors may be configured to determine the publishing priority based on the token group information.

In one embodiment, the one or more processors may be configured to determine the publishing priority based on the number of tokens belonging to each of the one or more token groups.

In one embodiment, the first token includes a first date attribute group that includes at least one date attribute, and the one or more processors are configured to select a date attribute that is different from the at least one date attribute of the first date attribute group. and configured to generate a second date attribute group comprising, and transmit a request for creation of a second token to at least one node of the blockchain network, wherein the request for creation of the second token comprises: information about the first token; and the second date attribute group.

In one embodiment, the one or more processors receive information indicating a specific object from the external device, and specify one or more tokens associated with the specific object and registered to each correspond to one or more registration dates, Based on information about each of the specified one or more tokens, it may be configured to generate history information for the specific target and transmit the history information to the external device.

According to another aspect of the present disclosure, a method performed by an electronic device may be provided. The method is performed by an electronic device including one or more processors and one or more memories storing at least one instruction to be executed by the one or more processors, wherein the one or more processors receive information on a specific date from an external device. Receiving a request for registration of a specific token and, based on the registration request, registering the specific token to correspond to the specific date, wherein the registration request includes date indication information indicating the specific date and the It may contain token identification information that identifies a specific token.

In one embodiment, registering the specific token may further include transmitting the date indication information and the token identification information to at least one node of the blockchain network.

In one embodiment, the method includes receiving, by the one or more processors, a transmission request for posting information for the specific date from the external device, generating token list information regarding tokens registered to correspond to the specific date. The method further includes generating posting information based on the token list information and transmitting the posting information to the external device, wherein the posting information may include information about each of the tokens.

According to another aspect of the present disclosure, a method performed by an electronic device may be provided. The method is performed by an electronic device including one or more processors and one or more memories that store at least one instruction to be executed by the one or more processors, wherein the one or more processors send information to an external device for a specific date. Transmitting a registration request for a specific token and receiving approval information or rejection information for the registration request for the specific token from the external device that responds to the registration request, wherein the registration request is made on the specific date. It may include date indication information and token identification information identifying the specific token.

In one embodiment, the method includes the steps of transmitting, by the one or more processors, a transmission request for publication information for the specific date to the external device and receiving the publication information from the external device in response to the transmission request. It further includes, wherein the posting information is generated based on token list information about tokens registered to correspond to the specific date, and may include information about each of the tokens.

An electronic device according to another aspect of the present disclosure includes one or more processors and one or more memories that store at least one instruction to be executed by the one or more processors, and the one or more processors are associated with a specific object from the external device. Receive a registration request for a first token, and, based on the registration request, register the first token to be locked up for a specific period of time and, based on information about the first token, to be owned by the owner of the first token. and determine a second token and transmit information about the second token to the owner.

According to at least one embodiment disclosed in this specification, a user who has purchased a token that can be registered to correspond to one specific date can be prevented from registering tokens on multiple specific dates.

According to at least one embodiment disclosed in this specification, it is possible to prevent an area for a specific date on a calendar screen displayed on a user terminal from being excessively filled with a specific object corresponding to a token.

According to at least one embodiment disclosed in this specification, a user can easily determine history information about a specific object.

According to at least one embodiment disclosed in this specification, a user who has registered a token to correspond to a specific date can arbitrarily change the registered token to another token.

FIG. 1 is a diagram illustrating a system including a server, a user terminal, a blockchain network, and a communication network according to an embodiment of the content disclosed in this specification.
Figure 2 is a block diagram of a server according to an embodiment of the content disclosed herein.
Figure 3 is a block diagram of a user terminal according to an embodiment of the content disclosed in this specification.
Figure 4 is a conceptual diagram of a blockchain network according to an embodiment of the content disclosed in this specification.
Figure 5 is a flowchart of the operation of a server that processes a registration request for a specific token for a specific date received from a user terminal according to an embodiment of the content disclosed in this specification.
FIG. 6 is a flowchart illustrating a method in which a server processes a registration request for a specific token for a specific date received from a user terminal according to another embodiment of the content disclosed in this specification.
FIG. 7 is a flowchart of the operation of a server that processes a request for registration of a specific token for a specific person received from a user terminal according to another embodiment of the content disclosed in this specification.
Figure 8 is a flowchart of the operation of a server that processes a transmission request for posting information received from a user terminal according to an embodiment of the content disclosed in this specification.
FIG. 9A is a diagram illustrating a screen that can be displayed when posted information according to an embodiment of the disclosure disclosed in this specification is displayed through an output unit of a user terminal.
FIG. 9B is a diagram illustrating a screen that can be displayed when posted information according to another embodiment of the disclosure disclosed in this specification is displayed through an output unit of a user terminal.
FIG. 9C is a diagram illustrating a screen that can be displayed when posted information according to another embodiment of the content disclosed in this specification is displayed through an output unit of a user terminal.
FIG. 9D is a diagram illustrating an example of a screen that can be displayed when posted information according to another embodiment of the content disclosed in this specification is displayed through an output unit of a user terminal.
Figure 10 is a flowchart of the operation of a server that processes information indicating a specific target received from a user terminal according to an embodiment of the content disclosed in this specification.
Figure 11 is a flowchart of the operation of a server that processes a replacement request received from a user terminal according to an embodiment of the content disclosed in this specification.
FIG. 12 is a flowchart illustrating a method of processing a replacement request for a user terminal according to another embodiment of the content disclosed in this specification.

The various embodiments described in this document are illustrative for the purpose of clearly explaining the technical idea of the present disclosure, and are not intended to limit them to specific embodiments. The technical idea of the present disclosure includes various modifications, equivalents, and alternatives of each embodiment described in this document, and embodiments selectively combined from all or part of each embodiment. In addition, the scope of the technical idea of the present disclosure is not limited to the various embodiments or specific descriptions thereof presented below.

Unless otherwise defined, terms used in this document, including technical or scientific terms, may have meanings commonly understood by those skilled in the art to which this disclosure pertains.

Expressions such as "includes", "may include", "provided", "may be provided", "have", "may have", etc. used in this document refer to the target characteristics (e.g. For example, a function, operation or component, etc.) is present and does not exclude the presence of other additional features. In other words, such expressions should be understood as open-ended terms that imply the possibility of including other embodiments.

Singular expressions used in this document may include plural meanings, unless the context indicates otherwise, and this also applies to singular expressions described in the claims.

Expressions such as "first", "second", or "first", "second", etc. used in this document refer to multiple objects of the same type and distinguish one object from another object, unless the context indicates otherwise. It is used to do so, and does not limit the order or importance of the objects. For example, each user included in the plurality of users according to the present disclosure may be distinguished from each other by being expressed as “first user” and “second user.” Additionally, a plurality of tokens according to the present disclosure may be distinguished from each other by being expressed as “first token” and “second token”. Additionally, one or more date attribute groups according to the present disclosure may be distinguished from each other by being expressed as “first date attribute group” and “second date attribute group”.

As used herein, expressions such as “A, B, and C,” “A, B, or C,” “at least one of A, B, and C,” or “at least one of A, B, or C” refer to , can mean each listed item or all possible combinations of listed items. For example, “at least one of A or B” may refer to both (1) at least one A, (2) at least one B, (3) at least one A and at least one B.

The expression “unit” used in this document may refer to software or hardware components such as FPGA (Field-Programmable Gate Array) or ASIC (Application Specific Integrated Circuit). However, “wealth” is not limited to hardware and software. The “copy” may be configured to be stored on an addressable storage medium and may be configured to execute on one or more processors. In one embodiment, a “part” refers to components such as software components, object-oriented software components, class components, and task components, as well as processors, functions, properties, procedures, subroutines, and programs. Can contain segments of code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables.

As used in this document, the expression "based on" is used to describe one or more factors influencing the decision, act of judgment, or action described in the phrase or sentence containing the expression, and does not exclude additional factors affecting the decision, act or action of judgment.

As used in this document, the expression that a component (e.g., a first component) is “connected” or “connected” to another component (e.g., a second component) means that any of the above It may mean that a component is not only directly connected or connected to the other component, but is also connected or connected through another new component (for example, a third component).

As used in this document, the expression "configured to" means "set to," "having the ability to," "changed to," "made to," and "capable of," depending on the context. It can have meanings such as “possible.” The expression is not limited to the meaning of "specially designed in hardware," and for example, a processor configured to perform a specific operation refers to a general purpose processor capable of performing that specific operation by executing software. Alternatively, it may mean a special purpose computer structured through programming to perform the specific operation.

Hereinafter, various embodiments of the present disclosure will be described with reference to the attached drawings. In the accompanying drawings and descriptions of the drawings, identical or substantially equivalent components may be assigned the same reference numerals. Additionally, in the description of various embodiments below, duplicate descriptions of the same or corresponding components may be omitted, but this does not mean that the corresponding components are not included in the embodiments.

FIG. 1 is a diagram illustrating a system including a server 100, a user terminal 200, a blockchain network 300, and a communication network 400 according to an embodiment of the content disclosed in this specification. The server 100, the user terminal 200, and at least one node 310 included in the blockchain network 300 provide information to each other through the communication network 400 according to the non-fungible token management technology disclosed herein. You can receive it. In this specification, the calendar may be displayed on the server 100, the user terminal 200, or other electronic devices by software or applications running on the corresponding devices. A calendar may include information about at least one date.

Server 100 may be an electronic device of a service provider. The service provider may be the operator of a service that provides a calendar according to the non-fungible token management technology disclosed herein. The server 100 is an electronic device that transmits information or provides services to the user terminal 200 connected by wire or wirelessly, and may be, for example, an application server, proxy server, cloud server, etc.

The user terminal 200 may be a user terminal that uses the above-described calendar providing service. The user terminal 200 may be, for example, a smartphone, a tablet computer, a personal computer (PC), a mobile phone, a personal digital assistant (PDA), an audio player, or a wearable device. It can be at least one of:

When describing the configuration or operation of a device in the disclosure of this specification, the term "device" is a term to refer to the device that is the subject of description, and the term "external device" is a term used to refer to the device that is the subject of description. From this point of view, each can be used as a term to refer to a device that exists externally. For example, when the server 100 is described as a “device,” the user terminal 200 may be called an “external device” from the perspective of the server 100. Additionally, for example, when the user terminal 200 is described as a “device,” the server 100 may be called an “external device” from the perspective of the user terminal 200. That is, the server 100 and the user terminal 200 may each be referred to as “device” and “external device” or as “external device” and “device”, respectively, depending on the perspective of the operating entity.

The blockchain network 300 may include at least one node 310 that manages the blockchain. Each of at least one node included in the blockchain network 300 may be an independent electronic device capable of processing operations required to manage or operate the blockchain. At least some operations of the non-fungible token management technology disclosed in this specification may be performed by a smart contract recorded on a blockchain. To this end, the server 100 or the user terminal 200 can exchange information with at least one node included in the blockchain network 300.

The communication network 400 may include both a wired or wireless communication network. The communication network 400 may allow data to be exchanged between at least two of the server 100, the user terminal 200, or the blockchain network 300. The wired communication network may include, for example, a communication network based on USB (Universal Serial Bus), HDMI (High Definition Multimedia Interface), RS-232 (Recommended Standard-232), or POTS (Plain Old Telephone Service). . Wireless communication networks include, for example, enhanced Mobile Broadband (eMBB), Ultra Reliable Low-Latency Communications (URLLC), Massive Machine Type Communications (MMTC), Long-Term Evolution (LTE), LTE Advance (LTE-A), and NR ( New Radio), UMTS (Universal Mobile Telecommunications System), GSM (Global System for Mobile communications), CDMA (Code Division Multiple Access), WCDMA (Wideband CDMA), WiBro (Wireless Broadband), WiFi (Wireless Fidelity), Bluetooth ), NFC (Near Field Communication), GPS (Global Positioning System), or GNSS (Global Navigation Satellite System). The communication network 400 of this specification is not limited to the examples described above, and may include various types of communication networks that allow data to be exchanged between a plurality of subjects or devices without limitation.

Figure 2 is a block diagram of the server 100 according to an embodiment of the content disclosed herein. The server 100 may include one or more processors 110, a communication interface 120, or a memory 130 as components. In some embodiments, at least one of these components of server 100 may be omitted, or other components may be added to server 100. In some embodiments, additionally or alternatively, some components may be integrated and implemented, or may be implemented as a single or plural entity. At least some of the components inside or outside the server 100 are connected to each other through a bus, General Purpose Input/Output (GPIO), Serial Peripheral Interface (SPI), or Mobile Industry Processor Interface (MIPI), etc. to exchange data. Alternatively, signals can be given or received.

One or more processors 110 may be referred to as processor 110. The term processor 110 may refer to a set of one or more processors, unless the context clearly expresses otherwise. The processor 110 may control at least one component of the server 100 connected to the processor 110 by running software (eg, commands, programs, etc.). Additionally, the processor 110 may perform various operations such as calculation, processing, data generation or processing. Additionally, the processor 110 may load data, etc. from the memory 130 or store it in the memory 130 .

The communication interface 120 may perform wireless or wired communication between the server 100 and another device (eg, the user terminal 200 or another server). For example, the communication interface 120 may be used for wireless communication such as eMBB, URLLLC, MMTC, LTE, LTE-A, NR, UMTS, GSM, CDMA, WCDMA, WiBro, WiFi, Bluetooth, NFC, GPS or GNSS. can be performed. In addition, for example, the communication interface 120 may be wired according to a method such as USB (Universal Serial Bus), HDMI (High Definition Multimedia Interface), RS-232 (Recommended Standard-232), or POTS (Plain Old Telephone Service). Communication can be performed.

Memory 130 can store various data. Data stored in the memory 130 is data acquired, processed, or used by at least one component of the server 100, and may include software (eg, commands, programs, etc.). Memory 130 may include volatile or non-volatile memory. The term memory 130 may refer to a set of one or more memories, unless the context clearly expresses otherwise. As used herein, the expression “a set of instructions stored in the memory 130” or “a program stored in the memory 130” refers to an operating system, application, or application for controlling the resources of the server 100. It can be used to refer to middleware that provides various functions to an application so that it can utilize the resources of the server 100. In one embodiment, when the processor 110 performs a specific operation, the memory 130 may store instructions performed by the processor 110 and corresponding to the specific operation.

In one embodiment, the server 100 may transmit data according to an operation result of the processor 110, data received by the communication interface 120, or data stored in the memory 130 to an external device. An external device may be a device for displaying, displaying, or outputting received data.

Figure 3 is a block diagram of a user terminal 200 according to an embodiment of the content disclosed in this specification. The user terminal 200 may include one or more processors 210, a communication interface 220, or a memory 230 as components. Additionally, the user terminal 200 may further include at least one of an input unit 240 or an output unit 250.

The processor 210 may control at least one component of the user terminal 200 connected to the processor 110 by running software (eg, commands, programs, etc.). Additionally, the processor 210 may perform various operations such as calculation, processing, data generation or processing. Additionally, the processor 210 may load data, etc. from the memory 230 or store it in the memory 230 .

The communication interface 220 may perform wireless or wired communication between the user terminal 200 and another device (eg, the server 100 or another user terminal). For example, the communication interface 220 may be used for wireless communication such as eMBB, URLLLC, MMTC, LTE, LTE-A, NR, UMTS, GSM, CDMA, WCDMA, WiBro, WiFi, Bluetooth, NFC, GPS or GNSS. can be performed. Additionally, for example, the communication interface 220 may perform wired communication using USB, HDMI, RS-232, or POTS.

Memory 230 can store various data. Data stored in the memory 230 is data acquired, processed, or used by at least one component of the user terminal 200, and may include software (e.g., commands, programs, etc.) . Memory 230 may include volatile or non-volatile memory. The term memory 230 may refer to a set of one or more memories, unless the context clearly expresses otherwise. As used herein, the expression “a set of instructions stored in the memory 230” or “a program stored in the memory 230” refers to an operating system, an application, or an operating system for controlling the resources of the user terminal 200. It may be used to refer to middleware that provides various functions to an application so that the application can utilize the resources of the user terminal 200. In one embodiment, when the processor 210 performs a specific operation, the memory 230 may store instructions performed by the processor 210 and corresponding to the specific operation.

In one embodiment, the user terminal 200 may further include an input unit 240. The input unit 240 may be a component that transmits data received from the outside to at least one component included in the user terminal 200. For example, the input unit 240 may include a mouse, keyboard, or touch pad.

In one embodiment, the user terminal 200 may further include an output unit 250. The output unit 250 may display (output) information processed in the user terminal 200 or transmit (send) it to the outside. For example, the output unit 250 may visually display information processed in the user terminal 200. The output unit 250 may display User Interface (UI) information or Graphic User Interface (GUI) information. In this case, the output unit 250 includes a liquid crystal display (LCD), a thin film transistor-liquid crystal display (TFT-LCD), an organic light-emitting diode (OLED), It may include at least one of a flexible display, a 3D display, and an electronic ink display. Additionally, for example, the output unit 250 may audibly display information processed in the user terminal 200. The output unit 250 can display audio data in any audio file format (eg, MP3, FLAC, WAV, etc.) through an audio device. In this case, the output unit 250 may include at least one of a speaker, a headset, and headphones. Additionally, for example, the output unit 250 may transmit information processed in the user terminal 200 to an external output device. The output unit 250 may transmit or transmit information processed in the user terminal 200 to an external output device using the communication interface 220. The output unit 250 may transmit or transmit information processed in the user terminal 200 to an external output device using a separate output communication interface.

Figure 4 is a conceptual diagram of a blockchain network 300 according to an embodiment of the content disclosed in this specification. In the disclosure of this specification, block may refer to a specific data type. Additionally, in the disclosure of this specification, blockchain may refer to a data structure in which one or more blocks 331, 333, and 335 are connected in a chain form. One or more blocks 331, 333, and 335 included in the blockchain may be stored independently in one or more nodes included in the blockchain network 300, or may be distributed and stored across multiple nodes. Each of one or more blocks 331, 333, and 335 may include a block hash, a block header, or a block body. A block hash is unique information that can identify a block and, for example, may be a string expressed in 256 bits. Block headers include, for example, software or protocol version information, hash of the previous block according to the block connection order on the blockchain, Merkle root, time information indicating the time the block was created, and difficulty of calculation. It may contain at least one of Bits, which represents , and Nonce, which is a value needed in the mining operation of adding a new block to the blockchain. A block body may include at least one transaction. A transaction is a set of data with a specific data structure and can be a unit of information stored in a block body. Transactions may include information regarding the creation or transaction of tokens. For example, the transaction may be information that “the first node included in the blockchain network 300 transmits a virtual currency token to the second node.” For another example, the transaction may be information that “the first node included in the blockchain network 300 transmits an NFT (Non-Fungible Token) to the second node.”

A blockchain may be managed by a blockchain network 300 that includes at least one node. Each of at least one node included in the blockchain network 300 may be referred to as a “participant” of the blockchain network 300. At least one node included in the blockchain network 300 may operate in a hierarchical structure. The hierarchical structure includes, for example, a data layer that defines the structure of data handled by the blockchain network 300 and manages the data, verifies the validity of blocks, performs mining to generate blocks, and performs mining during the mining process. Includes at least one of the following: a consensus layer responsible for processing fees paid to parties, a common layer that implements or manages P2P network protocols, hash functions, digital signatures, encoding, and common storage, or an application layer where various applications are created or processed. can do.

At least one node included in the blockchain network 300 may share or store transactions recorded on the blockchain. In addition, at least one node included in the blockchain network 300 performs a verification operation on the transaction transmitted to the blockchain network 300 through the blockchain consensus algorithm, and when verification is completed, the verified transaction is block It can perform the function of recording in a block on the chain. The consensus algorithms performed by the blockchain network 300 include Proof of Work (PoW) algorithm, Proof of Stake (PoS) algorithm, Delegated Proof of Stage (DPoS) algorithm, Practical Byzantine Fault Tolerance (PBFT) algorithm, and Delegated Proof of Stage (DBFT) algorithm. It may include at least one of the Byzantine Fault Tolerance (RBFT) algorithm, Redundant Byzantine Fault Tolerance (RBFT) algorithm, Sieve algorithm, Tendermint algorithm, Paxos algorithm, Raft algorithm, Proof of Authority (PoA) algorithm, or Proof of Elapsed Time (PoET) algorithm. there is.

Each of at least one node included in the blockchain network 300 can store a smart contract. Through this, at least one node included in the blockchain network 300 can share the same smart contract. Additionally, a smart contract may be recorded in a block on a blockchain managed by the blockchain network 300.

A smart contract is, for example, a document or script written in a programming language such as Solidity, and is a program or application that runs on a virtual machine executed by at least one node included in the blockchain network 300. You can. Smart contracts can be written to execute specific actions when certain conditions are met. At this time, the specific condition may be, for example, a condition such as a specific type of token being input or a specific type of file being input. Additionally, the specific operation may be, for example, an operation such as transmitting a specific type of token to a random node of the blockchain network 300.

Smart contracts can be written to follow certain rules (or protocols). For example, a smart contract can be written including one or more functions corresponding to each ERC-20 or ERC-721 protocol. However, various types of smart contracts can be created by including other functions not included in the illustrated protocol (e.g., one or more functions corresponding to ERC-1155) in the smart contract.

In the disclosure of this specification, a token is a token that can be used on a blockchain managed by the blockchain network 300, and may be a virtual currency token (or fungible token) or a non-fungible token (NFT). “Non-Fungible Token” may refer to a virtual token created according to a smart contract written with reference to certain protocols (e.g., ERC-721 or ERC-1155, etc.). This non-fungible token can be recorded on the blockchain, a decentralized storage, so its integrity can be maintained, and by creating this non-fungible token to contain a specific type of data, the existence of a specific type of data can be guaranteed. Hereinafter, an object simply referred to as a “token” in the disclosure of this specification may be an NFT, unless otherwise expressed in context.

A token can be a set of data containing a specific type of data. In a specific embodiment, the token includes information for accessing a digital file (e.g., a specific image) associated with the token (hereinafter, also referred to as “digital file URI (Uniform Resource Identifier)”) and metadata of the token. It may include at least one of information for accessing (hereinafter also referred to as “metadata URI”) or information on the current owner of the token (for example, the address on the blockchain of the current owner node of the token). In another embodiment, the token may further include metadata of the token or a digital file associated with the token. However, for convenience of explanation, the following description hereinafter assumes that the token includes a digital file URI or metadata URI.

The digital file URI associated with the token may be the address of a centralized server or cloud server where the digital file is stored. Alternatively, the digital file URI may be a hash value (for example, "ipfs.io/ipfs/12345678") of a digital file stored on IPFS (InterPlanetary File System), which stores files distributed across multiple devices. Digital files accessed through digital file URIs may be, for example, image files, video files, or music files. Hereinafter, in this specification, the expression "digital file connected to the token" refers to a digital file obtained through a digital file URI recorded in the token, and is interchangeable with expressions such as "digital file possessed by the token". can be used A token according to the disclosure of this specification may be associated with a specific object. The expression "the token is associated with a specific object" means that if the digital file associated with the token is a digital file of a specific object (for example, an image, video, or music composed by a specific object), the token and It may be an expression that represents a relationship between specific objects. For example, a specific target may be a real person such as a celebrity or celebrity, a virtual person such as a character, a group of such persons, or an animal such as a dog or cat.

The token's metadata URI may be the address of a centralized server or cloud server where the token's metadata is stored. Additionally, it may be a hash value of metadata stored on IPFS. A token's metadata may refer to a data set containing various information about the token. Metadata may include, for example, the token name, token identification information (hereinafter also referred to as “token ID”), the name of the specific entity associated with the token, when the token was created, information about the current owner of the token, history of token owner changes, or token It may include at least one of information for accessing a digital file linked to (i.e., the digital file URI described above). Additionally, in various embodiments, the metadata of the token may further include token group information indicating a date attribute group including at least one date attribute related to the token or one or more token groups to which the token belongs. When expressing arbitrary metadata in JSON (JavaScript Object Notation) format, the metadata is {"Name": "V", "Image URI": "https://ipfs.io/ipfs/12345678", "Token ID ": "0xA024ED", "Date Attributes Group": ["Debut Date": "2013-06-13", "Second Album Release Date": "2016-10-10", "Concert Date": "2021-11 -27"], "Token Group Information": "John"}. In the example of the metadata described above, "Name" is a key value indicating the token name, "Image URI" is a key value indicating a digital file URI, "Token ID" is a key value indicating the token ID, " “Date Attributes Group” may be a key value indicating a date attribute group including at least one date attribute, and “Token Group Information” may be a key value indicating token group information of the corresponding token. Hereinafter, in this specification, the expression “first information included in the metadata of the token” may be expressed as “first information included in the token” or “first information included in the token” for convenience of explanation.

Tokens according to the disclosure of this specification may belong to one or more token groups. Token group information corresponding to a token may include information (eg, a string of token group name) each indicating one or more token groups to which the token belongs. For example, if the first token is a token created to correspond to person A, token group information corresponding to the first token may include information indicating “person A token group”. Additionally, when the first token is a token created to correspond to Team B, token group information corresponding to the first token may include information indicating the “Team B token group.” In addition, if the first token is a token created to correspond to person C, and person C is a person belonging to team D composed of multiple people, the first token belongs to the "person C token group" and at the same time "team D It may belong to a “token group”. At this time, the token group information corresponding to the first token may include information indicating the “person C token group” and information indicating the “team D token group.” Token group information corresponding to the token may be stored in the memory 130 of the server 100, recorded in a block on the blockchain, or included in the metadata of the token.

Tokens according to the disclosure of this specification may be managed by smart contracts. In the disclosure of this specification, the expression "tokens are managed by a smart contract" means that tokens are created by a smart contract, tokens are transferred from one user's address to another user's address, or tokens are burned, etc. It can comprehensively refer to various movements. Smart contracts can contain various types of functions.

Smart contracts can be written to follow certain rules (or protocols). For example, a smart contract written to follow any first protocol (e.g., ERC-20) may include a function that returns the entire supply of virtual currency tokens. A smart contract written to follow the first protocol may include a function that obtains the address on the blockchain of a specific node and returns the quantity of virtual currency tokens held by that address. A smart contract written to follow the first protocol may include a function to obtain a random quantity of virtual currency tokens and an address on the blockchain of a node receiving virtual currency tokens, and transmit the virtual currency token to the address of the receiving node. A smart contract written to follow the first protocol obtains a random quantity of virtual currency tokens, the address on the blockchain of the node sending the virtual currency token, and the address on the blockchain of the node receiving the virtual currency token, and obtains the address on the blockchain of the node receiving the virtual currency token, and It may include a function that transmits a virtual currency token to the address of the receiving node. A smart contract written to follow the first protocol may include a function that returns whether a withdrawal is allowed to limit the quantity of virtual currency tokens that can be withdrawn. Additionally, a smart contract written to follow the first protocol may include a function that returns the remaining quantity that can be withdrawn.

In addition, a smart contract written to follow any second protocol (e.g., ERC-721) may use a function (hereinafter referred to as " may also include a “token generation function”). For example, the token creation function can obtain the URI of a specific digital file received from a specific node and the address on the blockchain of a random node and generate a token corresponding to the URI of the digital file. When a token is generated by a token creation function, the owner information of the token may be determined according to the address on the blockchain of a random node entered into the token creation function. The token creation function may additionally obtain one or more information to be included in the token metadata (e.g., a token name or a date attribute group containing at least one date attribute related to the token, etc.) and generate a token. In the disclosure of this specification, the expression “creating an NFT” may be used interchangeably with the expression “minting an NFT.” Additionally, a smart contract written to follow the second protocol may include a function that obtains the address on the blockchain of a random node and returns the quantity of tokens held by that address. A smart contract written to follow the second protocol may include a function that obtains the token ID of an arbitrary token and returns information about the owner who owns the token. A smart contract written to follow the second protocol may include a function that obtains the address on the blockchain of an arbitrary node and the token ID of an arbitrary token and authorizes the transfer of tokens with that token ID to that node. . A smart contract written to follow the second protocol may include a function that obtains the token ID of a random token and returns the address on the blockchain of one or more nodes that have the authority to transmit that token.

The description of the smart contract written to comply with the above-mentioned first and second regulations is only a description to illustratively explain the functions included in the smart contract and does not limit the disclosure of this specification, and does not limit the disclosure of this specification. Smart contracts according to content may include various types of smart contracts that include at least one function related to a token.

Hereinafter, an embodiment in which the server 100 receives a request for registration of a specific token for a specific date from the user terminal 200 will be described with reference to FIGS. 5 and 6.

FIG. 5 is a flowchart of the operation of the server 100 that processes a registration request for a specific token for a specific date received from the user terminal 200 according to an embodiment of the disclosure in this specification. The server 100 may receive a request for registration of a specific token for a specific date from the user terminal 200 (S510). In the disclosure herein, a “request for registration of a specific token for a specific date” refers to, for example, a Hyper Text Transfer Protocol (HTTP) request, which includes date indication information indicating a specific date and token identification information identifying a specific token (e.g. For example, a token ID). A specific date is an arbitrary date including the values of Year, Month, and Day, and may be specified by date indication information included in the registration request. The date indication information may be a string representing the date. For example, a request for registration of a specific token for a specific date may include date indication information expressed as "2022-07-15" and a token ID expressed in hexadecimal, such as "0xA024ED". In one embodiment, a request for registration of a specific token for a specific date may further include memo information. The memo information may include a string with a specific length, for example, “Wishing the new album success!” Hereinafter, for convenience of explanation, the specific date indicated by the date indication information included in the request for registration of a specific token for a specific date may be referred to as the “desired registration date.” Additionally, the time when the server 100 receives the registration request transmitted from the user terminal 200 may be referred to as the “registration request reception time.”

Next, the server 100 may register a specific token to correspond to a specific date based on the received registration request (S520). In this specification, the expression "a specific token is registered to correspond to a specific date" refers to information indicating that the server 100 matches a specific token to a specific date and that a specific token is registered to correspond to a specific date (hereinafter, "token -Date registration information") may be created. In other words, the date included at the time of receipt of the registration request and the desired registration date may be independent dates that are unrelated to each other. For example, if the registration request for the first token for January 1, 2023 (desired registration date) reaches the server 100 at 1:10:30 PM on July 1, 2022, the server 100 ) corresponds the first token to the desired registration date, January 1, 2023, immediately after receiving the registration request or within a certain period of time, and generates information indicating that the first token has been registered to correspond to January 1, 2023. You can. Hereinafter, when the server 100 registers a specific token to correspond to a specific date based on the registration request, the specific date indicated by the date indication information included in the registration request may be referred to as the “registration date.” Additionally, the expression “a token is registered to correspond to a specific date” can be used interchangeably with expressions such as “a token is registered to a specific date” for convenience of explanation.

Token-date registration information may include, for example, at least one of the registration date (or desired registration date), the token ID of the token for which registration is requested, the time of receipt of the registration request, or memo information included in the registration request. For example, the token-date properties are {"Registration Date": "2022-08-15", "Token ID": "0x123456", "When registration request was received": "2022-07-01 18:30: 00", "memo": "My favorite!"}. Additionally, the token-date registration information may further include the point in time when registration was started. The time when registration starts may be set to the same time as the time when the registration request is received. The point in time when registration begins is the point in time after the registration request is received, when a token is registered to correspond to a specific date, when token-date registration information is created, or when token-date registration information is recorded in a block on the blockchain. It can be set to at least one of the points in time.

Token-date registration information may be recorded in any storage space. The token-date registration information may be stored in memory 130 of server 100 or recorded on the blockchain. In embodiments where token-date registration information is stored in memory 130 of server 100, processor 110 may store token-date registration information generated based on the registration request in memory 130. For example, when the server 100 receives a registration request to register token A to correspond to January 1, 2023, the processor 110 stores the token ID of token A and the token ID of token A in memory 130. Token-date registration information may be stored, including the registration date (i.e., January 1, 2023).

In embodiments where token-date registration information is recorded on a blockchain, processor 110 may transmit token-date registration information generated based on the registration request to at least one node of blockchain network 300. As a result, the fact that a specific token was registered on a specific date can be recorded in a block on the blockchain. For example, if server 100 receives a registration request to register token A to correspond to January 1, 2023, processor 110 may enter token A's token ID and token A's registration date (i.e. Token-date registration information including (January 1, 2023) may be generated, and a transaction including the generated token-date registration information may be transmitted to at least one node of the blockchain network 300. The blockchain network 300 verifies the received transaction, and when verification is complete, the transaction including the token-date registration information can be recorded in a block on the blockchain.

Meanwhile, the server 100 may receive a request for deregistration of a specific token registered to correspond to a specific date from the user terminal 200. The server 100 may deregister a token registered to correspond to a specific date based on the deregistration request. “Deregistration request” may include token identification information that identifies a specific token. Additionally, the time when the server 100 receives the deregistration request transmitted from the user terminal 200 may be referred to as the “time of receiving the deregistration request.”

In this specification, the expression “the registration of a specific token registered to correspond to a specific date is deregistered” means that the token-date registration information stored in the memory 130 of the server 100 is deleted or the specific date of the specific token is deleted. This may mean that information indicating that registration has been canceled (hereinafter, also referred to as "token-date registration deregistration information") is recorded in a block on the blockchain managed by the blockchain network 300. Specifically, when a request for deregistration of the first token for a specific date is received by the server 100 while the token-date registration information is stored in the memory 130 of the server 100, the processor 110 stores the memory 130 ), the token-date registration information indicating the fact that the first token was registered to correspond to a specific date can be deleted.

In addition, when a request for deregistration of the first token for a specific date is received from the server 100 while the token-date registration information is recorded on the blockchain, the processor 110 transmits the token-date deregistration information to the blockchain. It can be transmitted to at least one node of the network 300. Token-date deregistration information may include, for example, at least one of the token ID of the token for which deregistration is requested, the time of receipt of the deregistration request, or transaction information of the corresponding token-date registration information. At this time, “transaction information of the corresponding token-date registration information” may mean the unique ID of the transaction including the existing token-date registration information for the token for which deregistration has been requested. For example, the token-date deregistration information is {"Token ID": "0x123456", "When deregistration request was received": "2022-07-02 15:30:00", "Transaction information": "0e3e2357e806b6cdb1f70b54c3a3a17b6714ee1f0e69bebb" } can be illustratively expressed as follows.

In various embodiments according to the disclosure herein, tokens may be locked up for a specific period of time after registration. In this specification, the expression "tokens are locked up for a specific period after registration" means that deregistration of tokens, transfer of ownership of tokens, or incineration of tokens is not possible until the elapse of a certain period from the time token registration begins. It can mean. Hereinafter, tokens that are locked up for a specific period of time after registration may be referred to as “tokens in a locked-up state” for convenience.

The lockup state of a token in a locked up state can be released if certain conditions are met. In one embodiment, the condition for releasing the lockup state (hereinafter also referred to as “lockup release condition”) may be a condition that is satisfied only when a specific period for releasing the lockup elapses from the time registration starts. For example, if the specific period for unlocking is 3 months, and the token-date property information of the first token registered to correspond to a specific date is {"Registration Date": "2022-08-15", "Token ID" : "0x123456", "Time of receipt of registration request": "2022-07-01 18:30:00", "Time of registration start": "2022-07-01 18:31:00"}. At this time, the first token is in a locked-up state until 6:31:00 p.m. on October 1, 2022, which is 3 months from the time registration began (6:31:00 p.m. on July 1, 2022). As a token, it may not be possible to unlock it. That is, the server 100 receives a request from the user terminal 200 to deregister the first token before 6:31:00 PM on October 1, 2022, a request to transfer ownership of the first token, and a request to transfer the first token. When receiving an incineration request, etc., the processor 110 may refuse to process the received request and transmit rejection information to the user terminal 200.

FIG. 6 is a flowchart illustrating a method by which the server 100 processes a registration request for a specific token for a specific date received from the user terminal 200 according to another embodiment of the content disclosed in this specification. When the server 100 receives a request for registration of a specific token for a specific date, the server 100 may register the token depending on whether registration of the token is possible on that date.

The server 100 may receive a request for registration of a specific token for a specific date from the user terminal 200 (S610). Next, the processor 110 may obtain the first date attribute group related to the specific token for which registration has been requested (S620). A token according to the disclosure herein may be associated with a date attribute group that includes at least one date attribute. The “date attribute” associated with a token may be information indicating the date on which a registration request can be made for the token. For example, the first date attribute group for token A may include date attributes such as “2013-06-12”, “2013-09-11”, or “2014-02-12”. In this case, token A may be registered only for one of the dates “2013-06-12”, “2013-09-11”, or “2014-02-12” included in the first date attribute group.

A date attribute group containing at least one date attribute for a token may be recorded in any storage space. The date attribute group may be stored in the memory 130 of the server 100 or in metadata of the corresponding token. In one embodiment where a date attribute group for a token is stored in memory 130 of server 100, processor 110 may obtain a first date attribute group for a particular token from memory 130. In another embodiment in which a date attribute group for a token is included in the token's metadata, the processor 110 may select a first date attribute group for a particular token for which registration has been requested from at least one node of the blockchain network 300. can be obtained. Specifically, the processor 110 transmits a request or transaction for a function call to at least one node of the blockchain network 300 to query a first date attribute group including at least one date attribute related to a specific token. And, as a result, the first date attribute group for a specific token can be obtained.

Next, the processor 110 determines whether the specific date (i.e., desired registration date) indicated by the date indication information included in the registration request matches one of at least one date attribute included in the first date attribute group. (S630). If it is determined that the desired registration date does not match all of the date attributes included in the first date attribute group, the processor 110 may transmit rejection information for the registration request to the user terminal 200 (S635). For example, the first date attribute group for token A includes "2013-06-13", "2016-10-10", and "2021-11-27", and the desired registration date is "2021-01- In the case of "01", the processor 110 determines through calculation that the desired registration date does not match all of the date attributes included in the first date attribute group, and transmits rejection information for the registration request to the user terminal 200. You can.

In the case where token-date registration information is recorded on the blockchain, if the desired registration date is determined to match any one of at least one date attribute included in the first date attribute group, the processor 110 registers The date indication information and token identification information included in the request may be transmitted to at least one node of the blockchain network 300 (S640). At this time, the blockchain network 300 may record information indicating that a token with token identification information has been registered to correspond to the date indicated by the date indication information (i.e., token-date registration information) in one block on the blockchain. . The processor 110 may transmit approval information for the registration request to the user terminal 200 prior to or following step S640 (S650). Additionally, the processor 110 may transmit approval information for the registration request to the user terminal 200 at the same time as step S640. For example, the first date attribute group for token A includes "2013-06-13", "2016-10-10", and "2021-11-27", and the desired registration date is "2021-01- If "01", the processor 110 determines through operation that the desired registration date matches any one of the date attributes included in the first date attribute group, and uses the date indication information and token identification information included in the registration request. It can be transmitted to at least one node of the blockchain network 300 and approval information for the registration request can be transmitted to the user terminal 200.

In the case of an embodiment in which token-date registration information is stored in the memory 130 of the server 100, if the desired registration date is determined to match any one of at least one date attribute included in the first date attribute group In this case, instead of the above-described step (S640), the processor 110 generates information (token-date registration information) indicating that a token with token identification information has been registered to correspond to the date indicated by the date indication information, and the generated token -Storing date registration information in the memory 130 may be performed. Thereafter, the processor 110 may transmit approval information for the registration request to the user terminal 200.

The date attribute group for tokens according to the disclosure of this specification may be changed. For example, assume that the specific object associated with the token is singer A. At this time, when singer A releases a new album, a date attribute indicating the new album release date may need to be added as a date attribute associated with the token. Additionally, if the token for singer A already included a date attribute indicating the release date of a new album, but the new album release date has changed, the date attribute indicating the release date of the new album may need to be deleted or changed. Accordingly, the following describes various embodiments in which a date attribute group including at least one date attribute associated with a token is changed.

In one embodiment where a date attribute group for a token is stored in memory 130 of server 100, processor 110 may change the date attribute group stored in memory 130. Specifically, when the first date attribute group including the first token and at least one date attribute are stored in the memory 130 to correspond to each other, the processor 110 selects the at least one date attribute of the first date attribute group. You can change this to have different dates. Additionally, the processor 110 may add a new date attribute to the first date attribute group or delete at least one date attribute from the first date attribute group.

In another embodiment in which a date attribute group related to a token is included in the token's metadata, the processor 110 may perform an operation to swap an existing token with a new token. Specifically, when the first date attribute group includes at least one date attribute and the first token includes the first date attribute group, the processor 110 selects the at least one date attribute included in the first date attribute group. A second date attribute group containing different date attributes may be created. For example, the second date attribute group is included in the first date attribute group by additionally including a new date attribute with respect to the first date attribute group or not including at least one date attribute included in the first date attribute group. It may contain at least one date attribute and different date attributes. The processor 110 may transmit a request for generating a second token to at least one node of the blockchain network 300. The request to create a second token may include information about the first token (eg, a token ID of the first token) and a second date attribute group. The blockchain network 300, which has received a request for generating a second token, acquires metadata of the first token corresponding to the existing token based on the token ID of the first token included in the request for generating the second token, The first date attribute group included in the metadata of the first token may be changed to the second date attribute group, and the second token may be generated based on the changed metadata. Through this, the second token, which is a new token, has the same information as the first token, which is an existing token, except for the first date attribute group, but has a second date attribute group, which is a changed date attribute group, instead of the first date attribute group. It can be.

FIG. 7 is a flowchart of the operation of the server 100 that processes a registration request for a specific token associated with a specific object received from the user terminal 200 according to another embodiment of the disclosure in this specification. The server 100 may receive a request for registration of a first token associated with a specific target from the user terminal 200 (S710). The first token for which registration is requested may be a token that has already been created to be associated with a specific object. That is, the digital file contained in the first token associated with person A may be an image or video taken of person A. In one embodiment, a “request for registration of a first token associated with a particular subject” may include token identification information (e.g., token ID) that identifies the particular token, for example. In another embodiment, the “request for registration of a first token associated with a specific object” may further include date indication information indicating a specific date, similar to the “request for registration of a specific token on a specific date” described above. .

Next, the server 100 may register the first token to be locked up for a specific period of time based on the registration request received from the user terminal 200 (S720). The specific period for which the registered first token is locked may be, for example, 1 month, 3 months, or 1 year. For the first token locked up for a specific period, at least one of deregistration, transfer of token ownership, or token burning may not be possible until the specific period elapses. In this specification, the expression “a specific token is registered to be locked up for a specific period of time” means that the server 100 provides information indicating that a specific token (first token) is locked up (hereinafter also referred to as “token-lockup registration information”). It can mean creating. For example, if the registration of the first token associated with person A started at 1:10:30 PM on July 1, 2022, and the specific period for which the first token is locked is 1 year, the server 100 Information indicating that the first token has been locked up can be generated until 1:10:30 p.m. on July 1, 2023, one year from the time registration of the first token began. Token-lockup registration information may be recorded in any storage space, similar to the token-date registration information described above. For example, token-lockup registration information may be recorded in memory 130 of server 100 or on a blockchain.

Next, the server 100 may determine the second token to be owned by the owner of the first token, based on information about the first token registered to be locked up (S730). Specifically, the processor 110 may determine the second token to be owned by the owner of the first token when information about the first token registered to be locked up for a specific period satisfies a specific condition. The second token may be a type of compensation given to the owner of the first token when a specific condition is satisfied according to the lock-up of the first token. In one embodiment, other forms of compensation (e.g., coupons, etc.) may be provided in lieu of the second token.

In one embodiment, processor 110 may determine that a specific condition is satisfied if the registered first token is a token associated with a specific object and determine a second token to be owned by the owner of the first token. For example, assume that a certain condition is satisfied when the first registered token is a token associated with person A. At this time, if the first token registered to be locked up for a specific period is a token associated with person A, the processor 110 determines that the specific condition is satisfied and determines the second token to be owned by the owner of the first token. there is.

In another embodiment, the processor 110 may determine that a specific condition is satisfied if the registered first token is a token registered to correspond to a specific date and determine the second token to be owned by the owner of the first token. . For example, assume that a specific condition is satisfied when the first registered token is a token registered to correspond to a specific date of January 1, 2023. At this time, if the first token registered to be locked up for a specific period is a token registered to correspond to January 1, 2023, the processor 110 determines that the specific condition is satisfied and the owner of the first token owns it. The second token to be used can be determined.

In another embodiment, the processor 110 determines that a certain condition is satisfied if the first registered token is a token associated with a specific object and registered to correspond to a specific date, and determines that a second token to be owned by the owner of the first token The token can be determined. For example, assume that a specific condition is satisfied when the first registered token is a token associated with person A and is a token registered to correspond to a specific date of January 1, 2023. At this time, if the first token registered to be locked up for a specific period is a token associated with person A and a token registered to correspond to January 1, 2023, the processor 110 determines that the specific condition is satisfied, and the first token is The owner of the token can decide which second token to own.

In another embodiment, the processor 110 determines that a specific condition is satisfied when the token group information corresponding to the registered first token is specific token group information and determines the second token to be owned by the owner of the first token. You can. For example, assume that a certain condition is satisfied when the registered first token is a token belonging to the Team B token group and the token group information includes information indicating “Team B token group.” At this time, if the token group information corresponding to the first token registered to be locked up for a specific period includes information indicating “Team B token group”, the processor 110 determines that the specific condition has been satisfied, and the first token The owner of the token can decide which second token will be owned.

In various embodiments consistent with the disclosure herein, the specific object associated with the second token to be owned by the owner of the first token may be the same object as the specific object associated with the first token. That is, the digital file held by the second token may be an image of a specific object associated with the first token. Meanwhile, in one embodiment, the second token may be a token registered in the blockchain network 300 as a previously created NFT. At this time, the processor 110 may modify the current owner information of the second token so that the owner of the first token owns the second token. Specifically, the processor 110 transmits a request or transaction for a function call to at least one node of the blockchain network 300 to change the owner information of the second token, and as a result, changes the owner information of the second token. You can change it. In another embodiment, processor 110 may generate a second token to be owned by the owner of the first token. Specifically, the processor 110 generates a second token to be owned by the owner of the first token when information about the first token registered to be locked up for a specific period satisfies a specific condition, thereby creating a second token to be owned by the owner of the first token. A second token may be determined. Specifically, the processor 110 transmits a request or transaction for a function call to at least one node of the blockchain network 300 to generate a new token (second token) owned by the owner of the first token, As a result, a second token owned by the first token owner can be created.

Next, the server 100 may transmit information about the second token to the owner of the first token (S740). Specifically, the processor 110 transmits information about the second token to the user terminal of the owner of the registered first token, or sends the second token to a node on the blockchain network 300 of the owner of the registered first token. Information can be transmitted. Information about the second token may include, for example, token identification information of the second token or a digital file held by the second token.

FIG. 8 is a flowchart of the operation of the server 100 that processes a transmission request for posting information received from the user terminal 200 according to an embodiment of the disclosure in this specification. The user terminal 200 may request transmission of posted information for a specific date to the server 100.

The server 100 may receive a request to transmit posting information for a specific date from the user terminal 200 (S810). In this specification, posting information is information corresponding to a specific date, and is generated based on a token registered to correspond to a specific date. When a calendar is displayed on any device, the area corresponding to the specific date is displayed on the calendar screen. This may be information for you. A transmission request requesting transmission of such posted information may include date indication information indicating a specific date. In some embodiments below, the specific date on which transmission of posting information is requested from the user terminal 200 may also be referred to as a “first date” for convenience of explanation.

Next, the server 100 may generate token list information about tokens registered to correspond to a specific date (S820). Token list information according to the disclosure of this specification is information corresponding to a specific date on which transmission of posting information was requested, and is specific data such as a list, array, or set of information about the token. It may be information that has a structure.

The processor 110 may obtain information about at least one token registered to correspond to a specific date from the memory 130 or from at least one node of the blockchain network 300. In one embodiment in which the token-date registration information described above is stored in memory 130 of server 100, processor 110 receives information about at least one token registered to correspond to a specific date from memory 130. You can acquire and create token list information. In another embodiment in which token-date registration information is recorded on a blockchain, processor 110 receives information about at least one token registered to correspond to a specific date from at least one node of blockchain network 300. The token list information may be received and generated based on information about at least one received token. At least one node of the blockchain network 300 may include a smart contract that includes a function to query tokens registered on a specific date. A function that searches for tokens registered on a specific date can obtain a specific date and return information about at least one token registered to correspond to that date. The processor 110 sends a function call request or transaction that includes a specific date included in the request to transmit posting information to at least one node of the blockchain network 300 to call a function to query a token registered on a specific date. Can be transmitted. As a result, the processor 110 may receive information about at least one token registered to correspond to a specific date from at least one node of the blockchain network 300 and generate token list information accordingly.

Information about registered tokens corresponding to a specific date that the processor 110 obtains from the memory 130 or the blockchain network 300 includes, for example, token ID, metadata URI, time of receipt of the registration request, or memo information. It may include etc. Specifically, when information about a token registered to correspond to a specific date is expressed as {"Token ID": [{"Token ID": Z2}], it can be expressed as an array containing information about one or more tokens as elements.

Next, the server 100 may generate posting information based on the generated token list information (S830). Posting information may include information about each token registered to correspond to a specific date. Posting information on a specific date (the first date) includes, for each of at least one token registered to correspond to the first date, an image associated with each token, a time of receipt of a registration request for each token, and a token group corresponding to each token. It may include at least one of information or memo information of each token. Additionally, the posting information may further include information indicating a posting priority among tokens registered to correspond to the first date (hereinafter, also referred to as “posting priority”).

The processor 110 may determine the posting priority based on the timing of receiving the registration request for each of the tokens registered to correspond to the first date. That is, if a plurality of tokens are registered for the first date, the processor 110 can compare the registration request reception time of each token and determine the posting priority so that the registration request reception time has a higher priority in the order of earliest. there is. For example, the token list information includes information about each of the first token and the second token registered to correspond to the first date, and the registration request for the first token is received at 12:00 PM on January 1, 2022. Assume that the minute is 00 seconds, and the registration request for the second token is received at 12:00:01 PM on January 1, 2022. At this time, the processor 110 determines that the first token has a higher priority than the second token because the time of receipt of the registration request for the first token for the first date is earlier than the time of receipt of the registration request for the second token for the first date. You can determine the posting priority to have a ranking.

The processor 110 may determine the posting priority based on token group information corresponding to each token. In one embodiment in which the processor 110 determines the posting priority based on token group information, the processor 110 determines the posting priority based on the number of tokens belonging to each of one or more token groups included in the token group information. You can decide. For example, 100 tokens belonging to the Person A token group (i.e., 100 tokens created to correspond to Person A) are registered to correspond on the first date, and 200 tokens belonging to the Person B token group (i.e. , 200 tokens generated to correspond to person B) are registered to correspond to the first date, the processor 110 generates more tokens belonging to the person B token group than tokens belonging to the person A token group on the first date. Since it is registered in , the posting priority can be determined so that tokens belonging to the person B token group have a higher priority than tokens belonging to the person A token group. Additionally, as the number of tokens belonging to each of one or more token groups changes, the posting priority of tokens belonging to each token group may change. For example, the number of tokens belonging to the Person A token group registered to correspond to the first date increases from 100 to 150, and the number of tokens belonging to the Person B token group registered to correspond to the first date increases to 200. When the number is reduced to 100, the processor 110 may determine the posting priority so that tokens belonging to the person A token group have a higher priority than tokens belonging to the person B token group. Meanwhile, the processor 110 may determine that tokens belonging to the same token group have the same publishing priority.

In another embodiment in which the processor 110 determines publishing priority based on token group information, the processor 110 determines on a specific date among all tokens issued to belong to each of one or more token groups included in the token group information. Publishing priority can be determined based on the ratio of registered tokens. For example, if the total number of tokens belonging to the person A token group is 200, of which 100 tokens are registered corresponding to the first date, and the total number of tokens belonging to the person B token group is 1,000, of which 200 tokens are registered corresponding to the first date. 1 Assume that it is registered to correspond to the date. In this case, processor 110 determines that a proportion (i.e., 100/200, 50%) of the tokens registered on the first date out of all tokens issued to belong to the Person A token group are issued to belong to the Person B token group. Posting so that tokens belonging to the Person A token group have a higher priority than tokens belonging to the Person B token group, as they are greater than the proportion of tokens registered on the first date out of all tokens (i.e. 200/1000, 20%). You can decide priorities. Additionally, as the ratio of tokens registered on a specific date among all tokens issued to belong to each of one or more token groups changes, the posting priority of tokens belonging to each token group may change. For example, the proportion of tokens registered on the first date among all tokens issued to belong to the Person A token group is 50%, and the proportion of tokens registered on the first date among all tokens issued to belong to the Person B token group is 50%. When the ratio increases from 20% to 100%, processor 110 may determine the posting priority such that tokens belonging to the Person B token group have a higher priority than tokens belonging to the Person A group. Meanwhile, the processor 110 may determine that tokens belonging to the same token group have the same publishing priority.

In another embodiment in which the processor 110 determines the posting priority based on token group information, the processor 110 determines the average registration request reception time of tokens belonging to each of one or more token groups included in the token group information ( That is, the posting priority can be determined based on the average value at the time of receiving the registration request for each token. For example, the average registration request receipt time for tokens registered to correspond to the first date and belonging to the person A token group is 1:30:00 PM on July 11, 2022, and the tokens registered to correspond to the first date and belonging to the person A token group are registered to correspond to the first date and belong to the person A token group. Assume that the average registration request submission time for tokens belonging to the B token group is 1:31:00 PM on July 12, 2022. In this case, the processor 110 determines that the average registration request reception time of tokens belonging to the person A token group is faster than the average registration request reception time of tokens belonging to the person B token group, so that the tokens belonging to the person A token group are The posting priority can be determined to have a higher priority than tokens belonging to a token group. Additionally, as the average registration request reception time for tokens belonging to each of one or more token groups changes, the posting priority of tokens belonging to each token group may change. For example, the registration request receipt for each of the first, second, and third tokens registered to correspond to the first date and belonging to the Person A token group is, in that order, July 10, 2022, at 12:00:00 AM. seconds, 12:00:00 AM on July 14, 2022 and 12:00:00 AM on July 15, 2022 (i.e., the average registration of tokens belonging to the Person A token group registered to correspond to the first date The request receipt time is 12:00:00 AM on July 13, 2022), and receipt of registration requests for each of the 4th token, 5th token, and 6th token that are registered to correspond to the first date and belong to the Person B token group. The timings, in that order, are 12:00:00 AM on July 13, 2022, 12:00:00 AM on July 14, 2022, and 12:00:00 AM on July 15, 2022 (i.e., 12:00:00 AM on July 15, 2022). Assume that the average registration request reception time for tokens belonging to the person B token group registered to correspond to the date is 12:00:00 a.m. on July 14, 2022. In the hypothetical state, the average registration request reception time for tokens belonging to the person A token group is faster than the average registration request reception time for tokens belonging to the person B token group, so the tokens belonging to the person A token group are in the person B token group. It may have a higher priority than the token it belongs to. At this time, if the first token belonging to the Person A token group is deregistered, the average registration request reception time for tokens belonging to the Person A token group may be changed to 12:00:00 PM on July 14, 2022. As a result, the average registration request reception time for tokens belonging to the person B token group (12:00:00 a.m. on July 14, 2022) is the average registration request receipt time for tokens belonging to the person A token group (July 2022) (12:00:00 PM on the 14th), the processor 110 may determine the posting priority such that tokens belonging to the person B token group have a higher priority than tokens belonging to the person A token group. Meanwhile, the processor 110 may determine that tokens belonging to the same token group have different publishing priorities depending on the timing of receipt of the registration request for each token. Referring back to the above example, the 4th token, 5th token, and 6th token registered to correspond to the first date and belonging to the Person B token group may have publishing priority according to the order of when each token's registration request is received. there is. That is, the fourth token may have the highest priority, the sixth token may have the lowest publishing priority, and the fifth token may have a publishing priority that is lower than the fourth token and higher than the sixth token.

The various embodiments of posting priority as described above are merely illustrative explanations for specifically explaining a method of determining posting priorities between tokens included in posting information and do not limit the disclosure of this specification.

The posting priority between tokens included in the posting information may be used when the calendar is displayed on an electronic device such as the server 100 or the user terminal 200. As an example, assume that the user terminal 200 displays a calendar through the output unit 250, and that posting information for a specific date includes information about each of a plurality of tokens and a posting priority between the plurality of tokens. . At this time, based on the posting priority included in the posting information, the user terminal 200 determines which token among the plurality of tokens and which image associated with it will be exposed at the top within an area for a specific date on the calendar screen. You can decide whether to expose the image linked to a certain token first, whether to expose the image linked to a certain token larger, or place the image linked to a certain token closer to the center of the screen than other images.

Next, the server 100 may transmit posting information to the user terminal 200 (S840). The user terminal 200 can display posted information in various ways through the output unit 250. Specifically, the processor 210 of the user terminal 200 may receive posting information for a specific date from the server 100 and display a calendar screen through the output unit 250 based on the posting information. The calendar screen may include at least one area allocated to a specific date. Specifically, the processor 210 may determine information to be displayed in an area allocated on a specific date based on posted information on a specific date. The area allocated to a specific date may include the area allocated to at least one token. The processor 210 may determine a display method or order of areas allocated to each token within the area allocated on a specific date based on the posting priority included in the posting information. In one embodiment, posted information may be displayed through an output unit such as the server 100.

Hereinafter, a specific embodiment of the case in which posted information is displayed through the output unit 250 of the user terminal 200 will be described with reference to FIGS. 9A to 9D.

FIG. 9A is a diagram illustrating a screen that can be displayed when posted information according to an embodiment of the disclosure disclosed in this specification is displayed through the output unit 250 of the user terminal 200. In one embodiment, tokens with a higher posting priority may be posted at the top of the date on the calendar screen. In the example of FIG. 9A, it is assumed that the posting information for a specific date (the first date) includes information about the first token and information about the second token. The processor 210 configures the allocated area 910 on the first date to include the area allocated to the first token 911 and the area allocated to the second token 913 based on the publication information for the first date. You can decide. Both the first token and the second token are tokens registered to correspond to the first date, and the processor 210 selects a token with a high posting priority among the tokens included in the posting information as the first token and a token with a low posting priority. can be determined as the second token. An image connected to the first token may be displayed in the area 911 allocated to the first token. An image connected to the second token may be displayed in the area 913 allocated to the second token. If the first token has a higher publishing priority than the second token, the processor 210 determines the region allocated to the first token ( 911) may be determined to be located above the area 913 allocated to the second token.

FIG. 9B is a diagram illustrating a screen that can be displayed when posted information according to another embodiment of the disclosure disclosed in this specification is displayed through the output unit 250 of the user terminal 200. In one embodiment, tokens with a higher posting priority may be posted to occupy a larger area on the calendar screen. In the example of FIG. 9B, it is assumed that the posting information for a specific date (the first date) includes information about the first token, information about the second token, and information about the third token. The processor 210 determines that the area 910 allocated on the first date is divided into an area allocated to the first token 911, an area allocated to the second token 913, and a third area based on the posting information for the first date. It may be decided to include the area 915 allocated to the token. The first token, the second token, and the third token are all tokens registered to correspond to the first date, and the processor 210 selects the token with the highest posting priority among the tokens included in the posting information as the first token. The token with the lowest priority can be determined as the third token, and the token with a posting priority lower than the first token and higher than the third token can be determined as the second token. The area allocated to the first token 911, the area allocated to the second token 913, and the area allocated to the third token 915 include an image associated with the first token, an image associated with the second token, and an image associated with the third token. Images linked to can be displayed respectively. If the first token has a higher publishing priority than the other tokens (i.e., the second token or the third token), the processor 210 selects the region 910 for the first date, as shown in FIG. 9B. Within this, it may be determined that the area 911 allocated to the first token occupies a wider size range than the area 913 allocated to the second token or the area 915 allocated to the third token. At this time, the image displayed in the area 911 allocated to the first token may be displayed larger than the image displayed in other areas. In Figure 9b, the area allocated to the second token 913 and the area allocated to the third token 915 occupy the same size range, but the area allocated to the second token 913 and the area allocated to the third token are The area 915 may occupy a range of different sizes depending on the posting priority of each token.

FIG. 9C is a diagram illustrating a screen that can be displayed when posted information according to another embodiment of the content disclosed in this specification is displayed through the output unit 250 of the user terminal 200. Posting information on a specific date (first date) received by the user terminal 200 from the server 100 may include memo information of a token registered to correspond to the first date. When the posting information includes memo information of a specific token, the processor 210 may display the memo information through the output unit 250. Specifically, when the posting information includes memo information of the first token registered to correspond to the first date, the processor 210 may display the memo information 931 of the first token in at least one area on the calendar screen. there is. The memo information 931 of the first token may be, for example, “My favorite!” It may contain strings such as: In one embodiment, the memo information 931 of the first token may be displayed as a result of the user touching or clicking the area 911 allocated to the first token. In another embodiment, the memo information 931 of the first token may be displayed at any location within the area allocated to the first token.

FIG. 9D is a diagram illustrating a screen that can be displayed when posted information according to another embodiment of the content disclosed in this specification is displayed through the output unit 250 of the user terminal 200. A token according to the disclosure of this specification may be a token (hereinafter also referred to as an “advertising token”) containing information for accessing an advertising image (i.e., advertising image URI). The advertising image URI linked to the advertising token is a type of digital file URI described above and may refer to the address of a centralized server or cloud server where the advertising image is stored or the hash value of the advertising image stored on IPFS. Below, descriptions of overlapping matters will be omitted and the main differences between advertising tokens will be explained.

An advertising token may be a token generated by a specific function (hereinafter also referred to as an “advertising token generation function”) included in a smart contract executed by at least one node of the blockchain network 300. The advertising token creation function specifically obtains the advertising image URI, one or more virtual currency tokens corresponding to a specific amount, and the address on the blockchain of the first node (i.e., the node of the user requesting the advertisement), and obtains the URI of the advertising image. It may be a function that creates a token with . The advertising token creation function may be a function written to generate an advertising token and then transmit one or more virtual currency tokens obtained to an address on the blockchain of a second node (i.e., a server node or a user's node providing advertising). . The address on the blockchain of the second node may be included in the smart contract when the smart contract containing the advertising token creation function is created.

The server 100 may receive a request for registration of an advertising token for a specific date from the user terminal 200. The server 100 may register the advertisement token to correspond to a specific date (first date) based on the registration request for the received advertisement token. In addition, when the advertising token is registered to correspond to the first date and the server 100 receives a request to transmit posting information for the first date from the user terminal 200, the server 100 receives the user terminal 200 ) may include information about advertising tokens.

The posting information about the first date received by the user terminal 200 from the server 100 may include information about an advertising token registered to correspond to the first date. For example, the processor 210 may display an image associated with an advertising token registered to correspond to the first date in the advertising area 950 included in the area 910 allocated to the first date. Advertising area 950 may exist at any location within area 910 allocated on the first date. In another example, the processor 210 may display the advertising token within the allocated area 910 on the first date by treating it similarly to other tokens that are not advertising tokens. For example, posting information for a first date includes information about a first token and information about a second token, and at least one of the first token or the second token may be an advertising token. At this time, if the first token is an advertising token, the processor 210 may display an advertising image associated with the first token in the area 911 allocated to the first token. Additionally, when the second token is an advertising token, the processor 210 may display an advertising image associated with the second token in the area 913 allocated to the second token.

FIG. 10 is a flowchart of the operation of the server 100 that processes information indicating a specific target received from the user terminal 200 according to an embodiment of the disclosure disclosed herein. The server 100 according to the disclosure of this specification receives information indicating a specific target from the user terminal 200, generates history information for the specific target, and transmits the generated history information to the user terminal 200. You can.

The server 100 may receive information indicating a specific target from the user terminal 200 (S1010). Information indicating a specific object may be, for example, the name of a specific object associated with a token (eg, the name of a specific person). Next, the server 100 may specify or determine one or more tokens that are associated with a specific object and registered to each correspond to one or more registration dates (S1020). As described above, “registration date” refers to a specific date when a specific token is registered to correspond to a specific date based on the registration request. For example, “one or more tokens associated with a specific object and registered to each correspond to one or more registration dates” includes a first token or a second token associated with person A and registered to correspond to different dates respectively, etc. can do. Hereinafter, the expression "one or more tokens associated with a specific object and registered to each correspond to one or more registration dates" is used interchangeably with the expression "registration token associated with a specific object" for convenience of explanation. That is, one or more registration tokens associated with a specific object may be one or more tokens registered to correspond to different registration dates.

In one embodiment, memory 130 of server 100 may store information regarding one or more registration tokens associated with a particular entity. At this time, the processor 110 may obtain information about one or more tokens that are associated with a specific object and registered to correspond to one or more registration dates, respectively, from the memory 130. For example, a plurality of tokens registered to correspond to one or more registration dates are stored in the memory 130, and among the plurality of tokens, tokens corresponding to person A are referred to as token a1, token a2, and token a3, respectively. Assuming that this is the case, the processor 110 can specify token a1, token a2, and token a3 from the memory 130.

In another embodiment, the server 100 may specify one or more tokens by receiving information about one or more registration tokens associated with a specific object from the blockchain network 300. At least one node of the blockchain network 300 is associated with a specific object, and returns information about one or more tokens registered to each correspond to one or more registration dates (hereinafter, “registered token specific function associated with a specific object). It may contain a smart contract that includes "(also known as "). The “registration token specific function associated with a specific object” may obtain information indicating a specific object and return a token associated with a specific object among tokens registered to correspond to one or more registration dates. The processor 110 may transmit a function call request or transaction containing information indicating a specific target to at least one node of the blockchain network 300 to call a function. For example, if processor 110 transmits information indicating person A to at least one node of blockchain network 300, then at least one node of blockchain network 300 generates a “registration token associated with a specific object. By executing a “specific function,” information about one or more tokens (e.g., token a1, token a2, token a3) registered to correspond to person A, respectively, on one or more dates is stored on the blockchain. It can be obtained from at least one recorded transaction. As a result, the processor 110 can receive information about one or more tokens from at least one node of the blockchain network 300 and specify token a1, token a2, and token a3, which are one or more tokens associated with person A. there is.

Next, the server 100 may generate history information for a specific target based on information about each of the specified one or more tokens (S1030). History information may include the token's registration date and an image associated with the token. When the history information includes information about a plurality of tokens, the history information may include the order of each token according to the registration date. For example, assuming that the registration date of token a1 is June 5, 2022, the registration date of token a2 is January 19, 2020, and the registration date of token a3 is May 10, 2015, the processor (110 ) can generate history information including a plurality of images linked to the token in the order of the image linked to token a3, the image linked to token a2, and the image linked to token a1 according to the order of the registration date.

Next, the server 100 may transmit the generated history information to the user terminal 200 (S1040). Through this, the user terminal 200 can obtain history information about a specific object including an image of the specific object (that is, person A).

FIG. 11 is a flowchart of the operation of the server 100 to process a replacement request received from the user terminal 200 according to an embodiment of the disclosure in this specification. In the disclosure herein, the server 100 may replace a specific token registered to correspond to a specific date with another token. In some embodiments of the present specification described below with reference to FIGS. 11 and 12, for convenience of explanation, a specific token may be referred to as a “first token” and another token may be referred to as a “second token.” When a first token registered to correspond to a specific date is replaced with a second token, the second token may be registered to correspond to the same specific date as the first token. Additionally, when the first token registered to correspond to a specific date is replaced with a second token, the time of receipt of the registration request for the second token may be the same time as the time of receipt of the registration request for the first token.

The server 100 may receive a replacement request from the user terminal 200 to replace the first token registered to correspond to a specific date with a second token (S1110). The “replacement request” may include information about the first token and information about the second token. For example, the replacement request may include the token ID of the first token and the token ID of the second token. Additionally, the time when the server 100 receives the replacement request transmitted from the user terminal 200 may be referred to as the “replacement request reception time.”

Next, the server 100 may deregister the first token based on the replacement request and register the second token to correspond to a specific date (S1120). In an embodiment in which information indicating that a particular token has been registered to correspond to a particular date is stored in memory 130 of server 100, processor 110 obtains token-date registration information of the first token from memory 130. can do. Processor 110 may delete token-date registration information of the first token from memory 130 and generate token-date registration information of the second token. At this time, the processor 110 may generate token-date registration information of the second token including the same registration date and registration request reception time as the token-date registration information of the first token. For example, if the first token's token-date properties are {"Registration Date": "2023-01-01", "Token ID": "0x1234", "When Registration Request Was Received": "2022-07-01 When equal to 12:00:00"}, the token-date property information of the generated second token is {"Registration Date": "2023-01-01", "Token ID": "0x5678", "Registration Request Received It can be exemplified as "point of time": "2022-07-01 12:00:00"}.

In another embodiment, where information indicating that a particular token has been registered to correspond to a particular date is recorded in a block on a blockchain managed by blockchain network 300, processor 110 may The information may be transmitted to at least one node of the blockchain network 300, and token-date registration information of the first token may be obtained from the blockchain network 300. Processor 110 may generate token-date registration information for a second token that includes the same registration date as the token-date registration information for the first token, when the registration request was received, and information about the second token included in the replacement request. You can. The processor 110 may deregister the first token on a specific date by transmitting token-date deregistration information of the first token to at least one node of the blockchain network 300. The processor 110 transmits the token-date registration information of the second token to at least one node of the blockchain network 300, so that the fact that the second token was registered on a specific date can be recorded in one block on the blockchain. there is.

In one embodiment, when replacing the first token with a second token, the server 100 may deregister the first token depending on whether the lockup release condition for the first token is satisfied. In an embodiment in which information indicating that a particular token has been registered to correspond to a particular date is stored in memory 130 of server 100, processor 110 obtains token-date registration information of the first token from memory 130. And, the time when registration of the first token included in the token-date registration information of the first token started and the time when the replacement request was received can be compared. The processor 110 may determine whether a specific period of time (eg, 3 months) has elapsed from the time registration of the first token began when the replacement request was received. If the replacement request is received more than a certain period of time from the start of registration of the first token, the processor 110 may determine that the lockup release condition is satisfied. On the other hand, if the replacement request is received less than a certain period of time has elapsed from the start of registration of the first token, the processor 110 may determine that the lockup release condition is not satisfied. If the lockup release condition is satisfied, the processor 110 deletes the token-date registration information of the first token from memory 130 and performs an operation to replace the first token with the second token as described above. You can. If the lockup release condition is not satisfied, the processor 110 may transmit rejection information to the user terminal 200 in response to the replacement request.

In another embodiment, where information indicating that a specific token has been registered to correspond to a specific date is recorded in a block on a blockchain managed by blockchain network 300, processor 110 may select the first token included in the replacement request. Information regarding may be transmitted to at least one node of the blockchain network 300, and token-date registration information of the first token may be obtained from the blockchain network 300. The processor 110 may determine whether the lockup release condition is satisfied by comparing the time when registration of the first token included in the token-date registration information of the first token started and the time when the replacement request was received. When the lockup release condition is satisfied, the processor 110 transmits the token-date deregistration information of the first token to at least one node of the blockchain network 300, and converts the first token into a second token as described above. You can perform an operation to replace it with . If the lockup release condition is not satisfied, the processor 110 may transmit rejection information to the user terminal 200 in response to the replacement request.

FIG. 12 is a flowchart illustrating a method of processing a replacement request for the user terminal 200 according to another embodiment of the content disclosed in this specification. The server 100 may receive a replacement request from the user terminal 200 to replace the first token registered to correspond to a specific date with a second token (S1210). The replacement request may include information about the first token and information about the second token.

Next, the server 100 may obtain the registration date of the first token and the date attribute group related to the second token (S1220). As described above, a date attribute group or token-date registration information including at least one date attribute related to a token may be recorded on memory 130 or a blockchain, respectively. Processor 110 may obtain token-date registration information of the first token, including the registration date of the first token, from memory 130 or blockchain network 300. The processor 110 may obtain the date attribute group for the second token from the memory 130 or the blockchain network 300. For example, the token-date properties of the first token may be {"Registration Date": "2021-11-27", "Token ID": "0x123456", "When Registration Request Was Received": "2021-07-01 It can be expressed as 18:30:00"}. Additionally, the date attribute group for the second token is {"Date Attributes Group": ["Debut Date": "2013-06-13", "Second Album Release Date": "2016-10-10", "Concert Date It can be expressed as ": "2021-11-27"]}.

Next, the processor 110 may determine whether the registration date of the first token matches one of at least one date attribute included in the date attribute group for the second token (S1230). If it is determined that the registration date of the first token does not match all of the date attributes included in the date attribute group for the second token, the processor 110 may transmit rejection information for the replacement request to the user terminal 200. There is (S1235).

In the case where token-date registration information is recorded on the blockchain, if the registration date of the first token is determined to match any of the date attributes included in the date attribute group for the second token, processor 110 Can transmit the token-date registration deregistration information of the first token and the token-date registration information of the second token to at least one node of the blockchain network 300 (S1240). Referring back to the above example, the registration date of the first token is November 27, 2021, and the date attributes included in the date attribute group for the second token are June 13, 2013 and October 10, 2016. and November 27, 2021, which is the registration date of the first token, which is November 27, 2021, so the processor 110 stores the token-date deregistration information of the first token and the token-date registration information of the second token. It can be transmitted to at least one node of the blockchain network 300. The processor 110 may transmit approval information for the replacement request to the user terminal 200 prior to or following step S1240 (S1250). Additionally, the processor 110 may transmit approval information for the replacement request to the user terminal 200 at the same time as step S1240.

In the case of an embodiment in which token-date registration information is stored in memory 130 of server 100, if the registration date of the first token matches any of the date attributes included in the date attribute group for the second token. If it is determined that, instead of the above-described step (S1240), the processor 110 deletes the token-date registration information of the first token from memory 130, generates token-date registration information of the second token, and generates the token-date registration information of the second token. Storing token-date registration information of the second token in memory 130 may be performed. Thereafter, the processor 110 may transmit approval information for the replacement request to the user terminal 200.

In the flowchart or flowchart according to the disclosure herein, each step of the method or algorithm is described in sequential order, but each step may be performed in an order that can be arbitrarily combined in addition to being performed sequentially. The description of a flowchart or flow chart herein does not exclude making changes or modifications to the method or algorithm, nor does it imply that any step is required or desirable. In one embodiment, at least some of the steps may be performed in parallel, iteratively, or heuristically. In one embodiment, at least some steps may be omitted or other steps may be added.

Various embodiments according to the disclosure of this specification may be implemented as software on a machine-readable storage medium. The software may be software for implementing various embodiments of the present specification. Software can be inferred from various embodiments of this specification by programmers in the art to which the disclosure of this specification pertains. For example, software may be a program that contains machine-readable instructions (e.g., code or code segments). A device is a device that can operate according to commands retrieved from a storage medium, and may be, for example, a computer. In one embodiment, the device may be a computing device according to various embodiments herein. In one embodiment, the device's processor may execute a called instruction and cause the device's components to perform a function corresponding to the instruction. In one embodiment, the processor may be processors 110 and 210 according to embodiments of the present specification. A storage medium can refer to any type of recording medium in which data that can be read by a device is stored. Storage media may include, for example, ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage, etc. In one embodiment, the storage medium may be memory 130, 230. In one embodiment, the storage medium may be implemented in a distributed form, such as in a computer system connected to a network. Software may be distributed, stored, and executed on a computer system, etc. The storage medium may be a non-transitory storage medium. Non-transitory storage media refers to a medium that exists regardless of whether data is stored semi-permanently or temporarily, and does not include signals that are transmitted temporarily.

Although the technical idea according to the disclosure of the present specification has been described above through various embodiments, the technical idea according to the disclosure of the present specification is within the range that can be understood by a person skilled in the art to which the disclosure of the present specification pertains. Includes various substitutions, modifications and changes that can be made. Additionally, it is to be understood that such substitutions, modifications and alterations may be included within the scope of the appended claims.

Claims (20)

A communication interface for communicating with at least one node of the blockchain network and an external device;
One or more processors; and
one or more memories storing at least one instruction to be executed by the one or more processors,
The one or more processors:
Receiving a request for registration of a specific token for a specific date from the external device,
Based on the registration request, configured to register the specific token to correspond to the specific date,
The registration request includes date indication information indicating the specific date and token identification information identifying the specific token. According to paragraph 1,
The one or more processors:
An electronic device configured to transmit the date indication information and the token identification information to at least one node of the blockchain network in order to register the specific token to correspond to the specific date. According to paragraph 2,
wherein the specific token includes a first date attribute group comprising at least one date attribute,
The one or more processors:
Obtain, from at least one node of the blockchain network, the first date attribute group,
Determine whether the specific date indicated by the date indication information matches one of the at least one date attribute,
In response to a determination of a match, the electronic device is configured to transmit the date indication information and the token identification information to at least one node of the blockchain network. According to paragraph 2,
The one or more memories further store a first date attribute group including at least one date attribute corresponding to the specific token,
The one or more processors:
obtain the first date attribute group from the one or more memories;
Determine whether the specific date indicated by the date indication information matches one of the at least one date attribute,
In response to a determination of a match, the electronic device is configured to transmit the date indication information and the token identification information to at least one node of the blockchain network. According to paragraph 1,
The one or more processors:
Receiving a replacement request from the external device to replace the specific token registered to correspond to the specific date with another token,
Based on the replacement request, deregister the specific token and register the other token to correspond to the specific date,
The replacement request includes information about the specific token and information about the other token. According to clause 5,
The one or more processors:
Configured to de-register the specific token depending on whether the lock-up release conditions for the specific token are satisfied,
The lockup release condition is a condition that is satisfied when a specific period of time elapses from the start of registration of the specific token. According to paragraph 1,
The electronic device wherein the specific token contains information for accessing a specific image. According to paragraph 1,
The one or more processors:
Receiving a request to transmit posting information for the specific date from the external device,
Generate token list information about tokens registered to correspond to the specific date,
Generate posting information based on the token list information,
configured to transmit the posted information to the external device,
The electronic device, wherein the posting information includes information about each of the tokens. According to clause 8,
The one or more processors:
Receiving, from at least one node of the blockchain network, information about at least one token among the tokens registered to correspond to the specific date,
An electronic device configured to generate the token list information based on information about the at least one token. According to clause 8,
The posting information includes posting priorities between the tokens,
The one or more processors:
The electronic device is configured to determine the posting priority based on the timing of receipt of a registration request for each of the tokens, so as to correspond to the specific date. According to clause 8,
The token list information includes token group information, and the token group information indicates one or more token groups to which each of the tokens belongs,
The posting information includes posting priorities between the tokens,
The one or more processors:
The electronic device is configured to determine the posting priority based on the token group information. According to clause 11,
The one or more processors:
The electronic device is configured to determine the posting priority based on the number of tokens belonging to each of the one or more token groups. According to clause 8,
The first token comprises a first date attribute group comprising at least one date attribute,
The one or more processors:
Create a second date attribute group including a date attribute different from the at least one date attribute of the first date attribute group,
configured to transmit a request for creation of a second token to at least one node of the blockchain network,
The request for generating the second token includes information about the first token and the second date attribute group. According to clause 8,
The one or more processors:
Receive information indicating a specific target from the external device,
Specifies one or more tokens associated with the specific object and registered to each correspond to one or more registration dates,
Based on information about each of the specified one or more tokens, generate history information about the specific object,
An electronic device configured to transmit the history information to the external device. 1. A method performed by an electronic device comprising one or more processors and one or more memories storing at least one instruction to be executed by the one or more processors, comprising:
The one or more processors,
Receiving a request for registration of a specific token for a specific date from an external device; and
Based on the registration request, registering the specific token to correspond to the specific date,
The registration request includes date indication information indicating the specific date and token identification information identifying the specific token. According to clause 15,
The step of registering the specific token is,
The method further comprising transmitting the date indication information and the token identification information to at least one node of the blockchain network. According to clause 15,
The one or more processors,
Receiving a request to transmit posting information for the specific date from the external device;
generating token list information about tokens registered to correspond to the specific date;
generating posting information based on the token list information; and
Further comprising transmitting the posted information to the external device,
The method of claim 1, wherein the posting information includes information regarding each of the tokens. 1. A method performed by an electronic device comprising one or more processors and one or more memories storing at least one instruction to be executed by the one or more processors, comprising:
The one or more processors,
transmitting a request for registration of a specific token for a specific date to an external device; and
Receiving approval information or rejection information for a registration request for the specific token from the external device that responds to the registration request,
The registration request includes date indication information indicating the specific date and token identification information identifying the specific token. According to clause 18,
The one or more processors,
transmitting a transmission request for posting information for the specific date to the external device; and
Further comprising receiving the posted information from the external device that responds to the transmission request,
The posting information is generated based on token list information about tokens registered to correspond to the specific date, and includes information about each of the tokens. A communication interface for communicating with at least one node of the blockchain network and an external device;
One or more processors; and
one or more memories storing at least one instruction to be executed by the one or more processors,
The one or more processors:
Receive a registration request for a first token associated with a specific target from the external device,
Based on the registration request, register the first token to be locked up for a specific period of time,
Based on the information about the first token, determine a second token to be owned by the owner of the first token,
An electronic device configured to transmit information about the second token to the owner.

Images