APPARATUS AND METHOD FOR MANAGING NON-FUNGABLE TOKENS BASED ON BLOCKCHAIN

Abstract

An electronic device according to one 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 for storing at least one instruction executed by the one or more processors, wherein the one or more processors may be configured to receive a registration request for a token for a date from the external device, register the token to correspond to the date based on the registration request, and transmit posting information associated with the date to the external device, wherein the posting information may include display attributes of an item corresponding to the token, and the registration request may include date indication information indicating the date, and token identification information identifying the token.

Description

[Technical field]

[0001] The present disclosure relates to techniques for managing non-fungible tokens based on a blockchain network. [Background technology]

[0002] Recently, with the emergence of various media, various types of entertainers and famous people have appeared, including not only idols and actors but also influencers, YouTubers, etc. In the entertainment business related to such entertainers and famous people, it is becoming increasingly common for fans of a particular entertainer to record the schedule of their favorite entertainer and promote that entertainer to others.

[0003] Recently, fans have also increasingly promoted their favorite celebrities to others by posting photos of the celebrities directly in areas where they are visible to the general public (for example, advertising panels at subway platforms or bus stops, or outdoor billboards). Summary of the Invention [Problem to be solved by the invention]

[0004] The present disclosure provides a technique for preventing a problem in which an area for a specific date on a calendar screen displayed on a user terminal is filled with a specific object that corresponds to a token.

[0005] The present disclosure provides techniques for preventing a user who has purchased a token that can be registered to correspond to one specific date from registering the token to multiple specific dates.

[0006] The present disclosure provides techniques for enabling a user to easily grasp historical information relating to a specific subject.

[0007] The present disclosure provides a technique that allows a user who has registered a token to correspond to a specific date to arbitrarily change the registered token to another token. [Means for solving the problem]

[0008] Additional aspects will be set forth in part in the description that follows, and in part will be obvious from the description, or may be learned by practicing the presented embodiments.

[0009] An electronic device according to one 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 for storing at least one instruction executed by the one or more processors, wherein the one or more processors may be configured to receive a registration request for a token for a date from the external device, register the token to correspond to the date based on the registration request, and transmit posting information associated with the date to the external device, wherein the posting information may include display attributes of an item corresponding to the token, and the registration request may include date indication information indicating the date and token identification information identifying the token.

[0010] A display attribute of an image corresponding to the token can be determined based on the date display information. The display attributes may include at least one of a display priority of the image, a display position of the image, and a display size of the image.

[0011] The display attributes may be determined based on date indication information, and may include at least one of a display priority of the item, a display position of the item, and a display size of the item.

[0012] The one or more processors may be configured to register the token in the blockchain network by transmitting the date indication information and the token identification information to at least one node of the blockchain network.

[0013] The token may include a first date attribute group including at least one date attribute, and the one or more processors may be configured to obtain the first date attribute group from at least one node of the blockchain network, determine whether the date indicated by the date indication information matches one of the at least one date attribute, and, in accordance with a determination that there is a match, transmit the date indication information and the token identification information to at least one node of the blockchain network.

[0014] The one or more memories may additionally store a first date attribute group including at least one date attribute corresponding to the token, and the one or more processors may be configured to retrieve the first date attribute group from the one or more memories, determine whether the date indicated by the date indication information matches one of the at least one date attribute, and, according to a determination that there is a match, transmit the date indication information and the token identification information to at least one node of the blockchain network.

[0015] The one or more processors are configured to receive an exchange request from the external device to exchange the token registered to correspond to the date for another token, and to deregister the token and register the other token to correspond to the date based on the exchange request, where the exchange request may include information about the token and information about the other token.

[0016] The one or more processors are configured to deregister the token depending on whether a lock-up release condition for the token is satisfied, and the lock-up release condition may be a condition that is satisfied when a predetermined period of time has elapsed from the time when registration of the token began.

[0017] The token may include information for accessing the image. The one or more processors are configured to receive a request to transmit notice information for the date from the external device, generate token list information for a plurality of tokens registered to correspond to the date, generate notice information based on the token list information, and transmit the notice information to the external device, and the notice information may include information regarding each of the plurality of tokens.

[0018] The one or more processors may be configured to receive, from at least one node of the blockchain network, information regarding at least one token of the plurality of tokens registered corresponding to the date, and generate the token list information based on the information regarding the at least one token.

[0019] The posting information may include a priority of the posting among the plurality of tokens, and the one or more processors may be configured to determine a priority of the posting based on a time of receipt of a registration request for each of the plurality of tokens.

[0020] The token list information may include token group information indicating one or more token groups to which each of the plurality of tokens belongs, and the posting information may include a priority of posting among the plurality of tokens, and the one or more processors may be configured to determine a priority of the posting based on the token group information.

[0021] The one or more processors may be configured to prioritize the postings based on a number of tokens that belong to each of the one or more token groups.

[0022] The first token may include a first date attribute group including at least one date attribute, and the one or more processors may be configured to generate a second date attribute group including a date attribute different from the at least one date attribute of the first date attribute group, and transmit a request to generate a second token to at least one node of the blockchain network, the request to generate a second token may include information about the first token and information about the second date attribute group.

[0023] The one or more processors may be configured to receive information indicative of an object from the external device, identify one or more tokens associated with the object and registered corresponding to one or more registration dates, respectively, generate historical information about the object based on information about each of the identified one or more tokens, and transmit the historical information to the external device.

[0024] According to another aspect of the present disclosure, there may be provided a method performed by an electronic device, the method being performed by an electronic device including one or more processors and one or more memories storing at least one instruction executed by the one or more processors, the method including receiving a token registration request for a date from an external device, registering the token to correspond to the date based on the registration request, and transmitting posting information associated with the date to the external device, the posting information including display attributes of an item corresponding to the token, and the registration request including date designation information indicating the date and token identification information identifying the token.

[0025] The display attributes are determined based on the date indication information, and may include at least one of a display priority of the item, a display position of the item, and a display size of the item.

[0026] The step of registering the token may further include transmitting the date indication information and the token identification information to at least one node of the blockchain network.

[0027] The method may further include the one or more processors receiving a request to transmit posting information for the date from the external device, generating token list information regarding a plurality of tokens registered to correspond to the date, 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 regarding each of the plurality of tokens.

[0028] According to another aspect of the present disclosure, a method performed by an electronic device may be provided, the method being performed by an electronic device including one or more processors and one or more memories storing at least one instruction executed by the one or more processors, the one or more processors may include transmitting a token registration request for a date to an external device, receiving approval information for the registration request from the external device in response to the registration request and information stored in at least one node of a blockchain network, receiving posting information related to the date from the external device, the posting information including display attributes of an item corresponding to the token, and displaying the item on a display of the electronic device according to the display attributes, the registration request may include date indication information indicating the date, and token identification information identifying the token.

[0029] The display attributes are determined based on the date indication information, and may include at least one of a display priority of the item, a display position of the item, and a display size of the item.

[0030] The method may further include the one or more processors transmitting a request to transmit posting information for the date to the external device, and receiving the posting information from the external device in response to the transmission request, wherein the posting information may be generated based on token list information regarding a plurality of tokens registered to correspond to the date, and may include information regarding each of the plurality of tokens.

[0031] According to another aspect of the present disclosure, an electronic device may include one or more processors and one or more memories storing at least one instruction executed by the one or more processors, wherein the one or more processors may be configured to receive a registration request for a first token associated with an object from the external device, register the first token to be locked up for a predetermined period of time based on the registration request, determine a second token owned by an owner of the first token based on information about the first token, and transmit information about the second token to the owner. Effect of the Invention

[0032] In accordance with at least one embodiment of the present disclosure, a user who purchases a token that can be registered to correspond to one specific date can be prevented from registering the token to multiple specific dates.

[0033] According to at least one embodiment of the present disclosure, it is possible to prevent an area for a specific date on a calendar screen displayed on a user terminal from being filled with a specific object corresponding to a token.

[0034] According to at least one embodiment of the present disclosure, a user can easily grasp historical information regarding a particular subject.

[0035] According to at least one embodiment of the present disclosure, a user who registers a token to correspond to a particular date may optionally change the registered token to another token.

[0036] These and other aspects, features and advantages of particular embodiments of the present invention will become more apparent from the following description and accompanying drawings. [Brief description of the drawings]

[0037] [Figure 1]FIG. 1 is a diagram showing a system including a server, a user terminal, a blockchain network, and a communication network according to one embodiment of the present disclosure. [Diagram 2] FIG. 2 is a block diagram of a server according to one embodiment of the present disclosure. [Diagram 3] FIG. 3 is a block diagram of a user terminal according to one embodiment of the present disclosure. [Figure 4] FIG. 4 is a conceptual diagram of a blockchain network according to one embodiment of the present disclosure. [Diagram 5] FIG. 5 is a flow chart illustrating the operation of a server for processing a registration request for a specific token for a specific date received from a user terminal according to one embodiment of the present disclosure. [Figure 6] FIG. 6 is a flow diagram illustrating a method for a server to process a registration request for a particular token for a particular date received from a user terminal, according to another embodiment of the present disclosure. [Figure 7] FIG. 7 is a flowchart illustrating an operation of a server that processes a registration request for a specific token for a specific person received from a user terminal according to another embodiment of the present disclosure. [Figure 8] FIG. 8 is a flowchart illustrating an operation of a server that processes a request for transmitting posting information received from a user terminal according to an embodiment of the present disclosure. [Figure 9a] FIG. 9a is a diagram illustrating an example of a screen that may be displayed when bulletin information according to an embodiment of the present disclosure is displayed through an output unit of a user terminal. [Figure 9b] FIG. 9b is a diagram illustrating an example of a screen that may be displayed when bulletin information is displayed through an output unit of a user terminal according to another embodiment of the present disclosure. [Figure 9c] FIG. 9c is a diagram illustrating an example of a screen that may be displayed when bulletin information is displayed through an output unit of a user terminal according to still another embodiment of the present disclosure. [Figure 9d] FIG. 9d is a diagram illustrating an example of a screen that may be displayed when bulletin information is displayed through an output unit of a user terminal according to still another embodiment of the present disclosure. [Figure 10] FIG. 10 is a flow chart illustrating the operation of a server for processing information indicating a specific object received from a user terminal according to one embodiment of the present disclosure. [Figure 11] FIG. 11 is a flow chart illustrating an operation of a server for processing an exchange request received from a user terminal according to one embodiment of the present disclosure. [Figure 12] FIG. 12 is a flow diagram illustrating a method for processing a replacement request of a user terminal according to another embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0038] The various examples described in this document are exemplified for the purpose of clearly explaining the technical idea of ​​the present disclosure, and are not limited to a specific embodiment. The technical idea of ​​the present disclosure may include various modifications, equivalents, alternatives, and embodiments in which all or part of each embodiment is selectively combined. In addition, the scope of the technical idea of ​​the present disclosure is not limited to the various embodiments presented below and the specific description thereof.

