HEAT Ledger is a self-appointed “Gen 3.0” cryptocurrency platform focusing on resolving the two
most pressing pitfalls of the existing 2.0 and 1.0 cryptocurrency server software solutions; Low
transaction rate throughput and the burden of hosting large blockchain files on any single p2p node.
Like the HEAT software itself, this document is work in progress that will be amended and expanded
as the project evolves. V1.0 is designed to deliver a reasonably complete, quasi-technical treatise on
the basic elements of the initial HEAT system available at the time of genesis block in September
HEAT is in part inspired by open source NXT as it uses the time proven Proof-of-Stake consensus
algorithm but tuned up for 25-second blocks. Feature wise, many parts of the HEAT service offering
and middleware solutions are based on those originally developed for FIMK. On other parts the
HEAT core is fully rewritten in Java, making it optimally suited for custom financial business
applications by providing microsecond latency (up to 15-30 million writes per second), vastly
increased vertical scalability, and superior failover resiliency when compared to legacy datasystems.
HEAT general technical highlights:
● Written in enterprise friendly Java
● Based on secure, MIT licensed NXT for cryptography and p2p consensus code
● Architected with re-use for private chains in mind
● Optimized for speed and low memory usage
● Massively scalable through the use of not one single blockchain, but a chain of
blockchains (only the last one in the chain is required on each node)
● On application level contains all the latest 2.0 cryptocurrency features and more,
including custom asset-to-asset trading, distributed apps and end-to-end encrypted
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. Another major core
change consists of changes to the mechanism the network layer works.
For storing the consensus blockchain, HEAT does not use single blockchain file ever increasing in
size. Instead HEAT makes use of serialized blockchain files of a limited size, accompanied by small
balance files. When the latest blockchain file reaches threshold size (of a few GB, specified at genesis
block) the protocol will automatically switch to a new blocks file cryptographically linked to the
previous blocks & balance files. The details to achieve this are in principle rather similar to how
blocks are chained to each other.