Server, method, and program

A server system using NFTs for alcoholic beverages manages ownership and provides ancillary data, ensuring quality and preventing illegal resale by delivering detailed product information to consumers.

JP7596577B1Active Publication Date: 2024-12-09SUMITOMO MITSUI BANKING CORP

Patent Information

Application Number
JP2024038758
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2024-03-13
Publication Date
2024-12-09
Estimated Expiration
2044-03-13

AI Technical Summary

Technical Problem

Existing technologies using NFTs for managing the transfer of ownership of alcoholic beverages, such as whiskey and wine, do not provide additional information or data related to these products to consumers.

Method used

A server system that issues both a first non-fungible token for the delivery claim of an alcoholic beverage product and a second non-fungible token for ancillary data, utilizing a blockchain to manage transactions, and includes a shipping management unit to deliver the product.

Benefits of technology

Consumers are provided with detailed information about the alcoholic beverage product, enabling them to make informed choices and enhancing the brand's value by preventing quality deterioration and illegal resale.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007596577000001_ABST
    Figure 0007596577000001_ABST
Patent Text Reader

Abstract

Along with a non-fungible token associated with a right to claim delivery of an alcoholic beverage product, a consumer may be provided with a non-fungible token associated with ancillary data related to the alcoholic beverage product. [Solution] A server 20 according to an exemplary embodiment of the present disclosure includes a non-fungible token issuing unit 221, a transaction management unit 223, and a shipping management unit 225. The non-fungible token issuing unit 221 issues a first non-fungible token associated with a right to claim delivery of an alcoholic product, and a second non-fungible token associated with incidental data related to the alcoholic product, in a blockchain. The transaction management unit 223 manages transactions in the blockchain of the first non-fungible token and the second non-fungible token. When a request for deletion of the first non-fungible token is made in a transaction, the shipping management unit 225 instructs a manufacturer terminal of the alcoholic product to ship the alcoholic product to a delivery destination specified by the terminal that requested the deletion.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to a server, a method, and a program. [Background technology]

[0002] There is a technology that uses blockchain technology (e.g., non-fungible tokens) to manage the transfer of ownership of barrels of alcoholic beverages such as whiskey and wine. A non-fungible token (NFT) is a type of token in which transactions are recorded on a blockchain, and is issued in compliance with the ERC (Ethereum Request for Comments) 721 standard, which is a standard for NFTs. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 6829927 [Patent Document 2] Patent No. 7389527 Summary of the Invention [Problem to be solved by the invention]

[0004] However, existing technologies using NFTs only allow the transfer of ownership of alcoholic beverages (barrels) to be managed using NFTs. Therefore, there is room for consideration in presenting additional information or data related to alcoholic beverages to consumers who hold ownership of the alcoholic beverages.

[0005] One exemplary objective of the present disclosure is to enable consumers to be provided with a non-fungible token associated with a claim for delivery of an alcoholic beverage product, along with ancillary data related to the alcoholic beverage product. [Means for solving the problem]

[0006] Therefore, a server according to an exemplary embodiment of the present disclosure includes a non-fungible token issuing unit that issues, in a blockchain, a first non-fungible token associated with a right to claim delivery of an alcoholic product and a second non-fungible token associated with ancillary data related to the alcoholic product, a transaction management unit that manages transactions in the blockchain of the first non-fungible token and the second non-fungible token, and a shipping management unit that, when a request for deletion of the first non-fungible token is made in the transaction, instructs a manufacturer terminal of the alcoholic product to ship the alcoholic product to a delivery destination specified by the terminal that requested the deletion. Effect of the Invention

[0007] According to one exemplary aspect of the present disclosure, a consumer may be provided with a non-fungible token associated with a right to claim delivery of an alcoholic beverage product, along with a non-fungible token associated with ancillary data related to the alcoholic beverage product. [Brief description of the drawings]

[0008] [Figure 1] A diagram showing an example configuration of an NFT service system according to one embodiment. [Diagram 2] A block diagram showing an example configuration of the NFT server illustrated in Figure 1. [Diagram 3] FIG. 2 is a diagram showing an example of customer data illustrated in FIG. 1. [Figure 4] FIG. 2 is a diagram showing an example of RWA (real world asset) related data illustrated in FIG. 1. [Diagram 5] A figure showing an example of NFT management data illustrated in Figure 1. [Figure 6] A figure showing an example of the data structure of an NFT according to one embodiment. [Figure 7] This figure shows the overall operational flow in the case where a consumer consumes a product at home in the NFT service system illustrated in Figure 1. [Figure 8]This is a diagram showing the overall operational flow in the case where a consumer gifts a product to another consumer in the NFT service system illustrated in Figure 1. [Figure 9] 9 is a flowchart showing an example of operation focusing on the NFT server in the flow of operation illustrated in Figures 7 and 8. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, the embodiments will be described in detail with reference to the drawings. However, the accompanying drawings and the following description are provided for those skilled in the art to fully understand the present disclosure, and are not intended to limit the subject matter described in the claims. In addition, more detailed descriptions than necessary may be omitted.

[0010] For example, detailed descriptions of already well-known matters and duplicate descriptions of substantially identical configurations may be omitted. This is to avoid unnecessary redundancy in the following description and to facilitate understanding by those skilled in the art. Furthermore, identical or similar symbols indicate identical or similar elements, and repeated descriptions may be omitted. When numerical values ​​are described in the following description, the numerical values ​​are merely examples, and other numerical values ​​may be used in addition or instead.

[0011] <System configuration example> 1 is a diagram showing an example of the configuration of an NFT service system 10 according to one embodiment. The NFT service system 10 (hereinafter sometimes abbreviated as "system 10") shown in FIG. 1 includes, for example, a server computer 20 that provides an NFT service PF (platform), a blockchain system 40, and client computers 60, 80A, 80B, and 100.

[0012] The server computer 20 may be conveniently referred to as the "NFT server 20" or the "NFT service PF20." The "computer" may be replaced with other terms, such as, for example, an "apparatus," "terminal," "node," or "entity." One or more of the NFT server 20 and the client terminals 60, 80A, 80B, and 100 may correspond to nodes constituting the blockchain system 40.

[0013] The NFT server 20, the blockchain system 40, and the client terminals 60, 80A, 80B, and 100 are connected to a network (NW) 120 and can communicate with each other. The network 120 may be either a wired or wireless network, or may be a mixed wired and wireless network.