[0039] Terms used in this document, including technical or scientific terms, may have the meaning commonly understood by one of ordinary skill in the art to which this disclosure belongs, unless defined differently.

[0040] As used in this document, the terms "including," "may include," "include," "may comprise," "can comprise," "have," "can have," and the like refer to the presence of a subject feature (e.g., a function, operation, or component) and do not preclude the presence of other additional features, i.e., such terms should be understood as open-ended terms that include the possibility of including other embodiments.

[0041] As used in this document, singular terms may include plural meanings unless the context indicates otherwise, and this also applies to singular terms recited in the claims.

[0042] As used herein, the terms "first", "second", "first", "second", and the like, unless otherwise indicated in the context, are used to distinguish one object from another when referring to multiple similar objects, and do not limit the order or importance of the objects. For example, users included in a plurality of users according to the present disclosure may be distinguished from one another by being represented as a "first user" and a "second user". Also, a plurality of tokens according to the present disclosure may be distinguished from one another by being represented as a "first token" and a "second token". Also, one or more date attribute groups according to the present disclosure may be distinguished from one another by being represented as a "first date attribute group" and a "second date attribute group".

[0043] As used in this document, phrases 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" may refer to the listed items or to all possible combinations of the listed items. For example, "at least one of A or B" may refer to any of (1) at least one A, (2) at least one B, or (3) at least one A and at least one B.

[0044] The term "module" as used in this disclosure means software or hardware components such as field-programmable gate arrays (FPGAs) and application specific integrated circuits (ASICs). However, "module" is not limited to hardware and software. A "module" may be configured to reside on an addressable storage medium and to execute on one or more processors. In one embodiment, a "module" may include components such as software components, object-oriented software components, class components, and task components, as well as processors, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables.

[0045] As used in this disclosure, the phrase "based on" is used to describe one or more factors that influence the decision, judgment, act, or behavior described in the phrase or sentence in which it is included, and does not exclude additional factors that influence the decision, judgment, act, or behavior.

[0046] As used in this document, the expression that a component (e.g., a first component) is "coupled" or "connected" to another component (e.g., a second component) may mean not only that the one component is directly coupled or connected to the other component, but also that the one component is coupled or connected via a new other component (e.g., a third component).

[0047] The expression "configured to" used in this document may have the meanings of "set to," "capable of," "modified to," "made to," "capable of," etc., depending on the context. The expression is not limited to the meaning of "specially designed in terms of hardware." For example, a processor configured to perform a specific operation may mean a generic purpose processor that can perform the specific operation by executing software, or a special purpose computer that is structured through programming to perform the specific operation.

[0048] Hereinafter, various embodiments of the present disclosure will be described with reference to the accompanying drawings. In the accompanying drawings and the description of the drawings, identical or substantially equivalent components may be given the same reference numerals. In addition, in the following description of various embodiments, repeated descriptions of identical or corresponding components may be omitted, but this does not mean that the components are not included in the embodiments.

[0049] FIG. 1 is a diagram showing 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 present disclosure. The server (100), the user terminal (200), and at least one node (310) included in the blockchain network (300) can exchange information with each other via the communication network (400) using the non-fungible token management technology of the present disclosure. The calendar in this specification may be displayed on the server (100), the user terminal (200), or other electronic device by software or an application running on the device. The calendar may include information regarding at least one date.

[0050] The server (100) may be an electronic device of a service provider. The service provider may be an operator of a service that provides a calendar using the non-fungible token management technology of the present disclosure. The server (100) is an electronic device that transmits information or provides services to a user terminal (200) connected by wire or wirelessly, and may be, for example, an application server, a proxy server, a cloud server, etc.

[0051] The user terminal 200 may be a terminal of a user who uses the above-mentioned calendar providing service. The user terminal 200 may be, for example, at least one of a smartphone, a tablet computer, a personal computer (PC), a mobile phone, a personal digital assistant (PDA), an audio player, and a wearable device.

[0052] When describing the configuration or operation of an apparatus in this disclosure, the term "apparatus" is used to refer to the apparatus being described, and the term "external apparatus" is used to refer to an apparatus that exists outside the apparatus being described. For example, when the server (100) is described as an "apparatus", the user terminal (200) may be called an "external apparatus" from the viewpoint of the server (100). Also, when the user terminal (200) is described as an "apparatus", the server (100) may be called an "external apparatus" from the viewpoint of the user terminal (200). That is, the server (100) and the user terminal (200) may be called an "apparatus" and an "external apparatus", respectively, or an "external apparatus" and an "apparatus", respectively, depending on the viewpoint of the subject of the operation.

[0053] The blockchain network (300) may include at least one node (310) that manages the blockchain. Each of the at least one node included in the blockchain network (300) may be an independent electronic device that can process operations necessary to manage or operate the blockchain. At least some of the operations of the non-fungible token management technology of the present disclosure may be performed by a smart contract recorded in the blockchain. To this end, the server (100) or the user terminal (200) may exchange information with at least one node included in the blockchain network (300).

[0054] The communication network 400 may include any 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 Universal Serial Bus (USB), a High Definition Multimedia Interface (HDMI), a Recommended Standard-232 (RS-232), or a Plain Old Telephone Service (POTS) communication network. The wireless communication network may include, for example, communication networks using methods such as eMBB (enhanced Mobile Broadband), URLLC (Ultra Reliable Low-Latency Communications), MMTC (Massive Machine Type Communications), LTE (Long-Term Evolution), LTE-A (LTE Advance), 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 (Bluetooth), NFC (Near Field Communication), GPS (Global Positioning System), or GNSS (Global Navigation Satellite System). The communication network (400) in this specification is not limited to the above examples and may include, without limitation, various types of communication networks that allow data to be exchanged between multiple entities or devices.

[0055] FIG. 2 is a block diagram of a server (100) according to an embodiment of the present disclosure. The server (100) may include one or more processors (110), communication interfaces (120), or memories (130) as components. In some embodiments, at least one of the components of the server (100) may be omitted, or other components may be added to the server (100). In some embodiments, in addition, or in alternative to, some components may be integrated or embodied in one or more individual components. At least some of the components inside or outside the server (100) may be connected via a bus, a general purpose input / output (GPIO), a serial peripheral interface (SPI), or a mobile industry processor interface (MIPI), etc., to transmit data or signals.

[0056] One or more processors (110) may be referred to as processor (110). The term processor (110) may refer to a collection of one or more processors, unless otherwise clearly indicated in the context. The processor (110) may run software (e.g., instructions, programs, etc.) to control at least one component of the server (100) coupled to the processor (110). The processor (110) may also perform various operations such as calculations, processing, data generation or processing, etc. The processor (110) may also load data, etc. from the memory (130) or store data, etc. in the memory (130).

[0057] The communication interface 120 can perform wireless or wired communication between the server 100 and another device (e.g., the user terminal 200 or another server). For example, the communication interface 120 can perform wireless communication using eMBB, URLLC, MMTC, LTE, LTE-A, NR, UMTS, GSM, CDMA, WCDMA, WiBro, WiFi, Bluetooth, NFC, GPS, or GNSS. For example, the communication interface 120 can perform wired communication using Universal Serial Bus (USB), High Definition Multimedia Interface (HDMI), Recommended Standard-232 (RS-232), or Plain Old Telephone Service (POTS).

[0058] The memory (130) may store various data. The data stored in the memory (130) may include software (e.g., instructions, programs, etc.) as data acquired, processed, or used by at least one component of the server (100). The memory (130) may include volatile or non-volatile memory. The term memory (130) may refer to one or more sets of memories, unless the context clearly indicates otherwise. As used herein, the terms "set of instructions stored in the memory (130)" or "programs stored in the memory (130)" may refer to an operation system for controlling resources of the server (100), an application, or middleware that provides various functions to an application so that the application can utilize the resources of the server (100). In one embodiment, when the processor (110) performs a particular operation, the memory (130) may store instructions corresponding to the particular operation performed by the processor (110).

[0059] In one embodiment, the server 100 may transmit data corresponding to the calculation results of the processor 110, data received via the communication interface 120, or data stored in the memory 130 to an external device. The external device may be a device for displaying, displaying, or outputting the received data.

[0060] 3 is a block diagram of a user terminal (200) according to an embodiment of the present disclosure. The user terminal (200) may include one or more processors (210), a communication interface (220), or a memory (230) as components. The user terminal (200) may further include at least one of an input unit (240) or an output unit (250).

[0061] The processor (210) may run software (e.g., instructions, programs, etc.) to control at least one component of the user terminal (200) coupled to the processor (110). The processor (210) may also perform various operations such as calculations, processing, data generation or processing, etc. The processor (210) may also load data, etc. from the memory (230) or store data, etc. in the memory (230).

[0062] The communication interface 220 can perform wireless or wired communication between the user terminal 200 and another device (e.g., the server 100 or another user terminal). For example, the communication interface 220 can perform wireless communication using eMBB, URLLC, MMTC, LTE, LTE-A, NR, UMTS, GSM, CDMA, WCDMA, WiBro, WiFi, Bluetooth, NFC, GPS, or GNSS. For example, the communication interface 220 can perform wired communication using USB, HDMI, RS-232, or POTS.

[0063] The memory (230) may store various data. The data stored in the memory (230) may include software (e.g., instructions, programs, etc.) as data acquired, processed, or used by at least one component of the user terminal (200). The memory (230) may include volatile or non-volatile memory. The term memory (230) may refer to one or more sets of memories, unless the context clearly indicates otherwise. As used herein, the terms "set of instructions stored in the memory (230)" or "programs stored in the memory (230)" may refer to an operation system for controlling resources of the user terminal (200), an application, or middleware that provides various functions to an application so that the application can utilize resources of the user terminal (200), etc. In one embodiment, when the processor (210) performs a particular operation, the memory (230) may store instructions corresponding to the particular operation performed by the processor (210).

[0064] 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 an external source to at least one component included in the user terminal 200. For example, the input unit 240 may include a mouse, a keyboard, or a touchpad.

