Information processing device, system and information processing program

Abstract

To guarantee the legitimacy of a correspondence relation between two addresses on different block chains.SOLUTION: An information processing device 100 initiates monitoring of a Tx on a BC-Priv 510 and a Tx on a BC-Pub 520, in response to a request for correspondence. The information processing device 100 detects a correspondence Tx 601 including an address 0xabcd in a field of an issuer on the BC-Priv 510. The information processing device 100 detects a correspondence Tx 602 including an address 0x1234 in a field of an issuer on the BC-Pub 520. The information processing device 100 determines whether or not an address on an association BC 530 set in the field of a message of the correspondence Tx 601 matches an address on the association BC 530 set in the field of a message of the correspondence Tx 602. The information processing device 100, when it is determined that the addresses match, registers the correspondence relation.SELECTED DRAWING: Figure 6

Description

[Technical field]

[0001] The present invention relates to an information processing device, a system, and an information processing program. [Background technology]

[0002] Conventionally, there are tokens called NFTs (Non-Fungible Tokens) that are issued and managed on a blockchain and have non-fungibility. The address on the blockchain corresponding to the owner of the NFT is the payment destination of royalties. Here, an NFT may be transferred from a source blockchain to a destination blockchain. At this time, it is desirable for a linking unit that links between blockchains to identify the correspondence between the addresses on the source blockchain and the addresses on the destination blockchain that correspond to the respective NFT owners, and to set the payment destination of royalties.

[0003] Prior art includes, for example, a technique for granting a given amount of cryptocurrency to a user from a designated cryptocurrency account in exchange for an object owned by the user. In addition, for example, a technique for issuing a second NFT to a second wallet of a second user in a second blockchain on the condition that a first NFT stored in a first wallet of a first user in a first blockchain is made unusable. In addition, for example, a technique for transferring ownership of a digital asset in response to a transfer request. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent Publication No. 2021-189475 [Patent Document 2] JP 2023-066919 A [Patent Document 3] US Patent Application Publication No. 2022 / 0215361 Summary of the Invention [Problem to be solved by the invention]

[0005] However, with conventional technology, it is difficult to guarantee the validity of the correspondence between two addresses on different blockchains. For example, it is possible that the linking unit is attacked to associate an address on the blockchain of the transfer source corresponding to the owner of the NFT with an address on the blockchain of the transfer destination corresponding to an attacker.

[0006] In one aspect, the present invention aims to ensure the validity of the correspondence between two addresses on different blockchains. [Means for solving the problem]

[0007] According to one embodiment, an information processing device, system, and information processing program are proposed that include a first address on a first blockchain and a second address on a second blockchain, acquire a request requesting to associate the first address with the second address, detect a first transaction including the first address and a third address on a third blockchain managed by the device, which is issued by the first blockchain in response to a request by a user having the first address, based on the first address included in the acquired request, detect a second transaction including the second address and a fourth address on the third blockchain, which is issued by the second blockchain in response to a request by a user having the second address, based on the second address included in the acquired request, determine to associate the first address with the second address if the third address and the fourth address match based on the detected first transaction and the detected second transaction, and determine not to associate the first address with the second address if the third address and the fourth address do not match. Effect of the Invention

[0008] According to one embodiment, it becomes possible to guarantee the validity of the correspondence between two addresses on different blockchains. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram illustrating an example of an information processing method according to an embodiment. [Diagram 2] FIG. 2 is an explanatory diagram illustrating an example of an information processing system 200. As shown in FIG. [Diagram 3] FIG. 3 is a block diagram showing an example of a hardware configuration of the information processing device 100. As shown in FIG. [Figure 4] FIG. 4 is a block diagram showing an example of a functional configuration of the information processing system 200. As shown in FIG. [Diagram 5] FIG. 5 is an explanatory diagram (part 1) showing an example of the operation of the information processing system 200. [Figure 6] FIG. 6 is an explanatory diagram (part 2) showing an example of the operation of the information processing system 200. [Figure 7] FIG. 7 is an explanatory diagram (part 1) showing a specific example of the operation of the information processing system 200. [Figure 8] FIG. 8 is an explanatory diagram (part 2) showing a specific example of the operation of the information processing system 200. [Figure 9] FIG. 9 is an explanatory diagram (part 3) showing a specific example of the operation of the information processing system 200. [Figure 10] FIG. 10 is an explanatory diagram (part 4) showing a specific example of the operation of the information processing system 200. [Figure 11] FIG. 11 is an explanatory diagram (part 5) showing a specific example of the operation of the information processing system 200. [Figure 12] FIG. 12 is a flowchart illustrating an example of a procedure of the association process. [Figure 13] FIG. 13 is a flowchart illustrating an example of a transfer process procedure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, an information processing device, a system, and an information processing program according to embodiments of the present invention will be described in detail with reference to the accompanying drawings.

[0011] (An example of an information processing method according to an embodiment) FIG. 1 is an explanatory diagram showing an example of an information processing method according to an embodiment. The information processing device 100 is a computer for managing the correspondence between two addresses on different blockchains. The information processing device 100 is, for example, a server or a PC (Personal Computer). In the following description, the blockchain may be written as "BC (Block Chain)".

[0012] Conventionally, there are NFTs that are issued and managed on BC. NFTs, for example, associate data with royalty information. The royalty information includes, for example, an address on BC to which the royalty for the data is paid. The royalty information may include, for example, a method for calculating the royalty for the data. The address on BC is, for example, specified by the owner of the NFT. NFTs are utilized in fields such as art, sports, or the metaverse. The owner of the NFT is, for example, an art creator.

[0013] Here, there are cases where it is desirable to transfer an NFT from a source BC to a destination BC. For example, a creator may want to transfer an NFT that was issued on a trial basis in a private BC in association with art, taking into account financial risks, to a public BC, taking into account the ease of use of the art.

[0014] In contrast, when transferring NFTs between BCs, there is a method 1 in which the NFT is deleted in the source BC and generated in the destination BC. Deletion is also called "burn", for example. Generation is also called "mint", for example.

[0015] However, method 1 has the problem that royalty information corresponding to the NFT on the source BC cannot be transferred to the NFT on the destination BC. Therefore, even if the art corresponding to the NFT on the destination BC is used, the creator cannot receive royalties for the NFT.

[0016] Therefore, a second method is considered in which a linking unit that links between BCs refers to a correspondence relationship between an address on the transfer source BC and an address on the transfer destination BC that is registered in advance, rewrites royalty information corresponding to the NFT on the transfer source BC, and transfers it to the NFT on the transfer destination BC. The linking unit, for example, manages a linking BC that records processing history and correspondence relationships. The linking unit, for example, registers the correspondence relationship between an address on the transfer source BC and an address on the transfer destination BC in the linking BC. It is preferable that the linking BC is a public BC from the viewpoint of permanence or neutrality.

[0017] In method 2, there is a problem that it is difficult to guarantee the validity of the correspondence between the address on the transfer source BC and the address on the transfer destination BC, which are registered in the linking BC. For example, it is possible that the linking unit is attacked so that the correspondence between the address on the transfer source BC corresponding to the NFT owner and the address on the transfer destination BC corresponding to the attacker is registered in the linking BC. As a result, the attacker may fraudulently receive royalties for the NFT on the transfer destination BC.

[0018] Therefore, it is desirable to guarantee the validity of the correspondence between two addresses on different BCs. For example, it is desirable to guarantee that the two addresses on different BCs to be associated are both addresses designated by the owner of the NFT and corresponding to the owner of the NFT.

[0019] Here, for example, a method 3 is considered in which the smart contract of the linking BC accepts two addresses on different BCs, a signature based on a private key corresponding to each address, and a public key corresponding to each address. In the following explanation, the smart contract may be written as "SC (Smart Contract)".

[0020] In method 3, the SC determines that the correspondence between the addresses is valid only if it determines that the signatures based on the private keys corresponding to the addresses are both valid based on the public keys corresponding to the addresses. If the correspondence between the addresses is valid, the SC registers the correspondence between the addresses in the cooperation BC.

[0021] In method 3, if there is no pair of private key and public key corresponding to an address on the BC, the SC cannot determine whether the correspondence between the addresses is valid. For example, if the BC is a format that identifies users by linking with a social networking service (SNS), there is no pair of private key and public key corresponding to an address on the BC.

[0022] Also, for example, method 4 is possible in which the linking unit receives two addresses on different BCs and authentication keys corresponding to each address. In method 4, the linking unit registers the correspondence between each address in the linking BC only when it determines that the correspondence between each address is valid based on the authentication keys corresponding to each address.

[0023] Method 4 has a problem in that the neutrality of the linking part is relatively low. It is difficult for a third party to verify after the fact the legitimacy of the process in the linking part to determine whether the correspondence between each address is valid. For this reason, it is difficult to guarantee the legitimacy of the correspondence between two addresses registered on different BCs.

[0024] Therefore, in this embodiment, an information processing method that can guarantee the validity of the corresponding relationship between two addresses on different blockchains will be described.

[0025] 1, there are a first BC 110, a second BC 120, and a third BC 130. The information processing device 100 can access the first BC 110. The information processing device 100 can access the second BC 120. The information processing device 100 manages the third BC 130. The third BC 130 is preferably a public BC.

[0026] The first BC 110 has one or more addresses. The first BC 110 has, for example, a first address 101. The first BC 110 has a function of issuing and recording transactions. The second BC 120 has one or more addresses. The second BC 120 has, for example, a second address 102. The second BC 120 has a function of issuing and recording transactions. The second BC 120 is, for example, a BC different from the first BC 110. The third BC 130 has one or more addresses. In the following description, a transaction may be written as "Tx".

[0027] (1-1) A user having the first address 101 uses a specific computer to request the first BC 110 to issue a first Tx 111 including the first address 101 and a third address on the third BC 130. The first BC 110 issues the first Tx 111 including the first address 101 and the third address on the third BC 130 in response to the request by the user having the first address 101.

[0028] (1-2) A user having the second address 102 uses a specific computer to request the second BC 120 to issue a second Tx 121 including the second address 102 and the fourth address on the third BC 130. The second BC 120 issues the second Tx 121 including the second address 102 and the fourth address on the third BC 130 in response to the request by the user having the second address 102.