[0014] The wireless network may be a network conforming to standards established by 3GPP (3rd Generation Partnership Project) (registered trademark), such as 3G, LTE (Long Term Evolution), 4G, 5G, or 6G, or a Wi-Fi network conforming to the IEEE (Institute of Electrical and Electronics Engineers) 802.11 series standards. A non-limiting example of the network 120 may include the Internet.

[0015] The blockchain system 40 (hereinafter sometimes abbreviated as "blockchain 40") is a computer system (or network) including a plurality of nodes (computers) connected by, for example, P2P (peer-to-peer). The blockchain 40 is illustratively configured to record transactions related to NFTs in a distributed manner between wallet addresses assigned to each user of the NFT service system 10.

[0016] Transactions involving NFTs may include, by way of example, issuing (or mapping) an NFT to a particular wallet address, transferring an NFT between wallet addresses, and / or "burning," which means deleting or deactivating an NFT. Issuing an NFT is also referred to as "minting."

[0017] Note that an NFT is one-of-a-kind, non-substitutable digital data that is uniquely identified in the blockchain 40. For example, an NFT can function as digital data with an unforgeable certificate of authenticity and proof of ownership by being decentralizedly recorded in the blockchain 40.

[0018] The wallet address is, for example, address information indicating the location of a wallet associated with a resource of the blockchain 40. In comparison between the digital space and the real world in the blockchain 40, a "wallet" (or may be referred to as a "wallet account") may correspond to, for example, a "bank account," and a "wallet address" may correspond to, for example, an "account number."

[0019] A "wallet address" may be a character string (e.g., a public key) that is paired with a character string (e.g., a private key) held by a user who has access rights to a "wallet," or a character string generated based on the public key. In this case, the private key represents a legitimate access right to a "wallet account," and may correspond to, for example, a password for logging in or signing in to a "wallet account."

[0020] The issuance and / or management of wallet addresses may be performed, for example, by the NFT server 20, or by a wallet management server (not shown) different from the NFT server 20 and connected to the NW120.

[0021] In addition, each user of the NFT service system 10 may include, for example, a manufacturer that provides a product (or a commodity) as a real world asset (RWA), a wholesaler of the product, a retail store of the product, and a consumer of the product. In addition, the consumer may include one or both of a consumer who acquires a product for personal consumption and a consumer who acquires (transfers) a product from another consumer, for example, as a gift. A non-limiting example of a product is an alcoholic beverage such as whiskey or wine.

[0022] In Fig. 1, for example, client terminal 60 corresponds to a "manufacturer terminal 60" that may be operated by a manufacturer of alcoholic beverage products. Client terminal 80A corresponds to a "wholesaler terminal 80A" that may be operated by a wholesaler of alcoholic beverage products, and client terminal 80B corresponds to a "retailer terminal 80B" that may be operated by a retailer of alcoholic beverage products. Since both wholesalers and retail stores are sellers of alcoholic beverage products, wholesaler terminal 80A and retailer terminal 80B may be collectively referred to as "seller terminal 80".

[0023] The client terminal 100 corresponds to, for example, a "consumer terminal 100" that can be operated by a consumer of alcoholic beverage products. The manufacturer terminal 60, the wholesaler terminal 80A, the retail store terminal 80B, and the consumer terminal 100 may each be provided in the system 10 in two or more units.

[0024] Each of the client terminals 60, 80A, 80B, and 100 may be any type of apparatus or device having communication capabilities. As a non-limiting example, one or more of the client terminals 60, 80A, 80B, and 100 may be a laptop or desktop type personal computer (PC), a mobile phone, a smartphone, a tablet PC, or any combination thereof.

[0025] The NFT server 20 is configured to be able to mint, for example, an NFT associated with (or representing) an exercisable right regarding an alcoholic beverage product provided by a manufacturer, such as a right to request delivery of the alcoholic beverage product (hereinafter also referred to as an "acquisition right"), to a wallet address to which a user who wishes to purchase the alcoholic beverage product has access.

[0026] The terminal operated to purchase alcoholic beverage products may be any of the wholesaler terminal 80A, the retail store terminal 80B, and the consumer terminal 100. In addition, multiple NFTs may be minted together as a virtual inventory of alcoholic beverage products in a wallet address to which the manufacturer terminal 60 has access.

[0027] An NFT with associated purchase rights is an example of a first NFT and may be conveniently referred to as a "purchase rights NFT." Purchase rights NFTs may be understood to function as a "voucher" for a physical alcoholic beverage product (hereinafter also referred to as a "real product").

[0028] An "Access Right" may be, for example, a "Priority Access Right" (also referred to as an "Allow List") that may receive priority over an "Access Right" with respect to the purchase price and / or availability of the alcoholic beverage product. A "Priority Access Right" may be understood to function as a "Reservation Voucher."

[0029] The alcoholic beverage product associated with an access rights NFT (including priority access rights NFT; the same applies below) may be an alcoholic beverage product (actual product) that actually exists as a finished product at the time the NFT is issued, or it may be an alcoholic beverage product that is scheduled to be manufactured or completed after the NFT is issued.

[0030] When a distributor terminal 80 of an alcoholic beverage product wishes to purchase one or more alcoholic beverage products manufactured by a manufacturer, the distributor terminal 80 purchases an acquisition right NFT in place of the actual product. Similarly, a consumer terminal 100 purchases an acquisition right NFT from a manufacturer terminal 60 or a distributor terminal 80 in place of the actual product.

[0031] In this way, the right to purchase an alcoholic product NFT is distributed from the manufacturer to the distributor and from the distributor to the consumer without the actual product. In other words, every time a purchase of the right to purchase NFT (sales contract or transfer contract) is completed, a transfer transaction of the right to purchase NFT between wallet addresses is recorded in the blockchain 40.

[0032] A consumer of an alcoholic beverage product may, for example, operate the consumer terminal 100 to burn the acquisition right NFT minted to the consumer's wallet address, thereby declaring or expressing to the NFT server 20 that he or she will exercise the right to request delivery of the actual alcoholic beverage product.

[0033] Upon receiving a declaration or representation of the exercise of the delivery request right, the NFT server 20 instructs, for example, the manufacturer terminal 60 to deliver the alcoholic beverage product. As a result, the consumer obtains the actual alcoholic beverage product represented by the burned purchase right NFT.