[0065] In one embodiment, the user terminal (200) may further include an output unit (250). The output unit (250) may display (output) or transmit (send) information processed by the user terminal (200) to the outside. For example, the output unit (250) may visually display information processed by the user terminal (200). The output unit (250) may display UI (User Interface) information or GUI (Graphic User Interface) information. In this case, the output unit (250) may include at least one of a Liquid Crystal Display (LCD), a Thin Film Transistor-Liquid Crystal Display (TFT-LCD), an Organic Light-Emitting Diode (OLED), a Flexible Display, a 3D Display, and an E-ink Display. Also, for example, the output unit (250) may audibly display information processed by the user terminal (200). The output unit (250) may display audio data in any audio file format (e.g., 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. For example, the output unit (250) may also transmit information processed in the user terminal (200) to an external output device. The output unit (250) may transmit or send information processed in the user terminal (200) to an external output device using the communication interface (220). The output unit (250) may also transmit or send information processed in the user terminal (200) to an external output device using a separate output communication interface.

[0066] FIG. 4 is a conceptual diagram of a blockchain network (300) according to an embodiment of the present disclosure. In the present disclosure, a block may refer to a specific material type. In addition, in the present disclosure, a blockchain may refer to a material structure in which one or more blocks (331, 333, 335) are linked in the form of a chain. One or more blocks (331, 333, 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 various nodes. Each of the one or more blocks (331, 333, 335) may include a block hash, a block header, or a block body. The block hash is unique information that can identify a block, and may be, for example, a character string represented by 256 bits. The block header may include at least one of the following: software or protocol version information, a hash of the previous block according to the order of block concatenation on the blockchain, a Merkle root, time information indicating the time when the block was generated, bits indicating the difficulty of calculation, and a nonce, which is a value required for mining operations to add a new block to the blockchain. The block body may include at least one transaction. A transaction may be a unit of information stored in the block body as a collection of data having a specific material structure. A transaction may include information regarding the generation or trading of tokens. For example, a transaction may be information that "a first node included in the blockchain network (300) transmits a virtual currency token to a second node". As another example, a transaction may be information that "a first node included in the blockchain network (300) transmits an NFT (Non-Fungible Token) to a second node".

[0067] The blockchain may be managed by a blockchain network (300) including at least one node. Each of the at least one node included in the blockchain network (300) may be referred to as a "participant" of the blockchain network (300). The at least one node included in the blockchain network (300) may be operated in a hierarchical structure. The hierarchical structure may include, for example, at least one of a data layer that defines a structure of data handled by the blockchain network (300) and manages the data, a consensus layer that verifies the validity of blocks, performs mining to generate blocks, and is responsible for processing fees paid to miners in the mining process, a common layer that realizes or manages a P2P network protocol, a hash function, a digital signature, encoding, and a common storage medium, or an application layer in which various applications are generated or processed.

[0068] 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) may perform a function of verifying a transaction transmitted to the blockchain network (300) through a blockchain consensus algorithm, and, when the verification is completed, recording the verified transaction in a block on the blockchain. The consensus algorithm performed by the blockchain network (300) may include at least one of a Proof of Work (PoW) algorithm, a Proof of Stake (PoS) algorithm, a Delegated Proof of Stage (DPoS) algorithm, a Practical Byzantine Fault Tolerance (PBFT) algorithm, a Delegated Byzantine Fault Tolerance (DBFT) algorithm, a Redundant Byzantine Fault Tolerance (RBFT) algorithm, a Sieve algorithm, a Tendermint algorithm, a Paxos algorithm, a Raft algorithm, a Proof of Authority (PoA) algorithm, or a Proof of Elapsed Time (PoET) algorithm.

[0069] At least one node included in the blockchain network (300) may each store a smart contract. Through this, at least one node included in the blockchain network (300) may share the same smart contract. In addition, the smart contract may be recorded in a block on the blockchain managed by the blockchain network (300).

[0070] A smart contract may be a document or script written in a programming language such as Solidity, and may be a program or application that runs on a virtual machine executed by at least one node included in the blockchain network (300). A smart contract may be created to perform a specific action if a specific condition is met. In this case, the specific condition may be, for example, a condition in which a specific type of token is input or a file in a specific format is input. In addition, the specific action may be, for example, an action such as transmitting a specific type of token to any node in the blockchain network (300).

[0071] A smart contract may be created according to a certain set of rules (or protocols). For example, a smart contract may be created that includes one or more functions corresponding to the ERC-20 or ERC-721 protocol, respectively. However, various types of smart contracts may be created by including other functions not included in the example protocols (for example, one or more functions corresponding to ERC-1155).

[0072] The token in this disclosure is a token used on a blockchain managed by a blockchain network (300), and may be a virtual currency token (or a fungible token) or a non-fungible token (NFT). A "non-fungible token" may mean a virtual token generated by a smart contract created with reference to certain rules (e.g., ERC-721 or ERC-1155). The integrity of this non-fungible token can be maintained by being recorded in a blockchain, which is a distributed storage, and the existence of a specific type of data can be guaranteed by generating this non-fungible token to include a specific type of data. Hereinafter, in this disclosure, an object simply referred to as a "token" may be an NFT unless otherwise indicated in the context.

[0073] A token may be a data set including a specific type of data. In a specific embodiment, the token may include at least one of information for accessing a digital file linked to the token (hereinafter also referred to as a "Uniform Resource Identifier (URI) of the digital file"), information for accessing metadata of the token (hereinafter also referred to as a "URI of the metadata"), or information on the current owner of the token (e.g., the address of the current owner node of the token on the blockchain). In another embodiment, the token may further include a digital file linked to the token or metadata of the token. However, in the following specification, for convenience of explanation, it is assumed that the token includes the URI of the digital file or the URI of the metadata.

[0074] The URI of the digital file linked to the token may be the address of a centralized server or a cloud server where the digital file is stored. Alternatively, the URI of the digital file may be a hash value (e.g., "ipfs.io / ipfs / 12345678") of the digital file stored on an InterPlanetary File System (IPFS) that distributes and stores files on various devices. The digital file accessed through the URI of the digital file may be, for example, an image file, a video file, or a music file. Hereinafter, the expression "digital file linked to a token" in this specification refers to a digital file obtained through the URI of the digital file recorded in the token, and is used interchangeably with expressions such as "digital file owned by a token." The token according to the present disclosure may be associated with a specific object. The expression "the token is associated with a specific object" may be an expression indicating the relationship between the token and the specific object when the digital file linked to the token is a digital file of a specific object (e.g., an image or video taken of a specific object, or music composed by a specific object). The particular subject may be a real person, such as a celebrity or famous person, a fictional person, such as a character, or a group of such people, or may be an animal, such as a puppy or a cat.

[0075] The URI of the token metadata may be an address of a centralized server or a cloud server where the token metadata is stored. It may also be a hash value of the metadata stored on IPFS. The token metadata may refer to a data set including various information related to the token. The metadata may include at least one of the following: the name of the token, token identification information (hereinafter also referred to as "token ID"), the name of a specific object associated with the token, the time of token generation, the current owner information of the token, the change history of the token owner, or information for accessing a digital file linked to the token (i.e., the URI of the digital file described above). In various embodiments, the token metadata may further include a date attribute group including at least one date attribute related to the token, or token group information indicating one or more token groups to which the token belongs. When any metadata is represented in JSON (JavaScript Object Notation) format, the metadata may be exemplarily represented as {"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"}. As an example of the above metadata, "Name" may be a key value indicating the name of the token, "Image URI" may be a key value indicating the URI of the digital file, "Token ID" may be 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 the token group information of the token.In the following specification, the expression "first information contained in the metadata of a token" may be expressed as "first information possessed by a token" or "first information contained in a token" for convenience of explanation.

[0076] A token according to the present disclosure may belong to one or more token groups. The token group information corresponding to the token may include information indicating one or more token groups to which the token belongs (e.g., a character string of the name of the token group). For example, if the first token is a token generated to correspond to person A, the token group information corresponding to the first token may include information indicating "person A's token group". Also, if the first token is a token generated to correspond to team B, the token group information corresponding to the first token may include information indicating "team B token group". Also, if the first token is a token generated to correspond to person C, and person C is a person who belongs to team D consisting of multiple people, the first token may belong to "person C's token group" and at the same time, to "team D's token group". In this case, the token group information corresponding to the first token may include information indicating "person C's token group" and information indicating "team D's token group". The 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.

[0077] Tokens according to the present disclosure may be managed by a smart contract. In the present disclosure, the phrase "tokens are managed by a smart contract" may refer generically to various actions such as tokens being generated by a smart contract, tokens being transferred from one user's address to another user's address, or tokens being burned. Smart contracts may include various types of functions.

[0078] A smart contract may be created according to a certain protocol (or protocol). For example, a smart contract created according to any first protocol (e.g., ERC-20) may include a function that returns the total supply of cryptocurrency tokens. A smart contract created according to the first protocol may include a function that takes an address on the blockchain of a particular node and returns the amount of cryptocurrency tokens held by the address. A smart contract created according to the first protocol may include a function that takes a number of any cryptocurrency tokens and an address on the blockchain of a node that will receive the cryptocurrency tokens, and transmits the cryptocurrency tokens to the address of the receiving node. A smart contract created according to the first protocol may include a function that takes a quantity of any cryptocurrency tokens, an address on the blockchain of a node that will send the cryptocurrency tokens, and an address on the blockchain of a node that will receive the cryptocurrency tokens, and transmits the cryptocurrency tokens from the address of the sending node to the address of the receiving node. A smart contract created according to the first protocol may include a function that returns whether withdrawal is allowed to limit the number of cryptocurrency tokens that can be withdrawn. Additionally, a smart contract created in accordance with the first protocol may include a function that returns the remaining amount available for withdrawal.

[0079] In addition, a smart contract created in accordance with any second protocol (e.g., ERC-721) may include a function (hereinafter also referred to as a "token generation function") that generates a token (e.g., an NFT) based on one or more pieces of information received from a specific node. For example, the token generation function may obtain a URI of a specific digital file received from a specific node and an address on the blockchain of an arbitrary node, and generate a token corresponding to the URI of the digital file. When a token is generated by the token generation function, the owner information of the token may be determined by the address on the blockchain of an arbitrary node inputted in the token generation function. The token generation function may also generate a token by additionally obtaining one or more pieces of information included in the token metadata (e.g., the name of the token or a date attribute group including at least one date attribute related to the token, etc.). In this disclosure, the expression "generating an NFT" is used interchangeably with the expression "minting an NFT". In addition, a smart contract created in accordance with the second protocol may include a function that obtains an address on the blockchain of an arbitrary node and returns the number of tokens held by the address. A smart contract created in accordance with the second protocol may include a function that obtains the token ID of any token and returns owner information of the token. A smart contract created in accordance with the second protocol may include a function that obtains the address of any node on the blockchain and the token ID of any token, and grants the node the authority to transmit a token having the token ID. A smart contract created in accordance with the second protocol may include a function that obtains the token ID of any token, and returns the addresses on the blockchain of one or more nodes that have the authority to transmit the token.

[0080] The description of smart contracts created in accordance with the above-mentioned First and Second Terms is merely for illustrative purposes of the functions included in the smart contracts and does not limit the present disclosure, and smart contracts according to the present disclosure may include various types of smart contracts that include at least one function associated with a token, for example at least one of the functions described above for the above-mentioned first and second protocols.

[0081] Hereinafter, with reference to FIG. 5 and FIG. 6, an embodiment in which the server (100) receives a registration request for a specific token for a specific date from the user terminal (200) will be described.

[0082] FIG. 5 is a flowchart of the operation of the server (100) for processing a registration request for a specific token for a specific date received from a user terminal (200) according to an embodiment of the present disclosure. The server (100) may receive a registration request for a specific token for a specific date from the user terminal (200) (S510). In the present disclosure, the "registration request for a specific token for a specific date" may include date designation information designating a specific date and token identification information (e.g., a token ID) identifying a specific token, for example, as an HTTP (Hyper Text Transfer Protocol) request. The specific date is any date including values ​​of year, month, and day, and may be identified by the date designation information included in the registration request. The date designation information may be a character string indicating a date. For example, the registration request for a specific token for a specific date may include date designation information indicated as "2022-07-15" and a token ID expressed in hexadecimal, such as "0xA024ED". In one embodiment, the registration request for a specific token for a specific date may further include memo information. The memo information may include a character string having a specific length, such as "Let's hope BTS's new album is a big hit!". For the sake of convenience, the specific date indicated by the date indication information included in the registration request for a specific token for a specific date may be referred to as the "desired registration date." In addition, the time when the server (100) receives the registration request transmitted from the user terminal (200) may be referred to as the "time of receipt of the registration request."

[0083] 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" may mean that the server (100) generates information indicating that the specific token has been registered to correspond to a specific date by associating the specific token with a specific date (hereinafter, also referred to as "token-date registration information"). That is, the date included in the registration request acceptance time and the desired registration date may be independent dates that are unrelated to each other. For example, if a registration request for a first token for January 1, 2023 (desired registration date) arrives at the server (100) at 1:10:30 p.m. on July 1, 2022, the server (100) may associate the first token with January 1, 2023, which is the desired registration date, immediately after receiving the registration request or within a certain period of time, and generate information indicating that the first token has been registered to correspond to January 1, 2023. Hereinafter, when the server (100) registers a specific token to correspond to a specific date based on a registration request, the specific date indicated by the date indication information included in the registration request may be referred to as the "registration date." In addition, for convenience of explanation, the expression "a token is registered to correspond to a specific date" is used interchangeably with expressions such as "a token is registered on a specific date."

[0084] The token-date registration information may include at least one of the registration date (or the desired registration date), the token ID of the token requested to be registered, the time of receipt of the registration request, or memo information included in the registration request. For example, the token-date registration information may be exemplarily shown as {"Registration date": "2022-08-15", "Token ID": "0x123456", "Time of receipt of registration request": "2022-07-01 18:30:00", "Memo": "My favorite!"}. The token-date registration information may further include the time when the registration started. The time when the registration started may be set to the same time as the time when the registration request was received. The time when the registration started is a point in time after the time when the registration request was received, and may be set to at least one of the time when the token is registered to correspond to a specific date, the time when the token-date registration information is generated, or the time when the token-date registration information is recorded in a block on the blockchain.

[0085] The token-date registration information may be recorded in any storage medium. The token-date registration information may be stored in the memory (130) of the server (100) or recorded on the blockchain. In an embodiment in which the token-date registration information is stored in the memory (130) of the server (100), the processor (110) may store in the memory (130) the token-date registration information generated based on the registration request. For example, if the server (100) receives a registration request to register token A to correspond to January 1, 2023, the processor (110) may store in the memory (130) the token-date registration information including the token ID of token A and the registration date of token A (i.e., January 1, 2023).

[0086] In an embodiment in which the token-date registration information is recorded on the blockchain, the processor (110) may transmit the token-date registration information generated based on the registration request to at least one node of the blockchain network (300). As a result, the fact that a particular token was registered on a particular date may be recorded in a block on the blockchain. For example, if the server (100) receives a registration request to register token A to correspond to January 1, 2023, the processor (110) may generate token-date registration information including the token ID of token A and the registration date of token A (i.e., January 1, 2023) and transmit a transaction including the generated token-date registration information to at least one node of the blockchain network (300). The blockchain network (300) may verify the received transaction, and when the verification is completed, record the transaction including the token-date registration information in a block on the blockchain.

[0087] Meanwhile, the server (100) may receive a deregistration request for a specific token registered to correspond to a specific date from the user terminal (200). The server (100) may deregister the token registered to correspond to a specific date based on the deregistration request. The "deregistration request" may include token identification information that identifies the specific token. In addition, 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."

[0088] In this specification, the expression "a specific token registered to correspond to a specific date is deregistered" may mean that the token-date registration information stored in the memory (130) of the server (100) is deleted, or information indicating that the registration of a specific token for a specific date has been deregistered (hereinafter also referred to as "token-date deregistration information") is recorded in a block on the blockchain managed by the blockchain network (300). Specifically, when the token-date registration information is stored in the memory (130) of the server (100) and the server (100) receives a request to deregister a first token for a specific date, the processor (110) may delete the token-date registration information indicating the fact that the first token was registered to correspond to a specific date from the memory (130).

[0089] In addition, when the server (100) receives a request to deregister a first token for a specific date while the token-date registration information is recorded on the blockchain, the processor (110) may transmit the token-date deregistration information to at least one node of the blockchain network (300). The 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. In this case, the "transaction information of the corresponding token-date registration information" may refer to a unique ID of a transaction including the existing token-date registration information for the token for which deregistration is requested. For example, the token-date deregistration information may be exemplarily shown as follows: {"Token ID":"0x123456", "Deregistration request receipt time":"2022-07-02 15:30:00", "Transaction information":"0e3e2357e806b6cdb1f70b54c3a3a17b6714ee1f0e69bebb"}.

[0090] In various embodiments according to the present disclosure, a token may be locked up for a specific period after it is registered. In this specification, the expression "a token is locked up for a specific period after it is registered" may mean that it is not possible to deregister the token, transfer ownership of the token, or burn the token before a specific period has elapsed from the time when the token registration began. Hereinafter, a token that is locked up for a specific period after it is registered may be referred to as a "token in a locked-up state" for convenience.

[0091] The lock-up state of a token in a locked-up state may be released when a certain condition is met. In one embodiment, the condition for releasing the lock-up state (hereinafter also referred to as the "lock-up release condition") may be a condition that is met when a certain period for releasing the lock-up has passed from the time when registration began. For example, assume that the certain period for releasing the lock-up is three months, and the token-date registration information of a first token registered to correspond to a certain date is as follows: {"Registration date": "2022-08-15", "Token ID": "0x123456", "Registration request acceptance time": "2022-07-01 18:30:00", "Registration start time": "2022-07-01 18:31:00"}. In this case, the first token is in a locked-up state from the start of registration (July 1, 2022, 6:31:00 PM) until before October 1, 2022, 6:31:00 PM, three months after the start of registration, and may not be unlocked. That is, if the server (100) receives a request for deregistration of the first token, a request for transferring ownership of the first token, a request for burning the first token, etc. from the user terminal (200) before October 1, 2022, 6:31:00 PM, the processor (110) may reject the processing of the received request and transmit rejection information to the user terminal (200).

[0092] When data or information is stored and managed in a server using a centralized database according to conventional database management methods, the burden on the server's storage space increases, and data or information may be leaked or damaged due to hacking or server attacks. Furthermore, since a normal server is managed by a single entity, such data or information may be changed by the entity, which may reduce the reliability of the information. However, according to the present disclosure, when the server (100) manages tokens using blockchain technology, token-related information is managed by the blockchain network (300), which strengthens security, reduces the burden on the server's storage space, and improves the reliability of the information. As a result, improvements in database-related technologies may be made.

[0093] 6 is a flow diagram illustrating a method in 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 present disclosure. When the server 100 receives a registration request for 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.

[0094] The server (100) may receive a registration request for a particular token for a particular date from the user terminal (200) (S610). The processor (110) may then obtain a first date attribute group for the particular token for which registration is requested (S620). A token according to the present disclosure may be associated with a date attribute group including at least one date attribute. A "date attribute" associated with a token may be information indicating a date for which a registration request can be made for the token. For example, a 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 can only be registered for one of the dates "2013-06-12", "2013-09-11", or "2014-02-12" included in the first date attribute group.

[0095] The date attribute group including at least one date attribute for the token may be recorded in any storage medium. The date attribute group may be stored in the memory (130) of the server (100) or may be stored in the metadata of the token. In an embodiment in which the date attribute group for the token is stored in the memory (130) of the server (100), the processor (110) may obtain the first date attribute group for the specific token from the memory (130). In another embodiment in which the date attribute group for the token is included in the metadata of the token, the processor (110) may obtain the first date attribute group for the specific token requested for registration from at least one node of the blockchain network (300). Specifically, the processor (110) may transmit a request for a function call or a transaction to at least one node of the blockchain network (300) to inquire about the first date attribute group including at least one date attribute for the specific token, thereby obtaining the first date attribute group for the specific token.

[0096] Next, the processor (110) may determine whether a specific date indicated by the date indication information included in the registration request (i.e., the desired registration date) 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, if 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-01", the processor (110) may determine through calculation that the desired registration date does not match all of the date attributes included in the first date attribute group, and transmit rejection information for the registration request to the user terminal (200).

[0097] In the case where the token-date registration information is recorded on the blockchain, if it is determined that the desired registration date matches any one of at least one date attribute included in the first date attribute group, the processor (110) may transmit the date indication information and the token identification information included in the registration request to at least one node of the blockchain network (300) (S640). In this case, the blockchain network (300) may record information indicating that the token having the token identification information has been registered to correspond to the date indicated by the date indication information (i.e., the 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) before or after step S640 (S650). The processor (110) may also transmit approval information for the registration request to the user terminal (200) simultaneously with step S640. For example, if 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-01," the processor (110) may determine through calculation that the desired registration date matches one of the date attributes included in the first date attribute group, transmit the date indication information and token identification information included in the registration request to at least one node in the blockchain network (300), and transmit approval information for the registration request to the user terminal (200).

[0098] In the case of an embodiment in which the token-date registration information is stored in the memory 130 of the server 100, if it is determined that the desired registration date matches any one of at least one date attribute included in the first date attribute group, instead of the above-mentioned step S640, the processor 110 may generate information (token-date registration information) indicating that a token having the token identification information has been registered corresponding to the date indicated by the date indication information, and store the generated token-date registration information in the memory 130. Thereafter, the processor 110 may transmit approval information for the registration request to the user terminal 200.

[0099] The date attribute group for a token according to the present disclosure may be modified. For example, assume that a particular object associated with a token is singer A. In this case, if singer A releases a new album, a date attribute indicating the new album release date may need to be added to the date attribute associated with the token. Also, if a token for singer A already includes a date attribute indicating the new album release date, but the new album release date changes, the date attribute indicating the new album release date may need to be deleted or modified. Therefore, various embodiments in which a date attribute group including at least one date attribute associated with a token is modified will be described below.

[0100] In an embodiment where a date attribute group for a token is stored in the memory (130) of the server (100), the processor (110) may modify the date attribute group stored in the memory (130). Specifically, when a first token and a first date attribute group including at least one date attribute are stored in the memory (130) in correspondence with each other, the processor (110) may modify at least one date attribute of the first date attribute group to have a different date. The processor (110) may also add a new date attribute to the first date attribute group or delete at least one date attribute of the first date attribute group.

[0101] In another embodiment, where a date attribute group for a token is included in the token 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) may generate a second date attribute group including a date attribute different from the at least one date attribute included in the first date attribute group. For example, the second date attribute group may include a date attribute different from the at least one date attribute included in the first date attribute group by further including a new date attribute for the first date attribute group or by not including the at least one date attribute included in the first date attribute group. The processor (110) may transmit a request to generate a second token to at least one node of the blockchain network (300). The request to generate the second token may include information about the first token (e.g., a token ID of the first token) and the second date attribute group. The blockchain network (300) that receives the request to generate a second token may acquire metadata of the first token corresponding to the existing token based on the token ID of the first token included in the request to generate a second token, change the first date attribute group included in the metadata of the first token to a second date attribute group, and generate a second token based on the changed metadata. Through this, the second token, which is a new token, may have the same information as the first token, which is an existing token, except for the first date attribute group, but may have a token having the second date attribute group, which is a changed date attribute group, instead of the first date attribute group.