[0029] (1-3) A user who wishes to associate the first address 101 with the second address 102 uses a specific computer to transmit a request to the information processing device 100 to request that the first address 101 and the second address 102 be associated with each other. The request includes, for example, the first address 101 on the first BC 110 and the second address 102 on the second BC 120. The information processing device 100 receives and acquires the request. The information processing device 100 identifies the first address 101 and the second address 102 based on the acquired request. This allows the information processing device 100 to identify a combination of addresses to be associated with each other.

[0030] (1-4) The information processing device 100 detects the first Tx111 issued by the first BC 110 based on the first address 101 included in the acquired request. The information processing device 100 identifies the third address based on the detected first Tx111. This allows the information processing device 100 to obtain a guideline for determining whether to associate the first address 101 with the second address 102. Furthermore, the information processing device 100 can guarantee the legitimacy of associating the first address 101 based on the property that the first BC 110 does not issue the first Tx111 in response to a request from any user other than the user having the first address 101.

[0031] (1-5) The information processing device 100 detects the second Tx 121 issued by the second BC 120 based on the second address 102 included in the acquired request. The information processing device 100 identifies the fourth address based on the detected second Tx 121. This allows the information processing device 100 to obtain a guideline for determining whether to associate the first address 101 with the second address 102. In addition, the information processing device 100 can guarantee the legitimacy of associating the second address 102 based on the property that the second BC 120 does not issue the first Tx 111 in response to a request from any user other than the user having the second address 102.

[0032] (1-6) The information processing device 100 determines whether or not the third address and the fourth address match based on the detected first Tx 111 and the detected second Tx 121. If the third address and the fourth address match, the information processing device 100 determines that the first address 101 and the second address 102 are associated with each other. On the other hand, if the third address and the fourth address do not match, the information processing device 100 determines that the first address 101 and the second address 102 are not associated with each other. This allows the information processing device 100 to appropriately determine whether or not to associate the first address 101 and the second address 102 with each other.

[0033] For example, the information processing device 100 can guarantee that the user having the first address 101 is the same as the user having the second address 102 because the third address and the fourth address match. For example, the information processing device 100 can guarantee the legitimacy of the user having the first address 101 and the second address 102 because the third address and the fourth address are both addresses owned by the third BC 130. In this way, the information processing device 100 can guarantee the legitimacy of the correspondence relationship between two addresses on different BCs. For example, the information processing device 100 can guarantee the legitimacy of the correspondence relationship between the first address 101 and the second address 102.

[0034] Even if the first BC 110 and the second BC 120 are BCs in which a pair of a private key and a public key corresponding to the address does not exist, the information processing device 100 can appropriately determine whether to associate the first address 101 with the second address 102. The information processing device 100 can guarantee the validity of the correspondence between the first address 101 and the second address 102.

[0035] When determining whether to associate the first address 101 with the second address 102, the information processing device 100 can utilize the first Tx 111 issued by the first BC 110 and the second Tx 121 issued by the second BC 120. Therefore, the information processing device 100 can improve neutrality when determining whether to associate the first address 101 with the second address 102.

[0036] When the information processing device 100 determines to associate the first address 101 with the second address 102, the information processing device 100 may register the correspondence between the first address 101 and the second address 102 in the third BC 130. This allows the information processing device 100 to subsequently verify the correspondence between the first address 101 and the second address 102. The information processing device 100 can leave evidence that the first address 101 and the second address 102 are associated with each other in the first BC 110, the second BC 120, and the third BC 130.

[0037] Furthermore, when the information processing device 100 receives a request to transfer an NFT on the first BC 110, with the first BC 110 as the transfer source and the second BC 120 as the transfer destination, the information processing device 100 can refer to the correspondence between the first address 101 and the second address 102. Therefore, when transferring an NFT on the first BC 110, the information processing device 100 can rewrite royalty information corresponding to the NFT and appropriately transfer it to the second BC 120.

[0038] Here, the case where the information processing device 100 determines whether or not to associate two addresses on different BCs and ensures the validity of the correspondence relationship between the two addresses on the different BCs has been described, but the present invention is not limited to this. For example, the information processing device 100 may determine whether or not to associate three or more addresses on different BCs and ensure the validity of the correspondence relationship between the three or more addresses on the different BCs.

[0039] Here, the case where the second BC 120 is a BC different from the first BC 110 has been described, but is not limited to this. For example, the second BC 120 may be the same BC as the first BC 110. Here, the case where the functions of the information processing device 100 are realized by a single computer has been described, but is not limited to this. For example, the functions of the information processing device 100 may be realized by multiple computers.

[0040] (An example of the information processing system 200) Next, an example of an information processing system 200 to which the information processing device 100 shown in FIG. 1 is applied will be described with reference to FIG.

[0041] Fig. 2 is an explanatory diagram showing an example of an information processing system 200. In Fig. 2, the information processing system 200 includes an information processing device 100, a first BC 210, a second BC 220, a third BC 230, and one or more client devices 201. The first BC 210 includes a plurality of first BC nodes 211. The second BC 220 includes a plurality of second BC nodes 221. The third BC 230 includes a plurality of third BC nodes 231.

[0042] In the information processing system 200, the information processing device 100 and the first BC node 211 are connected via a wired or wireless network 240. The network 240 is, for example, a local area network (LAN), a wide area network (WAN), or the Internet.

[0043] In the information processing system 200, the information processing device 100 and the second BC node 221 are connected via a wired or wireless network 240. In the information processing system 200, the information processing device 100 and the third BC node 231 are connected via a wired or wireless network 240.

[0044] Moreover, in the information processing system 200, the client device 201 and the first BC node 211 are connected via a wired or wireless network 240. Moreover, in the information processing system 200, the client device 201 and the second BC node 221 are connected via a wired or wireless network 240. Moreover, in the information processing system 200, the information processing device 100 and the client device 201 are connected via a wired or wireless network 240.

[0045] The client device 201 is a computer used by an operator who wishes to associate two addresses on different BCs. For example, the operator wishes to associate a first address on the first BC 210 with a second address on the second BC 220.

[0046] The client device 201 transmits an issuance request to the first BC node 211 to request that a Tx be issued based on an operational input by the worker. The client device 201 transmits an issuance request to the first BC node 211 to request that a first Tx be issued including a first address on the first BC 210 and a third address on the third BC 230 based on, for example, an operational input by the worker. The first address is an address owned by the worker. The third address is an address owned by the worker.

[0047] The client device 201 transmits an issuance request to the second BC node 221 to issue a Tx based on an operational input by the worker. The client device 201 transmits an issuance request to the second BC node 221 to issue a second Tx including a second address on the second BC 220 and a fourth address on the third BC 230 based on, for example, an operational input by the worker. The second address is an address owned by the worker. The fourth address is an address owned by the worker.

[0048] The client device 201 transmits an association request to the information processing device 100, requesting that two addresses on different BCs be associated with each other, based on an operational input by a worker. The client device 201 transmits an association request to the information processing device 100, requesting that a first address on the first BC 210 be associated with a second address on the second BC 220, based on, for example, an operational input by a worker. The client device 201 is, for example, a PC, a tablet terminal, or a smartphone.

[0049] The first BC node 211 is a computer forming the first BC 210. The first BC nodes 211 each store a common first distributed ledger to manage the first distributed ledger. The first BC node 211 receives an issuance request from the client device 201. The first BC node 211 issues a first Tx including a first address on the first BC 210 and a third address on the third BC 230 in response to the issuance request, for example.

[0050] The first Tx has, for example, a field representing an issuer and a field representing a message. The first BC node 211 specifically identifies a first address on the first BC 210 corresponding to the worker. The first BC node 211 specifically issues a first Tx in which the identified first address on the first BC 210 is set in the field representing the issuer and the third address on the third BC 230 is set in the message field. The first BC node 211 registers the issued first Tx in the first distributed ledger. The first BC node 211 is, for example, a server or a PC.

[0051] The second BC node 221 is a computer forming the second BC 220. The second BC nodes 221 each store a common second distributed ledger to manage the second distributed ledger. The second BC node 221 receives an issuance request from the client device 201. The second BC node 221 issues a second Tx including a second address on the second BC 220 and a fourth address on the third BC 230 in response to the issuance request, for example.

[0052] The second Tx has, for example, a field representing the issuer and a field representing the message. The second BC node 221 specifically identifies a second address on the second BC 220 corresponding to the worker. The second BC node 221 specifically issues a second Tx in which the identified second address on the second BC 220 is set in the field representing the issuer and the fourth address on the third BC 230 is set in the message field. The second BC node 221 registers the issued second Tx in the second distributed ledger. The second BC node 221 is, for example, a server or a PC.

[0053] The information processing device 100 is a computer for managing the correspondence relationship between two addresses on different BCs. The information processing device 100 receives a correspondence request from the client device 201. The information processing device 100 identifies a first address and a second address based on the received correspondence request.

[0054] In response to acquiring the association request, the information processing device 100 detects a first Tx including the first address in the first BC 210. When the information processing device 100 detects the first Tx, the information processing device 100 acquires a third address on the third BC 230 included in the first Tx. In response to acquiring the association request, the information processing device 100 detects a second Tx including the second address in the second BC 220. When the information processing device 100 detects the second Tx, the information processing device 100 acquires a fourth address on the third BC 230 included in the second Tx.

[0055] When the third address and the fourth address match, the information processing device 100 determines that the first address and the second address are associated with each other, and controls the third BC 230 to register the association between the first address and the second address. On the other hand, when the third address and the fourth address do not match, the information processing device 100 determines that the first address and the second address are not associated with each other. The information processing device 100 is, for example, a server or a PC.

[0056] The third BC node 231 is a computer forming the third BC 230. The multiple third BC nodes 231 each store a common third distributed ledger to manage the third distributed ledger. The third BC node 231 registers the correspondence between two addresses on different BCs in the third distributed ledger under the control of the information processing device 100. The third BC node 231 registers, for example, the correspondence between a first address on the first BC 210 and a second address on the second BC 220 in the third distributed ledger. The third BC node 231 is, for example, a server or a PC.

