Transaction support system, transaction support method and program
Patent Information
- Application Number
- JP2022019630
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2022-02-10
- Publication Date
- 2024-11-08
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
Managing consistency when moving non-fungible tokens (NFTs) between different blockchains is difficult.
A transaction support system that disables the first NFT in a first wallet, confirms its unusability, and issues a second NFT to a second wallet, with management by a third-party administrator ensuring atomicity and consistency across blockchains.
Enables safe and managed transfer of digital assets across blockchains, ensuring atomicity and consistency of NFT transactions.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a transaction support system, a transaction support method, and a program.
Background Art
[0002] Ownership is managed using non-fungible tokens.
Prior Art Documents
Patent Documents
[0003]
Patent Document 1
Summary of the Invention
Problems to be Solved by the Invention
[0004] When transferring tokens between different blockchains, it is difficult to manage their consistency.
[0005] The present invention has been made in view of such a background, and an object thereof is to provide a technology capable of managing the transfer of digital assets.
Means for Solving the Problems
[0006] The main invention of the present invention for solving the above problems is a transaction support system, comprising: an NFT discard processing unit that makes unusable a first NFT stored in a first wallet of a first user in a first blockchain; a confirmation unit that confirms that the first NFT has become unusable; and an NFT issuance processing unit that issues a second NFT to a second wallet of a second user in a second blockchain on the condition that it has been confirmed that the first NFT has become unusable.
[0007] Further issues and solutions disclosed in this application will be made clear in the section on embodiments of the invention and in the drawings. [Effects of the Invention]
[0008] According to the present invention, the transfer of digital assets can be managed. [Brief explanation of the drawing]
[0009] [Figure 1] This figure shows an example of the overall configuration of a transaction support system according to one embodiment of the present invention. [Figure 2] This diagram explains the wallets for each blockchain. [Figure 3] This figure shows an example of the hardware configuration of management server 3. [Figure 4] This figure shows an example of the software configuration for management server 3. [Figure 5] This diagram illustrates the operation of the transaction support system of this embodiment. [Figure 6] This figure shows an example of the overall configuration of the transaction support system according to the second embodiment. [Figure 7] This figure shows an example of the software configuration of the management server 3 according to the second embodiment. [Modes for carrying out the invention]
[0010] <Summary of the Invention> The embodiments of the present invention will be described by listing them. The present invention has, for example, the following configuration. [Item 1] An NFT destruction processing unit that renders a first NFT stored in the first user's first wallet unusable on the first blockchain, A confirmation unit that confirms that the first NFT has become unusable, A second NFT issuance processing unit issues a second NFT to a second user's second wallet on a second blockchain, subject to the condition that the first NFT has become unusable. A transaction support system characterized by comprising [Item 2] The transaction support system according to Item 1, further comprising a first transfer processing unit that transfers a first NFT from the first wallet to a third wallet of an administrator in the first blockchain, the confirmation unit confirms that the first NFT stored in the third wallet has become unusable, the NFT issuance processing unit stores the issued second NFT in a fourth wallet of the administrator in the second blockchain, the transaction support system further comprises a second transfer processing unit that transfers the second NFT from the fourth wallet to the second wallet on the condition that it is confirmed that the first NFT has become unusable, A transaction support system characterized by [Item 3] The transaction support system according to Item 1, further comprising an issuance number storage unit that manages the quantity of the unusable first NFT and the quantity of the issued second NFT, A transaction support system characterized by [Item 4] The transaction support system according to any one of Items 1 to 3, wherein the content associated with the first NFT is the same as the content associated with the second NFT, A transaction support system characterized by [Item 5] Steps of making unusable a first NFT stored in a first wallet of a first user in a first blockchain, confirming that the first NFT has become unusable, issuing a second NFT to a second wallet of a second user in a second blockchain on the condition that it is confirmed that the first NFT has become unusable, A transaction support method characterized by being executed by a computer. [Item 6] A step of disabling the first NFT stored in the first wallet of the first user in the first blockchain; A step of confirming that the first NFT has been disabled; A step of issuing a second NFT to the second wallet of the second user in the second blockchain on the condition that it has been confirmed that the first NFT has been disabled; A program for causing a computer to execute.
[0011] <Overview of the System> FIG. 1 is a diagram showing an example of the overall configuration of a transaction support system according to an embodiment of the present invention. The transaction support system of this embodiment includes a management server 3. The management server 3 can access the blockchain network 1 and the blockchain network 2. The user terminal 4 of the first user (User A) can access the blockchain network 1, and the user terminal 5 of the second user (User B) can access the blockchain network 2. Note that the user terminals 4 and 5 may be able to access the blockchain networks 2 and 1, respectively. Also, User A and User B may be the same person, and the user terminals 4 and 5 may be the same terminal.
[0012] The blockchain networks 1 and 2 are composed of a plurality of nodes (computers) and can manage ledger data in a distributed manner. The distributed ledger is managed in a tamper-resistant manner by the so-called blockchain mechanism. Here, a detailed description of the mechanism of distributed ledger management by blockchain is omitted as a general one is adopted. The blockchain networks 1 and 2 can be constructed by, for example, Ethereum.
[0013] Tokens that can be issued by blockchain networks 1 and 2, such as Ethereum (Ethereum tokens), include fungible tokens and non-fungible tokens (NFTs). Unlike fungible tokens, NFTs are tokens that do not have fungibility. NFTs can have their own unique value that distinguishes them from other NFTs. For this reason, NFTs have a unique identifier (NFT-ID) that enables them to be distinguished from other NFTs. An NFT is, for example, a token issued in accordance with the ERC (Ethereum Request for Comments) 721 standard. NFTs that comply with the ERC 721 standard are also called NFT-721 tokens. In this embodiment, as an example, we assume that the NFT is an NFT-721 token. Like fungible tokens, NFTs are tradable on blockchain networks 1 and 2. The transaction history of NFTs is recorded on blockchain networks 1 and 2. The distributed ledgers of blockchain networks 1 and 2 also record the owner and ownership history of NFTs.
[0014] In this embodiment of the transaction support system, when transferring an NFT stored in the wallet of user A on blockchain network 1 to the wallet of user B on blockchain network 2, the transfer can be performed securely. To transfer an NFT across blockchains, it is necessary to destroy the NFT on the source blockchain and issue a new NFT on the destination blockchain. To ensure the atomicity of these processes, this embodiment of the transaction support system allows the destruction and creation of the NFT to be performed as a series of processes under the management of administrator X by routing the transfer through the wallet of a third party (in this embodiment, administrator X of management server 3, referred to as the administrator user), who is different from the end users (users A and B).
[0015] Figure 2 illustrates the wallets for each blockchain. As shown in the figure, user A's wallet 11 is set up on blockchain network 1, and user B's wallet 22 is set up on blockchain network 2. Administrator X will open wallets for all blockchain networks that they support transactions for. In the example in Figure 2, administrator X's wallet 12 is set up on blockchain network 1, and administrator X's wallet 21 is set up on blockchain network 2.
[0016] <Management Server> The management server 3 may be a general-purpose computer such as a workstation or personal computer, or it may be logically implemented through cloud computing. Figure 3 shows an example of the hardware configuration of the management server 3. Note that the illustrated configuration is just one example, and other configurations are also possible. The management server 3 includes a CPU 301, memory 302, storage device 303, communication interface 304, input device 305, and output device 306. The storage device 303 stores various data and programs, such as a hard disk drive, solid-state drive, or flash memory. The communication interface 304 is an interface for connecting to a communication network, such as an adapter for connecting to Ethernet®, a modem for connecting to a public telephone network, a wireless communication device for wireless communication, or a USB (Universal Serial Bus) connector or RS232C connector for serial communication. The input device 305 is for inputting data, such as a keyboard, mouse, touch panel, button, or microphone. The output device 306 is for outputting data, such as a display, printer, or speaker. Furthermore, each functional unit of the management server device 3, described later, is realized by the CPU 301 reading programs stored in the storage device 303 into the memory 302 and executing them, and each storage unit of the management server 3 is realized as part of the storage area provided by the memory 302 and the storage device 303.
[0017] Figure 4 shows an example of the software configuration of the management server 3. The management server 3 includes a transfer instruction receiving unit 311, a first transfer processing unit 312, a payment confirmation unit 313, an NFT issuance processing unit 314, an NFT destruction processing unit 315, and a second transfer processing unit 316.
[0018] The transfer instruction receiving unit 311 receives an instruction to transfer an NFT (hereinafter referred to as a transfer instruction). In this embodiment, the transfer instruction receiving unit 311 can receive transfer instructions from the user terminal 4. The transfer instruction receiving unit 311 may also receive transfer instructions from a communication device other than the user terminal 4. The transfer instruction can specify the user who is the current owner of the source NFT (i.e., user A) and the user to whom the NFT will be transferred (i.e., user B).
[0019] The first transfer processing unit 312 transfers the NFT from the transferor's (user A's) wallet 11 to the administrator X's wallet 12. In this embodiment, the predetermined third party is assumed to be the administrator of the management server 3, and the user of this predetermined third party is referred to as the administrator user. However, this third party is not limited to the administrator of the management server 3, but can be any third party trusted by the user. The first transfer processing unit 312 can issue a transaction to the blockchain network 1 to transfer the NFT from the transferor user A to the administrator X.
[0020] The payment confirmation unit 313 confirms that payment has been completed when the transfer of the NFT involves payment of monetary consideration in legal currency. The payment confirmation unit 313 may, for example, confirm the completion of payment by receiving a payment completion notification from the payment provider's payment system (not shown). Alternatively, the payment confirmation unit 313 may access the payment provider's payment system (not shown) to confirm whether the payment from transferee user B to transferor user A has been successfully completed.
[0021] The NFT issuance processing unit 314 can issue NFTs corresponding to NFTs managed on blockchain network 1 on the destination blockchain network 2. The NFT issuance processing unit 314 can, for example, transfer and set the content ID, which indicates the content associated with the NFT, to the NFT issued on blockchain network 2. The NFT issuance processing unit 314 can store the newly issued NFT in the wallet 21 of administrator X on blockchain network 2.
[0022] The NFT destruction processing unit 315 destroys the NFT to be transferred. The NFT destruction processing unit 315 can, for example, issue a transaction to destroy the NFT. The NFT destruction processing unit 315 can destroy the NFT in blockchain network 1 after the NFT to be transferred has been transferred to administrator X's wallet 12 in blockchain network 1, and a corresponding NFT has been issued in blockchain network 2 and stored in administrator X's wallet 21.
[0023] The second transfer processing unit 316 transfers the NFT from administrator X's wallet 21 to destination user B's wallet 22 on the blockchain network 2. The second transfer processing unit 316 can perform this transfer process by issuing a transaction.
[0024] <Operation> Figure 5 is a diagram illustrating the operation of the transaction support system of this embodiment.
[0025] In response to the transfer instruction, the management server 3 transfers the NFT to be transferred from the wallet 11 of user A, who owns the NFT, to the wallet 12 of administrator X on the blockchain network 1 (S401). If there is a payment due for the transfer (S402: YES), the management server 3 confirms that payment in fiat currency has been made from the recipient user B to the source user A (or administrator X) (S403).
[0026] The management server 3 issues a new NFT corresponding to the NFT to be transferred on the blockchain network 2 and stores it in the administrator X's wallet 21 (S404). After the new NFT is issued on the blockchain network 2, the management server 3 destroys the NFT that is the subject of the transaction and is stored in the administrator X's wallet 12 on the blockchain network 1 (S405).
[0027] After the NFT is destroyed on blockchain network 1, the management server 3 can transfer the NFT from administrator X's wallet 21 to the destination user B's wallet 22 on blockchain network 2 (S406).
[0028] As described above, the transaction support system of this embodiment ensures the atomicity of a series of processes by transferring NFTs between blockchains via the administrator X's wallet.
[0029] <Second Embodiment> The second embodiment will be described below. In the second embodiment, the number of existing NFTs in each blockchain network 1 and 2 is managed without performing transfer processing via the administrator X's wallets 12 and 21. Figure 6 is a diagram showing an example of the overall configuration of the transaction support system according to the second embodiment. In the second embodiment, business devices 6 and 7 are connected to each blockchain network 1 and 2. Business devices 6 and 7 are computers of businesses that can issue and destroy NFTs in their respective blockchain networks 1 and 2.
[0030] Figure 7 shows an example of the software configuration of the management server 3 according to the second embodiment. As shown in Figure 7, in the second embodiment, the first transfer processing unit 312 and the second transfer processing unit 316 can be omitted. The management server 3 also further includes a transaction notification receiving unit 321, an issue count storage unit 322, a change history storage unit 323, and an issue count provision unit 324.
[0031] The issuance count storage unit 322 stores the number of NFTs in blockchain networks 1 and 2. The issuance count storage unit 322 can store the blockchain ID that identifies the blockchain network, the type ID that indicates the type of content associated with the NFT, the number of NFTs of that type that have been issued (issuance count), and the number of NFTs that have been destroyed after being issued (destroyed count). The issuance count storage unit 322 can also store the circulating number, which is the number remaining after subtracting the destroyed number from the issued number.
[0032] The fluctuation history storage unit 323 stores the history of NFT fluctuations in blockchain networks 1 and 2. The fluctuation history storage unit 323 can store transaction details by associating them with a blockchain ID that identifies the blockchain network and an NFT_ID that identifies the NFT. The fluctuation history storage unit 323 may also store a type ID that indicates the type of NFT that was traded.
[0033] The transaction notification receiving unit 321 receives notifications regarding NFT transactions (hereinafter referred to as transaction notifications) from the business operators' devices 6 and 7. In this embodiment, the business operators' devices 6 and 7 send notifications when an NFT is issued and when an NFT is destroyed in their respective blockchain networks 1 and 2. Transaction notifications are also sent for NFT transfers. Transaction notifications include information indicating the type of content associated with the NFT (hereinafter referred to as the type ID) and NFT identification information (hereinafter referred to as the NFT_ID). Transaction notifications related to transfers may also include information on the source and destination of the transfer.
[0034] The transaction notification receiving unit 321 can update the number of issued, destroyed, and circulating NFTs stored in the issuance number storage unit 322 based on the transaction notification. When the transaction notification receiving unit 321 receives a transaction notification indicating that an NFT has been issued, it can increment the number of issued and circulating NFTs corresponding to the blockchain ID indicating the blockchain network from which the transaction notification originated and the type ID specified in the transaction notification. When the transaction notification receiving unit 321 receives a transaction notification indicating that an NFT has been destroyed, it can increment the number of destroyed NFTs corresponding to the blockchain ID indicating the blockchain network from which the transaction notification originated and the type ID specified in the transaction notification, and decrement the circulating NFTs. In addition, the transaction notification receiving unit 321 can register a record in the change history storage unit 323 that contains the blockchain ID indicating the blockchain network from which the transaction notification originated, the NFT_ID and type ID set in the transaction notification, and the details of the processing (new issuance, destruction, transfer, etc.). Furthermore, if the transaction notification contains other information related to the transaction, such as the source and destination of the transfer, the transaction notification receiving unit 321 can add this information to the processing details.
[0035] The issuance quantity provision unit 324 can respond with the number of NFTs in the blockchain network in response to a request (hereinafter referred to as an issuance quantity request). An issuance quantity request includes the specification of one or all of the issuance quantity, the number to be destroyed, or the number in circulation, and the specification of the blockchain network. The issuance quantity provision unit 324 can read at least one of the specified issuance quantity, the number to be destroyed, and the number in circulation corresponding to the blockchain network specified in the issuance quantity request from the issuance quantity storage unit 322 and respond.
[0036] In this way, by having a third party, separate from the business operator, manage the number of NFTs circulating in blockchain networks 1 and 2, it becomes possible to verify, for example, whether the number of limited-edition items sold is genuine.
[0037] Although these embodiments have been described above, they are intended to facilitate understanding of the present invention and are not intended to limit its interpretation. The present invention can be modified and improved without departing from its spirit, and equivalents thereof are also included.
[0038] For example, in this embodiment, the consideration for the NFT is paid in legal tender, but it may also be paid in cryptocurrency. Alternatively, consideration may be paid in a form other than cryptocurrency.
[0039] Furthermore, in this embodiment, the management server 3 performs the transfer, destruction, and issuance of NFTs, but these can also be performed by smart contracts in blockchains 1 and 2. In addition, all functions of the management server 3, including the payment confirmation unit 313, can be implemented by smart contracts.
[0040] Furthermore, in this embodiment, the NFT is transferred to administrator X's wallet 12 in blockchain network 1 before being issued in blockchain network 2. However, the NFT may be issued in blockchain network 2 before being transferred to administrator X's wallet 12 in blockchain network 1.
[0041] Furthermore, in this embodiment, NFTs transferred from blockchain network 1 to blockchain network 2 are destroyed in blockchain network 1, but the embodiment is not limited to this; they can be made unusable in blockchain network 1. For example, an NFT can be made unusable by transferring it to a predetermined burn address in blockchain network 1. Alternatively, a flag value indicating whether the NFT is usable or unusable can be stored in the NFT's metadata, and the NFT can be made unusable by setting this flag value to a value indicating unusable (e.g., false). Alternatively, blockchain network 1 can maintain a distributed ledger for managing usable and / or unusable NFTs, and manage them as unusable NFTs instead of destroying them. [Explanation of Symbols]
[0042] 1 Blockchain 2 Blockchain 3. Management Server 4. User terminals 5. User terminals A User User B X Administrator
Claims
1. Disabling a first NFT associated with the content stored in a first wallet of a first user in a first blockchain; determining that the first NFT has been disabled; conditional on confirmation that the first NFT has become unusable, issuing a second NFT in a second blockchain associated with the content and transferring the second NFT to a second wallet of a second user; A transaction support system characterized by:
2. The transaction support system according to claim 1, In the step of disabling the first NFT, the first NFT is transferred from the first wallet to a third wallet of an administrator in the first blockchain, and the first NFT stored in the third wallet is made unusable; In the step of transferring the second NFT, storing the issued second NFT in a fourth wallet of the administrator in the second blockchain, and transferring the second NFT from the fourth wallet to the second wallet on the condition that it is confirmed that the first NFT has become unusable; A transaction support system characterized by:
3. Disabling a first NFT associated with the content stored in a first wallet of a first user in a first blockchain; determining that the first NFT has been disabled; issuing a second NFT associated with the content in a second blockchain and transferring the second NFT to a second wallet of a second user, on the condition that it is determined that the first NFT has become unusable; A transaction support method characterized in that the above steps are executed by a computer.
4. Disabling a first NFT associated with the content stored in a first wallet of a first user in a first blockchain; determining that the first NFT has been disabled; issuing a second NFT associated with the content in a second blockchain and transferring the second NFT to a second wallet of a second user, on the condition that it is determined that the first NFT has become unusable; A program for causing a computer to execute the following.
