NFT marketplace system

Abstract

This NFT marketplace system comprises a server to which a user terminal connects via the internet, a database which is connected to the server, and a provider which is capable of reading / writing data from / to a blockchain that comprises a plurality of nodes. The server is configured to enable transactions for NFTs which are created in advance and for which information that is to be made public is recorded in the blockchain. Registered in the database is information which is associated with a token ID of an NFT and which is subject to limited publication. When a user has used the user terminal to connect to the server and has purchased an NFT, the server records, in the blockchain and via the provider, a transaction history of the NFT as information to be made public. Only once the user that purchased the NFT has completed a payment procedure on a payment screen which is displayed on the user terminal at the time of purchase of the NFT and a result indicating that the purchase process for the NFT is complete has been returned from the provider having confirmed the transaction history of the NFT recorded in the blockchain, the server displays, on the user terminal of the user who purchased the NFT, information that is subject to limited publication and that is registered in the database.

Description

NFT Marketplace System

[0001] The present invention relates to a system for realizing an NFT marketplace, and more specifically to an NFT marketplace system that ensures both the transparency of NFT (non-fungible token) transactions and privacy.

[0002] In recent years, as disclosed in Patent Documents 1 and 2, NFT marketplaces have been developed that utilize public blockchain technology to trade NFTs (non-fungible tokens) over the Internet.

[0003] In such an NFT marketplace, the information necessary for NFT transactions (such as the user's wallet address, the NFT's contents and selling price) is disclosed, and transactions are conducted directly between users in accordance with an automated execution program (smart contract) built on a public blockchain.

[0004] The transaction history is recorded on an unspecified number of computers participating in the public blockchain, making it extremely difficult to tamper with or erase. Furthermore, just like the information necessary for a transaction, the transaction history is also freely accessible to anyone.

[0005] As a result, NFT marketplaces that utilize public blockchain technology make it possible to conduct small-scale direct transactions between individuals in a manner that guarantees speed, reliability, and transparency.

[0006] JP 2023-000072 A Patent No. 7180943 A

[0007] On the other hand, as mentioned above, in an NFT marketplace that utilizes public blockchain technology, the information necessary for NFT transactions and the transaction history can be freely viewed by anyone, and it is difficult to erase the transaction history, making it unsuitable for disclosing users' private information (information related to personal privacy, such as real names, schedules, and contact information).

[0008] However, depending on the nature of the transaction, such as the purchase and sale of NFTs that involve the provision of services, it may be necessary to provide private information to the other party. In such cases, it was previously necessary to provide personal information such as contact details and exchange schedules individually on a separate site (off-chain) from the NFT marketplace where NFT transactions take place, which was time-consuming. Furthermore, providing private information to individual users who have never met at their own discretion not only lacks the reliability of the transaction, but is also undesirable from a security standpoint.

[0009] In light of this current situation, the present invention aims to provide an NFT marketplace system that can ensure the speed, reliability, and transparency of NFT transactions while also ensuring user privacy.

[0010] The present invention has been invented to solve the problems in the prior art as described above, and the NFT marketplace system of the present invention includes the following configuration.

[0011] [1] An NFT marketplace system comprising: a server to which a user terminal connects via the Internet; a database connected to the server; and a provider capable of reading and writing data to a blockchain consisting of multiple nodes, wherein the server is configured to enable trading of NFTs that have been created in advance and have information to be made public on the blockchain recorded therein; the database registers information to be made private in association with the token ID of the NFT; when a user connects to the server using the user terminal and purchases the NFT, the server records the transaction history of the NFT via the provider as information to be made public on the blockchain; and, on a payment screen displayed on the user terminal at the time of purchasing the NFT, the server displays the information to be made private that is registered in the database on the user terminal of the user who purchased the NFT only when the user who purchased the NFT has completed the payment procedure and the provider, having confirmed the transaction history of the NFT recorded on the blockchain, returns a result indicating that the NFT purchase process has been completed.

[0012] [2] The NFT marketplace system according to [1], wherein the information to be made private includes appointment-related information including at least a candidate date and time.

[0013] [3] The NFT marketplace system described in [2], wherein when a user who purchased the NFT selects a date and time from the candidate dates and times displayed on the user terminal of the user who purchased the NFT, the server registers the selected date and time in the database in association with the token ID of the NFT.

[0014] According to the present invention, when a transaction is made on an NFT marketplace, only the information necessary for the transaction and its transaction history that should be made public for the transparency of NFT transactions are recorded on the public blockchain, while private information of users that should only be shared between the parties to the transaction is recorded off-chain, thereby ensuring both the transparency of NFT transactions and privacy.