[0057] (Application example of information processing system 200) Next, an application example of the information processing system 200 will be described. The information processing system 200 shown in FIG. 2 can be applied, for example, to a case where an NFT on the first BC 210 to which royalty information is attached is transferred to the second BC 220. The royalty information includes an address to which the NFT royalty is paid. The royalty information includes, for example, a first address. For example, the client device 201 transmits a transfer request to the information processing device 100, requesting that the NFT on the first BC 210 be transferred to the second BC 220, based on an operation input by an operator. The transfer request indicates the NFT to be transferred, the first BC 210 as the transfer source, and the second BC 220 as the transfer destination.

[0058] For example, the information processing device 100 receives a transfer request from the client device 201. Based on the transfer request, the information processing device 100 identifies the NFT to be transferred, the first BC 210 of the transfer source, and the second BC 220 of the transfer destination. For example, the information processing device 100 refers to the identified first BC 210 of the transfer source to acquire a first address included in the royalty information assigned to the identified NFT to be transferred. For example, the information processing device 100 refers to the third BC 230 to identify a second address corresponding to the acquired first address. For example, the information processing device 100 controls the first BC 210 to delete the NFT to be transferred on the first BC 210 of the transfer source, and controls the second BC 220 to generate the NFT to be transferred on the second BC 220 of the transfer destination. For example, the information processing device 100 controls the second BC 220 to assign royalty information including the identified second address to the NFT to be transferred on the generated second BC 220 of the transfer destination.

[0059] Here, the case where the NFT on the first BC 210 to which royalty information is assigned is transferred to the second BC 220 has been described, but the present invention is not limited to this. For example, the first BC 210 may be a BC that associates with a user's address and manages environmental contribution points according to the user's behavior, and the second BC 220 may be a BC that associates with the user's address and manages exchange points owned by the user that can be exchanged for products. In this case, the information processing system 200 may be applied to a case where the environmental contribution points on the first BC 210 are converted into exchange points on the second BC 220 and transferred.

[0060] (Example of hardware configuration of information processing device 100) Next, an example of the hardware configuration of the information processing device 100 will be described with reference to FIG.

[0061] Fig. 3 is a block diagram showing an example of a hardware configuration of the information processing device 100. In Fig. 3, the information processing device 100 has a CPU (Central Processing Unit) 301, a memory 302, a network I / F (Interface) 303, a recording medium I / F 304, and a recording medium 305. In addition, each component is connected to each other via a bus 300.

[0062] Here, the CPU 301 is responsible for the overall control of the information processing device 100. The memory 302 has, for example, a read only memory (ROM), a random access memory (RAM), and a flash ROM. Specifically, for example, the flash ROM and the ROM store various programs, and the RAM is used as a work area for the CPU 301. The programs stored in the memory 302 are loaded into the CPU 301, causing the CPU 301 to execute the coded processes.

[0063] The network I / F 303 is connected to the network 240 through a communication line, and is connected to other computers via the network 240. The network I / F 303 manages an internal interface with the network 240, and controls input and output of data from other computers. The network I / F 303 is, for example, a modem or a LAN adapter.

[0064] The recording medium I / F 304 controls reading / writing data from / to the recording medium 305 under the control of the CPU 301. The recording medium I / F 304 is, for example, a disk drive, a solid state drive (SSD), a universal serial bus (USB) port, etc. The recording medium 305 is a non-volatile memory that stores data written under the control of the recording medium I / F 304. The recording medium 305 is, for example, a disk, a semiconductor memory, a USB memory, etc. The recording medium 305 may be detachable from the information processing device 100.

[0065] In addition to the above-mentioned components, the information processing device 100 may have, for example, a keyboard, a mouse, a display, a printer, a scanner, a microphone, a speaker, etc. Furthermore, the information processing device 100 may have a plurality of recording medium I / Fs 304 and recording media 305. Furthermore, the information processing device 100 may not have the recording medium I / Fs 304 and the recording media 305.

[0066] (Example of Hardware Configuration of Client Device 201) Specifically, an example of the hardware configuration of the client device 201 is similar to the example of the hardware configuration of the information processing device 100 shown in FIG. 3, and therefore a description thereof will be omitted.

[0067] (Example of hardware configuration of the first BC node 211) Specifically, an example of the hardware configuration of the first BC node 211 is similar to the example of the hardware configuration of the information processing device 100 shown in FIG. 3, and therefore a description thereof will be omitted.

[0068] (Example of hardware configuration of the second BC node 221) Specifically, an example of the hardware configuration of the second BC node 221 is similar to the example of the hardware configuration of the information processing device 100 shown in FIG. 3, and therefore a description thereof will be omitted.

[0069] (Example of hardware configuration of the third BC node 231) Specifically, an example of the hardware configuration of the third BC node 231 is similar to the example of the hardware configuration of the information processing device 100 shown in FIG. 3, and therefore a description thereof will be omitted.

[0070] (Example of Functional Configuration of Information Processing System 200) Next, an example of a functional configuration of the information processing system 200 will be described with reference to FIG.

[0071] 4 is a block diagram showing an example of a functional configuration of the information processing system 200. In FIG. 4, the first BC node 211 includes a first storage unit 410, a first acquisition unit 411, and a first issuing unit 412.

[0072] The first storage unit 410 is realized by, for example, a storage area such as the memory 302 or the recording medium 305 shown in Fig. 3. In the following, a case where the first storage unit 410 is included in the information processing device 100 will be described, but this is not limiting. For example, the first storage unit 410 may be included in a device different from the information processing device 100, and the stored contents of the first storage unit 410 may be accessible from the information processing device 100.

[0073] Specifically, the first acquiring unit 411 and the first issuing unit 412 realize their functions by, for example, causing the CPU 301 to execute a program stored in a storage area such as the memory 302 or the recording medium 305 shown in Fig. 3, or by the network I / F 303. The processing results of each functional unit are stored in, for example, a storage area such as the memory 302 or the recording medium 305 shown in Fig. 3.

[0074] The first storage unit 410 stores various information that is referred to or updated in the processing of each functional unit. The first storage unit 410 stores, for example, the first distributed ledger. The first distributed ledger records, for example, Tx. The first storage unit 410 stores, for example, a token. The first storage unit 410 stores, for example, royalty information corresponding to the token. The royalty information indicates, for example, an address on the first BC 210 corresponding to the token. The royalty information may include, for example, a method for calculating the royalty. Specifically, the royalty information may include a calculation formula for calculating the royalty. The calculation formula is a formula indicating what percentage of the consideration for a commercial transaction using the token the royalty is. The token is, for example, an NFT. The token may be something other than an NFT.

[0075] The first acquisition unit 411 acquires various information used in the processing of each functional unit. The first acquisition unit 411 stores the acquired various information in the first storage unit 410 or outputs it to each functional unit. The first acquisition unit 411 may also output the various information stored in the first storage unit 410 to each functional unit. The first acquisition unit 411 acquires various information based on, for example, an operation input by an operator. The first acquisition unit 411 may receive various information from, for example, a device different from the information processing device 100.

[0076] The first acquisition unit 411 acquires, for example, an issuance request requesting the issuance of Tx. The issuance request requests the issuance of a first Tx including, for example, a first address on the first BC 210 and a third address on the third BC 230. The first Tx includes, for example, an issuer field and a message field. Specifically, the first Tx is a Tx in which the first address on the first BC 210 is set in the issuer field and the third address on the third BC 230 is set in the message field.

[0077] Specifically, the first acquisition unit 411 acquires the issuance request by receiving it from another computer. The other computer is, for example, the client device 201. Specifically, the first acquisition unit 411 acquires the issuance request by accepting an input of the issuance request based on an operation input by an operator. For example, the first acquisition unit 411 accepts the acquisition of the issuance request as a start trigger for starting the processing of the first issuing unit 412.

[0078] The first issuing unit 412 issues Tx in response to the issuance request and registers it in the first distributed ledger. For example, the first issuing unit 412 identifies a first address on the first BC 210 and a third address on the third BC 230 based on the issuance request. Specifically, the first issuing unit 412 identifies a first address on the first BC 210 corresponding to the requesting worker based on the issuance request. For example, the first issuing unit 412 issues a first Tx including the identified first address on the first BC 210 and the identified third address on the third BC 230, and registers it in the first distributed ledger. In this way, the first issuing unit 412 can leave evidence indicating that a legitimate worker who has the first address has requested that the first address be associated with another address.

[0079] The second BC node 221 includes a second storage unit 420, a second acquisition unit 421, and a second issuing unit 422.

[0080] The second storage unit 420 is realized by, for example, a storage area such as the memory 302 or the recording medium 305 shown in Fig. 3. In the following, a case where the second storage unit 420 is included in the information processing device 100 will be described, but this is not limiting. For example, the second storage unit 420 may be included in a device different from the information processing device 100, and the stored contents of the second storage unit 420 may be accessible from the information processing device 100.

[0081] Specifically, the second acquiring unit 421 and the second issuing unit 422 realize their functions by, for example, causing the CPU 301 to execute a program stored in a storage area such as the memory 302 or the recording medium 305 shown in Fig. 3, or by the network I / F 303. The processing results of each functional unit are stored in, for example, a storage area such as the memory 302 or the recording medium 305 shown in Fig. 3.

[0082] The second storage unit 420 stores various information that is referred to or updated in the processing of each functional unit. The second storage unit 420 stores, for example, a second distributed ledger. The second distributed ledger records, for example, Tx. The second storage unit 420 stores, for example, a token. The second storage unit 420 stores, for example, royalty information corresponding to the token. The royalty information indicates, for example, an address on the second BC 220 corresponding to the token. The royalty information may include, for example, a method for calculating the royalty. Specifically, the royalty information may include a calculation formula for calculating the royalty. The calculation formula is a formula indicating what percentage of the consideration for a commercial transaction using the token the royalty is. The token is, for example, an NFT. The token may be something other than an NFT.