[0034] The transactions of the right NFT on the blockchain 40 as described above (e.g., minting, transferring, and burning) are sequentially recorded in an unalterable state on the blockchain 40. For example, the NFT server 20 updates the owner (ownership) information of the right NFT to new owner information every time the right NFT is transferred between wallet addresses. The ownership information is also referred to as the owner (or holder) ID, and may be represented, for example, by the wallet address where the NFT was minted.

[0035] Therefore, for example, the NFT server 20 or a manufacturer terminal 60 that cooperates with the NFT server 20 can check the distribution route of the acquisition right NFT by referring to the transaction history of the acquisition right NFT recorded in the blockchain 40.

[0036] Therefore, the manufacturer terminal 60 can, for example, know information about a customer who used (burned or transferred) the purchase right NFT, and can trace what kind of transfer transaction was carried out and who ultimately consumed the alcoholic beverage product.

[0037] In this way, by distributing NFTs that are associated with the right to obtain the actual product instead of the actual product, it is possible to prevent, for example, deterioration in quality and the influx of counterfeits in the distribution route of the actual product. Popular alcoholic beverage products (e.g., whiskey) are easily subject to illegal resale at high prices that the manufacturer does not intend. For manufacturers, in a difficult-to-control commercial flow where illegal resale may occur, the deterioration of the quality of alcoholic beverage products during distribution (which may include, for example, illegal refilling of whiskey bottles) and the influx of counterfeits may damage the brand value.

[0038] According to the system 10 disclosed herein, by distributing the right to purchase NFTs instead of actual products, a trade flow can be formed that does not involve actual products and can be controlled or managed by the NFT server 20, thereby preventing deterioration of the quality of alcoholic beverage products and unauthorized resale, protecting the brand value of alcoholic beverage products, and ultimately protecting manufacturers and consumers.

[0039] Furthermore, information indicating whether or not a genuine alcoholic beverage product manufactured by the manufacturer has been delivered to a consumer through a regular distribution route can be confirmed on the NFT server 20 and provided to the manufacturer terminal 60. Therefore, for example, information on consumers who have purchased an alcoholic beverage product at a fair price through a regular distribution route can be visualized on the manufacturer terminal 60. Therefore, the manufacturer can use the provided information, for example, for strategies such as sales promotion, advertising, and marketing of alcoholic beverage products.

[0040] Here, the NFT server 20 of this embodiment may be configured to generate an NFT associated with (or representing) incidental data related to the alcoholic beverage product to be purchased with the acquisition right NFT (hereinafter, sometimes referred to as "RWA-related data"), and issue the NFT together with the acquisition right NFT to the blockchain 40. The RWA-related data may include collectible data that is valuable to consumers, and an NFT associated with such collectible data may be conveniently referred to as a "collectible NFT."

[0041] The collectible NFT is an example of a second NFT, and may be minted, for example, into the same wallet address together with the right to purchase NFT, and may be distributed together with the right to purchase NFT in the above-mentioned non-physical trade in the blockchain 40. The collectible NFT may be controlled or managed by the NFT server 20 so as to distribute the collectible NFT together with the right to purchase NFT on the blockchain 40 until it is delivered to the final consumer.

[0042] For example, a collectible NFT may be transferred between wallet addresses while bound to a rights NFT as a bindable NFT that can be linked to other NFTs, such as those described in the ERC5700 standard. Note that the binding can be released at any time by the owner of the NFT.

[0043] Of the acquisition rights NFT and the collectible NFT, the consumer can selectively burn or transfer the acquisition rights NFT and continue to hold the collectible NFT without burning or transferring it. If the collectible NFT is bound to the acquisition rights NFT, the consumer can cancel the binding (unbind) and burn the acquisition rights NFT.

[0044] The RWA-related data may include, by way of example, data regarding the manufacturing process of the alcoholic beverage product, data indicative of the etiquette (or label) of the alcoholic beverage product, data regarding the history of the manufacturer of the alcoholic beverage product (which may include, for example, a manufacturer and / or a brewery), data regarding the history of the alcoholic beverage product, data indicative of comments about the alcoholic beverage product (for example, tasting comments by the brewer), and other data related to the alcoholic beverage product. These data may be image data. The image data may be still image data or moving image data.

[0045] Data relating to the manufacturing process of alcoholic beverage products may include, for example, information indicating the aging period and / or the degree of aging (degree of aging) of whiskey (hereinafter sometimes abbreviated as "degree of aging information"). The degree of aging information may include, for example, not only information on the stage at which whiskey is drawn from the aging barrel (cask) and commercialized as a finished product (e.g., bottled), but also information on the intermediate stage of aging before commercialization as a finished product.

[0046] Because the quality of whiskey can vary depending on the length of time it is aged in the cask and / or the amount removed from the cask for bottling, by capturing NFTs of maturation information before it is bottled (during the maturation stage), consumers can be provided with information about the maturity of a whiskey product before they receive the finished product.

[0047] Therefore, a consumer can obtain a finished product with a maturity level that matches the consumer's preference by burning the acquisition right NFT at a timing of their choice regarding the maturity level of the whiskey. In other words, a consumer can select the timing of exercising the delivery request right for the finished alcoholic beverage product based on the maturity level information of the intermediate stage of maturation, and can instruct the manufacturer, for example, when the whiskey will be bottled as a finished product. Note that the maturation level information of the intermediate stage of maturation may be expressed as information indicating the planned time when the maturation in the cask will reach the desired maturity level.

[0048] By circulating collectible NFTs that are associated with maturation information for each alcoholic beverage product together with NFTs that give the right to purchase alcoholic beverages, intangible value such as the degree of maturation can be made visible as additional value and presented to consumers.

[0049] Therefore, consumers can enjoy a new experience that is different from collecting etiquette in the real world. In addition, by converting the history of the manufacturer and tasting comments about the whiskey product into NFTs and distributing them together with the acquisition rights NFTs, the manufacturer can directly convey the message they want to convey to consumers.

[0050] <Configuration Example of NFT Server 20> Hereinafter, a configuration example of the NFT server 20 that can provide the NFT service as described above will be described. FIG. 2 is a block diagram showing a configuration example of the NFT server (Service PF) 20 illustrated in FIG. 1.

[0051] As shown in FIG. 2, the NFT server 20 illustratively includes a processor 202, a memory 204, a storage device 206, an input device 208, an output device 210, and a communication device 212. These components are communicatively connected to each other, for example, by a bus 214.

[0052] In FIG. 2, the term "device" may be mutually read as other terms such as a circuit, a device, and a unit. The configuration of the NFT server 20 may be configured to include one or more of each device illustrated in FIG. 2, or may be configured without including some devices.

