Here is something I just found in the whitepaper:
"HEAT as a cryptocurrency employs radically new approaches to the way cryptocurrencies are built, the most notable of these being complete removal of the embedded database" (yes it is in bold in the whitepaper)
And then later in the same whitepaper:
"The replication layer is an event based optional and configurable event sink mechanism where you run HEAT together with a MySQL [or another brand of] database server. This server can be either on the same machine or somewhere else on the local network."
This is all so great. They have made so many contrary statements that they can basically say anything and find a reference to that somewhere.
"HEAT as a cryptocurrency employs radically new approaches to the way cryptocurrencies are built, the most notable of these being complete removal of the embedded database" (yes it is in bold in the whitepaper)
And then later in the same whitepaper:
"The replication layer is an event based optional and configurable event sink mechanism where you run HEAT together with a MySQL [or another brand of] database server. This server can be either on the same machine or somewhere else on the local network."
This is all so great. They have made so many contrary statements that they can basically say anything and find a reference to that somewhere.
These statements are not at all contradictory. You understand some words, but you lack comprehension.
What is described here is two separate pieces:
1) The P2P server, which remains barebones and optimized for the singular task of running the blockchain protocol. This includes memory-mapped data to allow very quick and lightweight access.
2) An optional replication layer. This layer will allow service providers to offer scaled database solutions to serve as many lightweight clients as their infrastructure allows.
Why cram all of this into a single piece of software? This is a smart approach.
Hooah!
+1000