[0015] Furthermore, by allowing NFT transactions and private information exchanges to take place on the same NFT marketplace, users can reduce their workload.

[0016] FIG. 1 is a schematic diagram illustrating the configuration of an NFT marketplace system according to this embodiment.

[0017] Hereinafter, embodiments (examples) of the present invention will be described in more detail with reference to the drawings. In this specification, the person who operates the NFT marketplace system will be referred to as the "service administrator," the person who uses the NFT marketplace system to view the information necessary for transactions and the transaction history will be referred to as the "user," and among the users, the consultants and advisors who conduct NFT transactions will be collectively referred to as the "user."

[0018] Furthermore, in this specification, "information to be made public" refers to information that can be viewed by any user connected to the Internet, "information to be made private" refers to information that can be viewed only by users who are parties to NFT transactions, and "information to be kept private" refers to information that can be viewed only by the user who registered the information. However, even if it is "information to be made private" or "information to be kept private," it is preferable that information necessary for operating the NFT marketplace be made available to the service administrator.

[0019] 1 is a schematic diagram illustrating the configuration of an NFT marketplace system according to this embodiment. As shown in FIG. 1, the NFT marketplace system 10 according to this embodiment includes a user terminal 50 and a server 20 to which user terminals 50A and 50B are connected via the Internet 70.

[0020] The server 20 is an off-chain server, and has functions such as a web server, a mail server, a calendar server, a web conference server, and a file server, and is composed of one or more computers.

[0021] The server 20 also includes a database 22. As will be described later, the database 22 stores private information of the user entered by the user via the website, information on the basic contract for providing advice entered by the advisor via the website, and information necessary for transactions acquired from the blockchain 60 and the transaction history.

[0022] The server 20 also includes a provider 30. The provider 30 is configured to be able to read / write data from / to a blockchain 60 made up of multiple nodes 60A to 60F, and exchanges data between an off-chain network (Internet 70) and the blockchain network (blockchain 60).

[0023] The provider 30 only needs to be configured to be able to read / write data to the blockchain 60, and may be configured as a node of the blockchain 60 or may not function as a node.

[0024] The nodes 60A to 60F of the blockchain 60 are configured so that each node can communicate with other nodes peer-to-peer and exchange data. At least one of the nodes 60A to 60F (hereinafter referred to as a "full node") records all of the information necessary for NFT transactions conducted in the NFT marketplace system 10 and the transaction history. Nodes other than the full nodes (hereinafter referred to as "SPV nodes") record only the information necessary for transactions and some of the transaction history. Note that these nodes 60A to 60F are configured by computers. There need only be multiple nodes, and the number is not limited. While not particularly limited, a public blockchain such as Ethereum can also be used as the blockchain 60.

[0025] Note that some functions such as the mail server, calendar server, web conferencing server, file server, database 22, and provider 30 may not be implemented in the server 20, but may be configured to use external services with equivalent functions, such as Gmail (registered trademark), Google Calendar (registered trademark), Google Meet (registered trademark), web3.storage, MetaMask, and Alchemy.

[0026] The user terminal 50 and the user terminals 50A and 50B are users and terminals used by users who connect to the NFT marketplace system 10 of this embodiment via the Internet 70, and can be, for example, smartphones, tablet computers, personal computers, etc.

[0027] The NFT marketplace system 10 of this embodiment is configured to operate as follows: Note that in this embodiment, an example is given in which an advisor provides advice to a client using a web conference system, commercializing the service as an NFT and selling it in the NFT marketplace system 10, and a client who purchases the NFT receives the service, but the present invention is not limited to this and can be used for various NFT transactions.

[0028] <User Registration of Consultant> A consultant, who is a user, performs user registration using the user (consultant) terminal 50A in order to purchase NFTs using the NFT marketplace system 10.

[0029] Specifically, the client connects to the server 20 using the user terminal 50A and enters client information such as real name, date of birth, postal code, address, email address, telephone number, information on payment method, etc. The client information entered on the website is registered in the database 22 as information that should be kept confidential, and is kept confidential from anyone other than the client and the service manager.

[0030] In addition, when using external services for some functions such as a mail server, calendar server, or web conferencing server, it is preferable to enter the account number for the external service as part of the client information and to perform authentication in advance to use the external service.

[0031] In addition, information related to payment methods may include, for example, wallet addresses, information on credit cards and debit cards, administrative accounts for external payment services (e.g., Google Pay (registered trademark) and Apple Pay (registered trademark)), administrative accounts for common point services (e.g., Rakuten Points (registered trademark) and d Points (registered trademark)), etc.

[0032] In addition, the NFT marketplace may issue unique points, and the inquirer may be able to use these unique points as a payment method. In this case, the unique points may be awarded for the purchase of an NFT, or the inquirer may be able to purchase the unique points in advance.