[0053] Each function in the NFT server 20 can be realized, for example, by the processor 202 reading and executing a program (or an application; the same applies hereinafter) 268 and / or data used in association with the execution of the program 268 from the storage device 206 via the memory 204. The processor 202 is an example of an arithmetic device having arithmetic capabilities, and is, for example, a central processing unit (CPU).

[0054] The program 268 may include instructions (for example, program codes) that cause the processor 202 to function or operate as an NFT issuance unit 221, an NFT management unit 222, a transaction management unit 223, a customer data management unit 224, and a shipping management unit 225 when read and executed by the processor 202.

[0055] The program 268 may be stored in advance in the storage device 206, or may be received by the NFT server 20 through a computer-readable storage medium or the network 120 (in other words, a telecommunications line). The program 268 may also be incorporated as part of the operating system (OS) of the NFT server 20.

[0056] The memory 204 and the storage device 206 are both examples of computer-readable storage media. The memory 204 may be composed of at least one of storage media such as a Read Only Memory (ROM), an Erasable Programmable ROM (EPROM), an Electrically Erasable Programmable ROM (EEPROM), and a Random Access Memory (RAM).

[0057] The storage device 206 may be composed of at least one of the following storage media: an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a solid-state drive (SSD), a flexible disk, a magneto-optical disk (e.g., a compact disk, a Blu-ray (registered trademark) disk), and a flash memory.

[0058] The input device 208 may correspond to an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, a camera, etc.) that receives input from an external device. The output device 210 may correspond to an output device (e.g., a display, a printer, a speaker, etc.) that performs output to an external device. The input device 208 and the output device 210 may be integrated into one device, such as a touch panel.

[0059] The communication device 212 is an example of a hardware device for communicating with an external device (e.g., the blockchain 40 as a communication partner, the terminal 60, 80A, 80B, or 100) via the network 120. The communication device 212 may be referred to as, for example, a network device, a network controller, a network card, or a communication module.

[0060] In addition to the above-mentioned program 268, the storage device 206 stores, for example, customer data 262, RWA-related data 264, and NFT management data 266. An example of the customer data 262 is shown in FIG. 3, an example of the RWA-related data 264 is shown in FIG. 4, and an example of the NFT management data 266 is shown in FIG. 5.

