@dmdeklerk dmdeklerk released this Sep 14, 2018

Assets 5

HEAT Wallet 2.7.0

This is the full desktop wallet version included is HEAT server 2.5.2

These are optional but recommended updates.

After introducing native Ethereum support to HEAT wallet allowing you to use your HEAT master key as a parent key for your Ethereum addresses, we now present native Bitcoin support to HEAT wallet. Supported are Bitcoin private keys as well as BIP44 compatible seeds.

To assist users downloading and setting up your own copy of HEAT wallet in order to store and handle your HEAT, Bitcoin or Ethereum we introduce this first part of Getting Started With HEAT Wallet, please check it out.

In addition to Bitcoin support, the following updates were made to the wallet:

  • Improved installer and settings handling. (Un)installing HEAT wallet will no longer delete your blockchain.
    -Improved mouseover features for charting in the Asset Exchange.
  • Improvements to the build system giving us much smaller compiled javascripts which helps render the pages faster when you visit the wallet online at heatwallet.com
  • Improvements to block explorer search when searching for Accounts, Blocks, Transactions.
    QR codes are now used to display Bitcoin deposit addresses in the Asset Exchange.
  • API failover. User interface automatically switches API servers in case one is performing badly.
  • External dependencies and Chrome app renderer upgraded to latest versions.
  • Legacy NXT API protocol support disabled for default desktop, see heat.legacy.enableAPIServer in the config files to enable this if you rely on that behavior.

Server updates:

The HEAT 2.5.2 Server is an optional update, it mostly aggregates completed improvements and a number of bug fixes.

An improvement deserving special mention - we’ve added a new dialect to the peer 2 peer communication protocol (how servers talk amongst each other). Only new servers using the 2.5.2 version are capable of using this more advanced protocol. When your server talks to older servers the old dialect will be used.

The new communication protocol is based on https://avro.apache.org/ instead of https://www.json.org/. HEAT has added full fledged AVRO encoding and decoding support to both the core HEAT server as well as the SDK https://github.com/Heat-Ledger-Ltd/heat-sdk (sdk = native browser + nodejs libs).

With AVRO enabled you can expect a ~3-5 times network traffic reduction.

The biggest boost however is its CPU usage. Especially on high loads the amount of memory used and CPU power needed drops from significant to almost non existent. Both encoding and decoding happens up to 100s of times faster than before.

Other notable updates to the server code:

  • Fixed a bug in reporting of the total coin supply. While not important in any way from a p2p or technical aspect, with this fix there now are 25,776 more HEAT than was thought before, an increase of 0,07%! Thanks to the sharp community members for pointing this out! You know how you are.
  • Support for WebRTC decentralized signaling server was added which plays a role in our future decentralized messaging network plans
  • All external dependencies have been upgraded to their latest versions
  • Support for use of OS environment variables in config files (heat.properties), use this syntax heat.name=ENV[NAME_OF_ENV_VAR_GOES_HERE]
  • Some new API methods and improvements
  • New p2p/network health/node monitoring system with build in email reporter

@dmdeklerk dmdeklerk released this May 30, 2018 · 1 commit to master since this release

Assets 5


This is a HEAT server included release which gives you the new HEAT multi-currency wallet manager.

Gradually we'll be adding more cryptocurrencies starting with this release for Ethereum
and the Ethereum ERC20 tokens.

An update to the HEAT twelve-word secret phrase generator was applied making HEAT seeds
compatible with BIP39 [https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki].

Your HEAT seed now also becomes the basis for your Ethereum and Bitcoin HD wallets.

So thats one 12-word phrase giving you access to all your crypto holdings.

The Ethereum part of the wallet manager is implemented on top of https://github.com/ConsenSys/eth-lightwallet/
which implements a HD wallet and gives you an endless list of addresses all derived
from a single seed.

ERC20 tokens sending feature is under development still and will follow soon.