[0102] FIG. 7 is a flowchart of the operation of the server (100) for processing a registration request for a specific token associated with a specific object received from a user terminal (200) according to another embodiment of the present disclosure. The server (100) may receive a registration request for a first token associated with a specific object from the user terminal (200) (S710). The first token for which registration is requested may be a token that has already been generated to be associated with a specific object. That is, the digital file held by the first token associated with person A may be an image, video, etc., of person A. In one embodiment, the "registration request for the first token associated with a specific object" may include, for example, token identification information (e.g., a token ID) that identifies the specific token. In another embodiment, the "registration request for the first token associated with a specific object" may further include date designation information that designates a specific date, similar to the above-described "registration request for a specific token for a specific date."

[0103] Next, the server (100) may register the first token to be locked up for a specific period based on the registration request received from the user terminal (200) (S720). The specific period for which the registered first token is locked up may be, for example, one month, three months, or one year. The first token that is locked up for a specific period may be unable to be deregistered, the token ownership may be transferred, or the token may be burned before the specific period has elapsed. In this specification, the expression "a specific token is registered to be locked up for a specific period" may mean that the server (100) generates information indicating that a specific token (first token) has been locked up (hereinafter, also referred to as "token-lockup registration information"). For example, if the registration of the first token associated with person A begins at 1:10:30 PM on July 1, 2022, and the specific period for which the first token is locked up is one year, the server (100) may generate information indicating that the first token is locked up until 1:10:30 PM on July 1, 2023, one year after the registration of the first token begins. The token-lockup registration information may be recorded in any storage medium, similar to the token-date registration information described above. For example, the token-lockup registration information may be recorded in the memory (130) of the server (100) or on the blockchain.