[0033] <Advisor User Registration and Product Registration> An advisor, who is a user, uses the user (advisor) terminal 50B to perform user registration and product registration in order to sell NFTs using the NFT marketplace system 10.

[0034] Specifically, the advisor connects to server 20 using user terminal 50B and enters advisor information, such as postal code, address, email address, telephone number, and information regarding the remittance destination, on the displayed website. The advisor information entered on the website is registered in database 22 as information that should be kept confidential, and is kept confidential from anyone other than the advisor himself or herself and the service administrator.

[0035] In addition, if external services are used for some functions such as the mail server, calendar server, or web conferencing server, it is preferable to enter the account for the external service as advisor information and perform authentication in advance to use the external service.

[0036] It is preferable to strictly verify the identity of advisors, who are service providers. For this reason, it is preferable to use an online identity verification system such as eKYC (Electronic Know Your Customer), or to have the service manager verify the identity of the advisor by telephone, telegram, or authorized mail based on the advisor information entered.

[0037] Furthermore, when registering a product, the advisor uses user terminal 50B to input information on the website regarding the basic agreement for providing advice, such as the advisor's real name, advice theme, image, sales price, length of advice implementation time, implementation deadline, and sales period, as well as appointment-related information, such as potential dates and times for providing advice. The information regarding the basic agreement for providing advice input on the website is registered in database 22 as information to be made public, and some of this information is sent from server 20 to provider 30, where it is recorded on blockchain 60 via provider 30 and converted into an NFT.

[0038] On the other hand, appointment-related information entered on the website is to be kept private and is registered only in the database 22. In this case, the information relating to the basic contract for providing advice and the appointment-related information are associated and registered in the database 22.

[0039] <Sale of Products> The NFTs created as described above are published on a website that is displayed by connecting to the server 20 using the user terminal 50 and the user terminals 50A and 50B.

[0040] In addition, in order to reduce the fees (so-called "gas fees") incurred in converting to NFT and processing delays, information regarding the basic contract for implementing advice registered in database 22 may be displayed on a website from server 20 via provider 30 without being recorded in blockchain 60, and only the transaction history may be recorded in blockchain 60 via provider 30 when the NFT purchase process described below is completed.

[0041] <Purchase of a Product> The consultant connects to the server 20 using the user terminal 50A and selects an NFT to purchase from the NFTs published on the displayed website. In this case, information regarding the master agreement for providing advice for each NFT is displayed on the website, and the consultant can select the NFT to purchase while checking the information regarding the master agreement for providing advice. Note that the information regarding the master agreement for providing advice displayed on the website may be information registered in the database 22, or may be data recorded on the blockchain 60 obtained via the provider 30 and displayed.

[0042] Once the NFT to be purchased is decided, a payment screen will be displayed on the website, and the inquirer will complete the payment procedure by following the displayed payment screen. Note that, in the payment procedure, information regarding the payment method registered in advance may be used, or additional information regarding the payment method may be entered here and the information regarding the added payment method may be used.

[0043] When purchasing NFTs, once the inquirer completes the payment procedure on the payment screen displayed on the website, the server 20 will request the blockchain 60 via the provider 30 to process the NFT purchase, and the NFT purchase process will be carried out in accordance with the smart contract implemented on the blockchain 60.

[0044] When the NFT purchase process is completed, transaction history such as the wallet addresses of the parties to the transaction (consultant and advisor), the token ID that identifies the NFT, the name of the NFT marketplace where the purchase was made (contract address), and the date and time of the purchase are added to the blockchain 60.

[0045] In addition, if only the transaction history is recorded in the blockchain 60 via the provider 30 at the time the NFT purchase process is completed, the advisor's wallet address will not be recorded in the blockchain 60.

[0046] If a payment method other than crypto assets, such as a credit card, is used as the payment method, the NFT will be purchased using a payment agency service. In this case, not only the wallet addresses of the parties to the transaction but also the wallet address of the payment agency service provider will be recorded on the blockchain 60.

[0047] <Determining the Schedule> The server 20 periodically checks the purchase status of the NFT with the provider 30. When the provider 30 receives confirmation of the purchase status of the NFT from the server 20, it checks the NFT recorded in the blockchain 60, confirms whether the purchase process has been completed, and returns the result to the server 20.

[0048] The server 20 displays a schedule selection screen on the website for the client only when the client completes the payment procedure on the payment screen displayed on the website and a result indicating that the NFT purchase process has been completed is returned from the provider 30.

