Nested Blockchain System

1 . A distributed database management system, the system comprising:

a plurality of distributed nodes in a network;

one or more of the plurality of nodes configured to:

generate a master cryptographically verifiable distributed ledger represented by a sequence of blocks, each block containing one or more transactions records and each subsequent block containing a hash value associated with the previous block;

generate a first block in the master cryptographically verifiable ledger for a first event in response to receipt of the first event from a third party system;

execute code included in an associated block of the master cryptographically verifiable ledger to verify that the first event corresponds with a first set of one or more conditions;

in response to verification of 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;

generate a second block in the first sub cryptographically verifiable ledger for a second event in response to receipt of a second event from the third party system;

execute code included in the first genesis block to verify that the second event corresponds with a second set of one or more conditions; and

in response to the verification of the second event, purge the first sub cryptographically verifiable ledger.

2 . The system of claim 1 , wherein the one or more of the plurality of nodes is programmed to receive a third event.

3 . The system of claim 2 , wherein the one or more of the plurality of nodes is programmed to:

generate a third block in the master cryptographically verifiable ledger containing transaction records of the third event;

execute code included in the third block to verify the third event corresponds with a third set of one or more conditions;

in response to verification of the third event, 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, associated with the third event.

4 . The system of claim 3 , wherein the one or more of the plurality of nodes is programmed to receive a fourth event.

5 . The system of claim 4 , wherein the one or more of the plurality of nodes is programmed to generate 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 one or more of the plurality of nodes 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 the request of a delivery of a physical object, the second event is associated with the completion of the delivery of the physical object.

8 . The system of claim 1 , wherein the one or more transaction records include one or more of a quantity of the at least one physical object, a name of the at least one physical object, a type of the at least one physical object and a size of the at least one physical object.

9 . The system of claim 1 , wherein 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:

generating, via one or more of a plurality of distributed nodes in a network, a master cryptographically verifiable distributed ledger represented by a sequence of blocks, each block containing one or more transactions records and each subsequent block containing a hash value associated with the previous block;

generating, via the one or more of the plurality of nodes, a first block in the master cryptographically verifiable ledger for a first event in response to receipt of the first event from a third party system;

executing, via the one or more of the plurality of nodes, code included in an associated block of the master cryptographically verifiable ledger to verify that the first event corresponds with a first set of one or more conditions;

in response to verification of the first event, spawning, via the one or more 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;

generating, via the one or more of the plurality of nodes, a second block in the first sub cryptographically verifiable ledger for a second event in response to receipt of a second event from the third party system;

executing, via the one or more of the plurality of nodes, code included in the first genesis block to verify that the second event corresponds with a second set of one or more conditions; and

in response to the verification of the second event, purging, via the one or more of the plurality of nodes, the first sub cryptographically verifiable ledger.

12 . The method of claim 11 , further comprising receiving, via the one or more of the plurality of nodes, a third event.

13 . The method of claim 12 , further comprising:

generating, via the one or more of the plurality of nodes, a third block in the master cryptographically verifiable ledger containing transaction records of the third event;

executing, via the one or more of the plurality of nodes, code included in the third block to verify the third event corresponds with a third set of one or more conditions;

in response to verification of the third event, spawning, via the one or more 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, associated with the third event.

14 . The method of claim 13 , further comprising receiving, via the one or more of the plurality of nodes, a fourth event.

15 . The method of claim 14 , further comprising generating, via the one or more 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 one or more 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 the request of a delivery of a physical object, the second event is associated with the completion of the delivery of the physical object.

18 . The method of claim 11 , wherein the one or more transaction records include one or more of a quantity of the at least one physical object, a name of the at least one physical object, a type of the at least one physical object and a size of the at least one physical object.

19 . The method of claim 11 , wherein the third party system is one or more of a: mobile device, a terminal or a computing device.

20 . The method of claim 9 , wherein the terminal is disposed in a facility.