[0083] The second acquisition unit 421 acquires, for example, an issuance request requesting the issuance of Tx. The issuance request requests the issuance of a second Tx including, for example, a second address on the second BC 220 and a fourth address on the third BC 230. The second Tx includes, for example, an issuer field and a message field. Specifically, the second Tx is a Tx in which the second address on the second BC 220 is set in the issuer field and the fourth address on the third BC 230 is set in the message field.

[0084] Specifically, the second acquisition unit 421 acquires the issuance request by receiving it from another computer. The other computer is, for example, the client device 201. Specifically, the second acquisition unit 421 acquires the issuance request by accepting an input of the issuance request based on an operation input by an operator. For example, the second acquisition unit 421 accepts the acquisition of the issuance request as a start trigger for starting the processing of the second issuing unit 422.

[0085] The second issuing unit 422 issues Tx in response to the issuance request and registers it in the second distributed ledger. For example, the second issuing unit 422 identifies the second address on the second BC220 and the fourth address on the third BC230 based on the issuance request. Specifically, the second issuing unit 422 identifies the second address on the second BC220 corresponding to the requesting worker based on the issuance request. For example, the second issuing unit 422 issues a second Tx including the identified second address on the second BC220 and the identified fourth address on the third BC230 and registers it in the second distributed ledger. In this way, the second issuing unit 422 can leave a trail indicating that a legitimate worker who has the second address has requested that the second address be associated with another address.

[0086] The information processing device 100 includes a third storage unit 430, a third acquisition unit 431, a detection unit 432, a correspondence unit 433, a transfer unit 434, and an output unit 435.

[0087] The third storage unit 430 is realized by, for example, a storage area such as the memory 302 or the recording medium 305 shown in Fig. 3. In the following, a case where the third storage unit 430 is included in the information processing device 100 will be described, but this is not limiting. For example, the third storage unit 430 may be included in a device different from the information processing device 100, and the stored contents of the third storage unit 430 may be accessible from the information processing device 100.

[0088] The third acquisition unit 431 to the output unit 435 function as an example of a control unit. Specifically, the third acquisition unit 431 to the output unit 435 realize their functions by, for example, causing the CPU 301 to execute a program stored in a storage area such as the memory 302 or the recording medium 305 shown in Fig. 3, or by the network I / F 303. The processing result of each functional unit is stored in, for example, a storage area such as the memory 302 or the recording medium 305 shown in Fig. 3.

[0089] The third storage unit 430 stores various information that is referred to or updated in the processing of each functional unit.

[0090] The third acquisition unit 431 acquires various information used in the processing of each functional unit. The third acquisition unit 431 stores the acquired various information in the third storage unit 430 or outputs it to each functional unit. The third acquisition unit 431 may also output the various information stored in the third storage unit 430 to each functional unit. The third acquisition unit 431 acquires the various information based on, for example, an operation input by an operator. The third acquisition unit 431 may receive the various information from, for example, a device different from the information processing device 100.

[0091] The third acquisition unit 431 acquires, for example, an association request requesting that a first address and a second address be associated with each other. The association request includes, for example, the first address on the first BC 210 and the second address on the second BC 220. Specifically, the third acquisition unit 431 acquires the association request by receiving it from another computer. The other computer is, for example, the client device 201. Specifically, the third acquisition unit 431 may acquire the association request by accepting an input of the association request based on an operation input by an operator.

[0092] The third acquisition unit 431 acquires a transfer request requesting that a token on the first BC 210 associated with the first address be transferred to the second BC 220. Specifically, the third acquisition unit 431 acquires the transfer request by receiving it from another computer. The other computer is, for example, the client device 201. Specifically, the third acquisition unit 431 may acquire the transfer request by accepting input of the transfer request based on an operation input by an operator.

[0093] The third acquisition unit 431 may receive a start trigger for starting processing of any of the functional units. The start trigger may be, for example, a predetermined operation input by an operator. The start trigger may be, for example, reception of predetermined information from another computer. The start trigger may be, for example, output of predetermined information by any of the functional units.

[0094] Specifically, the third acquisition unit 431 may accept the acquisition of the association request as a start trigger for starting the processes of the detection unit 432 and the correspondence unit 433. Specifically, the third acquisition unit 431 may accept the acquisition of the relocation request as a start trigger for starting the processes of the relocation unit 434.

[0095] The detection unit 432 detects the first Tx issued by the first BC 210 and including the first address and the third address on the third BC 230 based on the first address included in the association request acquired by the third acquisition unit 431. The detection unit 432 detects the first Tx by, for example, searching the first distributed ledger for the first Tx in which the first address is set in the issuer field using the first address as a key. The detection unit 432 identifies the third address based on the detected first Tx. This allows the detection unit 432 to obtain a guideline for determining whether or not to associate the first address with the second address. In addition, the detection unit 432 can guarantee the legitimacy of associating the first address with the second address based on the nature of the first BC 210 not issuing the first Tx in response to a request from anyone other than the worker having the first address.

[0096] The detection unit 432 detects the second Tx issued by the second BC 220 and including the second address and the fourth address on the third BC 230 based on the second address included in the association request acquired by the third acquisition unit 431. The detection unit 432 detects the second Tx by, for example, searching the second distributed ledger for the second Tx in which the second address is set in the issuer field using the second address as a key. The detection unit 432 identifies the fourth address based on the detected second Tx. This allows the detection unit 432 to obtain a guideline for determining whether or not to associate the second address with the second address. In addition, the detection unit 432 can guarantee the legitimacy of associating the second address with the second address based on the nature of the second BC 220 not issuing the second Tx in response to a request from anyone other than the worker having the second address.

[0097] The correspondence unit 433 judges whether or not to associate the first address with the second address. For example, the correspondence unit 433 judges whether or not the third address and the fourth address match based on the first Tx detected by the detection unit 432 and the second Tx detected by the detection unit 432. For example, when the correspondence unit 433 judges that the third address and the fourth address match, the correspondence unit 433 judges that the first address and the second address are associated. For example, when the correspondence unit 433 judges that the third address and the fourth address do not match, the correspondence unit 433 judges that the first address and the second address are not associated. This allows the correspondence unit 433 to appropriately judge whether or not to associate the first address with the second address. For example, the correspondence unit 433 can guarantee that the worker having the first address and the worker having the second address are the same because the third address and the fourth address match.

[0098] The correspondence unit 433 may determine, for example, whether the third address and the fourth address are valid addresses on the third BC 230. For example, when the correspondence unit 433 determines that the third address and the fourth address are not valid addresses on the third BC 230 even if they match, the correspondence unit 433 determines that the first address and the second address are not associated with each other. In this way, the correspondence unit 433 can guarantee the legitimacy of the user having the first Tx111 and the second Tx121, since, for example, both the third address and the fourth address are addresses owned by the third BC 230130.

[0099] When at least one of the detected first Tx and the detected second Tx has not been issued during a period from the present time until a predetermined time ago, the correspondence unit 433 determines that the first address and the second address are not associated. This allows the correspondence unit 433 to determine that the worker has no intention of associating the first address with the second address from a time perspective. Therefore, the correspondence unit 433 can appropriately determine whether to associate the first address with the second address.

[0100] When at least one of the first Tx and the second Tx is not detected within a certain time after the association request is acquired, the association unit 433 determines that the first address and the second address are not associated. This allows the association unit 433 to determine that the worker has no intention of associating the first address with the second address. Therefore, the association unit 433 can appropriately determine whether to associate the first address with the second address.

[0101] For example, when the correspondence unit 433 determines to associate the first address with the second address, the correspondence unit 433 registers the result of associating the first address with the second address in the third BC 230. Thereby, the correspondence unit 433 can make the result of associating the first address with the second address referable and verifiable thereafter.

[0102] Based on the transfer request, the transfer unit 434 identifies the token to be transferred, the transfer source first BC 210, and the transfer destination second BC 220. In response to acquiring the transfer request, the transfer unit 434 burns the identified token on the identified first BC 210 and generates the identified token on the identified second BC 220.

[0103] The transfer unit 434, for example, refers to the identified first BC 210 and identifies a first address based on royalty information corresponding to the identified token. The transfer unit 434, for example, refers to the third BC 230 and searches for a second address on the second BC 220 that corresponds to the identified first address. The transfer unit 434 determines not to transfer the token if, for example, there is no second address on the second BC 220 that corresponds to the first address.

[0104] On the other hand, for example, if there is a second address on the second BC220 corresponding to the first address, the transfer unit 434 determines to transfer the token, burns the identified token on the identified first BC210, and generates the identified token on the identified second BC220. For example, when determining to transfer the token, the transfer unit 434 associates the second address with the generated token on the second BC220. Specifically, the transfer unit 434 controls the second BC220 to associate royalty information including the second address with the token on the second BC220.

[0105] This allows the transfer unit 434 to transfer the token appropriately. The transfer unit 434 can associate an appropriate address with the token on the second BC 220. The transfer unit 434 can, for example, associate appropriate royalty information with the token on the second BC 220.

[0106] The output unit 435 outputs the processing result of at least one of the functional units. The output format is, for example, display on a display, printout on a printer, transmission to an external device via the network I / F 303, or storage in a storage area such as the memory 302 or the recording medium 305. In this way, the output unit 435 can notify the operator of the processing result of at least one of the functional units, thereby improving the convenience of the information processing device 100.

[0107] The output unit 435 outputs, for example, a result of the determination made by the correspondence unit 433 as to whether or not to associate the first address with the second address. Specifically, the output unit 435 outputs the result of the determination made by the correspondence unit 433 as to whether or not to associate the first address with the second address so that the worker can refer to it. Specifically, the output unit 435 may transmit the result of the determination made by the correspondence unit 433 as to whether or not to associate the first address with the second address to another computer. In this way, the output unit 435 can make it possible for an external reference as to whether or not the correspondence unit 433 has associated the first address with the second address.

[0108] The output unit 435 outputs, for example, information indicating whether or not the token has been transferred by the transfer unit 434. Specifically, the output unit 435 outputs the information indicating whether or not the token has been transferred by the transfer unit 434 so that an operator can refer to the information. Specifically, the output unit 435 may transmit the information indicating whether or not the token has been transferred by the transfer unit 434 to another computer. In this way, the output unit 435 can make it possible for an external party to refer to whether or not the token has been transferred by the transfer unit 434.