[0061] <Example of Customer Data 262> As shown in FIG. 3, customer data 262 includes, as a non-limiting example, data that associates, for each identifier for identifying a customer (customer ID #1 to #N; N is an integer greater than or equal to 1), information indicating a customer type (consumer, wholesaler, retail store, etc.), information indicating the customer's age or generation, wallet information (e.g., a wallet address) that identifies a wallet that the customer owns (or has access to) in blockchain 40, and delivery information (e.g., the customer's name or title, and address information that the customer has previously designated as the delivery destination for alcoholic beverage products, etc.).

[0062] In this embodiment, the customer data 262 is assumed to be data that has undergone KYC (Know Your Customer) procedures, for example, between the customer and the manufacturer, or between the customer and the provider (or administrator, for example, a system of a financial institution such as a bank) of the NFT server 20. In addition, in the customer data 262, the wallet information may be wallet information that the manufacturer has opened as a KYC-completed wallet and provided to the customer, or it may be wallet information that the customer has opened independently and provided by the customer.

[0063] Furthermore, in the customer data 262, personal information such as, for example, the customer's age and / or address information may be limited to personal information about customers who have consented to the acquisition of personal information, for example, in the KYC procedure. In cases such as when delivering alcoholic products to customers who have not consented to the acquisition of personal information, for example, the delivery destination may be communicated to the delivery operator using zero-knowledge proof (ZKP) technology.

[0064] When using ZKP technology, the customer data 262 may be encrypted and then stored in the storage device 206. Encryption and decryption of the customer data 262 may be performed, for example, in the processor 202 (for example, the shipping management unit 225). In other words, the processor 202 or the shipping management unit 225 may be provided with an encryption unit that encrypts the customer data 262 and a decryption unit that decrypts the encrypted customer data 262.

[0065] <Examples of RWA-related data 264> The RWA-related data 264 illustrated in FIG. 4 includes, as a non-limiting example, for each identifier (product ID) of an alcoholic product, a lot number, a cask number, aging degree information (for example, image data indicating the aging degree), label information (for example, label image data of the alcoholic product), comments about the alcoholic product (for example, tasting comments, etc.), and data associating historical information of the manufacturer or the product. The aging degree information and / or the comments may be one or more for one alcoholic product. In FIG. 4, m, p, q, M, and K are all integers of 1 or more.

[0066] The "product ID" is information that uniquely identifies an alcoholic product and may be, for example, a serial number assigned to each individual alcoholic product. The "lot number (LOT No.)" is, for example, a number that identifies products manufactured (for example, bottled) at the same time. The "cask number (Cask No.)" is, for example, a number that identifies the cask used in the brewing of whiskey.

[0067] In whiskey products, it is also possible that whiskies brewed and aged in a plurality of different aging barrels are blended to produce one product (e.g., a whiskey bottle). For example, in FIG. 4, the whiskey product with lot number #1 indicates that the whiskey drawn from one barrel identified by cask number #1 is bottled. On the other hand, the whiskey product with lot number #2 indicates that the whiskies drawn from two different barrels with cask numbers #1 and #2 are blended and bottled.

[0068] Note that the customer data 262 and the RWA-related data 264 are, for example, provided in advance from the manufacturer terminal 60 to the NFT server 20 and are shared (in other words, linked or synchronized) between the NFT server 20 and the manufacturer terminal 60.

[0069] <Example of NFT management data 266> The NFT management data 266 illustrated in FIG. 5 includes, as a non-limiting example, data associating the type of NFT (acquisition right or collectible), the owner ID identifying the current owner of the NFT, and the NFT status (e.g., valid or invalid) for each NFT issued by the NFT server 20. The owner ID can be represented, for example, by information on the wallet in which the NFT was minted (e.g., the wallet address).

[0070] For example, in FIG. 5, the acquisition right NFT identified by NFT ID#1, together with the collectible NFT identified by NFT ID#2, was minted to the wallet address #1 of the user (customer), and both NFTs are "valid" (in other words, not burned).

[0071] Note that, as illustrated by NFT ID#5 and NFT ID#n in FIG. 5, acquisition right NFTs without accompanying collectible NFTs may be issued by the NFT server 20.

[0072] Based on the above customer data 262, RWA-related data 264, and NFT management data 266, the NFT server 20 controls or manages transactions related to NFTs, such as the issuance, transfer, or burning of acquisition rights NFTs and collectible NFTs, in cooperation with the blockchain 40.

[0073] 2, for example, the NFT issuing unit 221 issues an alcohol product right NFT and a collectible NFT based on the customer data 262 and the RWA-related data 264 in response to receiving an NFT issuance request from the manufacturer terminal 60. The issued NFT is minted to the destination wallet address specified in the NFT issuance request based on the wallet information of the customer data 262, for example.

[0074] In addition, if a destination wallet address is not specified in the NFT issuance request, the NFT issuing unit 221 may mint the NFT set as part of the manufacturer's inventory of alcoholic beverage products to the wallet address of the manufacturer terminal 60, which is the source of the NFT issuance request, based on the wallet information in the customer data 262, for example.

[0075] 6 shows an example of a data structure 600 of an NFT. The data structure 600 illustrated in FIG. 6 may be common to an acquisition rights NFT and a collectible NFT. The data structure 600 illustratively includes index data 602, metadata 604, and content data 606.

[0076] The index data 602 may include, for example, an NFT ID 622, an owner ID 624, and a uniform resource identifier (URI) 626 indicating a link to the metadata 604. The NFT ID 621 is identification information for uniquely identifying the NFT, and the owner ID 624 may include the wallet address of the current owner of the NFT, etc. In the blockchain 40, the owner ID 624 is updated in response to the transfer of the NFT, whereby the ownership of the NFT is transferred in the blockchain 40.

[0077] The metadata 604 may include, for example, a name 642 of the NFT, a description 644 of the NFT, and a uniform resource locator (URL) 646 that provides a link to a location where the content data 606 is stored (e.g., a resource on the Internet).

[0078] The content data 606 linked to the metadata 604 by the URL 646 may include, for example, in the case of a rights NFT, image data evidencing the right to purchase an alcoholic beverage product, and in the case of a collectible NFT, may include the RWA-related data described above.

[0079] A terminal 60, 80A, 80B or 100 that has access to the wallet address where the NFT was minted can, for example, display on a display or print on a printer the metadata indicated by the URI 626 and the content data 606 indicated by the URL 646.

[0080] In addition, for example, NFT index data 602 may be recorded (on-chain) on the blockchain 40, and metadata 604 and content data 606 may be recorded (off-chain) in a storage medium other than the blockchain 40, for example, a distributed storage or network such as IPFS (InterPlanetary File System).

[0081] Returning to Figure 2, the NFT management unit 222, for example, in cooperation with the NFT issuing unit 221 and / or the transaction management unit 223, records and updates NFT management data 266 (see Figure 5) on an NFT-by-NFT basis in response to transactions related to NFTs on the blockchain 40 (such as issuance, transfer or burning of NFTs).

[0082] The transaction manager 223, for example, manages transactions related to NFTs (issuance, burning, or transfer of NFTs, etc.) in the blockchain 40. For example, the transaction manager 223 causes the NFT issuing unit 221 to issue an NFT in response to receiving an NFT issuance request from the manufacturer terminal 60. In response to the issuance of the NFT, the NFT manager 222 updates the NFT management data 266.

[0083] In addition, the transaction management unit 223, for example, in response to receiving an NFT transfer request or burn request from a client terminal 80A, 80B or 100, transfers or burns the corresponding NFT in the blockchain 40.

[0084] In response to the transfer of the NFT, for example, the NFT management unit 222 updates the owner ID 624 (e.g., wallet address) of the NFT identified by the NFT ID 622 specified in the transfer request to the new owner ID 624 of the transfer destination. In addition, the NFT management unit 222 updates the status of the NFT identified by the NFT ID 622 specified in the NFT burn request to invalid.

[0085] Customer data management unit 224 manages, for example, customer data 262 (see FIG. 3) as exemplified in FIG. 2 and FIG. 3. As described above, customer data 262 is linked or synchronized with customer data held by manufacturer terminal 60, and customer data management unit 224 can update customer data 262 in response to customer data provided by manufacturer terminal 60, for example.

[0086] The shipping management unit 225, for example, in cooperation with the NFT management unit 222 and / or the transaction management unit 223, performs a process in which, when a purchase right NFT is burned, an alcoholic beverage product associated with the burned purchase right NFT is shipped to the customer who burned the purchase right NFT.

[0087] For example, the shipping management unit 225 may identify the customer ID who burned the acquisition right NFT by referring to the customer data 262 based on the owner ID 624 (e.g., wallet address) of the burned (invalidated) NFT in the NFT management data 266. The shipping management unit 225 then performs shipping processing of the alcoholic beverage product to the shipping destination information corresponding to the identified customer ID in the customer data 262. The shipping processing may include, for example, instructing the manufacturer terminal 60 to ship the alcoholic beverage product, or requesting the delivery of the alcoholic beverage product to a terminal (not shown) of a delivery company affiliated with the manufacturer.

[0088] The shipping process may also include, for example, verifying the age or age of the customer who burned the right NFT. Verifying the age or age of the customer can prevent alcohol products from being shipped to customers of an age or age that is prohibited from purchasing alcohol.

[0089] The shipping instructions may include, for example, shipping destination information identified in customer data 262. If the shipping destination information is not registered in customer data 262, for example, for a customer who has not consented to the collection of personal information, the shipping destination information may be transmitted to the shipping company using ZKP technology.

[0090] In addition, in the above-described configuration example of the NFT server 20, the term "part" can be replaced with other terms such as "circuit", "block", "module", and "means". In addition, some or all of the components or functions illustrated for the NFT server 20 may be integrated into a single component or function, or may be separated into multiple components or functions.

[0091] Furthermore, any one or more of the functions of the above-mentioned NFT issuing unit 221, NFT management unit 222, transaction management unit 223, customer data management unit 224, and shipping management unit 225 may be distributed and executed in a distributed manner in multiple NFT servers 20. The multiple NFT servers 20 may be, for example, a group of cloud servers virtualized by virtualization technology.

[0092] Furthermore, any one or more of the NFT issuing unit 221, the NFT management unit 222, the transaction management unit 223, the customer data management unit 224, and the shipping management unit 225 may be implemented, for example, in the blockchain 40 (for example, as a smart contract). In other words, the NFT server 20 may correspond to any one or more of the multiple computers (nodes) that make up the blockchain 40.

[0093] In addition, each client terminal such as the manufacturer terminal 60, the wholesaler terminal 80A, the retail store terminal 80B, and the consumer terminal 100 may, as an example of a hardware configuration, be equipped with a processor, memory, a storage device, an input device, an output device, and a communication device, all interconnected by a bus, similar to the NFT server 20.

[0094] As an example of a functional configuration, each of the client terminals 60, 80A, 80B and 100 may be provided with a functional unit corresponding to an NFT management unit 222 and a transaction management unit 223, and a program that embodies the functional unit by being read and executed by a processor may be stored in a storage device.

[0095] <Example of operation> Next, an example of the operation of the system 10 configured as described above will be described with reference to Figs. 7, 8, and 9. Fig. 7 is a diagram showing the overall operation flow of the system 10 in a case where a consumer consumes an alcoholic beverage product (e.g., a whiskey product) at home, and Fig. 8 is a diagram showing the overall operation flow of the system 10 in a case where a consumer gives a whiskey product as a gift to another consumer. Fig. 9 is a flowchart showing an example of the operation focusing on the NFT server 20 in the operation flow exemplified in Figs. 7 and 8.

[0096] <Self-consumption case> In FIG. 7, the manufacturer terminal 60 provides customer data 262 and RWA-related data 264 to the NFT server 20, and data linkage is performed between the manufacturer terminal 60 and the NFT server 20 (S702).

[0097] After that, for example, when a purchase request for a whiskey product is received from the wholesaler terminal 80A (S704), an NFT issuance request for the whiskey product is sent to the NFT server 20 (S706).

[0098] In the NFT issuance request, for example, information on the whiskey product associated with the acquisition right NFT (e.g., product ID, quantity, etc.), RWA-related data associated with the collectible NFT (maturation level, manufacturer history, etc.), mint wallet address, etc. may be specified by the manufacturer terminal 60. In this example, the mint wallet address is the wallet address of the wholesaler terminal 80A that sent the NFT issuance request.

[0099] 9, the NFT server 20 checks whether an NFT issuance request has been received (S902; NO). If an NFT issuance request has been received (S902; YES), the NFT server 20, for example, in the NFT issuing unit 221, generates a right-of-purchase NFT and a collectible NFT based on the information specified in the NFT issuance request, the customer data 262, and the RWA-related data 264.

[0100] Then, the NFT issuing unit 221 issues (mints) the acquisition right NFT and the collectible NFT as a set to the wallet address of the wholesaler terminal 80A that sent the NFT issuance request, for example (S708 in FIG. 7 and S904 in FIG. 9). In response to the issuance of the NFT, the NFT server 20 updates the NFT management data 266, for example, via the NFT management unit 222 (S906 in FIG. 9).

[0101] Then, as shown in FIG. 7, for example, when a purchase request for a whiskey product is sent from the retail store terminal 80B to the wholesaler terminal 80A (S710), the wholesaler terminal 80A sells a set of the purchase right NFT and the collectible NFT to the retail store terminal 80B in place of the actual whiskey product (S712).

[0102] For example, the wholesaler terminal 80A requests the NFT server 20 to transfer each of the acquisition right NFT and the collectible NFT to the retail store terminal 80B. In this transfer request, for example, the ID 622 of the NFT to be transferred and the wallet address of the transfer destination (in this example, the retail store terminal 80B) are specified.

[0103] The NFT server 20 (e.g., the transaction management unit 223) checks whether a request regarding the transfer or burning of an NFT is received by the client terminal 80A, 80B or 100, as shown in FIG. 9 (NO in S908 and S912).

[0104] When an NFT transfer request is received by the NFT server 20 from the wholesaler terminal 80A (S908; YES), the transaction management unit 223, for example, updates the owner ID 624 of the acquisition right NFT and the collectible NFT related to the transfer request in the blockchain 40 to the wallet address of the retail store terminal 80B.

[0105] As a result, the ownership of the acquisition right NFT and the collectible NFT is transferred from the wholesaler terminal 80A to the retail store terminal 80B. In response to the transfer of the acquisition right NFT and the collectible NFT, for example, the NFT management unit 222 updates the owner ID of the NFT in the NFT management data 266 (S910).

[0106] Then, as shown in FIG. 7, for example, when a purchase request for a whiskey product is sent from the consumer terminal 100 to the retail store terminal 80B (S714), the retail store terminal 80B, like the wholesaler terminal 80A, sells a set of the purchase right NFT and the collectible NFT to the consumer terminal 100 in place of the actual whiskey product (S716).

[0107] For example, the retail store terminal 80B requests the NFT server 20 to transfer each of the acquisition right NFT and the collectible NFT to the consumer terminal 100. In this transfer request, for example, the ID 622 of the NFT to be transferred and the wallet address of the transfer destination (in this example, the consumer terminal 100) are specified.

[0108] When an NFT transfer request is received by the NFT server 20 from the retail store terminal 80B (S908; YES in Figure 9), for example, the transaction management unit 223 updates the owner ID of each of the acquisition right NFT and collectible NFT related to the transfer request in the blockchain 40 to the wallet address of the consumer terminal 100.

[0109] As a result, the ownership of the acquisition right NFT and the collectible NFT is transferred from the retail store terminal 80B to the consumer terminal 100. In response to the transfer of the acquisition right NFT and the collectible NFT, for example, the NFT management unit 222 updates the owner ID of the NFT in the NFT management data 266 (S910 in FIG. 9).

[0110] In the above transfer transactions of the acquisition right NFT and the collectible NFT, the payment method of the purchase price (in other words, the establishment of a sales contract or transfer contract) is not particularly limited, but may be, for example, a transfer between wallet addresses of virtual currency corresponding to the purchase price. The virtual currency transfer process may be realized, for example, by a smart contract on the blockchain 40.

[0111] 7, the consumer terminal 100 may exercise the right to request delivery of the whiskey product associated with the acquisition right NFT by requesting the NFT server 20 to burn the acquisition right NFT at any time, out of the acquisition right NFT and the collectible NFT, as shown in S718 in FIG. 7. In the request to burn the acquisition right NFT, for example, the ID 622 of the NFT to be burned is specified in the consumer terminal 100.

[0112] In the NFT server 20, for example, the transaction management unit 223 checks whether a request to burn the acquisition right NFT has been received from the consumer terminal 100 (NO in S908 and YES in S912 in FIG. 9).

[0113] When the burning request is received by the NFT server 20, the NFT server 20, for example, in the shipping management unit 225, identifies the owner ID by referring to the NFT management data 266 based on the NFT ID 622 specified in the received burning request.

[0114] Then, the shipping management unit 225 identifies a customer ID by referring to the customer data 262 illustrated in Figure 3 based on the identified owner ID, and confirms whether the user of the consumer terminal 100 identified by the identified customer ID is an appropriate purchaser of the whiskey product (S914 and S916 in Figure 9).

[0115] In addition, if consent to the acquisition of personal information has not been obtained for the user, age or generation verification may be carried out between the NFT server 20 and the consumer terminal 100, for example using ZKP technology.

[0116] If the result of this age or generation confirmation shows that the user of the consumer terminal 100 is of an age or generation permitted for the provision of alcoholic beverages, the shipping management unit 225 determines that the user of the consumer terminal 100 is appropriate to purchase whiskey products (S916; YES).

[0117] In response to determining that the purchaser is appropriate, the shipping management unit 225 instructs the manufacturer terminal 60, for example, to ship the actual whiskey product associated with the burned NFT to the user of the consumer terminal 100 (S720 in FIG. 7 and S918 in FIG. 9).

[0118] The shipping instruction includes, for example, the delivery destination information identified in the customer data 262 (see FIG. 3). In addition, the shipping management unit 225 instructs the transaction management unit 223 to invalidate the burned NFT, for example.

[0119] In response to an instruction from the delivery management unit 225, the transaction management unit 223, for example, burns and invalidates the acquisition right NFT of the NFT ID specified in the burn request in the blockchain 40. In response to the invalidation of this acquisition right NFT, for example, the NFT management unit 222 updates the status of the burned acquisition right NFT to invalid (burned) in the NFT management data 266 (S920 in FIG. 9).

[0120] When the manufacturer terminal 60 receives a shipping instruction from the NFT server 20, it ships the burned whiskey product to the shipping destination indicated by the shipping destination information specified in the received shipping instruction (S722 in FIG. 7). Note that the delivery of the whiskey product to the shipping destination may be performed, for example, by the manufacturer's shipping department or by a delivery company affiliated with the manufacturer.

[0121] When the delivery of the whiskey product is completed, the delivery company terminal (not shown) may notify, for example, the NFT server 20 of the completion of delivery. When the NFT server 20 (for example, the shipping management unit 225) receives the delivery completion notification, it may transmit the delivery completion notification to, for example, the manufacturer terminal 60.

[0122] In addition, in S916 of Figure 9, if the user of the consumer terminal 100 is not of the age or generation permitted to be served alcoholic beverages (S916; NO), the shipping management unit 225 will perform NG processing, such as notifying the consumer terminal 100 that serving alcoholic beverages is not permitted, without performing shipping processing of the whiskey product (S922 of Figure 9).

[0123] <Gift case> In the case of a gift, for example, as shown in FIG. 8, a first consumer terminal 100 that has acquired a set of acquisition rights NFTs and collectible NFTs requests the NFT server 20 to transfer (assign) the set of NFTs to another (second) consumer terminal 100A, for example for gift purposes (S802).

[0124] In this transfer request, for example, the ID 622 of the NFT to be transferred and the wallet address of the transfer destination (consumer terminal 100A) are specified. Note that the flow until the first consumer terminal 100 acquires the acquisition right NFT and the collectible NFT may be the same as that shown in FIG.

[0125] When the NFT server 20 receives an NFT transfer request from the first consumer terminal 100 to the second consumer terminal 100A (S908; YES in Figure 9), for example, the transaction management unit 223 updates the owner ID 624 of each of the acquisition right NFT and collectible NFT related to the transfer request to the wallet address of the consumer terminal 100A.

[0126] As a result, the ownership of the acquisition right NFT and the collectible NFT is transferred from the first consumer terminal 100 to the second consumer terminal 100A (S802 in FIG. 8). In response to the transfer of the acquisition right NFT and the collectible NFT, for example, the NFT management unit 222 updates the owner ID of the corresponding NFT identified by the NFT ID in the NFT management data 266 (S910 in FIG. 9).

[0127] 8, the second consumer terminal 100A may exercise the right to request delivery of the whiskey product associated with the acquisition right NFT by requesting the NFT server 20 to burn the acquisition right NFT at any time, out of the acquisition right NFT and the collectible NFT, as shown in S804 in FIG. 8. In the request to burn the acquisition right NFT, for example, the ID 622 of the NFT to be burned is specified in the second consumer terminal 100A.

[0128] 9, the NFT server 20 confirms that the request to burn the acquisition right NFT has been received in the transaction manager 223 (NO in S908 and YES in S912). After that, a process is carried out in which the "consumer terminal 100" in the process of the "self-consumption case" illustrated in FIG. 7 is replaced with the "consumer terminal 100A."

[0129] For example, when the NFT server 20 receives a request to burn a purchase right NFT (S912 in FIG. 9; YES), the transaction management unit 223 performs processing such as age verification as in the case of personal consumption, and then instructs the manufacturer terminal 60 to ship the actual whiskey product associated with the burned purchase right NFT to the delivery address specified by the second consumer terminal 100A (S806 in FIG. 7 and S918 in FIG. 9).

[0130] After that, as in the "self-consumption case" (Figure 7), the burnt whiskey product is shipped to the delivery destination identified by the delivery destination information specified in the shipping instruction (S808 in Figure 8).

[0131] In addition, there may be cases where the user of the second consumer terminal 100A, who is the transferee of the acquisition right NFT, transfers (assigns) the acquisition right NFT to another (third) consumer terminal for gift purposes without burning it. Even in such a case, the final transferee of the acquisition right NFT can burn the acquisition right NFT, and the whiskey product can be delivered to the final transferee in the same manner as in the above-mentioned operation example.

[0132] As described above, according to the system 10 of this embodiment, by using the acquisition right NFT to form a commercial flow without the need for physical products and distributing NFTs instead of physical products, it is possible to prevent deterioration of the quality of whiskey products and illegal resale, thereby protecting manufacturers and consumers.

[0133] In addition, by circulating collectible NFTs that are linked to the maturation information of each whiskey product together with the NFT that grants the right to purchase that whiskey product, intangible value such as the progress of maturation can be made visible as additional value and presented to consumers.

[0134] Therefore, consumers can enjoy a new experience value that is different from collecting etiquette in the real world. In addition, by converting the maturity information of the maturation stage before bottling into NFT, it is possible to present information about the maturity to consumers before obtaining the finished product.

[0135] Therefore, a consumer can control the timing of exercising the right to request delivery of a finished whiskey product based on, for example, the maturation information of the intermediate stages of maturation. Thus, the consumer can obtain a finished product with a maturation level that suits his / her taste at a time of his / her choice.

[0136] In addition, by converting the manufacturer's history and comments about the whiskey products into NFTs and distributing them together with the NFT purchase rights, the manufacturer can directly convey the message they want to convey to consumers.

[0137] <Additional information> In the operational example described above with reference to Figures 7 to 9, the wholesaler terminal 80A is the terminal from which a purchase request for a whiskey product is made to the manufacturer terminal 60, but the terminal from which a purchase request for a whiskey product is made to the manufacturer terminal 60 may be the retail store terminal 80B or the consumer terminal 100.

[0138] In other words, there may be cases where the retail store terminal 80B makes a purchase request for a whiskey product to the manufacturer terminal 60 without going through the wholesaler terminal 80A, and there may be cases where the consumer terminal 100 makes a purchase request for a whiskey product to the manufacturer terminal 60 without going through the distributor terminal 80.

[0139] In either case, the manufacturer terminal 60, for example, when requesting the NFT issuance from the NFT server 20, specifies the wallet address to which the NFT is to be issued as the wallet address of the terminal from which the product purchase request was made, and the purchase right NFT and collectible NFT are minted from the NFT server 20 to the wallet address of the terminal from which the product purchase request was made.

[0140] It is also possible to envision a case where one or more sets of purchase rights NFTs and collectible NFTs are minted into the wallet address of a manufacturer terminal 60 as, for example, a virtual inventory of whiskey products.

[0141] In such a case, in response to a purchase request for a whiskey product, the manufacturer terminal 60 may send an NFT transfer request to the wallet address of the purchase request source to the NFT server 20, instead of a request to issue an NFT to the wallet address of the purchase request source, for example at S706 in Figures 7 and 8.

[0142] The update of the NFT owner ID associated with such an NFT transfer transaction from the manufacturer terminal 60 to the purchase request terminal may be similar to the update associated with an NFT transfer transaction between the wholesaler terminal 80A and the retail store terminal 80B, or between the retail store terminal 80B and the consumer terminal 100.

[0143] In the above-described embodiment, there may be a plurality of blockchains 40. For example, the NFT server 20 (e.g., the transaction manager 223) may be configured to manage transactions of right NFTs and / or collectible NFTs based on a protocol called ILP (InterLedger Protocol) that links tokens between different blockchains 40.

[0144] Although the present disclosure has been described with reference to exemplary embodiments, various embodiments that are modified in configuration and detail can be realized without departing from the spirit of the present disclosure. [Explanation of symbols]

[0145] 10. NFT Service System 20 NFT Server 40 Blockchain System 60 Client terminals (manufacturer terminals) 80A Client terminal (wholesaler terminal) 80B Client terminals (retail store terminals) 100 Client terminals (consumer terminals) 120 Network (NW) 202 Processor 204 Memory 206 Storage device 208 Input Device 210 Output Device 212 Communication equipment 214 Bus 221 NFT Issuer 222 NFT Management Department 223 Transaction Management Unit 224 Customer Data Management Department 226 Shipping Management Department 262 Customer Data 264 RWA related data 266 NFT Management Data 268 Programs 602 Index Data 604 Metadata 606 Content Data 622 NFT ID 624 Owner ID 626 NFT URI 642 NFT Name 644 NFTs explained 646 URL

Claims

1. A non-fungible token issuing unit that issues, in a blockchain, a first non-fungible token associated with a right to claim delivery of an alcoholic beverage product and a second non-fungible token associated with incidental data related to the alcoholic beverage product; A transaction manager that manages transactions of the first non-fungible token and the second non-fungible token in the blockchain; a shipping management unit that, when a deletion request for the first non-fungible token is made in the transaction, instructs a manufacturer terminal of the alcoholic beverage product to ship the alcoholic beverage product to a delivery destination specified by the requester terminal of the deletion request; A server equipped with

2. The alcoholic beverage product is a whiskey product, 2. The server of claim 1, wherein the extrinsic data includes information about the stages during which the whiskey product is aged before being commercialized as a finished product.

3. The server of claim 2, wherein the ancillary data includes one or more of data indicative of a label of the whiskey product, data relating to a history of a manufacturer of the whiskey product, data relating to a history of the whiskey product, and data indicative of tasting comments about the whiskey product.

4. A server as described in any one of claims 1 to 3, wherein the shipping management unit checks whether the user is of an age or age group permitted to purchase the alcoholic product based on the user's age or age group previously registered for the requesting terminal, and if it is confirmed that the user is of an age or age group permitted to purchase the alcoholic product, instructs the manufacturer terminal to ship the alcoholic product.

5. 4. A server as claimed in any one of claims 1 to 3, wherein the requesting terminal is a first consumer terminal that receives the transfer of the first non-fungible token and the second non-fungible token in the transaction, or a second consumer terminal that receives the transfer of the first non-fungible token and the second non-fungible token from the first consumer terminal in the transaction.

6. 1. A method performed by a server, comprising: issuing, on a blockchain, a first non-fungible token associated with a right to claim delivery of an alcoholic beverage product and a second non-fungible token associated with ancillary data related to the alcoholic beverage product; Managing transactions of the first non-fungible token and the second non-fungible token on the blockchain; and When a deletion request for the first non-fungible token is made in the transaction, instructing a manufacturer terminal of the alcoholic beverage product to ship the alcoholic beverage product to a delivery destination specified by the requester terminal of the deletion request; A method comprising:

7. On the server, issuing, on a blockchain, a first non-fungible token associated with a right to claim delivery of an alcoholic beverage product and a second non-fungible token associated with ancillary data related to the alcoholic beverage product; Managing transactions of the first non-fungible token and the second non-fungible token on the blockchain; and When a deletion request for the first non-fungible token is made in the transaction, instructing a manufacturer terminal of the alcoholic beverage product to ship the alcoholic beverage product to a delivery destination specified by the requester terminal of the deletion request; A program that causes a process to be performed, including:

Citation Information

Patent Citations

  • A system for managing data on the storage status of barrels of sake and proof of ownership

    JP6829927B1

  • Alcohol token trading support device, alcohol token trading support method, program, and recording medium

    JP7389527B1

  • JPP7339406B

Cited By

  • Platform system and method for marketing support

    JP7843917B1