Distributed hash table based blockchain architecture for resource constrained environments
A blockchain architecture operating over a skip graph-based P2P overlay to improve a communication and storage efficiency, a convergence to centralization, and consistency problems of existing blockchain solutions is provided. The blockchain architecture provides addressable peers, blocks, and transactions within a network; making the addressable peers, the blocks and transactions efficiently accessible in an on-demand manner by peers using a skip graph lookup operation where no peer is required to store an entire blockchain, and stores a replicated subset of the blocks and transactions and answers queries of other peer on the blocks and transactions. The blockchain architecture discloses a fair blockchain with a uniform chance for participating peers to be involved in a consensus protocol regardless of an influence of the participating peers in a system with an improved consistency governing a deterministic fork-resolving policy.
1. An append-only distributed database system for blockchain transactions, cryptocurrency and internet-of-things, comprising at least one peer generating blocks of a blockchain and transactions, wherein
the append-only distributed database system further comprises a fair consensus layer with a proof-of-validation scheme using a uniform involvement probability for each participating peer; and
the append-only distributed database system further comprises a bandwidth efficient network layer with a distributed hash table based structured peer-to-peer topology,
wherein the distributed hash table based structured peer-to-peer topology is a skip graph, and
wherein the skip graph is configured to represent the blocks of the blockchain as nodes of the skip graph.
2. The append-only distributed database system according to claim 1 , further comprising a view layer with a randomized bootstrapping.
3. The append-only distributed database system according to claim 2 , wherein each participating peer is configured to keep a subset of a portion of the blocks and transactions.
4. The append-only distributed database system according to claim 2 , wherein an architecture is configured to have a fork-free ledger structure.
5. The append-only distributed database system according to claim 1 , further comprising a storage layer with a randomized replication.
6. The append-only distributed database system according to claim 5 , wherein each participating peer is configured to keep a subset of a portion of the blocks and transactions.
7. The append-only distributed database system according to claim 5 , wherein an architecture is configured to have a fork-free ledger structure.
8. The append-only distributed database system according to claim 1 , wherein each participating peer is configured to keep a subset of a portion of the blocks and transactions.
9. The append-only distributed database system according to claim 8 , wherein the portion of the blocks and transactions are chosen uniformly at random.
10. The append-only distributed database system according to claim 9 , wherein at least one copy of each of the blocks and transactions are configured to be accessible at any time.
11. The append-only distributed database system according to claim 8 , wherein at least one copy of each of the blocks and transactions are configured to be accessible at any time.
12. The append-only distributed database system according to claim 8 , wherein an architecture is configured to have a fork-free ledger structure.
13. The append-only distributed database system according to claim 1 , wherein an architecture is configured to have a fork-free ledger structure.
14. The append-only distributed database system according to claim 1 , wherein the nodes of the skip graph representing the blocks of the blockchain are different from any nodes of the skip graph that represent peers.