ABSTRACT
Abstract
Some embodiments are directed to a blockchain management device (100) configured to distribute a new block of a secondary blockchain to at least one further blockchain management device that manages the secondary blockchain, and to distribute a transaction to at least one blockchain management device that manages a primary blockchain, said transaction comprising an identification of a set of transactions in the new block.
Description
This application is the U.S. National Stage of International Application No. PCT/EP2018/078753, filed on Oct. 19, 2018, which designates the U.S., published in English, and claims priority under 35 U.S.C. § 119 or 365(c) to European Application No. 17197577.4, filed on Oct. 20, 2017. The entire teachings of the above applications are incorporated herein by reference.
FIELD OF THE INVENTION
The invention relates to a blockchain management device, a blockchain use device, a blockchain verification device, a blockchain management method, a blockchain use method, a blockchain verification method, and a computer readable medium.
BACKGROUND
Blockchains are a novel technology that allows distributed management of transactions while at the same time maintaining trust in those transactions. The latter may also be done in a distributed manner. A blockchain is a list of records, which are called blocks, which are linked. Each block contains a pointer as a link to a previous block. Multiple parties can record transactions in the blockchain or verify previous transactions of others. The blockchain is sometimes referred to as a (distributed) ledger.
An example of a known blockchain system is given in US Patent Application 20170031676, âBlockchain Computer Data Distributionâ (included herein by reference). The known system discloses various uses of such blockchains. For example, blockchains are used in cryptocurrency systems. For example, cryptocurrency transactions for a period may be stored in a block that is then added to the tail of the blockchain, thereby extending the blockchain. The history of the cryptocurrency can be accessed by moving along the blocks of the blockchain. The blockchain could be held privately, e.g., in a centralized manner, or held publicly in a less centralized manner. The latter is usual for cryptocurrencies.
Another example, is the distribution of patches to IoT devices through a blockchain environment. In the blockchain environment, blocks, which can hold data, are chained together by storing information in a block which indicates the preceding block. A block can further comprise timestamp information and validation information.
Recently a lot of new blockchain related implementations are created. These implementations provide all kinds of new ways of making transactions between multiple parties, e.g., based on bitcoin or bitcoin type blockchains. Other implementations make use of the immutability characteristic of the blockchain technologies, for example to enable a secure and tamper-proof notary system. From the perspective of the user the blockchain world is changing from clear to cluttered. This imposes new problems, e.g., where multiple blockchains exist in parallel, a verification mechanism is missing to verify the integrity of the data.
SUMMARY OF THE INVENTION
As the blockchain technology evolves, the number of blockchains grows fast. Not only public blockchains, but also private blockchains. Furthermore, the number of applications to which the blockchains may be applied is steadily increasing. The user may thus be confronted with various blockchains for various applications. Not all of these blockchains may be particularly well-known, used by many users, or see a lot of traffic. As a result, the user is in need of an additional way to verify the reliability of a particular blockchain. Apart from verifying the data that is present on a blockchain, a user may also need a reliable way to verify that a blockchain is still being maintained.
A blockchain management device as defined in the claims addresses these concerns. The blockchain management device maintains a secondary blockchain, but records the creation of blocks of the secondary blockchain on a different blockchain: the primary blockchain. The primary blockchain may be maintained by a different device, or devices, and in fact by an entirely different organization. Thus, the user, who may know little of the organization supporting the secondary blockchain, can verify the creation of blocks on the secondary blockchain by inspecting the primary blockchain. Moreover, if the user is unsure if the secondary blockchain is still being maintained, he can verify by inspecting the primary blockchain if blocks are still being created, even if, for some reason, new blocks of the secondary blockchain fail to reach him. Note that the overhead of posting an identification in the primary blockchain is much smaller than, e.g., reposting the entire new block of the secondary blockchain in the new block.
In an aspect of the invention, the blockchain management device produces new blocks according to a predictable schedule, which may be synchronized with the primary blockchain. This gives even better assurances to the user that the secondary blockchain is still being maintained, since by waiting until the predictable time, the user can verify if any block of the secondary blockchain is recorded on the primary blockchain.
An aspect of the invention concerns a blockchain verification device as defined in the claims. The blockchain verification device validates a blockchain, and in particular the transactions on the primary blockchain that refer to blocks on the secondary blockchain. For example, the blockchain verification device may verify that each secondary block indeed has a corresponding transaction on the primary blockchain, and/or that each such transaction on the primary blockchain indeed corresponds to a block on the secondary blockchain. If the system is arranged not to register a transaction on the primary blockchain for each secondary block, then the verification device may be correspondingly adapted.
An aspect of the invention concerns a blockchain use device arranged to receive a transaction and obtain part of a blockchain, e.g., a block thereof, to verify the transaction.
The blockchain management, verification and use devices are electronic devices. For example, they may be a mobile electronic device, in particular the blockchain use device may be a mobile phone. The blockchain management, verification and use devices may, e.g., be a set-top box, computer, etc.
The methods for blockchains described herein may be applied in a wide range of practical applications. Such practical applications include: crypto currencies, transfer systems such as digital notaries implemented on a blockchain, domain management using blockchains, etc. The invention may also be applied in situations in which no transfer is done. For example, in data recording applications, e.g., for recording sensor values and the like.
A method according to the invention may be implemented on a computer as a computer implemented method, or in dedicated hardware, or in a combination of both. Executable code for a method according to the invention may be stored on a computer program product. Examples of computer program products include memory devices, optical storage devices, integrated circuits, servers, online software, etc. Preferably, the computer program product comprises non-transitory program code stored on a computer readable medium for performing a method according to the invention when said program product is executed on a computer.
In a preferred embodiment, the computer program comprises computer program code adapted to perform all the steps of a method according to the invention when the computer program is run on a computer. Preferably, the computer program is embodied on a computer readable medium.
Another aspect of the invention provides a method of making the computer program available for downloading. This aspect is used when the computer program is uploaded into, e.g., Apple's App Store, Google's Play Store, or Microsoft's Windows Store, and when the computer program is available for downloading from such a store.
BRIEF DESCRIPTION OF THE DRAWINGS
Further details, aspects, and embodiments of the invention will be described, by way of example only, with reference to the drawings. Elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. In the Figures, elements which correspond to elements already described may have the same reference numerals. In the drawings,
FIG. 1 schematically shows an example of an embodiment of a blockchain system including a blockchain management device,
FIG. 2 a schematically shows an example of an embodiment of a blockchain,
FIG. 2 b schematically shows an example of an embodiment of a block,
FIG. 2 c schematically shows an example of an embodiment of a block,
FIG. 2 d schematically shows an example of an embodiment of a blockchain,
FIG. 2 e schematically shows an example of an embodiment of a blockchain,
FIG. 2 f schematically shows an example of an embodiment of a blockchain,
FIGS. 3 a , 3 b , 3 c and 3 d schematically shows an example of an embodiment of a blockchain system,
FIG. 4 schematically shows an example of an embodiment of a blockchain verification device
FIG. 5 schematically shows an example of an embodiment of a blockchain use device
FIG. 6 a schematically shows an example of an embodiment of a blockchain management method,
FIG. 6 b schematically shows an example of an embodiment of a blockchain use method,
FIG. 6 c schematically shows an example of an embodiment of a blockchain verification method,
FIG. 7 a schematically shows a computer readable medium having a writable part comprising a computer program according to an embodiment,
FIG. 7 b schematically shows a representation of a processor system according to an embodiment.
List of Reference Numerals in FIGS. 1-5, 7a-7b:
100
a secondary blockchain management device
110
a communication interface
120
block constructor
125
primary blockchain transaction unit
130
consensus prover
140
a hash unit
150
a computer network
151, 152
blockchain use device
160
a further secondary blockchain management device
170
a blockchain verification device
180
a blockchain system
190
a primary blockchain management device
200
a blockchain system
210
a primary blockchain
250
a secondary blockchain
211-215
a block
251-253
a block
220
a block
230
a block
221, 231
a reference to a preceding block
222, 232
multiple transactions
223, 233
a consensus proof
</t
This application is the U.S. National Stage of International Application No. PCT/EP2018/078753, filed on Oct. 19, 2018, which designates the U.S., published in English, and claims priority under 35 U.S.C. § 119 or 365(c) to European Application No. 17197577.4, filed on Oct. 20, 2017. The entire teachings of the above applications are incorporated herein by reference.
FIELD OF THE INVENTION
The invention relates to a blockchain management device, a blockchain use device, a blockchain verification device, a blockchain management method, a blockchain use method, a blockchain verification method, and a computer readable medium.
BACKGROUND
Blockchains are a novel technology that allows distributed management of transactions while at the same time maintaining trust in those transactions. The latter may also be done in a distributed manner. A blockchain is a list of records, which are called blocks, which are linked. Each block contains a pointer as a link to a previous block. Multiple parties can record transactions in the blockchain or verify previous transactions of others. The blockchain is sometimes referred to as a (distributed) ledger.
An example of a known blockchain system is given in US Patent Application 20170031676, âBlockchain Computer Data Distributionâ (included herein by reference). The known system discloses various uses of such blockchains. For example, blockchains are used in cryptocurrency systems. For example, cryptocurrency transactions for a period may be stored in a block that is then added to the tail of the blockchain, thereby extending the blockchain. The history of the cryptocurrency can be accessed by moving along the blocks of the blockchain. The blockchain could be held privately, e.g., in a centralized manner, or held publicly in a less centralized manner. The latter is usual for cryptocurrencies.
Another example, is the distribution of patches to IoT devices through a blockchain environment. In the blockchain environment, blocks, which can hold data, are chained together by storing information in a block which indicates the preceding block. A block can further comprise timestamp information and validation information.
Recently a lot of new blockchain related implementations are created. These implementations provide all kinds of new ways of making transactions between multiple parties, e.g., based on bitcoin or bitcoin type blockchains. Other implementations make use of the immutability characteristic of the blockchain technologies, for example to enable a secure and tamper-proof notary system. From the perspective of the user the blockchain world is changing from clear to cluttered. This imposes new problems, e.g., where multiple blockchains exist in parallel, a verification mechanism is missing to verify the integrity of the data.
SUMMARY OF THE INVENTION
As the blockchain technology evolves, the number of blockchains grows fast. Not only public blockchains, but also private blockchains. Furthermore, the number of applications to which the blockchains may be applied is steadily increasing. The user may thus be confronted with various blockchains for various applications. Not all of these blockchains may be particularly well-known, used by many users, or see a lot of traffic. As a result, the user is in need of an additional way to verify the reliability of a particular blockchain. Apart from verifying the data that is present on a blockchain, a user may also need a reliable way to verify that a blockchain is still being maintained.
A blockchain management device as defined in the claims addresses these concerns. The blockchain management device maintains a secondary blockchain, but records the creation of blocks of the secondary blockchain on a different blockchain: the primary blockchain. The primary blockchain may be maintained by a different device, or devices, and in fact by an entirely different organization. Thus, the user, who may know little of the organization supporting the secondary blockchain, can verify the creation of blocks on the secondary blockchain by inspecting the primary blockchain. Moreover, if the user is unsure if the secondary blockchain is still being maintained, he can verify by inspecting the primary blockchain if blocks are still being created, even if, for some reason, new blocks of the secondary blockchain fail to reach him. Note that the overhead of posting an identification in the primary blockchain is much smaller than, e.g., reposting the entire new block of the secondary blockchain in the new block.
In an aspect of the invention, the blockchain management device produces new blocks according to a predictable schedule, which may be synchronized with the primary blockchain. This gives even better assurances to the user that the secondary blockchain is still being maintained, since by waiting until the predictable time, the user can verify if any block of the secondary blockchain is recorded on the primary blockchain.
An aspect of the invention concerns a blockchain verification device as defined in the claims. The blockchain verification device validates a blockchain, and in particular the transactions on the primary blockchain that refer to blocks on the secondary blockchain. For example, the blockchain verification device may verify that each secondary block indeed has a corresponding transaction on the primary blockchain, and/or that each such transaction on the primary blockchain indeed corresponds to a block on the secondary blockchain. If the system is arranged not to register a transaction on the primary blockchain for each secondary block, then the verification device may be correspondingly adapted.
An aspect of the invention concerns a blockchain use device arranged to receive a transaction and obtain part of a blockchain, e.g., a block thereof, to verify the transaction.
The blockchain management, verification and use devices are electronic devices. For example, they may be a mobile electronic device, in particular the blockchain use device may be a mobile phone. The blockchain management, verification and use devices may, e.g., be a set-top box, computer, etc.
The methods for blockchains described herein may be applied in a wide range of practical applications. Such practical applications include: crypto currencies, transfer systems such as digital notaries implemented on a blockchain, domain management using blockchains, etc. The invention may also be applied in situations in which no transfer is done. For example, in data recording applications, e.g., for recording sensor values and the like.
A method according to the invention may be implemented on a computer as a computer implemented method, or in dedicated hardware, or in a combination of both. Executable code for a method according to the invention may be stored on a computer program product. Examples of computer program products include memory devices, optical storage devices, integrated circuits, servers, online software, etc. Preferably, the computer program product comprises non-transitory program code stored on a computer readable medium for performing a method according to the invention when said program product is executed on a computer.
In a preferred embodiment, the computer program comprises computer program code adapted to perform all the steps of a method according to the invention when the computer program is run on a computer. Preferably, the computer program is embodied on a computer readable medium.
Another aspect of the invention provides a method of making the computer program available for downloading. This aspect is used when the computer program is uploaded into, e.g., Apple's App Store, Google's Play Store, or Microsoft's Windows Store, and when the computer program is available for downloading from such a store.
BRIEF DESCRIPTION OF THE DRAWINGS
Further details, aspects, and embodiments of the invention will be described, by way of example only, with reference to the drawings. Elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. In the Figures, elements which correspond to elements already described may have the same reference numerals. In the drawings,
FIG. 1 schematically shows an example of an embodiment of a blockchain system including a blockchain management device,
FIG. 2 a schematically shows an example of an embodiment of a blockchain,
FIG. 2 b schematically shows an example of an embodiment of a block,
FIG. 2 c schematically shows an example of an embodiment of a block,
FIG. 2 d schematically shows an example of an embodiment of a blockchain,
FIG. 2 e schematically shows an example of an embodiment of a blockchain,
FIG. 2 f schematically shows an example of an embodiment of a blockchain,
FIGS. 3 a , 3 b , 3 c and 3 d schematically shows an example of an embodiment of a blockchain system,
FIG. 4 schematically shows an example of an embodiment of a blockchain verification device
FIG. 5 schematically shows an example of an embodiment of a blockchain use device
FIG. 6 a schematically shows an example of an embodiment of a blockchain management method,
FIG. 6 b schematically shows an example of an embodiment of a blockchain use method,
FIG. 6 c schematically shows an example of an embodiment of a blockchain verification method,
FIG. 7 a schematically shows a computer readable medium having a writable part comprising a computer program according to an embodiment,
FIG. 7 b schematically shows a representation of a processor system according to an embodiment.
List of Reference Numerals in FIGS. 1-5, 7a-7b:
100
a secondary blockchain management device
110
a communication interface
120
block constructor
125
primary blockchain transaction unit
130
consensus prover
140
a hash unit
150
a computer network
151, 152
blockchain use device
160
a further secondary blockchain management device
170
a blockchain verification device
180
a blockchain system
190
a primary blockchain management device
200
a blockchain system
210
a primary blockchain
250
a secondary blockchain
211-215
a block
251-253
a block
220
a block
230
a block
221, 231
a reference to a preceding block
222, 232
multiple transactions
223, 233
a consensus proof
224, 234
a block id
235
a transaction
300
a blockchain system
301
a first level
302
a second level
303
a third level
310-370
a blockchain
381-383
a blockchain
391-394
a blockchain
400
a blockchain use device
410
a communication interface
420
first block obtainer
422
second block obtainer
430
transaction verifier
500
a blockchain verification device
510
a communication interface
520
a verification unit
570
a blockchain storage
1000â
a computer readable medium
1010â
a writable part
1020â
a computer program
1110â
integrated circuit(s)
1120â
a processing unit
1122â
a memory
1124â
a dedicated integrated circuit
1126â
a communication element
1130â
an interconnect
1140â
a processor system
DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS
While this invention is susceptible of embodiment in many different forms, there are shown in the drawings and will herein be described in detail one or more specific embodiments, with the understanding that the present disclosure is to be considered as exemplary of the principles of the invention and not intended to limit the invention to the specific embodiments shown and described. In the following, for the sake of understanding, elements of embodiments are described in operation. However, it will be apparent that the respective elements are arranged to perform the functions being described as performed by them. Further, the invention is not limited to the embodiments, and the invention lies in each and every novel feature or combination of features described herein or recited in mutually different dependent claims.
FIG. 1 schematically shows an example of an embodiment of a blockchain system 180 including a blockchain management device 100 . The system may include various different entities. Included in system 180 may be one or more blockchain management devices; shown are blockchain management devices
100 , and 160 , which are arranged to add one or more blocks to a secondary blockchain. System 180 uses at least two blockchains, referred to as the primary blockchain and secondary blockchain. Transactions are recorded on the secondary blockchain. Some events on the secondary blockchains are recorded on the primary blockchain. For example, adding a new block to the secondary blockchain is recorded on the primary blockchain. This feature allows increased verification of the secondary blockchain. In recent years the number of different blockchains has increased rapidly. It has become increasingly harder to verify the trustworthiness of a particular secondary blockchain. However, by recording some features of the secondary blockchain on a primary blockchain, at least these aspects may be verified. For example, a user may have a high trust in the immutability of some particular primary blockchain, e.g., the primary blockchain may be a well-known blockchain such as the bitcoin blockchain, the Ethereum blockchain, etc. Other advantages and applications are discussed further below. There may be multiple blockchains organized hierarchically, wherein a blockchain at a lower hierarchical level record events in a blockchain on a higher hierarchical level, e.g., on the immediately higher level. The highest level blockchain may be referred to as the root blockchain. The primary blockchain may be the root blockchain.
For example, a lower level blockchain, say the secondary blockchain may be a private blockchain, e.g., for a particular application, a particular company, community or the like, whereas the primary blockchain may be a public blockchain, e.g., the Ethereum blockchain, etc.
FIG. 1 also shows a blockchain management device 190 which is configured to add blocks to a primary blockchain. There may be more than one or two blockchain management devices. For example, there may be more blockchain management devices responsible for the primary or secondary blockchain. There may be devices which are configured both for the primary and secondary blockchain; in other embodiments though a blockchain management device either manages the primary or secondary blockchain but not both. When necessary we will refer to a blockchain management device that adds blocks to a secondary blockchain as a secondary blockchain management device, and a blockchain management device that adds blocks to a primary blockchain as a primary blockchain management device. If observations relate to both type, or the type is clear from the context the classifier primary/secondary may be omitted.
Included in system 180 may further be one or more blockchain use devices. Shown in FIG. 1 is blockchain use device 150 and blockchain use device 151 . The blockchain use devices use the blockchain for some purpose, and may, e.g., generate transactions for inclusion in a future block of the blockchain, or may obtain part of the blockchain to at least partially verify a previous transaction. For example, if the blockchain is used for a cryptocurrency, a blockchain use device may verify that a particular transaction is valid and/or transfer or receive some amount of the crypto currency. There may be more or less blockchain use devices than shown in FIG. 1 . An example, of a blockchain use device 400 which may be, e.g., employed in system 180 is further disclosed below.
The use devices may also be used to store other transactions than currency transaction, e.g., the transactions may report the transfer of goods. The transactions need not necessarily involve two parties, for example, a transaction may record data on a blockchain, e.g., sensor data and the like.
The computer network 150 may be a peer-to-peer network. For example, messages in system 180 may be sent to part of the devices in system 180 , who then forward the message to further devices of system 180 . Peer to peer networking may increase the resiliency of the computer network, but it is not necessary. For example, the devices, e.g., the block management devices, may be programmed with one or more computer network addresses of the other devices in the system, e.g., of the other blockchain management devices.
System 180 may comprise one or more blockchain verification devices. Shown in FIG. 1 is blockchain verification device 170 . A blockchain verification device verifies at least part of the blockchain. There may be more or fewer blockchain verification devices than shown in FIG. 1 . An example, of a blockchain verification device 500 which may, e.g., be employed in system 180 is further disclosed below. A blockchain verification device may verify a primary blockchain, a secondary blockchain or both.
Some or all of the devices of system 180 may be integrated. For example, a blockchain verification device may be separate from a blockchain management device, e.g., to distribute these functions over different computers which may even be distributed geographically. However, a blockchain verification device may also advantageously be integrated with a blockchain management device. A blockchain verification device may also be integrated in a blockchain use device, e.g., to perform a more extensive verification at the use device.
A blockchain management device may also be integrated with a blockchain use device. In this case, the device that produces transactions may also be capable of processing such transactions. This has the advantage that blockchain management, e.g., of generating a new block is distributed over more devices.
The various devices of system 180 communicate with each other over a computer network 150 . The computer network may be an internet, an intranet, a LAN, a WLAN, etc. Computer network 150 may be the Internet. The computer network may be wholly or partly wired, and/or wholly or partly wireless. For example, the computer network may comprise Ethernet connections. For example, the computer network may comprise wireless connections, such as Wi-Fi, ZigBee, and the like. The devices comprise a connection interface which is arranged to communicate with other devices of system 180 as needed. For example, the connection interface may comprise a connector, e.g., a wired connector, e.g., an Ethernet connector, or a wireless connector, e.g., an antenna, e.g., a Wi-Fi, 4G or 5G antenna. For example, blockchain management device 100 , blockchain verification device 500 and blockchain use device 400 may comprise
communication interface
110 , 510 and 410 respectively. Computer network 150 may comprise additional elements, which are not separately shown in FIG. 1 , e.g., a router, a hub, etc. In blockchain management device 100 , the communication interface 110 may be used to receive transactions for recording in a blockchain. Transactions may be digital transactions, e.g., received in electronic form.
A blockchain management device, such as blockchain management device 100 , may comprise a block constructor 120 , a consensus prover 130 and a hash unit 140 . Blockchain management device 100 may also comprise a storage, e.g., to store the secondary blockchain. The stored secondary blockchain may be used to verify received transactions. The storage may also store the primary blockchain.
The execution of the blockchain management device 100 , but also of, blockchain verification device 500 , and blockchain use device 400 is implemented in a processor circuit, examples of which are shown herein. FIG. 1 , in particular blockchain management device 100 , FIG. 4 and FIG. 5 show possible functional units that may be functional units of the processor circuit. For example, FIGS. 1, 4 and 5 may be used as a blueprint of a possible functional organization of the processor circuit. The processor circuit is not shown separate from the units in FIGS. 1, 4 and 5 . For example, the functional units shown in FIGS. 1, 4 and 5 may be wholly or partially implemented in computer instructions that are stored at
device
100 , 400 and 500 , e.g., in an electronic memory of the device, and are executable by a microprocessor of the device. In hybrid embodiments, functional units are implemented partially in hardware, e.g., as coprocessors, e.g., crypto coprocessors, and partially in software stored and executed on the device.
Block constructor 120 may be used to construct, e.g., compute, a new block of the secondary blockchain. Over communication interface 110 , transactions are received from other elements in system 180 , e.g., from blockchain use devices
150 or 151 . Block constructor 120 collects a multiple of the received transactions, e.g., it selects them. For example, block constructor 120 may select all transactions that are received in a period. For example, block constructor 120 may prioritize certain transactions, e.g., by type, by origin, etc. Block constructor 120 may also verify the validity of the transactions. For example, in an embodiment in which transactions are signed, block constructor 120 may verify the signatures, and, e.g., discard invalid transactions. Verification and/or selection may be offloaded to a verification device.
In addition to collecting the multiple transactions, the block constructor 120 obtains other parts of the new block, e.g., a consensus proof and a reference to a previous block on the secondary blockchain. The new block is then assembled from at least the multiple transactions, the consensus proof, and a reference to a preceding block on the blockchain. For example, the reference may be to a last block, e.g., the tail block, of the current blockchain. For example, the current secondary blockchain may be stored on a storage of the blockchain management device, although this is not needed. The new block is then communicated to one or more other elements of system 180 . The new block is distributed, e.g., to at least further blockchain management device 160 .
Consensus prover 130 is arranged to generate a consensus proof over the selected transactions. For example, blockchain management device 100 may comprise an optional hash unit 140 arranged to compute a hash value s over the selected transactions. Hash unit 140 may be configured for a known cryptographic hash function. For example, a hash function from the SHA family, e.g., SHA-256.
The consensus proof may then be computed over the computed hash value or directly over the transactions. Any of the known consensus proofs may be adapted for an embodiment, for example, the consensus proof may comprise a proof of work. For example, the consensus proof may comprise a string x so that a hash function computed over string x and the hash s, e.g., h(x|s), has a particular form, e.g., is below some difficulty target. For example, the consensus proof may comprise consensus from some portion of the network, e.g., it may comprise signatures of one or more further blockchain management devices, e.g., secondary blockchain management devices. For example, consensus prover 130 may be arranged to obtain said digital signatures from the other secondary blockchain management devices over the digital network. For example, the consensus proof may be required to comprise a signature of at least 51% or more of the secondary blockchain management devices. Such signatures may be obtained over the computer network 150 . The consensus proof may also require some mix of signatures from secondary and primary blockchain management devices, e.g., 51% of the secondary blockchain management device, and at least 1, or at least 2, etc., of the primary blockchain management devices.
Once the block for the secondary blockchain is completed it may be distributed over system 180 , e.g., in a peer to peer fashion. Other blockchain management or verification devices may verify the block and include it in their blockchain. Once new blocks are added to the secondary blockchain which refer to the new block, the trust in the new block is increased, as it becomes increasingly harder to replace the new block with another block. This feature also resolves races. Even if parts of system 180 may adopt one new block while another part adopts another, in time this will be resolved, e.g., using the longest chain rule.
In blockchains the longest chain rule allows nodes, e.g., blockchain management devices to resolve races. It may happen that two blockchain management devices add a block to the blockchain independent from each other. The blockchain thus splits, becoming in essence a block tree. It may even happen that yet further blocks are added, or even further splits. The longest chain rule prescribes which of the blocks become the new blockchain: the active chain is the longest path from the genesis block to a leaf node, e.g., a block at the bottom of the block tree. This chain represents the most accumulated consensus, e.g., the most work. The consensus mechanism makes sure that the chance that two nodes disagree about blocks in the past decreases as the blocks are older. For example, when a new block arrives, and it extends the previous active chain, a blockchain management device may append it to the active chain. If it does not extend the previous active chain, it depends on whether the branch it does extend has more consensus, e.g., more work, e.g., more blocks, than the currently active chain. If not, the block is stored but the current chain is kept active. If it does have more work, a so-called reorganization is done: deactivating blocks from the old branch, and activating blocks from the new branch.
As said, once the new block is finished, e.g., when a consensus proof is available it is distributed, e.g., through communication interface 110 , e.g., initiated by block constructor 120 to other devices of blockchain system 180 . For example, the new block will be sent to other blockchain management devices, such as blockchain management device 160 . However, the new block will eventually reach all interested parties, e.g., verification devices, etc. Here the new block will become part of the secondary blockchain; that is unless it is rejected by the system for some reason, e.g., as a result of the longest chain rule.
Blockchain management device 100 further comprises a primary blockchain transaction unit 125 . Transaction unit 125 is configured to generate a transaction that comprises an identification of the new block, and in particular of the set of transactions. Transaction unit 125 distributes the transaction to at least one blockchain management device that manages a primary blockchain, e.g., to primary blockchain management device 190 . Note that the overhead of posting an identification in the primary blockchain is much smaller than, e.g., reposting the entire new block of the secondary blockchain in the new block.
There are several ways in which the identification for the transaction can be computed. For example, the transaction can comprise an identifier of the new block. For example, the new block may comprise an identifier, e.g., generated by block constructor 120 , which may also be comprised in the identification. It is preferable, if the identification is also linked to the transactions in the new block, but not the whole block. For example, in an embodiment, transaction unit 125 is configured to compute a hash, e.g., using hash unit 140 over the new block. The identification may comprise the hash. Alternatively, or additionally, the identification may comprise a hash over the transactions in the new block. An advantage of this identification is that the block is positively identified and cannot be modified in any way. In an embodiment, the identification or at least part thereof is also included in the new block itself. This is possible, for example, if the identification is built from part of the new block and/or from data in a previous block. In an embodiment, the identification is also computed over the consensus proof. For example, the identification may be a hash of set of the transactions, the consensus proof and possibly other metadata, such as an identifier of the new block, an identifier of the block management device etc. The identification may still be included in the new block, since the identification is not computed over the entire new block.
In an embodiment, the identifier comprises a first hash over all or part of the new block, and a second hash. The second hash ensures that the identifier is unique even if exactly the same transactions are processed in a new block as in a previous block. For example, the second hash may be a hash over the previous second hash, e.g., the second hash of the previous block. For example, the second hash may be a hash over the first hash and the previous second hash.
In an embodiment, the identification is computed, e.g., over a hash, over a previous block or more than one block back in the blockchain. For example, the identification may comprise a hash over the previous block, and/or the block before that. For example, there may be a number (e.g., n), say 2, or 3, or more, etc., so that the identification comprises a hash of each of the number (n) of previous blocks in the blockchain. In an embodiment, the identification comprises a Merkle tree of the new block of the secondary blockchain.
Primary blockchain management device 190 is configured to manage a primary blockchain. In an embodiment, a primary blockchain management device comprises
a communication interface arranged to receive digital transactions for recording in a primary blockchain; for example, the transactions may be received from secondary blockchain management devices. For example, at least one of the blocks may comprise an identification as explained above. Optionally, the primary blockchain management device may also receive the corresponding new block itself, e.g., so that the transaction can be verified. Typically, the new block will not be reposted on the primary blockchain device though. a processor circuit configured to
obtain a consensus proof for a set of transactions received over the communication interface, assemble a new block for inclusion in the primary blockchain, the new block comprising the set of transactions, the consensus proof, and a reference to a previous block on the primary blockchain; optional, the device may optionally verify that the block represented by a transaction is correct, e.g., satisfies the legality criteria of the secondary blockchain, e.g., the consensus proof is correct. distribute the new block over the communication interface to at least one further blockchain management device that manages the primary blockchain.
The primary blockchain management device will include the transaction in a new block of the primary blockchain. This means that a verifier of the secondary blockchain can verify the secondary blockchain in two ways. First of all, the verifier can verify the secondary blockchain in the usual way; for example, the verifier can verify that the blockchains have correct consensus proofs and that each block in the blockchain correctly refers back to its previous block, up to the genesis block. However, the verifier can also verify that the creation of the blocks was recorded in the primary blockchain. For example, the verifier can verify that the block of the secondary bock is reflected in a transaction on the primary blockchain, and that they are in the correct order, or at least approximately in the correct order, e.g., within a threshold of the correct order. The primary blockchain has an even higher assumption of immutability, and so this improves the trustworthiness of the secondary blockchain.
For example, consider two parties: Bob and Alice, who make a transaction. The transaction is sent to a secondary blockchain management device. The transaction will be included in a new block of the secondary blockchain probably together with many other transactions. Once the block is completed, e.g., the consensus proof is completed, and the new block is distributed, e.g., at least among other secondary blockchain management devices. The transaction that proves that the new block was completed is
CLAIMS
Claims ( 18 )
The invention claimed is:
1. A blockchain management device comprising:
a communication interface arranged to receive digital transactions for recording in a secondary blockchain,
a processor circuit configured to:
broadcast a time before which a new block will be created,
obtain a consensus proof for a set of transactions received over the communication interface,
assemble a new block for inclusion in the secondary blockchain, the new block comprising the set of transactions, the consensus proof, and a reference to a previous block on the secondary blockchain,
distribute the new block before the broadcasted time over the communication interface to at least one further blockchain management device that manages the secondary blockchain,
distribute a transaction at the time to at least one blockchain management device that manages a primary blockchain, said transaction comprising an identification of the set of transactions in the new block.
2. A blockchain management device as in claim 1 , wherein the identification comprises
a hash over at least the set of transactions, and/or
a hash over an identification of a previous block in the secondary blockchain.
3. A blockchain management device as in claim 1 , wherein the new block comprises the identification.
4. A blockchain management device as in claim 1 , wherein the identification comprises a hash over the new block.
5. A blockchain management device as in claim 1 , wherein the distribution of new blocks is synchronized to the distribution of new blocks in the primary blockchain.
6. A blockchain management device as in claim 5 , wherein an expected time to obtain a consensus proof for the primary blockchain is larger than the expected time to obtain a consensus proof for the secondary blockchain.
7. A blockchain management device as in claim 1 , wherein the processor circuit is configured to, if no valid transaction were received in time for the new block, assemble a default block without valid transactions.
8. A blockchain management device as in claim 1 , wherein an initial block in the secondary blockchain is a genesis block, a transaction being distributed to the at least one blockchain management device that manages the primary blockchain, said transaction comprising an identification of the genesis block.
9. A blockchain management device as in claim 1 , wherein the transaction comprises a signature of the blockchain management device.
10. A blockchain management method, the method comprising:
receiving digital transactions for recording in a secondary blockchain,
broadcasting a time before which a new block will be created,
obtaining a consensus proof for a set of received transactions,
assembling a new block for inclusion in the secondary blockchain, the new block comprising the set of transactions, the consensus proof, and a reference to a previous block on the secondary blockchain,
distributing the new block before the broadcasted time over the communication interface to a blockchain management device that manages the secondary blockchain,
distributing a transaction at the time to at least one blockchain management device that manages a primary blockchain, said transaction comprising an identification of the set of transactions in the new block.
11. A computer readable medium comprising non-transitory data representing instructions to cause a processor system to perform the method according to claim 10 .
12. A blockchain management method as in claim 10 , wherein the identification comprises:
a hash over at least the set of transactions, and/or
a hash over an identification of a previous block in the secondary blockchain.
13. A blockchain management method as in claim 10 , wherein the new block comprises the identification.
14. A blockchain management method as in claim 10 , wherein the identification comprises a hash over the new block.
15. A blockchain management method as in claim 10 , further comprising, if no valid transaction were received in time for the new block, assembling a default block without valid transactions.
16. A blockchain management method as in claim 10 , wherein an initial block in the secondary blockchain is a genesis block, the method further comprising distributing a transaction to the at least one blockchain management device that manages the primary blockchain, said transaction comprising an identification of the genesis block.
17. A blockchain management device comprising:
a communication interface arranged to receive digital transactions for recording in a secondary blockchain,
a processor circuit configured to:
obtain a consensus proof for a set of transactions received over the communication interface,
assemble a new block for inclusion in the secondary blockchain, the new block comprising the set of transactions, the consensus proof, and a reference to a previous block on the secondary blockchain,
distribute the new block over the communication interface to at least one further blockchain management device that manages the secondary blockchain,
distribute a transaction to at least one blockchain management device that manages a primary blockchain, said transaction comprising an identification of the set of transactions in the new block;
wherein the distribution of new blocks is synchronized to the distribution of new blocks in the primary blockchain; and
wherein an expected time to obtain a consensus proof for the primary blockchain is larger than the expected time to obtain a consensus proof for the secondary blockchain.
18. A blockchain management method, the method comprising:
receiving digital transactions for recording in a secondary blockchain,
obtaining a consensus proof for a set of received transactions,
assembling a new block for inclusion in the secondary blockchain, the new block comprising the set of transactions, the consensus proof, and a reference to a previous block on the secondary blockchain,
distributing the new block over the communication interface to a blockchain management device that manages the secondary blockchain,
distributing a transaction to at least one blockchain management device that manages a primary blockchain, said transaction comprising an identification of the set of transactions in the new block;
wherein the distribution of new blocks is synchronized to the distribution of new blocks in the primary blockchain; and
wherein an expected time to obtain a consensus proof for the primary blockchain is larger than the expected time to obtain a consensus proof for the secondary blockchain.
US16/756,357
2017-10-20
2018-10-19
Primary and secondary blockchain device
Active
2039-01-23
US11316659B2
( en )
Applications Claiming Priority (4)
Application Number
Priority Date
Filing Date
Title
EP17197577
2017-10-20
EP17197577
2017-10-20
EP17197577.4
2017-10-20
PCT/EP2018/078753
WO2019077126A1
( en )
2017-10-20
2018-10-19
Primary and secondary blockchain device
Publications (2)
Publication Number
Publication Date
US20210203476A1
US20210203476A1 ( en )
2021-07-01
US11316659B2
true
US11316659B2 ( en )
2022-04-26
Family
ID=60162007
Family Applications (1)
Application Number
Title
Priority Date
Filing Date
US16/756,357
Active
2039-01-23
US11316659B2
( en )
2017-10-20
2018-10-19
Primary and secondary blockchain device
Country Status (3)
Country
Link
US
( 1 )
US11316659B2
( en )
EP
( 1 )
EP3698518B1
( en )
WO
( 1 )
WO2019077126A1
( en )
Cited By (2)
* Cited by examiner, â Cited by third party
Publication number
Priority date
Publication date
Assignee
Title
US20220407726A1
( en )
*
2019-10-30
2022-12-22
Jingdong Technology Information Technology Co., Ltd.
Consensus method for blockchain, consensus node, electronic device, and storage medium
US20240097879A1
( en )
*
2021-01-28
2024-03-21
Emtruth, Inc.
Blockchain-based data management of distributed binary objects
Families Citing this family (17)
* Cited by examiner, â Cited by third party
Publication number
Priority date
Publication date
Assignee
Title
US11455643B2
( en )
2017-10-09
2022-09-27
Koninklijke Kpn N.V.
Blockchain with transaction cancellation
EP3698518B1
( en )
2017-10-20
2024-02-14
Koninklijke KPN N.V.
Primary and secondary blockchain device
US11139979B2
( en )
2017-12-18
2021-10-05
Koninklijke Kpn N.V.
Primary and secondary blockchain device
CN109359971B
( en )
2018-08-06
2020-05-05
é¿éå·´å·´éå¢æ§è¡æéå ¬å¸
Blockchain transaction method and device, electronic device
US11216573B1
( en )
2018-08-06
2022-01-04
United Services Automobile Association (Usaa)
Privacy preservation in private consensus networks
US11164180B1
( en )
*
2018-08-06
2021-11-02
United Services Automobile Association (Usaa)
Privacy preservation in private consensus networks
CN112651740B
( en )
*
2018-08-30
2024-10-29
èèé¾ææ¯æéå ¬å¸
Blockchain transaction method and device, and electronic device
ES2812282T3
( en )
*
2018-08-31
2021-03-16
Siemens Ag
Block formation equipment and procedure, node equipment and block confirmation procedure
EP3568826B1
( en )
2018-12-29
2021-09-29
Advanced New Technologies Co., Ltd.
System and method for information protection
GB2582978B
( en )
2019-04-12
2022-05-04
Nchain Holdings Ltd
Methods and devices for propagating blocks in a blockchain network
PH12021553118A1
( en )
*
2019-06-13
2022-08-01
Gutierrez Sheris Luis Eduardo
System and method using a fitness-gradient blockchain consensus and providing advanced distributed ledger capabilities via specialized data records
US11080412B1
( en )
2020-08-20
2021-08-03
Spideroak, Inc.
Efficiently computing validity of a block chain
GB2599735A
( en )
*
2020-10-12
2022-04-13
Cambridge Cryptographic Ltd
Blockchain
KR102514536B1
( en )
*
2020-11-06
2023-03-27
íêµì ìíµì ì°êµ¬ì
Method and apparatus for block propagation in blockchain platform
GB2601539A
( en )
2020-12-04
2022-06-08
Nchain Holdings Ltd
Methods and systems for streaming block templates with cross-references
CN115225982A
( en )
*
2022-05-12
2022-10-21
å½ç½æ²³åççµåæéå ¬å¸è¥éæå¡ä¸å¿
Data transmission method and device for distributed energy trading system
WO2024206255A1
( en )
*
2023-03-24
2024-10-03
TRETE Inc.
Metadata process, with static and evolving attributes, introduced into tokenization standards ledgers
Citations (24)
* Cited by examiner, â Cited by third party
Publication number
Priority date
Publication date
Assignee
Title
US20160028552A1
( en )
2014-07-25
2016-01-28
Blockchain Technologies Corporation
System and method for creating a multi-branched blockchain with configurable protocol rules
CN105488675A
( en )
2015-11-25
2016-04-13
å¸æ¯ï¼å京ï¼ç½ç»ææ¯æéå ¬å¸
Distributed shared general ledger construction method of block chain
US20160330034A1
( en )
2015-05-07
2016-11-10
Blockstream Corporation
Transferring ledger assets between blockchains via pegged sidechains
US20170005804A1
( en )
2015-07-02
2017-01-05
Nasdaq, Inc.
Systems and methods of secure provenance for distributed transaction databases
US20170031676A1
( en )
2015-07-27
2017-02-02
Deja Vu Security, Llc
Blockchain computer data distribution
US20170046698A1
( en )
*
2015-08-13
2017-02-16
The Toronto-Dominion Bank
Systems and methods for establishing and enforcing transaction-based restrictions using hybrid public-private blockchain ledgers
US20170116693A1
( en )
*
2015-10-27
2017-04-27
Verimatrix, Inc.
Systems and Methods for Decentralizing Commerce and Rights Management for Digital Assets Using a Blockchain Rights Ledger
US20170163733A1
( en )
2015-12-02
2017-06-08
Olea Networks, Inc.
System and method for data management structure using auditable delta records in a distributed environment
US20170230189A1
( en )
2016-02-04
2017-08-10
Nasdaq Technology Ab
Systems and methods for storing and sharing transactional data using a distributed computing systems
US9774578B1
( en )
2016-05-23
2017-09-26
Accenture Global Solutions Limited
Distributed key secret for rewritable blockchain
US20170295157A1
( en )
2016-04-06
2017-10-12
Avaya Inc.
Smartphone fraud-proof authorization and authentication for secure interactions
US20170323294A1
( en )
2016-05-06
2017-11-09
Mastercard International Incorporated
Method and system for instantaneous payment using recorded guarantees
US20170331896A1
( en )
2016-05-13
2017-11-16
De La Rue International Limited
Methods and systems for processing assets
US20170344988A1
( en )
2016-05-24
2017-11-30
Ubs Ag
System and method for facilitating blockchain-based validation
US20180089436A1
( en )
*
2016-09-29
2018-03-29
Intel Corporation
Methods And Apparatus To Facilitate Blockchain-based Boot Tracking
US20190026821A1
( en )
2017-07-21
2019-01-24
International Business Machines Corporation
Intermediate blockchain system for managing transactions
US20190058719A1
( en )
2017-08-21
2019-02-21
Cognizant Technology Solutions India Pvt. Ltd.
System and a method for detecting anomalous activities in a blockchain network
WO2019072670A1
( en )
2017-10-09
2019-04-18
Koninklijke Kpn N.V.
Blockchain with transaction cancellation
WO2019077126A1
( en )
2017-10-20
2019-04-25
Koninklijke Kpn N.V.
Primary and secondary blockchain device
US20190130387A1
( en )
2017-10-26
2019-05-02
Mastercard International Incorporated
Method and system for prevention of fraudulent gift cards via blockchain
US10305833B1
( en )
2017-07-23
2019-05-28
Turing Technology, Inc.
Blockchain based email procedures
EP3499789A1
( en )
2017-12-18
2019-06-19
Koninklijke KPN N.V.
Primary and secondary blockchain device
US10554649B1
( en )
2017-05-22
2020-02-04
State Farm Mutual Automobile Insurance Company
Systems and methods for blockchain validation of user identity and authority
US20200389294A1
( en )
2017-10-20
2020-12-10
Hewlett Packard Enterprise Development Lp
Transmitting or receiving blockchain information
2018
2018-10-19
EP
EP18786794.0A
patent/EP3698518B1/en
active
Active
2018-10-19
US
US16/756,357
patent/US11316659B2/en
active
Active
2018-10-19
WO
PCT/EP2018/078753
patent/WO2019077126A1/en
not_active
Ceased
Patent Citations (27)
* Cited by examiner, â Cited by third party
Publication number
Priority date
Publication date
Assignee
Title
US20160028552A1
( en )
2014-07-25
2016-01-28
Blockchain Technologies Corporation
System and method for creating a multi-branched blockchain with configurable protocol rules
US20160330034A1
( en )
2015-05-07
2016-11-10
Blockstream Corporation
Transferring ledger assets between blockchains via pegged sidechains
US20170005804A1
( en )
2015-07-02
2017-01-05
Nasdaq, Inc.
Systems and methods of secure provenance for distributed transaction databases
US20170031676A1
( en )
2015-07-27
2017-02-02
Deja Vu Security, Llc
Blockchain computer data distribution
US20170046698A1
( en )
*
2015-08-13
2017-02-16
The Toronto-Dominion Bank
Systems and methods for establishing and enforcing transaction-based restrictions using hybrid public-private blockchain ledgers
US20170116693A1
( en )
*
2015-10-27
2017-04-27
Verimatrix, Inc.
Systems and Methods for Decentralizing Commerce and Rights Management for Digital Assets Using a Blockchain Rights Ledger
CN105488675A
( en )
2015-11-25
2016-04-13
å¸æ¯ï¼å京ï¼ç½ç»ææ¯æéå ¬å¸
Distributed shared general ledger construction method of block chain
US20170163733A1
( en )
2015-12-02
2017-06-08
Olea Networks, Inc.
System and method for data management structure using auditable delta records in a distributed environment
US20170230189A1
( en )
2016-02-04
2017-08-10
Nasdaq Technology Ab
Systems and methods for storing and sharing transactional data using a distributed computing systems
US20170295157A1
( en )
2016-04-06
2017-10-12
Avaya Inc.
Smartphone fraud-proof authorization and authentication for secure interactions
US20170323294A1
( en )
2016-05-06
2017-11-09
Mastercard International Incorporated
Method and system for instantaneous payment using recorded guarantees
US20170331896A1
( en )
2016-05-13
2017-11-16
De La Rue International Limited
Methods and systems for processing assets
US9774578B1
( en )
2016-05-23
2017-09-26
Accenture Global Solutions Limited
Distributed key secret for rewritable blockchain
US20170344988A1
( en )
2016-05-24
2017-11-30
Ubs Ag
System and method for facilitating blockchain-based validation
US20180089436A1
( en )
*
2016-09-29
2018-03-29
Intel Corporation
Methods And Apparatus To Facilitate Blockchain-based Boot Tracking
US10554649B1
( en )
2017-05-22
2020-02-04
State Farm Mutual Automobile Insurance Company
Systems and methods for blockchain validation of user identity and authority
US20190026821A1
( en )
2017-07-21
2019-01-24
International Business Machines Corporation
Intermediate blockchain system for managing transactions
US10305833B1
( en )
2017-07-23
2019-05-28
Turing Technology, Inc.
Blockchain based email procedures
US20190058719A1
( en )
2017-08-21
2019-02-21
Cognizant Technology Solutions India Pvt. Ltd.
System and a method for detecting anomalous activities in a blockchain network
WO2019072670A1
( en )
2017-10-09
2019-04-18
Koninklijke Kpn N.V.
Blockchain with transaction cancellation
US20200258085A1
( en )
2017-10-09
2020-08-13
Koninklijke Kpn N.V.
Blockchain With Transaction Cancellation
WO2019077126A1
( en )
2017-10-20
2019-04-25
Koninklijke Kpn N.V.
Primary and secondary blockchain device
US20200389294A1
( en )
2017-10-20
2020-12-10
Hewlett Packard Enterprise Development Lp
Transmitting or receiving blockchain information
US20190130387A1
( en )
2017-10-26
2019-05-02
Mastercard International Incorporated
Method and system for prevention of fraudulent gift cards via blockchain
US20190190719A1
( en )
2017-12-18
2019-06-20
Koninklijke Kpn N.V.
Primary and secondary blockchain device
EP3499789A1
( en )
2017-12-18
2019-06-19
Koninklijke KPN N.V.
Primary and secondary blockchain device
US11139979B2
( en )
2017-12-18
2021-10-05
Koninklijke Kpn N.V.
Primary and secondary blockchain device
Non-Patent Citations (6)
* Cited by examiner, â Cited by third party
Title
Adam Back, et al., " Enabling Blockchain Innovations with Pegged Sidechains, " (Oct. 22, 2014).
Ateniese, G et al., " Redactable Blockchain-or-Rewriting History in Bitcoin and Friends, " 2017 IEEE European Symposium on Security and Privacy, IEEE, pp. 111-126 (Apr. 26, 2017).
Extended European Search Report, EP Application NO. 17197577.4 dated Apr. 6, 2018.
International Search Report and Written Opinion for Int'l Application No. PCT/EP2018/078753, titled: Primary and Secondary Blockchain Device, dated Dec. 11, 2018.
Solidity Documentation Release 0.4.19, Ethereum (Dec. 2017).
Tschorsch. F., et al., " Bitcoin and Beyond: A Technical Survey on Decentralized Digital Currencies, " International Association for Cryptologic Research, vol. 20150517:090557, May 15, 2015.
Cited By (4)
* Cited by examiner, â Cited by third party
Publication number
Priority date
Publication date
Assignee
Title
US20220407726A1
( en )
*
2019-10-30
2022-12-22
Jingdong Technology Information Technology Co., Ltd.
Consensus method for blockchain, consensus node, electronic device, and storage medium
US12284295B2
( en )
*
2019-10-30
2025-04-22
Jingdong Technology Information Technology Co., Ltd.
Consensus method for blockchain, consensus node, electronic device, and storage medium
US20240097879A1
( en )
*
2021-01-28
2024-03-21
Emtruth, Inc.
Blockchain-based data management of distributed binary objects
US12261934B2
( en )
*
2021-01-28
2025-03-25
Emtruth, Inc.
Blockchain-based data management of distributed binary objects
Also Published As
Publication number
Publication date
WO2019077126A1
( en )
2019-04-25
EP3698518A1
( en )
2020-08-26
US20210203476A1
( en )
2021-07-01
EP3698518B1
( en )
2024-02-14
Similar Documents
Publication
Publication Date
Title
EP3698518B1
( en )
2024-02-14
Primary and secondary blockchain device
US11139979B2
( en )
2021-10-05
Primary and secondary blockchain device
CN115210741B
( en )
2023-06-16
partially ordered blockchain
US12505254B2
( en )
2025-12-23
Data processing method and apparatus based on blockchain network, and computer device
US11455643B2
( en )
2022-09-27
Blockchain with transaction cancellation
US8719576B2
( en )
2014-05-06
Document verification with distributed calendar infrastructure
US20250328903A1
( en )
2025-10-23
Blockchain-based data processing method and apparatus, device, and medium
CN114240433A
( en )
2022-03-25
Data processing method and system based on block chain
JP2023515368A
( en )
2023-04-13
A proof service used with blockchain networks
Daraghmi et al.
2021
A BlockchainâBased Editorial Management System
JP7772791B2
( en )
2025-11-18
Merkle Proof Entity
US20230342437A1
( en )
2023-10-26
Blockchain-based system and method for publishing an operating system
CN110730081B
( en )
2020-04-14
Certificate revocation method, related equipment and medium based on blockchain network
Kaligotla et al.
2018
A generalized agent based framework for modeling a blockchain system
CN116614519A
( en )
2023-08-18
Video and related information lightweight trusted uplink method based on optimization consensus algorithm
CN117333175A
( en )
2024-01-02
Blockchain system, smart contract synchronization method, computer equipment and storage media
CN117251889B
( en )
2024-03-01
Block chain consensus method, related device and medium
CN118802433A
( en )
2024-10-18
Communication system for the Internet of Things environment and election method based on consensus group mechanism
US11741267B2
( en )
2023-08-29
Consensus method for a distributed database
CN116841991B
( en )
2025-10-03
On-chain data management method, device, storage medium, and program product
CN120525530A
( en )
2025-08-22
A data processing method and related equipment based on blockchain
CN122001900A
( en )
2026-05-08
Data synchronous updating method and device, storage medium and electronic equipment
CN117155953A
( en )
2023-12-01
Data processing method, device, computer equipment and readable storage medium
CN119172395A
( en )
2024-12-20
Data processing method, device, product, equipment and medium for blockchain network
HK40088245A
( en )
2023-09-29
Data processing method and related product
Legal Events
Date
Code
Title
Description
2020-04-15
FEPP
Fee payment procedure
Free format text : ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY
2020-06-24
AS
Assignment
Owner name : KONINKLIJKE KPN N.V., NETHERLANDS
Free format text : ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:VAN DE RUIT, DOUWE;MOUSTAKAS, NIKOS;SIGNING DATES FROM 20200610 TO 20200615;REEL/FRAME:053029/0814
2021-08-08
STPP
Information on status: patent application and granting procedure in general
Free format text : DOCKETED NEW CASE - READY FOR EXAMINATION
2021-10-18
STPP
Information on status: patent application and granting procedure in general
Free format text : NON FINAL ACTION MAILED
2022-02-23
STPP
Information on status: patent application and granting procedure in general
Free format text : RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER
2022-03-10
STPP
Information on status: patent application and granting procedure in general
Free format text : NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS
2022-03-23
STPP
Information on status: patent application and granting procedure in general
Free format text : PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED
2022-04-06
STCF
Information on status: patent grant
Free format text : PATENTED CASE
2025-10-16
MAFP
Maintenance fee payment
Free format text : PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY
Year of fee payment : 4