What is supported is the display of your token balances (HEAT Assets & ERC20 tokens), the
display of your transaction history (ABI aware transaction details which means transaction
details are parsed from the raw transaction.input - supported ABI's are expected to increase).

Most of the development work has been for behind the scenes stuff like remaking the client
structure to support multiple different currencies and updates to the wallet structure,
however experienced HEAT users will notice still quite a lot changed. The new
wallet manager screen is no doubt the largest visual update.

We hope you'll enjoy this release.

@dmdeklerk dmdeklerk released this Apr 3, 2018 · 2 commits to master since this release

Assets 5


Update: now includes Mac OS version

This desktop wallet release embeds the 2.5.0 server version which is a mandatory update. If your wallet does not use the built in server (default behavior of the wallet is to connect to a remote API node) you could still use that but you'll lack the client side (UI) improvements.


Windows, Linux and Mac OS versions.


Apart from the all important embedded server update this release contains dozens of fixes and improvements among some of the more notable are:

  1. Visual warning when sending to non existing accounts
  2. Visual warning when sending to accounts without public key
  3. Correct display of virtual balance in account explorer (virtual balance includes trades based on unconfirmed transactions)
  4. Asset Exchange websocket order books updates got fixed, updates as well when no new order is added but just on trades
  5. You can switch to beta network from the about dialog now (beta net toolbar color is red) (for developers and beta net testers)
  6. Recipient auto complete includes all numeric account ids now

About the HEAT LEDGER 2.5.0 server

This is a mandatory update, all nodes on the network need to run this version or higher.

Nodes below 2.4.0 will automatically be blacklisted by this version.

Nodes on 2.4.0 will remain working untill we reach block 1,245,000 as of when
a hardfork will take place.

This version will perform a one time scan of the blockchain on startup.


To install and run heatledger you need Java JDK 1.8 or higher installed, note that
JDK is different from standard java distributions.

On ubuntu we use sudo apt-get install default-jdk package. For other platforms
please look here http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html

For configuration settings see the conf/heat-default.properties files in the installation folder.

Whats in this release

No more forks

First and foremost this release fixes the occasional forks that occurred and which
required node operators to do the regular rescans of the blockchain. Those rescans
are not needed anymore as HEAT is now considered stable.

Stable Storage Engine

HEAT is different from other crypto currencies because of its special custom
build storage engine. Our unique storage engine is what allows us to scale in
size and speed. Building this engine however proved more difficult than
using a one size fits all - off-the shelf - storage engine like every other
crypto out there.

Our hard work however paid off which leads us to this stable and mature 2.5.0


This version supports benchmark mode which allows you to participate in the
upcoming HEAT Benchmark Competition. Instructions for this will follow but
participating requires at the very least that you run a HEAT server. Once you
run a HEAT server on main net it will be easy to run a second HEAT server
on the same machine but on benchmark net.

High Speed Binary API

We are moving away from JSON as a transport mechanism and are instead adopting
the binary AVRO encoding from HADOOP. One of the parts that makes it possible
to run a benchmark server which does many thousands of transactions a second
over the internet is the use of binary data over websockets.

This version has that new RPC mechanism to which you can talk from your browser,
mobile or NodeJS app. Interfacing with HEAT is made possible through our
officially supported HEAT-SDK https://www.npmjs.com/package/heat-sdk.

Adjustable Fees (spam protection)

Transaction fees can be remotely raised or lowered by the developers without the
need to update the software. An incubation period of 24 hours is observed before
the new fees take affect. This allows us to already lower the fees and raise
them again in case of misuse.

This is a temporary measure. Once block file splitting is enabled we dont care
about this anymore since the chain can grow indefinitely from then on.

We will start lowering the fees after the hard fork.

Mem Pool Fixes

While technically a part of the storage engine, it is worth mentioning that the
unconfirmed transaction pool had a bug fixed which caused unconfirmed transactions
to be improperly rolled back. Leading to forks due to balance differences between

Adjust heat.maxApiRecords

Use this setting to raise the number of rows returned from the various API's.

Virtual Order Matcher

This is enabled again by default, the virtual matcher matches orders and generates
trades in real-time based on unconfirmed transactions.

Numeric Account Ids

Numeric account ids are included in account search and in every autocomplete
now when sending transactions.

@dmdeklerk dmdeklerk released this Dec 28, 2017 · 3 commits to master since this release

Assets 4


This desktop wallet release embeds the 2.4.0 server version which is a mandatory update. If your wallet does not use the built in server (default behavior of the wallet is to connect to a remote API node) you could still use that but you'll lack the client side (UI) improvements.


The virtual order matcher (instant asset exchange order feedback) is still disabled, we are enabling that in the next wallet update. Because of this you have to wait until the next block (30 seconds) to see your balances updated and to see orders matched and trades made.

When the virtual order matcher is enabled we'll update the web based wallet on https://heatwallet.com and put out a new wallet release.

About the HEAT LEDGER 2.4.0 server

This is a hard fork, a mandatory update of the HEAT network. This update fixes a bug introduced in 2.1.0.

The hard fork will take effect at block 956000.

Nodes below 2.4.0 can not be used to forge in the main HEAT chain.

API Information





  • Updated default properties to always perform a scan and validation on every startup.
  • Set remaining balance limit of 0.01 HEAT for ask orders of HEAT due to large number of accidental account drainings and subsequent asset withdrawal incapacity

@dmdeklerk dmdeklerk released this Dec 21, 2017 · 4 commits to master since this release

Assets 4


Contains heatledger server 2.3.2.


We unfortunately introduced a bug in the previous 2.3.1 version basically making 2.3.1 incompatible with the last official guaranteed to work hard fork version 2.2.0 and its followup 2.3.0.

This version solves the problem where certain transactions could not be included in blocks forged by 2.3.1.

Apart from this fix we also fixed a bug in the display of transactions in the block explorer.

@dmdeklerk dmdeklerk released this Dec 19, 2017 · 5 commits to master since this release

Assets 4


Contains heatledger server 2.3.1.

About Heat server 2.3.1

Highly advisory update.

Blacklists nodes below 2.1.0 which is similar to most previous release.

Fixes the display of crossed out or pending cancelled orders.
Should reduce the chance of forks by disabling the last remaining part of the virtual order matcher that is being refactored.

A blockchain scan will be performed on startup.

Note about virtual order matcher

Heat server 2.3.1 fixes forking issues on the network caused by what we call the virtual order matcher, this virtual order matcher gives us the reall-time feedback of orders matched and balances updated even when the transaction is still unconfirmed.

The virtual order has been disabled and is being moved internally so it can no longer affect the consensus mechanism. Because of this you have to wait for the next block (max 30 seconds) before you see your orders matched, cancelled or balances updated.

We are working on an update that fully enables this great feature again, it will work even better and no longer interfere where it could cause forks to happen.

@dmdeklerk dmdeklerk released this Dec 3, 2017 · 6 commits to master since this release

Assets 4

Heatwallet 2.3.0

Windows and linux desktop editions of the HEAT wallet, embeds latest 2.2.0 server which is a mandatory update.

On Windows make sure to remove old version before installing this new version.

Contains server Heatledger 2.2.0

This is a mandatory update, all nodes on the network need to run this version
or higher.

Nodes below 2.1.0 will automatically be blacklisted with this version.

UPGRADE INSTRUCTIONS [upgrade only, new installations can ignore]

This version will perform a full rescan of the blockchain upon first use, this
happens automatically.

API Documentation

Please look here for API docs https://heatwallet.com/api

List of updates/fixes/features.

  • fixes bug involving the last hard fork and the way expired orders are handled

@dmdeklerk dmdeklerk released this Nov 26, 2017 · 7 commits to master since this release

Assets 4


Wallet/desktop specific changes:

  • Fixed Join Slack link
  • Orderbook alignment adjusted
  • Fixed history entries display bug

Contains SERVER >> Heatledger 2.1.0

This is a mandatory update, all nodes on the network need to run this version
or higher.

A hard fork will happen at block 870,000 at which we will update the block
version number, after that block older versions will not accept blocks from the
new fork and vice versa.

Nodes below 2.0.0 will automatically be blacklisted with this version.


To install and run heatledger server you need Java JDK 1.8 or higher installed, note that JDK is different from standard java distributions.

On ubuntu:

sudo apt-get install default-jdk

For other platforms look here


UPGRADE INSTRUCTIONS [upgrade only, new installations can ignore]

This version will perform a full rescan of the blockchain upon first use, this
happens automatically.

API Documentation

Please look here for API docs https://heatwallet.com/api

List of updates/fixes/features.

  • one critical and two lesser bugs are fixed with this release. details of which
    will be released when the fork is complete.
  • the custom memory mapped storage maps for storing things like account balances
    or block ids are reduced in size, this saves several Gigabytes of storage
    needed in the blockchain folder
  • in case storage maps grow too big they will now automatically be resized

@dmdeklerk dmdeklerk released this Oct 9, 2017 · 8 commits to master since this release

Assets 5


Includes HEAT server 2.0.0 see below for details.

This is a mandatory update, all nodes on the network need to run this version
or higher.

A hard fork will happen at block 777,777 which is approximately two weeks from
the moment we do this release (somewhere around 2017-10-22).


The following applies ONLY if you run in 'non-light' mode. (when you've added heat.replicatorEnabled=true to your configuration).

While you can re-use your existing blockchain which can be found in the blockchain directory in your previous 1.1.0 installation.

You now need to DELETE THE DIRECTORY CALLED heat_db before starting heat 2.0.0, doing this will force HEAT to rescan the blockchain and rebuild its replicator database model.

API Documentation

Please look here for API docs https://heatwallet.com/api

Balance Leasing

By sending a LEASE transaction you transfer your forging power (so thats your
effective balance or stake) to a different account.

The amount you lease is always your full stake at any given moment, you also
provide a period expressed in blocks after which the lease ends. The period has
to be between 1,440 and 300,000 blocks.

While your stake is leased you can still move your HEAT to another account or
receive HEAT in your account. The same rules that applied before for how to
calculate your effective balance apply now. Whenever you add HEAT to your account
those funds will add up to your leased balance after 1440 blocks. At the same
time whenever you transfer HEAT out of your account that will immediately be
deducted from your leased stake.

An account to which balances are leased can start forging as usual, when determining
the account stake during block creation and broadcasting we add up all leased
stakes to come to that account current forging power.

After sending a LEASE transaction and before that lease period is over you can
send any number of follow up LEASE transactions each one overwriting your 'next lease'
which takes effect automatically the moment your first lease ends.

Use case for balance leasing is two fold.

1. It allows accounts with small stakes to group together to form forging 
   pools. This way increasing your chance of forging blocks.
2. It's a security measure where you lease your (large) stake to a proxy
   account. Meaning you no longer have to expose your secret phrase of 
   your main account to the server you use for foring blocks.

As is the case with forging blocks without leasing your balance, we require a minimum of
1,000 HEAT in order for your stake to be counted as leased stake.

List of updates/fixes/features.

  • fixed placeAsk, placeBid unknown asset bug
  • replicator model schemas now support MYSQL
  • new replicator schema version manager based on external property files, please
    see 'resources' directory for all sql schemas
  • server side order book running total and sum calculations
  • changed the default logger to daily rollovers, logs are archived for 30 days
    and automatically deleted
  • forger rewards are traced by a new replictor
  • forger rewards can be returned by the API
  • order cancellations are now traced by a new replicator, now the UI can display
    order cancellation details including asset, currency, quantity and price
  • blocks generated per account are now traced in a new replicator and are availble
    in the UI and from the API
  • improvements/optimizations of replicator SQL and where needed combining SQL
    based solutions with custom caching solutions. this is an ongoing process,
    major updates to the way we deal with our rather unique replicator mechanism
    are to be expected
  • thread safety improvements

When the hard fork happens only servers running this version or higher will be
able to connect.

@dmdeklerk dmdeklerk released this Jun 30, 2017 · 9 commits to master since this release

Assets 4

Heat Wallet 2.0.0

Includes Heat Server 1.1.0, see below for details.

The HEAT 2.0 client consist of a major rewrite/improvement of the core workings as well of a brand new look and feel in line with the newly developed Heat Ledger Ltd corporate styling.

Focus has been on improving usability as well as performance, security and application stability.

Some of the improvements are:

  • your registered email account id is displayed now instead of the numeric id
  • others can address you now by your email account id
  • when sending heat, assets or messages there now is search as you type auto complete support which makes finding other accounts a breeze
  • wallets can now be imported and exported from/to your browser or the desktop app
  • individual accounts can be imported and exported using just their secret phrase
  • block explorer search for accounts, transactions, blocks
  • block explorer data display improvements
  • display assets issued and held by any account
  • preview message and display of full message in account history
  • exchange order expiry time period picker
  • deposit and withdrawal buttons for Heat Ledger certified asset gateways
  • fixed asset launch time display
  • real-time chart ticker picks up trades as they occur
  • uncertified markets hidden by default, expandable through clicker
  • improved trollbox chat with cryptographic identity proof (click on name to inspect account in real time in block explorer)

Included Server: Heatledger 1.1.0

While this version is backward compatible with previous versions when it comes to the p2p protocol level operations. To use the new 2.0 class of the HEAT clients you will need this upgraded version since those clients depend on extensions to the API not available in previous versions.

Focus for the 1.1.0 release has been on increasing system stability by hardening the existing code to better deal with multi threaded access to the core HEAT storage components (basically the blockchain itself).

In the upcoming versions of the HEAT server product focus will shift to replacing the peer 2 peer system inherited from HEAT's NXT origins (the p2p code is the last piece of original NXT code).

Now that this step was made, the core is ready to be used by the new intelligent and fast HEAT p2p protocol, the final bottle neck towards reaching transaction processing at lightning speeds.