[0104] Next, the server (100) may determine a second token to be owned by the owner of the first token based on the information about the first token registered to be locked up (S730). Specifically, the processor (110) may determine a second token to be owned by the owner of the first token when the information about the first token registered to be locked up for a certain period of time satisfies a certain condition. The second token may be a type of compensation given to the owner of the first token in return for the locking up of the first token satisfying a certain condition. In one embodiment, a different form of compensation (e.g., a coupon, etc.) may be provided in place of the second token.

[0105] In one embodiment, when the first registered token is associated with a particular object, the processor 110 may determine that a particular condition is met and determine a second token to be owned by the owner of the first token. For example, assume that a particular condition is met when the first registered token is associated with person A. In this case, when the first token registered to be locked up for a particular period of time is associated with person A, the processor 110 may determine that the particular condition is met and determine a second token to be owned by the owner of the first token.

[0106] In another embodiment, the processor 110 may determine that a certain condition is met when the first registered token is a token registered to correspond to a specific date and determine a second token to be owned by the owner of the first token. For example, assume that a certain condition is met when the first registered token is a token registered to correspond to a specific date, January 1, 2023. In this case, when the first token registered to be locked up for a specific period of time is a token registered to correspond to January 1, 2023, the processor 110 may determine that the certain condition is met and determine a second token to be owned by the owner of the first token.

[0107] In another embodiment, the processor 110 may determine that a certain condition is met when the first registered token is associated with a specific object and registered to correspond to a specific date, and may determine a second token owned by the owner of the first token. For example, assume that a certain condition is met when the first registered token is associated with person A and registered to correspond to a specific date, January 1, 2023. In this case, if the first token registered to be locked up for a specific period of time is associated with person A and registered to correspond to January 1, 2023, the processor 110 may determine that the certain condition is met and may determine a second token owned by the owner of the first token.

[0108] In another embodiment, when the token group information corresponding to the registered first token is specific token group information, the processor (110) may determine that a specific condition is met and determine a second token to be owned by the owner of the first token. For example, assume that a specific condition is met when the registered first token is a token belonging to team B's token group and the token group information includes information indicating "team B's token group." In this case, when the token group information corresponding to the first token registered to be locked up for a specific period includes information indicating "team B's token group," the processor (110) may determine that the specific condition is met and determine a second token to be owned by the owner of the first token.

[0109] In various embodiments according to the present disclosure, the specific object associated with the second token 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 the 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 generated NFT. In this case, 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) may transmit 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, thereby changing the owner information of the second token. In another embodiment, the processor (110) may generate a second token owned by the owner of the first token. Specifically, the processor (110) may determine the second token owned by the owner of the first token when information about the first token registered to be locked up for a specific period of time satisfies a specific condition, by generating a second token owned by the owner of the first token. Specifically, the processor (110) may transmit a request for a function call or a transaction 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, thereby generating the second token owned by the owner of the first token.

[0110] Next, the server (100) may transmit information about the second token to the owner of the first token (S740). Specifically, the processor (110) may transmit information about the second token to a user terminal of the registered owner of the first token, or transmit information about the second token to a node on the blockchain network (300) of the registered owner of the first token. The 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.

[0111] 8 is a flowchart of the operation of the server 100 for processing a request for transmission of message information received from a user terminal 200 according to an embodiment of the present disclosure. The user terminal 200 may request the server 100 to transmit message information for a specific date. In one embodiment, when message information is related to items displayed on a calendar, the message information may be referred to as calendar information.

[0112] The server (100) may receive a request to transmit posting information for a specific date from the user terminal (200) (S810). Posting information in this specification is information corresponding to a specific date, which may be generated based on a token registered to correspond to the specific date, and may be information for displaying an area corresponding to the specific date on a calendar screen when a calendar is displayed on an arbitrary device. Such a transmission request for requesting transmission of posting information may include date designation information designating the specific date. In some of the following embodiments, the specific date for which transmission of posting information is requested from the user terminal (200) may also be referred to as the "first date" for convenience of explanation.

[0113] Next, the server (100) may generate token list information regarding the tokens registered to correspond to a specific date (S820). The token list information according to the present disclosure may be information having a specific data structure, such as a list, an array, or a set, of information regarding the tokens, as information corresponding to a specific date for which transmission of posting information is requested.

[0114] The processor (110) may obtain information about at least one token registered to correspond to a particular date from the memory (130) or from at least one node of the blockchain network (300). In an embodiment in which the token-date registration information is stored in the memory (130) of the server (100), the processor (110) may obtain information about at least one token registered to correspond to a particular date from the memory (130) to generate the token list information. In another embodiment in which the token-date registration information is recorded on the blockchain, the processor (110) may receive information about at least one token registered to correspond to a particular date from at least one node of the blockchain network (300) and generate the token list information based on the received information about the at least one token. The at least one node of the blockchain network (300) may include a smart contract including a function for querying tokens registered on a particular date. The function for querying tokens registered on a particular date may receive a particular date and return information about at least one token registered to correspond to the date. The processor (110) may transmit a function invocation request or transaction including a specific date included in the request to transmit posting information to at least one node of the blockchain network (300) to invoke a function to query tokens registered on a specific date, so that the processor (110) can receive information regarding at least one token registered to correspond to a specific date from at least one node of the blockchain network (300), thereby generating token list information.

[0115] The information on the token registered to correspond to a specific date that the processor (110) acquires from the memory (130) or the blockchain network (300) may include, for example, a token ID, a metadata URI, a registration request acceptance time, or memo information. Specifically, when the information on the token registered to correspond to a specific date is expressed as {"token ID": X, "metadata URI": Y, "registration request acceptance time": Z}, the token list information may be expressed as an array including information on one or more tokens as elements, such as [{"token ID": X1, "metadata URI": Y1, "registration request acceptance time": Z1}, {"token ID": X2, "metadata URI": Y2, "registration request acceptance time": Z2}].

[0116] Next, the server (100) may generate posting information based on the generated token list information (S830). The posting information may include information about each of the tokens registered to correspond to a specific date. The posting information for a specific date (first date) may include, for each of at least one token registered to correspond to the first date, at least one of an image linked to each token, a time point when a registration request was received for each token, token group information corresponding to each token, or memo information for each token. In addition, the posting information may further include information indicating a posting priority among the tokens registered to correspond to the first date (hereinafter also referred to as "posting priority").

[0117] The processor 110 may determine the priority of posting based on the time of receipt of the registration request for each token registered to correspond to the first date. That is, if multiple tokens are registered for the first date, the processor 110 may compare the time of receipt of the registration request for each token and determine the priority of posting in the order of the time of receipt of the registration request. For example, the priority of posting may be determined such that the earlier the registration request is received, the higher the priority. However, the scope of the present disclosure is not limited thereto. For example, it is assumed that the token list information includes information on each of the first token and the second token registered to correspond to the first date, and the time of receipt of the registration request for the first token is 12:00:00 PM on January 1, 2022, and the time of receipt of the registration request for the second token is 12:00:01 PM on January 1, 2022. In this case, the processor (110) may determine the priority of the postings such that the first token has a higher priority than the second token because the time at which the registration request for the first token for the first date was received is earlier than the time at which the registration request for the second token for the first date was received.