[0109] (An example of the operation of the information processing system 200) Next, an example of the operation of the information processing system 200 will be described with reference to FIGS.

[0110] 5 and 6 are explanatory diagrams showing an example of the operation of the information processing system 200. In FIG. 5, there are BC-Priv 510 and BC-Pub 520. BC-Priv 510 corresponds to, for example, the first BC 210 described above. BC-Pub 520 corresponds to, for example, the second BC 220 described above. The information processing device 100 manages a cooperation BC 530. The cooperation BC 530 corresponds to, for example, the third BC 230 described above. The information processing device 100 realizes a BC cooperation function 500 together with the cooperation BC 530.

[0111] In response to a creator's request, the BC-Priv 510 issues a correspondence Tx that includes an address on the BC-Priv 510 as the issuer and an address on the cooperation BC 530 as the message. In response to a creator's request, the BC-Pub 520 issues a correspondence Tx that includes an address on the BC-Pub 520 as the issuer and an address on the cooperation BC 530 as the message.

[0112] By detecting each correspondence Tx, the information processing device 100 can distribute the verification process for verifying the validity of the correspondence between the address on BC-Priv 510 and the address on BC-Pub 520. When the correspondence between the address on BC-Priv 510 and the address on BC-Pub 520 is valid, the information processing device 100 can register the correspondence in the correspondence registration SC 531 of the cooperation BC 530 to ensure the validity of the correspondence.

[0113] Here, there is a property that BC will not issue a Tx including an address on BC as the issuer, except in response to a request from a creator who has an address on BC. In addition, there is a property that BC can issue a Tx regardless of the type of BC. Based on these properties, the information processing device 100 can ensure the flexibility of the verification process that verifies the validity of associating an address on BC-Priv510 with an address on BC-Pub520. The flexibility indicates that there are various environments in which the verification process can be realized.

[0114] Furthermore, the correspondence Tx on BC-Priv510, the correspondence Tx on BC-Pub520, and the correspondence relationship on the cooperation BC can be confirmed by a third party and are tamper-resistant. Therefore, the information processing device 100 can ensure the neutrality of the verification process that verifies the validity of the correspondence between the address on BC-Priv510 and the address on BC-Pub520. Next, we move on to the description of FIG. 6.

[0115] 6, an NFT exists on BC-Priv 510. The creator of the NFT has address 0xabcd on BC-Priv 510, address 0x1234 on BC-Pub 520, and address 0x0000 on the associated BC 530.

[0116] Each BC can issue a Tx. A Tx includes, for example, an issuer field and a message field. For example, only the creator can issue a Tx with their address in the issuer field in each BC.

[0117] The creator is the recipient of royalties for the NFT on BC-Priv510. On BC-Priv510, the address 0xabcd corresponding to the creator is registered as the payment destination of royalties for the NFT. The creator wants to transfer the NFT on BC-Priv510 to BC-Pub520.

[0118] (6-1) The client device 201 acquires multiple addresses to be associated and the address 0x0000 on the collaboration BC 530 owned by the creator based on the creator's operation input. The association targets are, for example, the address 0xabcd on the BC-Priv 510 and the address 0x1234 on the BC-Pub 520. The client device 201 generates an association request using the acquired address 0x0000 on the collaboration BC 530 and transmits it to the information processing device 100. The association request includes the address 0x0000 on the collaboration BC 530 as the sender's address. The association request includes, for example, multiple addresses to be associated. In the example of FIG. 6, the association request specifically includes the address 0xabcd on the BC-Priv 510 and the address 0x1234 on the BC-Pub 520 as the association targets.

[0119] The information processing device 100 acquires the address 0x0000 on the cooperation BC 530 as the sender's address. In response to the association request, the information processing device 100 starts monitoring Tx on the BC-Priv 510 and Tx on the BC-Pub 520. For example, the information processing device 100 acquires the address 0xabcd on the BC-Priv 510 and the address 0x1234 on the BC-Pub 520 based on the association request. For example, the information processing device 100 starts monitoring Tx including the address 0xabcd in the issuer field on the BC-Priv 510 based on the acquired address 0xabcd on the BC-Priv 510. For example, the information processing device 100 starts monitoring Tx including the address 0x1234 in the issuer field on the BC-Pub 520 based on the acquired address 0x1234 on the BC-Pub 520.

[0120] (6-2) The client device 201 transmits an issuance request to the BC-Priv 510 based on the address 0xabcd on the BC-Priv 510 acquired as the association target and the address 0x0000 on the associated BC 530 acquired. The issuance request requests the issuance of a Tx. For example, the issuance request requests the issuance of a Tx in which the address 0xabcd on the BC-Priv 510 is set in the issuer field and the address 0x0000 on the associated BC 530 is set in the message field.

[0121] In response to the issuance request, the BC-Priv510 issues a correspondence Tx601 in which the address 0xabcd on the BC-Priv510 is set in the issuer field and the address 0x0000 on the linking BC530 is set in the message field. The BC-Priv510 registers the issued correspondence Tx601 in the distributed ledger managed by the BC-Priv510. Since the correspondence Tx601 includes the address 0x0000 on the linking BC530, it can be shown that it is a Tx intentionally issued by the creator. Since the correspondence Tx601 includes the address 0xabcd on the BC-Priv510, it can be guaranteed that the address 0xabcd is the subject of correspondence.

[0122] The client device 201 transmits an issuance request to the BC-Priv 510 based on the address 0x1234 on the BC-Pub 520 acquired as the association target and the address 0x0000 on the association BC 530 acquired. The issuance request requests the issuance of a Tx. The issuance request requests the issuance of a Tx in which, for example, the address 0x1234 on the BC-Pub 520 is set in the issuer field and the address 0x0000 on the association BC 530 is set in the message field.

[0123] In response to the issuance request, the BC-Pub520 issues a correspondence Tx602 in which the issuer field is set to the address 0x1234 on the BC-Pub520 and the message field is set to the address 0x0000 on the BC530 for collaboration. The BC-Pub520 registers the issued correspondence Tx602 in the distributed ledger managed by the BC-Pub520. Since the correspondence Tx602 includes the address 0x0000 on the BC530 for collaboration, it can be shown that it is a Tx intentionally issued by the creator. Since the correspondence Tx602 includes the address 0x1234 on the BC-Pub520, it can be guaranteed that the address 0x1234 is the subject of the correspondence.

[0124] (6-3) The information processing device 100 detects, on the BC-Priv 510, an association Tx 601 that includes an address 0xabcd in the issuer field. The information processing device 100 acquires an address on the association BC 530 that is set in the message field of the detected association Tx 601. Specifically, the information processing device 100 acquires an address 0x0000 on the association BC 530 that is set in the message field of the association Tx 601.

[0125] The information processing device 100 detects an association Tx 602 that includes an address 0x1234 in the issuer field on the BC-Pub 520. The information processing device 100 acquires an address on the association BC 530 that is set in the message field of the detected association Tx 602. In the example of Fig. 6, the information processing device 100 specifically acquires an address 0x0000 on the association BC 530 that is set in the message field of the detected association Tx 602.

[0126] The information processing device 100 judges whether or not an address on the cooperation BC 530 set in the message field of the association Tx 601 matches an address on the cooperation BC 530 set in the message field of the association Tx 602. If they match, the association Tx 601 and the association Tx 602 are Txs issued by the same creator. On the other hand, if they do not match, the association Tx 601 and the association Tx 602 may not be Txs issued by the same creator.

[0127] Therefore, when the information processing device 100 determines that there is a match, it determines that the correspondence between the address 0xabcd on BC-Priv510 and the address 0x1234 on BC-Pub520, which are acquired as the correspondence target, is valid. On the other hand, when the information processing device 100 determines that there is no match, it determines that the correspondence between the address 0xabcd on BC-Priv510 and the address 0x1234 on BC-Pub520, which are acquired as the correspondence target, is invalid. In the example of FIG. 6, specifically, the information processing device 100 determines that the correspondence between the address 0xabcd on BC-Priv510 and the address 0x1234 on BC-Pub520, which are acquired as the correspondence target, is valid.

[0128] (6-4) When the information processing device 100 determines that the correspondence between the address 0xabcd on BC-Priv 510 and the address 0x1234 on BC-Pub 520 is valid, the information processing device 100 registers the correspondence in the correspondence registration SC 531 of the cooperation BC 530. For example, the information processing device 100 generates correspondence information 603 indicating that the address 0xabcd on BC-Priv 510 corresponds to the address 0x1234 on BC-Pub 520. For example, the information processing device 100 registers the correspondence information 603 in the correspondence registration SC 531 of the cooperation BC 530.

[0129] This allows the information processing device 100 to perform a verification process for verifying the validity of associating the address 0xabcd on the BC-Priv510 with the address 0x1234 on the BC-Pub520. The information processing device 100 can distribute the verification process based on the association Tx601 and the association Tx602. Furthermore, the information processing device 100 can ensure the flexibility of the verification process based on the association Tx601 and the association Tx602. Furthermore, since an attacker cannot issue the association Tx601 and the association Tx602, the information processing device 100 can avoid the erroneous association of two addresses on different BCs due to an attack by an attacker.

[0130] The information processing device 100 registers the correspondence between the address 0xabcd on the BC-Priv510 and the address 0x1234 on the BC-Pub520 in the correspondence registration SC531 of the cooperation BC530, so that the evidentiality can be guaranteed. Here, the correspondence Tx601, the correspondence Tx602, and the correspondence information 603 can each be confirmed by a third party and have tamper resistance. Therefore, the information processing device 100 can ensure the neutrality of the verification process. For these reasons, the information processing device 100 can easily take over royalty information when transferring the NFT on the BC-Priv510 to the BC-Pub520.

[0131] (Specific example of operation of information processing system 200) Next, a specific example of the operation of the information processing system 200 will be described with reference to FIGS.

[0132] 7 to 11 are explanatory diagrams showing a specific example of the operation of the information processing system 200. In Fig. 7, there are a BC-Priv 710 and a BC-Pub 720. The BC-Priv 710 corresponds to, for example, the first BC 210 described above. The BC-Pub 720 corresponds to, for example, the second BC 220 described above. The information processing device 100 manages a cooperation BC 730. The cooperation BC 730 corresponds to, for example, the third BC 230 described above.

