Abstract: A settlement system includes a service provider device 2 which transmits a template information transaction including a template of a transaction to a network 4 of a first blockchain, a user device which transmits, to the network 4 of the first blockchain, a payment information transaction that includes an electronic signature generated by using the template of the transaction and a payment amount, and a smart contract 41, wherein the smart contract 41 verifies the electronic signature by using the payment amount and the template of the transaction, the service provider device 2 generates a settlement transaction by using the template of the transaction, the electronic signature and the payment amount, and transmits the settlement transaction to a network 3 of a second blockchain, a plurality of output conditions are set to the template of the transaction, and the settlement transaction becomes usable when any one of the plurality of output conditions is satisfied.

Abstract: A user terminal generates a first key pair and a second key pair, transmits a permission request including a public encryption key of the second key pair after electronically signing the permission request with a secret encryption key, and acquires, from permission information transmitted from a right-holder terminal, a content decryption key by using a secret decryption key of the second key pair and uses the content. The right-holder terminal stores a third key pair and the content decryption key, verifies the permission request received, and encrypts the content decryption key by using the public encryption key of the second key pair included in the permission request and transmits the permission information including the encrypted content decryption key after electronically signing the permission information with a secret encryption key of the third key pair. The permission request and the permission information are transmitted and received via a blockchain.

Abstract: The blockchain generation apparatus 1 includes: a parameter calculator 122 that identifies a parameter type to be used for linkage of the new block, based on block approval method data 114, and calculates a value for the identified parameter type based on transaction datasets which are related to an identifier of a generating party; a block generation condition checker 125 that determines whether the generating party is qualified to generate the new blockchain data, based on the value calculated by the parameter calculator 122; and a blockchain generator 126 that tries to generate the new blockchain by referring to the shared data when the block generation condition checker 125 determines that the generating party is qualified. An identifier of the blend pattern included in the block approval method data 114 specifies a combination of the plurality of parameter types that conflict with each other.

Abstract: A user terminal according to the present embodiment is a user terminal connectable to a first distributed ledger network and a second distributed ledger network, and includes a generation unit, a first control unit, and a second control unit. The generation unit generates a decentralized identifier related to a user using a verification key. The first control unit generates a registration transaction including the verification key and the decentralized identifier, and transmits the registration transaction to the first distributed ledger network. The second control unit generates a token transaction related to issuance of a token, the token transaction including data of the user and the decentralized identifier, and transmits the token transaction to the second distributed ledger network.

Abstract: When an updated file that is an updated version of an original file is registered in a distributed file management system 100, a difference creation unit 222 creates a difference file between the original file and the updated file, a route object creation unit 223 creates a route object that includes an ID of the original file and an ID of the difference file, and a distributed file management client 11 causes the difference file and the route object to be registered in the distributed file management system 100.

Abstract: A settlement system includes a service provider device 2 which transmits a template information transaction including a template of a transaction to a network 4 of a first blockchain, a user device which transmits, to the network 4 of the first blockchain, a payment information transaction that includes an electronic signature generated by using the template of the transaction and a payment amount, and a smart contract 41, wherein the smart contract 41 verifies the electronic signature by using the payment amount and the template of the transaction, the service provider device 2 generates a settlement transaction by using the template of the transaction, the electronic signature and the payment amount, and transmits the settlement transaction to a network 3 of a second blockchain, a plurality of output conditions are set to the template of the transaction, and the settlement transaction becomes usable when any one of the plurality of output conditions is satisfied.

Abstract: A user terminal generates a first key pair and a second key pair, transmits a permission request including a public encryption key of the second key pair after electronically signing the permission request with a secret encryption key, and acquires, from permission information transmitted from a right-holder terminal, a content decryption key by using a secret decryption key of the second key pair and uses the content. The right-holder terminal stores a third key pair and the content decryption key, verifies the permission request received, and encrypts the content decryption key by using the public encryption key of the second key pair included in the permission request and transmits the permission information including the encrypted content decryption key after electronically signing the permission information with a secret encryption key of the third key pair. The permission request and the permission information are transmitted and received via a blockchain.

Abstract: A user terminal generates a first key pair and a second key pair, transmits a permission request including a public encryption key of the second key pair after electronically signing the permission request with a secret encryption key, and acquires, from permission information transmitted from a right-holder terminal, a content decryption key by using a secret decryption key of the second key pair and uses the content. The right-holder terminal stores a third key pair and the content decryption key, verifies the permission request received, and encrypts the content decryption key by using the public encryption key of the second key pair included in the permission request and transmits the permission information including the encrypted content decryption key after electronically signing the permission information with a secret encryption key of the third key pair. The permission request and the permission information are transmitted and received via a blockchain.