[0118] The processor 110 may determine the priority of the postings based on the token group information corresponding to each token. In an embodiment in which the processor 110 determines the priority of the postings based on the token group information, the processor 110 may determine the priority of the postings based on the number of tokens belonging to each of one or more token groups included in the token group information. For example, if 100 tokens belonging to person A's token group (i.e., 100 tokens generated to correspond to person A) are registered to correspond to the first date, and 200 tokens belonging to person B's token group (i.e., 200 tokens generated to correspond to person B) are registered to correspond to the first date, the processor 110 may determine the priority of the postings such that the tokens belonging to person B's token group have a higher priority than the tokens belonging to person A's token group, since more tokens belonging to person B's token group are registered on the first date than the tokens belonging to person A's token group. In addition, the priority of the postings of the tokens belonging to each token group may be changed as the number of tokens belonging to each of one or more token groups is changed. For example, if the number of tokens belonging to person A's token group registered to correspond to the first date increases from 100 to 150, and the number of tokens belonging to person B's token group registered to correspond to the first date decreases from 200 to 100, the processor (110) may determine the priority of postings such that tokens belonging to person A's token group have a higher priority than tokens belonging to person B's group. On the other hand, the processor (110) may determine that tokens belonging to the same token group have the same priority of postings.

[0119] In another embodiment in which the processor 110 determines the priority of postings based on the token group information, the processor 110 may determine the priority of postings based on the ratio of tokens registered on a specific date among all tokens issued to belong to one or more token groups included in the token group information. For example, assume that the total number of tokens belonging to person A's token group is 200, of which 100 tokens are registered to correspond to the first date, and the total number of tokens belonging to person B's token group is 1,000, of which 200 tokens are registered to correspond to the first date. In this case, the processor 110 may determine the priority of postings such that the tokens belonging to person A's token group have a higher priority than the tokens belonging to person B's token group, since the ratio of tokens registered on the first date among all tokens issued to belong to person A's token group (i.e., 100 / 200, 50%) is greater than the ratio of tokens registered on the first date among all tokens issued to belong to person B's token group (i.e., 200 / 1000, 20%). In addition, as the ratio of tokens registered on a specific date among all tokens issued to belong to one or more token groups changes, the posting priority of tokens belonging to each token group may be changed. For example, if the ratio of tokens registered on the first date among all tokens issued to belong to person A's token group is 50%, and the ratio of tokens registered on the first date among all tokens issued to belong to person B's token group increases from 20% to 100%, the processor (110) may determine the posting priority such that tokens belonging to person B's token group have a higher priority than tokens belonging to person A's group. On the other hand, the processor (110) may determine that tokens belonging to the same token group have the same posting priority.

[0120] In another embodiment in which the processor 110 determines the priority of postings based on the token group information, the processor 110 may determine the priority of postings based on the average registration request reception time of tokens belonging to each of one or more token groups included in the token group information (i.e., the average value of the registration request reception time of each token). For example, assume that the average registration request reception time of tokens belonging to person A's token group registered to correspond to the first date is 1:30:00 PM on July 11, 2022, and the average registration request reception time of tokens belonging to person B's token group registered to correspond to the first date is 1:31:00 PM on July 12, 2022. In this case, the processor 110 may determine the priority of postings such that tokens belonging to person A's token group have a higher priority than tokens belonging to person B's token group, since the average registration request reception time of tokens belonging to person A's token group is earlier than the average registration request reception time of tokens belonging to person B's token group. In addition, as the average registration request acceptance time of tokens belonging to one or more token groups is changed, the priority of posting of tokens belonging to each token group may be changed. For example, the registration request acceptance times of the first token, second token, and third token belonging to Person A's token group, which are registered to correspond to the first date, are 12:00:00 AM on July 10, 2022, 12:00:00 AM on July 14, 2022, and 12:00:00 AM on July 15, 2022, respectively (i.e., the average registration request acceptance time of tokens belonging to Person A's token group registered to correspond to the first date is 12:00:00 AM on July 13, 2022), and the first token, which belongs to Person A's token group, is 12:00:00 AM on July 14, 2022, and 12:00:00 AM on July 15, 2022, respectively (i.e., the average registration request acceptance time of tokens belonging to Person A's token group registered to correspond to the first date is 12:00:00 AM on July 13, 2022). It is assumed that the registration request acceptance times for the 4th, 5th, and 6th tokens belonging to Person B's token group and registered to correspond to Date 1 are, respectively, July 13, 2022, 12:00:00 AM, July 14, 2022, and 12:00:00 AM on July 15, 2022 (i.e., the average registration request acceptance time for tokens belonging to Person B's token group registered to correspond to Date 1 is July 14, 2022, 12:00:00 AM).In the hypothetical state, the average registration request acceptance time of the tokens belonging to person A's token group is earlier than the average registration request acceptance time of the tokens belonging to person B's token group, so the tokens belonging to person A's token group may have a higher priority than the tokens belonging to person B's token group. In this case, if the registration of the first token belonging to person A's token group is cancelled, the average registration request acceptance time of the tokens belonging to person A's token group may be changed to 12:00:00 PM on July 14, 2022. As a result, since the average registration request acceptance time of the tokens belonging to person B's token group (12:00:00 AM on July 14, 2022) is earlier than the average registration request acceptance time of the tokens belonging to person A's token group (12:00:00 PM on July 14, 2022), the processor (110) may determine the priority of posting such that the tokens belonging to person B's token group have a higher priority than the tokens belonging to person A's token group. Meanwhile, the processor 110 may determine that tokens belonging to the same token group have different posting priorities according to the time of receipt of the registration request for each token. Referring again to the above example, the fourth, fifth, and sixth tokens registered to correspond to the first date and belonging to the token group of person B may have posting priorities according to the order of the time of receipt of the registration request for each token. That is, the fourth token may have the highest posting priority, the sixth token may have the lowest posting priority, and the fifth token may have a posting priority lower than the fourth token and higher than the sixth token.

[0121] The various embodiments regarding the posting priority as described above are merely exemplary explanations for specifically explaining a method for determining the posting priority among tokens included in the posting information, and do not limit the present disclosure.

[0122] The priority order of postings among the tokens included in the posting information is used when a calendar is displayed on an electronic device such as the server (100) or the user terminal (200). As an example, it is assumed that the user terminal (200) displays a calendar via the output unit (250), and the posting information for a specific date includes information about each of a plurality of tokens and the priority order of postings among the plurality of tokens. In this case, the user terminal (200) may determine, based on the priority order of postings included in the posting information, which of the multiple tokens in one area for a specific date on the calendar screen should be exposed at the top, which token should be exposed first, which token should be exposed larger than other tokens, or which token should be placed closer to the center of the screen than other images.

[0123] Next, the server (100) may transmit the posting information to the user terminal (200) (S840). The user terminal (200) may display the posting information in various ways via 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 via the output unit (250) based on the posting information. The calendar screen may include at least one area assigned to a specific date. Specifically, the processor (210) may determine information to be displayed in an area assigned to a specific date based on the posting information for the specific date. The area assigned to a specific date may include an area assigned to at least one token. The processor (210) may determine a display method or order of areas assigned to each token within the area assigned to a specific date based on the priority of posts included in the posting information. In one embodiment, the posting information may be displayed via an output unit such as the server (100).

[0124] Hereinafter, a specific embodiment in which bulletin information is displayed via the output unit (250) of the user terminal (200) will be described with reference to FIGS. 9a to 9d.

[0125] FIG. 9a is a diagram showing an example of a screen that may be displayed when posting information according to an embodiment of the present disclosure is displayed through an output unit (250) of a user terminal (200). In an embodiment, a token with a higher posting priority may be posted to be located at the top of the date on a calendar screen. In the example of FIG. 9a, it is assumed that posting information for a specific date (first date) includes information on a first token and information on a second token. The processor (210) may determine that an area (910) assigned to the first date includes an area (911) assigned to the first token and an area (913) assigned to the second token based on the posting information for the first date. The first token and the second token are both tokens registered to correspond to the first date, and the processor (210) may determine that a token with a higher posting priority is the first token and a token with a lower posting priority is the second token among the tokens included in the posting information. An image linked to the first token may be displayed in the area (911) assigned to the first token. An image linked to the second token may be displayed in the area (913) assigned to the second token. If the first token has a higher posting priority than the second token, the processor (210) may determine that the area (911) assigned to the first token is located above the area (913) assigned to the second token within the first date area (910), as shown in Fig. 9a. In one embodiment, one or more of the first token, the second token, the image associated with the first token, the image associated with the second token, the area (811), and the area (813) may be referred to as an entry.

[0126] FIG. 9b is a diagram showing an example of a screen that may be displayed when bulletin information according to another embodiment of the present disclosure is displayed via an output unit (250) of a user terminal (200). In one embodiment, a token with a higher bulletin priority may be displayed to occupy a larger size range on the calendar screen. In the example of FIG. 9b, it is assumed that bulletin information for a specific date (first date) includes information on the first token, information on the second token, and information on the third token. The processor (210) may determine that an area (910) assigned to the first date includes an area (911) assigned to the first token, an area (913) assigned to the second token, and an area (915) assigned to the third token based on the bulletin information for the first date. The first token, the second token, and the third token are all registered to correspond to the first date, and the processor (210) may determine that the token with the highest posting priority among the tokens included in the posting information is the first token, the token with the lowest posting priority is the third token, and the token with a posting priority lower than the first token and higher than the third token is the second token. An image linked to the first token, an image linked to the second token, and an image linked to the third token may be displayed in the area (911) assigned to the first token, the area (913) assigned to the second token, and the area (915) assigned to the third token, respectively. If the first token has a posting priority higher than a different token (i.e., the second token or the third token), the processor (210) may determine that the area (911) assigned to the first token occupies a larger size range in the area (910) of the first date than the area (913) assigned to the second token or the area (915) assigned to the third token, as shown in FIG. 9b. In this case, an image displayed in the area assigned to the first token (911) may be displayed larger than images displayed in other areas. In Fig. 9b, the area assigned to the second token (913) and the area assigned to the third token (915) occupy the same size range.However, the scope of the present disclosure is not limited to this embodiment, and for example, the area allocated to the second token (913) and the area allocated to the third token (915) may occupy different size ranges depending on the posting priority of each token.

[0127] FIG. 9c is a diagram illustrating an example of a screen that may be displayed when bulletin information according to another embodiment of the present disclosure is displayed via the output unit (250) of the user terminal (200). Bulletin information for 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 bulletin information includes memo information of a specific token, the processor (210) may display the memo information via the output unit (250). Specifically, when the bulletin information includes memo information of a 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. The memo information (931) of the first token may include, for example, a character string such as "My favorite!". In one embodiment, the memo information (931) of the first token may be viewed as a result of a user touching or clicking the area (911) assigned to the first token. In another embodiment, the memo information (931) of the first token may be displayed anywhere within the area allocated to the first token.