[0133] The information processing device 100 realizes the BC cooperation function 700 together with the cooperation BC 730. The cooperation BC 730 has a correspondence relationship registration SC 731. The correspondence relationship registration SC 731 manages correspondence information indicating that two addresses on different BCs correspond to each other. The correspondence relationship registration SC 731 manages, for example, correspondence information indicating that an address on the BC-Priv 710 corresponds to an address on the BC-Pub 720.

[0134] BC-Priv710 has a royalty management SC740. The royalty management SC740 manages royalty information. The royalty information may include, for example, a calculation formula indicating what percentage of the price of a commercial transaction using an NFT the royalty is. The royalty management SC740 has, for example, a royalty information management table 741 that registers royalty information and stores the royalty information.

[0135] 7, the royalty information management table 741 has fields of tokenId and royalty receiver. The royalty information management table 741 stores royalty information as records by setting information in each field for each NFT on the BC-Priv 710.

[0136] The tokenId field is set with a tokenId that identifies the NFT on the BC-Priv710. The royalty receiver field is set with an address on the BC-Priv710 that indicates the destination of the royalty for the NFT. The royalty information management table 741 may further include a royalty field (not shown). The royalty field is set with a calculation formula that indicates what percentage of the price of the commercial transaction using the NFT the royalty is.

[0137] BC-Pub720 has a royalty management SC750. The royalty management SC750 manages royalty information. The royalty information may include, for example, a calculation formula indicating what percentage of the price of a commercial transaction using an NFT the royalty is. The royalty management SC750 has, for example, a royalty information management table 751 that registers royalty information and stores the royalty information.

[0138] 7, the royalty information management table 751 has fields of tokenId and royalty receiver. The royalty information management table 751 stores royalty information as records by setting information in each field for each NFT on the BC-Pub 720.

[0139] The tokenId field is set with a tokenId that identifies the NFT on BC-Pub720. The royalty receiver field is set with an address on BC-Pub720 that indicates the destination of the royalty for the NFT. The royalty information management table 751 may further include a royalty field (not shown). The royalty field is set with a calculation formula that indicates what percentage of the price of the commercial transaction using the NFT the royalty is.

[0140] The BC-Priv 710 has an association preparation SC 760. The association preparation SC 760 issues and manages association Tx. The BC-Pub 720 has an association preparation SC 770. The association preparation SC 770 issues and manages association Tx.

[0141] The creator has address 0xabcd on the BC-Priv 710, address 0x1234 on the BC-Pub 720, and address 0x0000 on the associated BC 730. The creator wants to generate an NFT on the BC-Priv 710.

[0142] Based on the creator's operational input, the client device 201 uses the address 0xabcd on the BC-Priv 710 to generate a generation request requesting the generation of an NFT, and sends the request to the BC-Priv 710. In response to the generation request, the BC-Priv 710 generates an NFT 701 with tokenId:token-x, and registers it in the distributed ledger.

[0143] Of the BC-Priv710, the royalty management SC740 sets the address 0xabcd, which indicates the sender of the generation request, on the BC-Priv710 to the royalty receiver, which is the payment destination of royalties for the NFT701. The royalty management SC740 generates royalty information that associates the tokenId:token-x of the NFT701 with the royalty receiver:address 0xabcd, and registers it in the royalty information management table 741. Next, we move on to the explanation of FIG. 8.

[0144] 8, a creator wishes to transfer an NFT 701 on a BC-Priv 710 to a BC-Pub 720. Based on the creator's operational input, the client device 201 acquires an address 0xabcd on the BC-Priv 710 and an address 0x1234 on the BC-Pub 720 to be associated. Based on the creator's operational input, the client device 201 acquires an address 0x0000 on the associated BC 730 owned by the creator.

[0145] The client device 201 uses the acquired address 0x0000 on the association BC 730 to generate an association request 800 and transmits it to the information processing device 100. The association request 800 has a sender field indicating the address of the sender, and a message field. The association request 800 includes the address 0x0000 on the association BC 730 in the sender field. The association request 800 includes the address 0xabcd on the BC-Priv 710 and the address 0x1234 on the BC-Pub 720 in the message field as association targets.

[0146] The information processing device 100 receives the association request 800. In response to the association request 800, the information processing device 100 acquires the address 0x0000 on the association BC 730, which is set in the sender field as the sender address. In response to the association request 800, the information processing device 100 starts monitoring Tx on the BC-Priv 710 and Tx on the BC-Pub 720.

[0147] For example, the information processing device 100 acquires the address 0xabcd on BC-Priv710 and the address 0x1234 on BC-Pub720, which are set in the message field, based on the association request 800. For example, the information processing device 100 starts monitoring Tx including the address 0xabcd in the sender field on BC-Priv710 based on the acquired address 0xabcd on BC-Priv710. An address representing the issuer is set in the sender field. For example, the information processing device 100 starts monitoring Tx including the address 0x1234 in the sender field on BC-Pub720 based on the acquired address 0x1234 on BC-Pub720. Next, the description of FIG. 9 will be moved to next.

[0148] 9, the client device 201 transmits an issuance request to the BC-Priv 710 based on the address 0xabcd on the BC-Priv 710 acquired as the association target and the address 0x0000 on the association BC 730 acquired. The issuance request requests the issuance of an association Tx in which the address 0xabcd on the BC-Priv 710 is set in the sender field and the address 0x0000 on the association BC 730 is set in the message field.

[0149] In response to the issuance request, the association preparation SC760 issues an association Tx901 in which the sender field is set to the address 0xabcd on the BC-Priv710 and the message field is set to the address 0x0000 on the linking BC730. The association preparation SC760 registers the issued association Tx901 in the distributed ledger managed by the BC-Priv710. Since the association Tx901 includes the address 0x0000 on the linking BC730, it can be shown that it is a Tx intentionally issued by the creator. Since the association Tx901 includes the address 0xabcd on the BC-Priv710, it can be guaranteed that the address 0xabcd is the target of association.

[0150] The client device 201 transmits an issuance request to the BC-Priv 710 based on the address 0x1234 on the BC-Pub 720 acquired as the association target and the address 0x0000 on the association BC 730 acquired. The issuance request requests the issuance of an association Tx 902 in which the address 0x1234 on the BC-Pub 720 is set in the sender field and the address 0x0000 on the association BC 730 is set in the message field.

[0151] In response to the issuance request, the BC-Pub720 issues a correspondence Tx902 in which the sender field is set to the address 0x1234 on the BC-Pub720 and the message field is set to the address 0x0000 on the BC730 for collaboration. The BC-Pub720 registers the issued correspondence Tx902 in the distributed ledger managed by the BC-Pub720. Since the correspondence Tx902 includes the address 0x0000 on the BC730 for collaboration, it can be shown that it is a Tx intentionally issued by the creator. Since the correspondence Tx902 includes the address 0x1234 on the BC-Pub720, it can be guaranteed that the address 0x1234 is the subject of the correspondence.

[0152] (9-1) The information processing device 100 detects an association Tx 901 including an address 0xabcd in the sender field on the BC-Priv 710. The information processing device 100 acquires an address 0x0000 on the cooperation BC 730 that is set in the message field of the detected association Tx 901.

[0153] The information processing device 100 detects an association Tx 902 that includes an address 0x1234 in the sender field on the BC-Pub 720. The information processing device 100 acquires an address 0x0000 on the cooperation BC 730 that is set in the message field of the detected association Tx 902.

[0154] The information processing device 100 determines whether or not the address on the association BC 730 acquired from the association Tx 901, the address on the association BC 730 acquired from the association Tx 902, and the address on the association BC 730 acquired from the association request 800 match. If they match, the association Tx 901 and the association Tx 902 are Txs issued by the creator who is the sender of the association request 800. On the other hand, if they do not match, the association Tx 901 and the association Tx 902 may not be Txs issued by the creator who is the sender of the association request 800.

[0155] Therefore, if the information processing device 100 determines that there is a match, it determines that the correspondence between the address 0xabcd on BC-Priv710 and the address 0x1234 on BC-Pub720, which were acquired as the correspondence target, is valid. On the other hand, if the information processing device 100 determines that there is no match, it determines that the correspondence between the address 0xabcd on BC-Priv710 and the address 0x1234 on BC-Pub720, which were acquired as the correspondence target, is invalid.

[0156] 9, the information processing device 100 specifically determines that there is a match, and therefore determines that the correspondence between the address 0xabcd on BC-Priv710 and the address 0x1234 on BC-Pub720, which are acquired as the correspondence target, is valid. This allows the information processing device 100 to ensure the validity of the correspondence between the address 0xabcd on BC-Priv710 and the address 0x1234 on BC-Pub720.

[0157] (9-2) The information processing device 100 determines that the correspondence between the address 0xabcd on the BC-Priv 710 and the address 0x1234 on the BC-Pub 720 is valid, and therefore registers the correspondence in the correspondence registration SC 731 of the cooperation BC 730. The information processing device 100 generates correspondence information indicating that the address 0xabcd on the BC-Priv 710 corresponds to the address 0x1234 on the BC-Pub 720, for example, by associating the address with the address 0x0000 on the cooperation BC 730.

[0158] The association information includes, for example, an address 0xabcd on the BC-Priv 710 and an address 0x1234 on the BC-Pub 720 as association targets in association with an address 0x0000 on the cooperation BC 730. The information processing device 100, for example, transmits the association information to the association registration SC 731 of the cooperation BC 730 and executes the association registration SC 731. The association registration SC 731 registers the received association information in the association information management table 910.

[0159] 9, the correspondence information management table 910 has fields for account and relation address. The correspondence information management table 910 stores correspondence information as records by setting information in each field for each address on the association BC 730.

[0160] In the account field, an address on the cooperation BC 730 is set. In the relation address field, a pair of two addresses on different BCs, which are associated with the address on the cooperation BC 730, is set. The pair is, for example, an address on the BC-Priv 710 and an address on the BC-Pub 720.

