Nested blockchain system
Described in detail herein is a nested blockchain system. The nested blockchain system can include distributed nodes in a network. A node is configured to generate a master cryptographically verifiable distributed ledger represented by a sequence of blocks. The node spawns a first sub cryptographically verifiable ledger represented by a first genesis block containing a hash value referencing the first block generated in the master cryptographically verifiable ledger, in response to a first event. The node purges the first sub cryptographically verifiable ledger, in response to a second event.
1 . A distributed database management system, the system comprising:
a node of a plurality of distributed nodes in a network, the node configured to:
receive a master cryptographically verifiable distributed ledger that will be represented by a sequence of blocks, each block to contain one or more transactions records and each subsequent block to contain a hash value associated with the previous block;
receive a first block in the master cryptographically verifiable ledger for a first event;
in response to the first event, spawn a first sub cryptographically verifiable ledger represented by a first genesis block containing a hash value referencing the first block generated in the master cryptographically verifiable ledger;
receive a second block in the first sub cryptographically verifiable ledger for a second event; and
in response to the second event, purge the first sub cryptographically verifiable ledger.
2 . The system of claim 1 , wherein the node is programmed to receive a third event.
3 . The system of claim 2 , wherein the node is programmed to:
receive a third block in the master cryptographically verifiable ledger containing transaction records of the third event; and
spawn a second sub cryptographically verifiable ledger represented by a second genesis block containing a hash value associated with the third block generated in the master cryptographically verifiable ledger and associated with the third event.
4 . The system of claim 3 , wherein the node is programmed to receive a fourth event.
5 . The system of claim 4 , wherein the node is programmed to receive a fourth block in the second sub cryptographically verifiable ledger containing transaction records associated with the fourth event.
6 . The system of claim 5 , wherein the node is programmed to purge the second sub cryptographically verifiable ledger after a specified amount of time after receiving the fourth event.
7 . The system of claim 1 , wherein the first event is associated with a request of a delivery of a physical object and the second event is associated with a completion of the delivery of the physical object.
8 . The system of claim 7 , wherein the one or more transaction records include one or more of a quantity of the physical object, a name of the physical object, a type of the physical object and a size of the physical object.
9 . The system of claim 1 , wherein:
the first block is generated for the first event in response to receipt of the first event at a third party system;
the second block is generated for the second event in response to receipt of the second event at the third party system; and
the third party system is one or more of a mobile device, a terminal, or a computing device.
10 . The system of claim 9 , wherein the terminal is disposed in a facility.
11 . A distributed database management method, the method comprising:
receiving, at a node of a plurality of distributed nodes in a network, a master cryptographically verifiable distributed ledger that will be represented by a sequence of blocks, each block to contain one or more transactions records and each subsequent block to contain a hash value associated with the previous block;
receiving, at the node of the plurality of nodes, a first block in the master cryptographically verifiable ledger for a first event;
in response to the first event, spawn, via the node of the plurality of nodes, a first sub cryptographically verifiable ledger represented by a first genesis block containing a hash value referencing the first block generated in the master cryptographically verifiable ledger;
receiving, at the node of the plurality of nodes, a second block in the first sub cryptographically verifiable ledger for a second event; and
in response to the second event, purging, via the node of the plurality of nodes, the first sub cryptographically verifiable ledger.
12 . The method of claim 11 , further comprising receiving, via the node of the plurality of nodes, a third event.
13 . The method of claim 12 , further comprising:
receiving, via the node of the plurality of nodes, a third block in the master cryptographically verifiable ledger containing transaction records of the third event; and
spawning, via the node of the plurality of nodes, a second sub cryptographically verifiable ledger represented by a second genesis block containing a hash value associated with the third block generated in the master cryptographically verifiable ledger and associated with the third event.
14 . The method of claim 13 , further comprising receiving, via the node of the plurality of nodes, a fourth event.
15 . The method of claim 14 , further comprising receiving, via the node of the plurality of nodes, a fourth block in the second sub cryptographically verifiable ledger containing transaction records associated with the fourth event.
16 . The method of claim 15 , purging, via the node of the plurality of nodes, the second sub cryptographically verifiable ledger after a specified amount of time after receiving the fourth event.
17 . The method of claim 11 , wherein the first event is associated with a request of a delivery of a physical object and the second event is associated with a completion of the delivery of the physical object.
18 . The method of claim 17 , wherein the one or more transaction records include one or more of a quantity of the physical object, a name of the physical object, a type of the physical object and a size of the physical object.
19 . The method of claim 11 , wherein:
the first block is generated for the first event in response to receipt of the first event at a third party system;
the second block is generated for the second event in response to receipt of the second event at the third party system; and
the third party system is one or more of a mobile device, a terminal, or a computing device.
20 . The method of claim 19 , wherein the terminal is disposed in a facility.