[0128] FIG. 9d is a diagram showing an example of a screen that may be displayed when posting information according to another embodiment of the present disclosure is displayed through an output unit (250) of a user terminal (200). The token according to the present disclosure may be a token (hereinafter, also referred to as an "advertising token") including information for accessing an advertising image (i.e., the URI of the advertising image). The advertising image URI linked to the advertising token may be a type of URI of the digital file described above, and may indicate the address of a centralized server or cloud server where the advertising image is stored, or a hash value of the advertising image stored on IPFS. In the following, a description of overlapping points will be omitted, and the main differences between the advertising tokens will be described.

[0129] The advertisement token may be 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). Specifically, the advertisement token generation function may be a function that obtains an advertisement image URI, one or more virtual currency tokens corresponding to a specific amount, and an address on the blockchain of a first node (i.e., a node of a user requesting an advertisement) and generates a token having the URI of the advertisement image. The advertisement token generation function may be a function created to generate the advertisement token and then transmit the obtained one or more virtual currency tokens to an address on the blockchain of a second node (i.e., a server node or a user node providing an advertisement). The address on the blockchain of the second node may be included in the smart contract when the smart contract including the advertisement token generation function is created.

[0130] The server (100) may receive an advertisement token registration request 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 received advertisement token registration request. In addition, when the advertisement token is registered to correspond to the first date, if the server (100) receives a request to transmit posting information for the first date from the user terminal (200), the posting information transmitted by the server (100) to the user terminal (200) may include information related to the advertisement token.

[0131] The posting information of the first date received by the user terminal (200) from the server (100) may include information about an advertisement token registered to correspond to the first date. As an example, the processor (210) may display an image linked to the advertisement token registered to correspond to the first date in an advertisement area (950) included in the area (910) assigned to the first date. The advertisement area (950) may be located at any position in the area (910) assigned to the first date. As another example, the processor (210) may display the advertisement token in the area (910) assigned to the first date by treating the advertisement token in the same manner as other tokens that are not advertisement tokens. For example, the posting information of the first date may include information about the first token and information about the second token, and at least one of the first token or the second token may be an advertisement token. In this case, if the first token is an advertisement token, the processor (210) may display an advertisement image linked to the first token in the area (911) assigned to the first token. Furthermore, if the second token is an advertisement token, the processor (210) may display an advertisement image linked to the second token in the area (913) allocated to the second token.

[0132] 10 is a flowchart showing an operation of a server (100) for processing information indicating a specific object received from a user terminal (200) according to an embodiment of the present disclosure. The server (100) according to the present disclosure may receive information indicating a specific object from the user terminal (200), generate history information for the specific object, and transmit the generated history information to the user terminal (200).

[0133] The server (100) may receive information indicating a specific object from the user terminal (200) (S1010). The information indicating the specific object may be, for example, the name of the specific object (e.g., the name of a specific person) associated with the token. Next, the server (100) may identify or determine one or more tokens associated with the specific object and registered to correspond to one or more registration dates (S1020). As described above, the "registration date" refers to a specific date when a specific token is registered to correspond to a specific date based on a registration request. For example, "one or more tokens associated with a specific object and registered to correspond to one or more registration dates" may include a first token or a second token registered to correspond to different dates associated with person A. Hereinafter, the expression "one or more tokens associated with a specific object and registered to correspond to one or more registration dates" is used interchangeably with the expression "registered tokens associated with a specific object" for convenience of explanation. That is, one or more registered tokens associated with a specific object may be one or more tokens registered to correspond to different registration dates.

[0134] In one embodiment, the memory 130 of the server 100 may store information about one or more registered tokens associated with a particular subject. In this case, the processor 110 may obtain information about one or more tokens associated with a particular subject and registered to correspond to one or more registration dates from the memory 130. For example, assuming that the memory 130 stores multiple tokens registered to correspond to one or more registration dates, and tokens corresponding to person A among the multiple tokens are designated as token a1, token a2, and token a3, respectively, the processor 110 may identify token a1, token a2, and token a3 from the memory 130.

[0135] In another embodiment, the server (100) may identify one or more tokens by receiving information on one or more registered tokens associated with a specific object from the blockchain network (300). At least one node of the blockchain network (300) may include a smart contract including a function (hereinafter also referred to as a “registered token identifying function associated with a specific object”) that returns information on one or more tokens associated with a specific object and registered to correspond to one or more registration dates. The “registered token identifying function associated with a specific object” may obtain information indicating a specific object and return a token associated with the specific object from among the tokens registered to correspond to one or more registration dates. The processor (110) may transmit a function invocation request or transaction including information indicating a specific object to at least one node of the blockchain network (300) to invoke the function. For example, when the processor (110) transmits information indicating person A to at least one node of the blockchain network (300), the at least one node of the blockchain network (300) may obtain information on one or more tokens (e.g., token a1, token a2, and token a3) registered to correspond to one or more dates as tokens corresponding to person A from at least one transaction recorded on the blockchain by executing a “registered token identification function associated with a specific object”. As a result, the processor (110) may receive information on one or more tokens from at least one node of the blockchain network (300) and identify one or more tokens associated with person A, namely, token a1, token a2, and token a3.

[0136] Next, the server (100) may generate historical information for a particular target based on information about each of the identified one or more tokens (S1030). The historical information may include the registration date of the token and an image linked to the token. If the historical information includes information about multiple tokens, the historical 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) may generate historical information including multiple images linked to the tokens such that the image linked to token a3, the image linked to token a2, and the image linked to token a1 are in the order of the registration dates.

[0137] Next, the server 100 may transmit the generated history information to the user terminal 200 (S1040). Through this, the user terminal 200 may obtain history information for a specific object, including an image of the specific object (i.e., person A).

[0138] FIG. 11 is a flowchart showing the operation of the server (100) for processing an exchange request received from a user terminal (200) according to an embodiment of the present disclosure. In the present disclosure, the server (100) may exchange a specific token registered to correspond to a specific date for another token. In some embodiments of the present specification described with reference to FIG. 11 and FIG. 12 below, for convenience of explanation, the specific token may be referred to as a "first token" and the other token may be referred to as a "second token". When the first token registered to correspond to a specific date is exchanged for the second token, the second token may be registered to correspond to the same specific date as the first token. Also, when the first token registered to correspond to a specific date is exchanged for the second token, the time of receiving the registration request for the second token may be the same time as the time of receiving the registration request for the first token.

[0139] The server (100) may receive an exchange request from the user terminal (200) to exchange a first token registered to correspond to a specific date for a second token (S1110). The "exchange request" may include information about the first token and information about the second token. For example, the exchange request may include the token ID of the first token and the token ID of the second token. In addition, the time when the server (100) receives the exchange request transmitted from the user terminal (200) may be referred to as the "exchange request reception time."

[0140] The server (100) may then de-register the first token based on the exchange request and register the second token to correspond to a specific date (S1120). In an embodiment in which information indicating that a specific token has been registered to correspond to a specific date is stored in the memory (130) of the server (100), the processor (110) may retrieve the token-date registration information of the first token from the memory (130). The processor (110) may delete the token-date registration information of the first token from the memory (130) and generate token-date registration information of the second token. In this case, the processor (110) may generate token-date registration information of the second token that includes the same registration date as the token-date registration information of the first token and the time of receipt of the registration request. For example, when the token-date registration information of a first token is {“Registration date”: “2023-01-01”, “Token ID”: “0x1234”, “Registration request acceptance time”: “2022-07-01 12:00:00”}, the token-date registration information of the generated second token may be {“Registration date”: “2023-01-01”, “Token ID”: “0x5678”, “Registration request acceptance time”: “2022-07-01 12:00:00”}.

[0141] In another embodiment in which information indicating that a specific token has been registered to correspond to a specific date is recorded in a block on the blockchain managed by the blockchain network (300), the processor (110) may transmit information about the first token included in the exchange request to at least one node of the blockchain network (300) and obtain token-date registration information of the first token from the blockchain network (300). The processor (110) may generate token-date registration information of the second token, the token-date registration information including the same registration date as the token-date registration information of the first token, the time of receipt of the registration request, and information about the second token included in the exchange request. The processor (110) may deregister the first token for a specific date by transmitting the token-date deregistration information of the first token to at least one node of the blockchain network (300). The processor (110) may record the fact that the second token has been registered on a specific date in a block on the blockchain by transmitting the token-date registration information of the second token to at least one node of the blockchain network (300).

[0142] In one embodiment, when exchanging the first token for the second token, the server (100) may deregister the first token depending on whether the lock-up release condition for the first token is satisfied. In an embodiment in which information indicating that a particular token is registered to correspond to a particular date is stored in the memory (130) of the server (100), the processor (110) may retrieve token-date registration information of the first token from the memory (130) and compare the time when the registration of the first token started and the time when the exchange request was received, which are included in the token-date registration information of the first token. The processor (110) may determine whether a particular period (e.g., three months) has passed since the time when the registration of the first token started until the time when the exchange request was received. If the particular period has passed since the time when the registration of the first token started until the time when the exchange request was received, the processor (110) may determine that the lock-up release condition is satisfied. On the other hand, if the particular period has not passed since the time when the registration of the first token started until the time when the exchange request was received, the processor (110) may determine that the lock-up release condition is not satisfied. If the lock-up release condition is met, the processor 110 may delete the token-date registration information of the first token from the memory 130 and perform operations to exchange the first token for the second token as described above. If the lock-up release condition is not met, the processor 110 may transmit a rejection to the user terminal 200 in response to the exchange request.

[0143] In another embodiment, in which information indicating that a specific token has been registered to correspond to a specific date is recorded in a block on the blockchain managed by the blockchain network (300), the processor (110) may transmit information about the first token included in the exchange request to at least one node of the blockchain network (300) and obtain token-date registration information of the first token from the blockchain network (300). The processor (110) may determine whether the lock-up release condition is satisfied by comparing the time when the registration of the first token began, which is included in the token-date registration information of the first token, with the time when the exchange request was received. If the lock-up release condition is satisfied, the processor (110) may transmit the token-date deregistration information of the first token to at least one node of the blockchain network (300) and perform an operation to exchange the first token for the second token according to the above content. If the lock-up release condition is not satisfied, the processor (110) may transmit rejection information to the user terminal (200) in response to the exchange request.

[0144] 12 is a flow diagram illustrating a method for processing an exchange request from a user terminal (200) according to another embodiment of the present disclosure. The server (100) may receive an exchange request from the user terminal (200) to exchange a first token registered to correspond to a specific date for a second token (S1210). The exchange request may include information about the first token and information about the second token.

[0145] Next, the server (100) may obtain the registration date of the first token and the date attribute group for the second token (S1220). As described above, the date attribute group including at least one date attribute for the tokens, or the token-date registration information, may be recorded in the respective memory (130) or on the blockchain. The processor (110) may obtain the token-date registration information of the first token including the registration date of the first token from the memory (130) or the 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 registration information of the first token may be expressed as {"Registration Date": "2021-11-27", "Token ID": "0x123456", "Registration Request Acceptance Time": "2021-07-01 18:30:00"}. Also, the date attribute group for the second token can be expressed as {“Date Attributes Group”:[“Debut Date”:“2013-06-13”, “Second Album Release Date”:“2016-10-10”, “Concert Date”:“2021-11-27”]}.