[0049] The schedule selection screen displays appointment-related information including candidate advice implementation dates and times registered in the database 22, and the client selects one desired advice implementation date and time from the displayed candidate advice implementation dates and times. The selected advice implementation date and time is associated with the NFT token ID and registered in the database 22, thereby finalizing the advice implementation date and time (appointment).

[0050] When the advice date and time is determined, the server 20 registers the advice date and time and the URL for the web conference in the calendars of the client and the advisor, which is realized by the calendar server function.The server 20 also uses the mail server function to send emails containing the advice date and time and the URL for the web conference to the email addresses of the client and the advisor.

[0051] It is preferable that if the schedule selection screen is closed, for example, because the client closes the browser before the advice date and time is fixed, the appointment-related information is displayed and the client can select a schedule when the client displays the website again using the user terminal 50A.

[0052] Furthermore, when purchasing NFTs using a payment method other than crypto assets, such as a credit card, it is necessary to transition to the website of an external service, and therefore it is not possible to display the schedule selection screen synchronously with the completion of the NFT purchase process. Therefore, as described above, it is preferable to configure the system so that, after the NFT purchase process is completed, when the client displays the website again using user terminal 50A, appointment-related information is displayed and the client can select a schedule.

[0053] For example, when a client connects to server 20 using user terminal 50A, the website displayed displays the NFT held by the client, and if the date and time of advice provision is not registered in database 22 in association with the token ID of the NFT, a link to display appointment-related information can be displayed on the website, allowing the client to select a schedule. In this case, server 20 needs to be configured to obtain NFT holder information recorded in blockchain 60 via provider 30 and confirm whether the client holds NFT on blockchain 60.

[0054] The server 20 can also be configured to use the mail server function to send reminder emails to the email addresses of the client and advisor when the advice implementation date and time approaches.

[0055] The server 20 can also be configured to display a message screen on the website for exchanging messages between the client and the advisor. Specifically, the message entered by the client on the message screen is registered in the database 22, and the message can be displayed on the website that the advisor opens when he or she connects to the server using the user terminal 50B.

[0056] <Providing Advice> Using user terminals 50A and 50B, the client and advisor connect to server 20 by opening the web conference URL in a browser or the like on the date and time the advice is to be provided, and server 20 then uses the web conference server functions to enable audio and video exchange between user terminals 50A and 50B. Note that communication between user terminals 50A and 50B may be configured to occur via server 20, or user terminals 50A and 50B may be configured to communicate peer-to-peer.

[0057] The advisor provides advice to the client through the web conference prepared in this manner. After the advice implementation date and time has passed, the server 20 adds information that the advice implementation has been completed via the provider 30, by associating it with the NFT token ID recorded in the blockchain 60, and can also register information that the advice implementation has been completed by associating it with information on the basic contract for the advice implementation registered in the database 22.

[0058] In this way, the NFT marketplace system 10 is configured so that private information of users that should only be shared between the parties to the transaction is registered only in the off-chain database 22, and information that should be made public, such as information necessary for the transaction and its transaction history, is registered in the database 22 and also recorded in the blockchain 60. This makes it possible to ensure the speed, reliability, and transparency of NFT transactions while also ensuring user privacy, without increasing the burden on users.

[0059] Although the preferred embodiment of the present invention has been described above, the present invention is not limited to this, and various modifications are possible within the scope of the object of the present invention.

[0060] 10 NFT marketplace system 20 Server 22 Database 30 Provider 50 User terminal 50A User (consultant) terminal 50B User (advisor) terminal 60 Blockchain 60A Node 60B Node 60C Node 60D Node 60E Node 60F Node 70 Internet

Claims

1. An NFT marketplace system comprising: a server to which a user terminal connects via the internet; a database connected to the server; and a provider capable of reading / writing data to a blockchain consisting of multiple nodes, wherein the server is configured to enable trading of NFTs that have been created in advance and have information to be made public on the blockchain recorded therein; information to be made private in association with the token ID of the NFT is registered in the database; when a user connects to the server using the user terminal and purchases the NFT, the server records the transaction history of the NFT as information to be made public on the blockchain via the provider, and displays the information to be made private that is registered in the database on the user terminal of the user who purchased the NFT on a payment screen displayed on the user terminal at the time of purchasing the NFT only when the user who purchased the NFT has completed the payment procedure and the provider has confirmed the transaction history of the NFT recorded on the blockchain and returned a result indicating that the purchase process of the NFT has been completed.

2. The NFT marketplace system of claim 1, wherein the information to be made private includes appointment-related information including at least a potential date and time.

3. The NFT marketplace system of claim 2, wherein when a user who purchased the NFT selects a date and time from the candidate dates and times displayed on the user terminal of the user who purchased the NFT, the server registers the selected date and time in association with the token ID of the NFT in the database.

Images