[0161] This allows the information processing device 100 to make the association information verifiable by a third party, and ensures evidence that an address on the BC-Priv710 has been associated with an address on the BC-Pub720. Here, since an attacker cannot issue association Tx901 and association Tx902, the information processing device 100 can avoid an attack by an attacker to erroneously associate two addresses on different BCs. Next, we move on to the description of FIG. 10.

[0162] 10, (10-1) the client device 201 generates a transfer request requesting the transfer of an NFT 701 on a BC-Priv 710 with tokenId:token-x to a BC-Pub 720 based on an operational input from a creator. The client device 201 transmits the generated transfer request to the information processing device 100. The transfer request includes, for example, tokenId:token-x. The transfer request includes, for example, information identifying the BC-Priv 710 that is the transfer source and information identifying the BC-Pub 720 that is the transfer destination.

[0163] (10-2) The information processing device 100 receives a transfer request from the client device 201. The information processing device 100 acquires tokenId:token-x based on the transfer request. The information processing device 100 identifies the BC-Priv 710 that will be the transfer source and the BC-Pub 720 that will be the transfer destination based on the transfer request. The information processing device 100 acquires royalty information corresponding to the acquired tokenId:token-x from the identified BC-Priv 710 that will be the transfer source.

[0164] Based on the royalty receiver field of the acquired royalty information, the information processing device 100 acquires the address 0xabcd on the BC-Priv 710 that indicates the payment destination of the royalty for the NFT 701. The information processing device 100 may acquire a calculation formula for calculating the royalty based on the acquired royalty information.

[0165] (10-3) The information processing device 100 queries the correspondence registration SC731 for association information including the address 0xabcd, using the acquired address 0xabcd on BC-Priv710 as a key. The information processing device 100 acquires association information indicating that the address 0xabcd on BC-Priv710 corresponds to the address 0x1234 on BC-Pub720 from the correspondence registration SC731. The information processing device 100 determines the address 0x1234 on BC-Pub720 as the new royalty payment destination based on the acquired association information. Next, the description will move to FIG. 11.

[0166] 11, (11-1) the information processing device 100 controls the BC-Priv 710 to burn the NFT 701 on the BC-Priv 710 with tokenId:token-x. The information processing device 100 transmits, for example, a burn command to the BC-Priv 710 requesting to burn the NFT 701 on the BC-Priv 710 with tokenId:token-x. In response to the burn command, the BC-Priv 710 burns the NFT 701 with tokenId:token-x.

[0167] (11-2) The information processing device 100 controls the BC-Pub 720 to generate an NFT 1100 having the same contents as the NFT 701 on the BC-Priv 710, which is tokenId:token-x. The information processing device 100 transmits, for example, a mint command to the BC-Pub 720 requesting the generation of the NFT 1100. The BC-Pub 720 generates the NFT 1100 in response to the mint command. The BC-Pub 720 transmits the tokenId:token-x of the NFT 1100 to the information processing device 100. Here, for convenience, it is assumed that the tokenId of the NFT 701 and the tokenId of the NFT 1100 are the same, but this is not limited thereto. For example, the tokenId of the NFT 701 and the tokenId of the NFT 1100 may be different.

[0168] (11-3) The information processing device 100 receives the tokenId:token-x of the NFT 1100. The information processing device 100 transmits a registration request to the BC-Pub 720, requesting that the address 0x1234 on the BC-Pub 720, which has been determined as the new payment destination of the royalty, and the tokenId:token-x of the received NFT 1100 be registered in association with each other. The registration request includes the address 0x1234 on the BC-Pub 720, which represents the payment destination of the royalty, and the tokenId:token-x of the NFT 1100. The registration request may include, for example, a calculation formula for calculating the royalty acquired by the information processing device 100.

[0169] Of the BC-Pub720, the royalty management SC750 receives a registration request from the information processing device 100. Based on the registration request, the royalty management SC750 sets the address 0x1234 on the BC-Pub720 as the royalty receiver, which is the payment destination of royalties for the NFT1100. The royalty management SC740 generates royalty information that associates the tokenId:token-x of the NFT1100 with the royalty receiver:address 0x1234, and registers it in the royalty information management table 751. The royalty management SC740 may include a calculation formula for calculating royalties in the royalty information.

[0170] This allows the information processing device 100 to substantially transfer the NFT 701 on the BC-Priv 710 to the BC-Pub 720. The information processing device 100 can substantially transfer the royalty information corresponding to the NFT 701 on the BC-Priv 710 to the NFT 1100 on the BC-Pub 720.

[0171] (Matching process procedure) Next, an example of a procedure of the association process executed by the information processing device 100 will be described with reference to Fig. 12. The association process is realized by, for example, the CPU 301, storage areas such as the memory 302 and the recording medium 305, and the network I / F 303 shown in Fig. 3.

[0172] Fig. 12 is a flowchart showing an example of a procedure of the association process. In Fig. 12, the information processing device 100 receives an association request from the client device 201, which requests associating a first address on the first BC 210 with a second address on the second BC 220 (step S1201). The association request includes, for example, an identifier of the first BC 210, a first address on the first BC 210, an identifier of the second BC 220, and a second address on the second BC 220. In response to receiving the association request, the information processing device 100 identifies the first BC 210 and the second BC 220, and starts monitoring the Tx on the first BC 210 and the Tx on the second BC 220 (step S1202).

[0173] The information processing device 100 judges whether or not both the first Tx on the first BC 210 including the first address and the second Tx on the second BC 220 including the second address are detected within a certain time from the start of monitoring (step S1203). If both the first Tx and the second Tx are detected (step S1203: Yes), the information processing device 100 proceeds to the process of step S1204. On the other hand, if at least one of the first Tx and the second Tx is not detected (step S1203: No), the information processing device 100 ends the association process.

[0174] In step S1204, the information processing device 100 determines whether the value of the message in the first Tx matches the value of the message in the second Tx (step S1204). If they do not match (step S1204: No), the information processing device 100 ends the association process. On the other hand, if they match (step S1204: Yes), the information processing device 100 proceeds to the process of step S1205.

[0175] In step S1205, the information processing device 100 registers the correspondence between the first address and the second address in the third BC 230 (step S1205). Then, the information processing device 100 ends the association process. This allows the information processing device 100 to associate the first address with the second address. The information processing device 100 can guarantee the validity of the correspondence between the first address and the second address.

[0176] (Transfer Processing Procedure) Next, an example of a transfer process procedure executed by the information processing device 100 will be described with reference to Fig. 13. The transfer process is realized by, for example, the CPU 301, storage areas such as the memory 302 and the recording medium 305, and the network I / F 303 shown in Fig. 3.

[0177] Fig. 13 is a flowchart showing an example of a transfer process procedure. In Fig. 13, the information processing device 100 receives a transfer request requesting that an NFT on the first BC 210 be transferred to the second BC 220 (step S1301). The transfer request includes, for example, an identifier of the first BC 210 that is the transfer source, an identifier of the NFT on the first BC 210, and an identifier of the second BC 220 that is the transfer destination.

[0178] The information processing device 100 refers to the first BC 210 and identifies a first address to which royalties for the NFT on the first BC 210 are paid (step S1302). The information processing device 100 refers to the third BC 230 and identifies a second address on the second BC 220 that corresponds to the first address (step S1303). The information processing device 100 burns the NFT on the first BC 210 that is the transfer source (step S1304). The information processing device 100 generates an NFT on the second BC 220 that is the transfer destination (step S1305).

[0179] The information processing device 100 generates royalty information representing the identified second address as the payment destination of the royalty for the NFT on the first BC 210, and registers it on the second BC 220 (step S1306). The information processing device 100 ends the transfer process. This allows the information processing device 100 to appropriately transfer the NFT.

[0180] Here, the information processing device 100 may change the order of the processes of some steps in the flowcharts of Figures 12 and 13. For example, the order of the processes of steps S1302 and S1303 may be changed. Furthermore, the information processing device 100 may omit the processes of some steps in the flowcharts of Figures 12 and 13.

[0181] As described above, the information processing device 100 can acquire a first request including a first address on the first BC 210 and a second address on the second BC 220, and requesting that the first address and the second address be associated with each other. The information processing device 100 can detect a first Tx including the first address and a third address on the third BC 230 issued by the first BC 210 in response to a request by a user having the first address, based on the first address included in the first request. The information processing device 100 can detect a second Tx including the second address and a fourth address on the third BC 230 issued by the second BC 220 in response to a request by a user having the second address, based on the second address included in the first request. The information processing device 100 can determine that the first address and the second address are associated with each other when the third address and the fourth address match, based on the detected first Tx and the detected second Tx. According to information processing device 100, if the third address and the fourth address do not match, it can be determined that the first address and the second address are not associated with each other. This allows information processing device 100 to appropriately determine whether or not to associate the first address with the second address, and makes it easier to ensure the validity of the association between the first address and the second address.

[0182] According to the information processing device 100, when it is determined that the first address and the second address are associated with each other, the result of associating the first address with the second address can be registered in the third BC 230. This allows the information processing device 100 to leave evidence regarding the association of the first address with the second address.

[0183] According to the information processing device 100, it is possible to acquire a second request requesting that a token on the first BC 210 associated with the first address be transferred onto the second BC 220. According to the information processing device 100, when it is determined that the first address and the second address are associated with each other, it is possible to burn the token on the first BC 210 and generate a token on the second BC 220 in response to acquiring the second request. According to the information processing device 100, it is possible to associate the second address with the generated token. In this way, the information processing device 100 can associate an appropriate address with the generated token.

[0184] According to the information processing device 100, the second address can be associated with the generated token as a payment destination of royalties for the token on the second BC 220. This allows the information processing device 100 to appropriately set a payment destination of royalties for the generated token.

[0185] According to the information processing device 100, if the third address and the fourth address are not valid addresses on the third BC 230, it can be determined that the first address and the second address are not associated with each other. This makes it easier for the information processing device 100 to ensure the validity of associating the first address with the second address.

[0186] According to the information processing device 100, if at least one of the detected first Tx and the detected second Tx has not been issued within a period from the present time to a predetermined time ago, it can be determined that the first address and the second address are not associated. This makes it easier for the information processing device 100 to guarantee the validity of associating the first address with the second address.

