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.

Includes

Windows and Linux versions.Mac OS version will follow.

Updates

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

Visual warning when sending to non existing accounts

Visual warning when sending to accounts without public key

Correct display of virtual balance in account explorer (virtual balance includes trades based on unconfirmed transactions)

Asset Exchange websocket order books updates got fixed, updates as well when no new order is added but just on trades

You can switch to beta network from the about dialog now (beta net toolbar color is red) (for developers and beta net testers)

Recipient auto complete includes all numeric account ids now

Heatledger 2.5.0

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.

## Installation

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

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 whichrequired 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 custombuild 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 othercrypto out there.

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

### Benchmark

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 adoptingthe 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 secondover 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 theneed 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 transactionsto be improperly rolled back. Leading to forks due to balance differences betweennodes.

### 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 autocompletenow when sending transactions.

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 whichrequired 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 custombuild 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 othercrypto out there.

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

### Benchmark

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 adoptingthe 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 secondover 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 theneed 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 transactionsto be improperly rolled back. Leading to forks due to balance differences betweennodes.

### 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 autocompletenow when sending transactions.

Recently ran into a problem sending HEAT from cryptopia to my heatledger wallet. I used my 19 digit numeric account number, and the transaction was hung in a pending status. Cryptopia support was able to undo the transaction and restore my balance. Is there different or additional information I should have been using for the account number for the transfer?