Abstract: A user terminal generates a first key pair and a second key pair, transmits a permission request including a public encryption key of the second key pair after electronically signing the permission request with a secret encryption key, and acquires, from permission information transmitted from a right-holder terminal, a content decryption key by using a secret decryption key of the second key pair and uses the content. The right-holder terminal stores a third key pair and the content decryption key, verifies the permission request received, and encrypts the content decryption key by using the public encryption key of the second key pair included in the permission request and transmits the permission information including the encrypted content decryption key after electronically signing the permission information with a secret encryption key of the third key pair. The permission request and the permission information are transmitted and received via a blockchain.

Abstract: The blockchain generation apparatus 1 includes: a parameter calculator 122 that identifies a parameter type to be used for linkage of the new block, based on block approval method data 114, and calculates a value for the identified parameter type based on transaction datasets which are related to an identifier of a generating party; a block generation condition checker 125 that determines whether the generating party is qualified to generate the new blockchain data, based on the value calculated by the parameter calculator 122; and a blockchain generator 126 that tries to generate the new blockchain by referring to the shared data when the block generation condition checker 125 determines that the generating party is qualified. An identifier of the blend pattern included in the block approval method data 114 specifies a combination of the plurality of parameter types that conflict with each other.

Abstract: The blockchain generation apparatus 1 includes: a parameter calculator 122 that identifies a parameter type to be used for linkage of the new block, based on block approval method data 114, and calculates a value for the identified parameter type based on transaction datasets which are related to an identifier of a generating party; a block generation condition checker 125 that determines whether the generating party is qualified to generate the new blockchain data, based on the value calculated by the parameter calculator 122; and a blockchain generator 126 that tries to generate the new blockchain by referring to the shared data when the block generation condition checker 125 determines that the generating party is qualified. An identifier of the blend pattern included in the block approval method data 114 specifies a combination of the plurality of parameter types that conflict with each other.

Abstract: The blockchain generation apparatus 1 includes: a synchronizer 121 that acquires shared data 111 which includes the blockchain data 112 and transaction datasets 113 not included in the blockchain data 112; a transaction pattern count calculator 124 that calculates the number of transaction patterns for a generating party using the blockchain generation apparatus 1, based on the transaction datasets which are in the blockchain data 112 and are related to an identifier of the generating party; a block generation condition checker 125 that determines whether the generating party is qualified to generate the new blockchain data, based on the number of transaction patterns calculated by the transaction pattern count calculator; and a blockchain generator 126 that tries to generate the new blockchain by referring to the shared data 111 if the block generation condition checker 125 determines that the generating party is qualified.

Abstract: The blockchain generation apparatus 1 includes: a parameter calculator 122 that identifies a parameter type to be used for linkage of the new block, based on block approval method data 114, and calculates a value for the identified parameter type based on transaction datasets which are related to an identifier of a generating party; a block generation condition checker 125 that determines whether the generating party is qualified to generate the new blockchain data, based on the value calculated by the parameter calculator 122; and a blockchain generator 126 that tries to generate the new blockchain by referring to the shared data when the block generation condition checker 125 determines that the generating party is qualified. An identifier of the blend pattern included in the block approval method data 114 specifies a combination of the plurality of parameter types that conflict with each other.

Abstract: This block chain generation device 1 is provided with: a synchronizing means 121 which acquires shared data 111 which includes block chain data 112 and transaction data 113 not contained in the block chain 112; a transaction pattern amount calculation means 124 which calculates the transaction pattern amount of a creator from the transaction data in the block chain data 112 that relates to an identifier of the creator who is using the block chain generation device 1; a block generation condition confirmation means 125 which, on the basis of the transaction pattern amount, determines whether or not the creator is qualified to generate new block chain data; and a block chain generation means 126 which, if the block generation condition confirmation means 125 determines that the creator is qualified, refers to the shared data 111 to attempt generation of a new block chain.

Abstract: A user terminal generates a first key pair and a second key pair, transmits a permission request including a public encryption key of the second key pair after electronically signing the permission request with a secret encryption key, and acquires, from permission information transmitted from a right-holder terminal, a content decryption key by using a secret decryption key of the second key pair and uses the content. The right-holder terminal stores a third key pair and the content decryption key, verifies the permission request received, and encrypts the content decryption key by using the public encryption key of the second key pair included in the permission request and transmits the permission information including the encrypted content decryption key after electronically signing the permission information with a secret encryption key of the third key pair. The permission request and the permission information are transmitted and received via a blockchain.