[0187] According to the information processing device 100, if at least one of the first Tx and the second Tx is not detected within a certain time after the first request is acquired, it can be determined that the first address is not associated with the second address. This makes it easier for the information processing device 100 to ensure the validity of associating the first address with the second address.

[0188] The information processing device 100 can be applied to a case where the first BC 210 is a BC different from the second BC 220. This allows the information processing device 100 to associate the first address and the second address on the different BCs.

[0189] According to the information processing device 100, it is possible to detect a first Tx including the first address as an address representing an authenticated issuer. According to the information processing device 100, it is possible to detect a second Tx including the second address as an address representing an authenticated issuer. This makes it possible for the information processing device 100 to easily guarantee the legitimacy of associating the first address with the second address.

[0190] The information processing method described in this embodiment can be realized by executing a prepared program on a computer such as a PC or a workstation. The information processing program described in this embodiment is recorded on a computer-readable recording medium, and is executed by being read from the recording medium by the computer. The recording medium may be a hard disk, a flexible disk, a CD (Compact Disc)-ROM, an MO (Magneto Optical disc), a DVD (Digital Versatile Disc), or the like. The information processing program described in this embodiment may also be distributed via a network such as the Internet.

[0191] The following supplementary notes are further disclosed regarding the above-described embodiment.

[0192] (Supplementary Note 1) Acquire a request including a first address on a first blockchain and a second address on a second blockchain, and requesting that the first address and the second address be associated with each other; Based on the first address included in the acquired request, detect a first transaction that is issued by the first blockchain in response to a request by a user having the first address and that includes the first address and a third address on a third blockchain managed by the device; Based on the second address included in the acquired request, detect a second transaction that includes the second address and a fourth address on the third blockchain and that was issued by the second blockchain in response to a request by a user having the second address; determining, based on the detected first transaction and the detected second transaction, that the first address and the second address are associated if the third address and the fourth address match, and determining, based on the detected first transaction and the detected second transaction, that the first address and the second address are not associated if the third address and the fourth address do not match; An information processing device comprising a control unit.

[0193] (Additional Note 2) The control unit is The information processing device described in Appendix 1, characterized in that when it is determined that the first address and the second address are associated, the result of associating the first address and the second address is registered in the third blockchain.

[0194] (Additional Note 3) The control unit is Obtain a second request to transfer the tokens on the first blockchain associated with the first address onto the second blockchain; The information processing device described in Appendix 2, characterized in that if it is determined that the first address and the second address are associated, in response to receiving the second request, the information processing device burns the token on the first blockchain, generates the token on the second blockchain, and associates the second address with the generated token.

[0195] (Additional Note 4) The first address is associated with the token on the first blockchain as a payment destination of royalties for the token, The control unit is The information processing device described in Appendix 3, characterized in that the second address is associated with the generated token as a payment destination of royalties for the token on the second blockchain.

[0196] (Additional Note 5) The control unit is The information processing device described in Appendix 1, characterized in that if the third address and the fourth address are not legitimate addresses on the third blockchain, it determines that the first address and the second address are not associated with each other.

[0197] (Additional Note 6) The control unit is 2. The information processing device according to claim 1, further comprising: a first address and a second address that are associated with each other when at least one of the detected first transaction and the detected second transaction has not been issued within a period from the present time to a predetermined time ago.

[0198] (Supplementary Note 7) The control unit is The information processing device described in Appendix 1, characterized in that if at least one of the first transaction and the second transaction is not detected within a certain time after receiving the request, it is determined that the first address and the second address are not associated.

[0199] (Supplementary Note 8) The information processing device according to any one of Supplementary Notes 1 to 7, wherein the first blockchain is a blockchain different from the second blockchain.

[0200] (Supplementary Note 9) The first transaction includes the first address as an address representing an authenticated issuer; 8. The information processing device according to claim 1, wherein the second transaction includes the second address as an address representing an authenticated issuer.

[0201] (Supplementary Note 10) A system including a first blockchain in which a first address exists, a second blockchain in which a second address exists, an information processing device, and a third blockchain managed by the information processing device, The first blockchain is In response to a request by a user having the first address, issue a first transaction that includes the first address and a third address on the third blockchain; The second blockchain is In response to a request by a user having the second address, issue a second transaction that includes the second address and a fourth address on the third blockchain; The information processing device includes: acquiring a request including the first address and the second address and requesting that the first address be associated with the second address; Detecting the first transaction issued by the first blockchain based on the first address included in the acquired request; Detecting the second transaction issued by the second blockchain based on the second address included in the acquired request; determining, based on the detected first transaction and the detected second transaction, that the first address and the second address are associated if the third address and the fourth address match, and determining, based on the detected first transaction and the detected second transaction, that the first address and the second address are not associated if the third address and the fourth address do not match; A system characterized by:

[0202] (Supplementary Note 11) Acquire a request including a first address on a first blockchain and a second address on a second blockchain, the request requesting that the first address and the second address be associated with each other; Based on the first address included in the acquired request, detect a first transaction that is issued by the first blockchain in response to a request by a user having the first address and that includes the first address and a third address on a third blockchain managed by the device; Based on the second address included in the acquired request, detect a second transaction that includes the second address and a fourth address on the third blockchain and that was issued by the second blockchain in response to a request by a user having the second address; determining, based on the detected first transaction and the detected second transaction, that the first address and the second address are associated if the third address and the fourth address match, and determining, based on the detected first transaction and the detected second transaction, that the first address and the second address are not associated if the third address and the fourth address do not match; An information processing program that causes a computer to execute a process. [Explanation of symbols]

[0203] 100 Information processing device 101 First Address 102 Second Address 110,210 1st BC 111 1st Tx 120,220 2nd BC 121 2nd Tx 130,230 3rd BC 200 Information Processing Systems 201 Client device 211 1st BC Node 221 2nd BC Node 231 3rd BC Node 240 Network 300 Bus 301 CPU 302 Memory 303 Network Interface 304 Recording media I / F 305 Recording media 410 1st memory section 411 First acquisition part 412 1st Publishing Division 420 2nd memory section 421 Second Acquisition Department 422 2nd Publishing Division 430 Third memory section 431 Third Acquisition Department 432 Detection unit 433 Correspondence Department 434 Relocation Department 435 Output section 500,700 BC link function 510,710 BC-Priv 520,720 BC-Pub 530,730 Linked BC 531,731 Correspondence registration SC 601,602,901,902 Matching Tx 603 Mapping Information 701,1100 NFT 740,750 Royalty Management SC 741,751 Royalty information management table 760,770 Matching preparation SC 800 Matching Request 910 Information Management Table

Claims

1. receiving a request including a first address on a first blockchain and a second address on a second blockchain, the request requesting that the first address be associated with the second address; Based on the first address included in the acquired request, detect a first transaction that is issued by the first blockchain in response to a request by a user having the first address and that includes the first address and a third address on a third blockchain managed by the device; Based on the second address included in the acquired request, detect a second transaction that includes the second address and a fourth address on the third blockchain and that was issued by the second blockchain in response to a request by a user having the second address; determining, based on the detected first transaction and the detected second transaction, that the first address and the second address are associated with each other if the third address and the fourth address match, and determining, based on the detected first transaction and the detected second transaction, that the first address and the second address are not associated with each other if the third address and the fourth address do not match; An information processing device comprising a control unit.

2. The control unit is The information processing device according to claim 1, characterized in that, when it is determined that the first address and the second address are associated, the result of associating the first address and the second address is registered in the third blockchain.

3. The control unit is Obtain a second request to transfer the tokens on the first blockchain associated with the first address onto the second blockchain; The information processing device according to claim 2, characterized in that when it is determined that the first address and the second address are associated, in response to receiving the second request, the token is burned on the first blockchain, the token is generated on the second blockchain, and the second address is associated with the generated token.

4. The control unit is The information processing device according to claim 1, characterized in that if the third address and the fourth address are not legitimate addresses on the third blockchain, it is determined that the first address and the second address are not associated with each other.

5. The control unit is 2. The information processing device according to claim 1, further comprising: a processor that detects a first address and a second address, the processor determining that the first address and the second address are not associated with each other if at least one of the detected first transaction and the detected second transaction has not been issued within a period from the present time to a predetermined time ago.

6. The control unit is 2. The information processing device according to claim 1, wherein if at least one of the first transaction and the second transaction is not detected within a certain time period after the request is received, it is determined that the first address is not associated with the second address.

7. A system including a first blockchain in which a first address exists, a second blockchain in which a second address exists, an information processing device, and a third blockchain managed by the information processing device, The first blockchain is In response to a request by a user having the first address, issuing a first transaction including the first address and a third address on the third blockchain; The second blockchain is In response to a request by a user having the second address, issue a second transaction including the second address and a fourth address on the third blockchain; The information processing device includes: acquiring a request including the first address and the second address and requesting that the first address be associated with the second address; Detecting the first transaction issued by the first blockchain based on the first address included in the acquired request; Detecting the second transaction issued by the second blockchain based on the second address included in the acquired request; determining, based on the detected first transaction and the detected second transaction, that the first address and the second address are associated with each other if the third address and the fourth address match, and determining, based on the detected first transaction and the detected second transaction, that the first address and the second address are not associated with each other if the third address and the fourth address do not match; A system characterized by:

8. receiving a request including a first address on a first blockchain and a second address on a second blockchain, the request requesting that the first address be associated with the second address; Based on the first address included in the acquired request, detect a first transaction that is issued by the first blockchain in response to a request by a user having the first address and that includes the first address and a third address on a third blockchain managed by the device; Based on the second address included in the acquired request, detect a second transaction that includes the second address and a fourth address on the third blockchain and that was issued by the second blockchain in response to a request by a user having the second address; determining, based on the detected first transaction and the detected second transaction, that the first address and the second address are associated with each other if the third address and the fourth address match, and determining, based on the detected first transaction and the detected second transaction, that the first address and the second address are not associated with each other if the third address and the fourth address do not match; An information processing program that causes a computer to execute a process.

Images