[0146] 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 exchange request to the user terminal (200) (S1235).

[0147] When the token-date registration information is recorded on the blockchain, if it is determined that the registration date of the first token matches any one of the date attributes included in the date attribute group for the second token, the processor (110) may transmit the token-date 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 again to the above example, since 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 include June 13, 2013, October 10, 2016, and November 27, 2021, which is the registration date of the first token, the processor (110) may transmit the token-date 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). The processor 110 may transmit approval information for the exchange request to the user terminal 200 (S1250) prior to or following step S1240. Also, the processor 110 may transmit approval information for the exchange request to the user terminal 200 simultaneously with step S1240.

[0148] In the case of an embodiment in which the token-date registration information is stored in the memory 130 of the server 100, if it is determined that the registration date of the first token matches any one of the date attributes included in the date attribute group for the second token, instead of the above-mentioned step S1240, the processor 110 may delete the token-date registration information of the first token from the memory 130, generate token-date registration information of the second token, and store the generated token-date registration information of the second token in the memory 130. The processor 110 may then transmit approval information for the exchange request to the user terminal 200.

[0149] In the flowcharts or flow diagrams according to the present disclosure, the steps of a method or algorithm are described in a sequential order, but the steps may be performed not only sequentially but also in any combined order. The description of a flowchart or flow diagram herein does not imply that any step is essential or desirable, except to make changes or modifications to the method or algorithm. In an embodiment, at least some steps may be performed in parallel, iteratively, or heuristically. In an embodiment, at least some steps may be omitted, and other steps may be added. In an embodiment, one or more steps or operations of one or more methods or algorithms corresponding to one or more flowcharts or flow diagrams may be combined in any order.

[0150] Various embodiments according to the present disclosure may be embodied as software in a machine-readable storage medium. The software may be software for implementing various embodiments of the present disclosure. The software may be inferred from various embodiments of the present disclosure by a programmer skilled in the art to which the present disclosure pertains. For example, the software may be a program including machine-readable instructions (e.g., code or code segments). The device may be a device that can operate according to instructions retrieved from a storage medium, such as a computer. In one embodiment, the device may be a computing device according to various embodiments of the present disclosure. In one embodiment, the processor of the device may execute the retrieved instructions and cause the components of the device to perform the functions corresponding to the instructions. In one embodiment, the processor may be a processor (110, 210) according to an embodiment of the present disclosure. The storage medium may refer to any type of recording medium on which data is stored that can be read by the device. The storage medium may include, for example, a ROM, a RAM, a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like. In one embodiment, the storage medium may be a memory (130, 230). In one embodiment, the storage medium may be embodied in a distributed form in computer systems connected by a network. Software may be stored and executed in a distributed manner in computer systems. The storage medium may be a non-transitory storage medium. A non-transitory storage medium refers to a tangible medium that exists regardless of whether data is stored semi-permanently or temporarily, and does not include a signal that is transmitted transitorily.

[0151] Although the technical idea of ​​the present disclosure has been described above by various embodiments, the technical idea of ​​the present disclosure may include various replacements, modifications, and alterations that can be understood by a person having ordinary skill in the art to which the present disclosure pertains. In addition, such replacements, modifications, and alterations should be understood to be included in the scope of the appended claims.

[0152] In accordance with at least one embodiment of the present disclosure, a user who purchases a token that can be registered to correspond to one specific date can be prevented from registering the token to multiple specific dates.

[0153] According to at least one embodiment of the present disclosure, it is possible to prevent an area for a specific date on a calendar screen displayed on a user terminal from being filled with a specific object corresponding to a token.

[0154] According to at least one embodiment of the present disclosure, a user can easily grasp historical information regarding a particular subject.

[0155] According to at least one embodiment of the present disclosure, a user who registers a token to correspond to a particular date may optionally change the registered token to another token.

[0156] Although the above description focuses on specific embodiments, these methods can be realized as computer readable codes on a computer readable recording medium. The computer readable recording medium includes all kinds of data storage devices readable by a computer system. Examples of the computer readable recording medium include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage device, etc. Also, the computer readable recording medium can be distributed among computer systems connected to a network, and the computer readable codes can be stored and executed in a distributed manner. Also, functional programs, codes, and code segments for implementing the above-described embodiments can be easily inferred by a programmer skilled in the art to which the present invention pertains.

[0157] In addition, although specific embodiments have been described, these embodiments are merely examples and are not intended to limit the scope of the present disclosure. In fact, the embodiments described herein may be realized in various other forms. In addition, various omissions, substitutions, and modifications may be made from the forms of the embodiments described herein without departing from the technical spirit of the present disclosure. The appended claims and their equivalents are intended to cover forms or modifications that fall within the scope and technical spirit of the disclosure.

Claims

1. a communication interface for communicating with at least one node of the blockchain network and with an external device; one or more processors; and one or more memories storing at least one instruction executed by the one or more processors; The one or more processors: Receive a token registration request for a date from the external device; registering the token corresponding to the date based on the registration request; configured to transmit posting information associated with the date to the external device; The posting information includes display attributes of the item corresponding to the token; The registration request includes date indication information indicating the date and token identification information identifying the token, The display attributes are determined based on the date indication information and include at least one of a display priority of the items, a display position of the items, and a display size of the items.

2. The one or more processors:

2. The electronic device of claim 1, configured to register the token in the blockchain network by transmitting the date indication information and the token identification information to at least one node of the blockchain network.

3. the token includes a first date attribute group including at least one date attribute; The one or more processors: Obtaining the first date attribute group from at least one node of the blockchain network; determining whether the date indicated by the date indication information matches one of the at least one date attribute; The electronic device of claim 2, configured to transmit the date indication information and the token identification information to at least one node of the blockchain network in accordance with a determination of a match.

4. the one or more memories additionally store a first date attribute group including at least one date attribute corresponding to the token; The one or more processors: obtaining the first date attribute group from the one or more memories; determining whether the date indicated by the date indication information matches one of the at least one date attribute; The electronic device of claim 2, configured to transmit the date indication information and the token identification information to at least one node of the blockchain network in accordance with a determination of a match.

5. The one or more processors: receiving an exchange request from the external device to exchange the token registered to correspond to the date for another token; configured to deregister the token based on the exchange request and register the other token to correspond to the date; The electronic device of claim 1 , wherein the exchange request includes information about the token and information about the other token.

6. The one or more processors: The token is deregistered depending on whether a lock-up release condition for the token is satisfied, The electronic device according to claim 5 , wherein the lock-up release condition is satisfied when a predetermined period of time has elapsed since registration of the token began.

7. The electronic device of claim 1 , wherein the token is an advertising token that includes information for accessing an image.

8. The one or more processors: receiving a request for transmission of bulletin information for the date from the external device; generating token list information for a plurality of tokens registered corresponding to the date; generating posting information based on the token list information; configured to transmit the posting information to the external device; The electronic device of claim 1 , wherein the posting information includes information regarding each of the plurality of tokens.

9. The one or more processors: receiving, from at least one node of the blockchain network, information regarding at least one token of the plurality of tokens registered corresponding to the date; The electronic device of claim 8 , configured to generate the token list information based on information about the at least one token.

10. the posting information includes a posting priority among the plurality of tokens; The one or more processors: The electronic device of claim 8 , configured to prioritize the postings based on a time of receipt of a registration request for each of the plurality of tokens.

11. the token list information includes token group information, the token group information indicating one or more token groups to which each of the plurality of tokens belongs; the posting information includes a posting priority among the plurality of tokens; The one or more processors: The electronic device of claim 8 , configured to prioritize the postings based on the token group information.

12. The one or more processors: The electronic device of claim 11 , configured to prioritize the postings based on a number of tokens that belong to each of the one or more token groups.

13. the first token includes a first date attribute group including at least one date attribute; The one or more processors: generating a second date attribute group including a date attribute different from the at least one date attribute of the first date attribute group; The blockchain network is configured to transmit a request for generating a second token to at least one node of the blockchain network; The electronic device of claim 8 , wherein the request to generate the second token includes information about the first token and information about the second date attribute group.

14. The one or more processors: receiving information indicating a target from the external device; identifying one or more tokens associated with the object and registered corresponding to one or more registration dates; generating historical information for the object based on information regarding each of the identified one or more tokens; The electronic device of claim 8 , configured to transmit the history information to the external device.

15. 1. A method performed by an electronic device including one or more processors and one or more memories storing at least one instruction executed by the one or more processors, the method comprising: the one or more processors: receiving a request for registration of the token for a date from the external device; registering the token corresponding to the date based on the registration request; and transmitting posting information associated with the date to the external device; The posting information includes display attributes of the item corresponding to the token; the registration request includes date indication information indicating the date and token identification information identifying the token, The method, wherein the display attributes are determined based on the date indication information and include at least one of a display priority of the items, a display position of the items, and a display size of the items.

16. The step of registering the token comprises:

16. The method of claim 15, further comprising transmitting the date indication information and the token identification information to at least one node of the blockchain network.

17. the one or more processors: receiving a request for transmission of bulletin information for the date from the external device; generating token list information regarding a plurality of tokens registered corresponding to said date; generating posting information based on the token list information; and transmitting the notice information to the external device; The method of claim 15 , wherein the posting information includes information regarding each of the plurality of tokens.

18. 1. A method performed by an electronic device including one or more processors and one or more memories storing at least one instruction executed by the one or more processors, comprising: the one or more processors: transmitting a request for registration of the token for the date to an external device; receiving, from the external device responding to the registration request, approval information for the registration request and information stored in at least one node of a blockchain network; receiving from the external device bulletin information associated with the date, the bulletin information including display attributes of an item corresponding to the token; and displaying the item on a display of the electronic device according to the display attributes; The registration request includes date indication information indicating the date and token identification information identifying the token. The method, wherein the display attributes are determined based on the date indication information and include at least one of a display priority of the items, a display position of the items, and a display size of the items.

19. the one or more processors: transmitting a request for transmitting bulletin information for the date to the external device; and receiving the notice from the external device in response to the transmission request; The method of claim 18 , wherein the posting information is generated based on token list information regarding a plurality of tokens registered corresponding to the date, and includes information regarding each of the plurality of tokens.

20. a communication interface for communicating with at least one node of the blockchain network and with an external device; one or more processors; and one or more memories storing at least one instruction executed by the one or more processors; The one or more processors: receiving a registration request for a first token associated with an object from the external device; registering the first token to be locked up for a predetermined period of time based on the registration request; determining a second token owned by the owner of the first token based on information about the first token; An electronic device configured to transmit information about the second token to the owner.

Images