This is a friendly update to an older channel.
Please find us here meanwhile https://discord.com/invite/9aS72N2

Heat Server 4.1.1

This is the backend blockchain server to join the HEAT p2p blockchain network.

Available as stand alone and Docker images (docker is Heats preferred way of deploys) note that docker image is available with blockchain bootstrap as well.

- docker = https://hub.docker.com/r/heatcrypto/heatledger/
- java + shell start script = https://github.com/heatcrypto/heatledger/releases/tag/v4.1.1
 
New features

Messaging File Transfer

Send files up to 2 MB using U2U protocol (via heatledger node), no fee
File is encrypted by sender, only recipient can decrypt it
File is removed on the server on delivering to the recipient

Changes

- Add API to get HEAT messages by timestamp range
- Fix minor bugs


---------------------

This is a friendly update to an older channel.
Please find us here meanwhile https://discord.com/invite/9aS72N2

Heat Client 4.1.0

Available as light (no embedded server, uses public nodes) and full version (comes with blockchain embedded)

Available for Windows and Linux.

- full release = https://github.com/heatcrypto/heatwallet/releases/tag/v4.1.0
- light release = https://github.com/heatcrypto/heat-ui/releases/tag/v4.1.0

Changes

Add feature File Transfer in messaging:
- Send files up to 2 MB
- File is encrypted by sender for recipient
- After delivering the encrypted file is removed on the server

- Add removing not delivered message (with transferred file also) on the server side on deleting the message by sender
- Separate the Heat and Offchain message lists to have robust manageable messaging
- Ability to add visible label (not encrypted) in addition to encrypted label for entry in wallet

- Fix storage namespace changing on account changing on page Wallet
- Fix path to config files for desktop HEAT wallet
- Minor UI fixes

Please note that this is a MANDATORY update.
A NETWORK WIDE HARD FORK will happen at block 4,372,000, which is expected to happen already Saturday after midnight Amsterdam time.

This is a friendly update to an older channel.
Please find us here meanwhile https://discord.com/invite/9aS72N2

Heat Client 4.0.0

Available as light (no embedded server, uses public nodes) and full version (comes with blockchain embedded)

Available for Windows and Linux.

- full release = https://github.com/heatcrypto/heatwallet/releases/tag/v4.0.0
- light release = https://github.com/heatcrypto/heat-ui/releases/tag/v4.0.0
 
New features

Private Asset feature:

- Issue asset of type Standard or Private
- Whitelist accounts permitted to access private asset
- Specify private asset fees for order creation, trade, and the recipient account of these fees
- Specify default network fee payer for private asset at whitelisting of market

Asset expiration feature:

- Specify asset expiration time at asset issuance
- Specify asset expiration time separately

Supervisory Account feature:

- Assign account under control of another account.
- Limited transfer amount during interval feature:
- Limit through supervisory account how much max amount of an asset the account can send in a specific interval.

Messaging through server feature:

- Added persistent messaging (no fee) through signaling server in case it is not possible to establish a direct WebRTC channel between endpoint devices.

Benchmark reward token released in main net
- https://benchmarkrewards.com now uses BERT tokens in mainnet for reward payments every minute.

Changes

- UI showing Private Key with QR code.
- Display Multi Atomic Transfers in the Payments section on the account home screen.
- Display valid masternode list in the dialog “Register Masternode Address”.
- Access Benchmark client inside Heatwallet application.
- Display account number on top left in case name or email does not exist.
- Smooth (without blinking) update of the list of blocks and transactions.
- Updated data sources for NXT and ARDR
- Display extended info about asset.
- Updated 3rd party libraries.
- Minor UI changes.
- Bug fixes and optimisations
- Prevent creation of multiple equal markets.
- Fix decimals displaying and editing for currency/asset.
- Fix last 4 lines of server log auto visible without scrolling.
- Fix switching between mainnet and testnet local blockchains in the desktop Heatwallet.
- Fix incoming message notification placement
- Fix switching online/offline status in peer-to-peer messaging.

Please note that this is a MANDATORY update.
A NETWORK WIDE HARD FORK will happen at block 4,372,000, which is expected to happen already Saturday after midnight Amsterdam time.

This is a friendly update to an older channel.
Please find us here meanwhile https://discord.com/invite/9aS72N2

Heat Server 4.0.0

This is the backend blockchain server to join the HEAT p2p blockchain network.

Available as stand alone and Docker images (docker is Heats preferred way of deploys) note that docker image is available with blockchain bootstrap as well.

- docker = https://hub.docker.com/r/heatcrypto/heatledger/
- java + shell start script = https://github.com/heatcrypto/heatledger/releases/tag/v4.0.0
 
New features

Private Asset feature:

- Issue asset of type Standard or Private;
- Specify whitelist of accounts available to use the private asset;
- Specify the fee on order creation, the fee on trade, the recipient of these fees;
- Define default network fee payer for private asset on whitelisting market;
- Calculate and charge the fees on order creation, on trading;
- API functions to support private assets;

Asset expiration feature:

- Asset trading available until asset expiration time;
- New transaction type to assign the expiration;

Supervisory Account feature:

- New transaction type (type 4 subtype 2) to assign one account under the control of another account;

Limited Amount of Account Asset in interval feature:

- New transaction type (type 4 subtype 3) to limit the account by supervisory account how much max amount of the asset the account can send in the interval;

Microservice engine:

- Implement listeners “onConfirmed”, “onComplete”;
- Fix minor bugs;

API updates

- API to get the Multi Atomic Transfers.
- Add field height for API function /account/payments.
- API to get the list of actual masternodes.
- API to get messages by transaction type (e.g. get messages of order placements).
- Add to API the ability to send messages by transactions of types Ask order, Bid order, Cancel order, Issue Asset, Set Fee for private asset.

Other updates

- Change masternode registration fee to 50 HEAT, enhance validity period to 622080 blocks (~180 days).
- Added new ways to set server properties.
- Support encrypted messaging through server when direct WebRTC is not allowed for endpoints.

Bug fixes and optimisations

- Optimise performance of processing block with big number of transactions.
- Fix getting highest transaction for benchmarking: compare longs as unsigned values. Prevent bloating cache of the highest transactions.
- Fix processing broadcast request with multiple transactions if one of transactions is failed.
- Fix applying unconfirmed transactions for atomic multi transfers to guarantee all transfers or nothing (truly atomic).
- Fix description of API function. Update Swagger UI.
- Fix minor bugs.

HEAT 3.1.0 Wallet, Client and server

Server Updates

1. Implemented compatibility in addition to Java 1.8 with Java 9, 10, 11, 12
2. Upgraded 3rd party java librares
3. Added POP POS Rewards history storage to have ability to get account and amount of rewards at any height
4. Scanning optimization: disabling storage map versioning on scanning before 1440 blocks until blockchain end
5. Improved embeddability: make Genesis class embeddable
6. Fixed erroneously persisting peer blacklisting due to old version
7. Fixed bug: on scanning storing genesis account at wrong version height
8. Fixed API bug: getting Last Price for market
9. Fixed minor bugs

Wallet and Client updates

# HEAT Wallet 3.1.0

This is the full wallet version that comes with the embedded Heat server. Please see https://github.com/heatcrypto/heat-ui/releases for the light wallet edition without embedded server.

Support for Ethereum (ETH) wallet

Support for Litecoin (LTC) wallet

Support for BitcoinCash (BCH) wallet

Speed up wallet loading by storing encrypted currency wallets

Merge offchain (peer-to-peer) and onchain messages lists

Store wallet address created in local storage

Support failover option for crypto nodes providing services for currency wallet

New configuration (including failover config) of application in one editable file

Cosmetic UI changes

Fixed minor bugs

---

Server:
https://github.com/heatcrypto/heat-ui/releases/tag/v3.1.0

Wallet (with server):
https://github.com/heatcrypto/heatwallet/releases/tag/v3.1.0

Client (without server):
https://github.com/heatcrypto/heatledger/releases/tag/v3.1.0

Minor wallet update 3.0.1

Heat wallet 3.0.1

Contains heat server 3.0.0

Minor updates next to release 3.0.0.

## Notable changes in Heatwallet client:

- Display IOTA address including checksum
- Fixed and improved the UI of the list of IOTA transactions
- Fixed Eth transaction history rounding error
- Fixed switching between child currencies under the different master accounts
- Cosmetic UI improvements on the wallet page

https://github.com/Heat-Ledger-Ltd/heat-ui/releases/tag/v3.0.1
https://github.com/Heat-Ledger-Ltd/heatwallet/releases/tag/v3.0.1

That bug report is a bit on the light side.
What does the console output say?

DESKTOP WALLET...

Heatwallet 3.0.0

Includes Heatledger 3.0.0

Notable server changes

See https://github.com/Heat-Ledger-Ltd/heatledger/releases/tag/v.3.0.0

Notable changes in Heatwallet client:

- Support storage of BTC messages in Local storage space.
- Support BTC transfer using HEAT accountId
- Support for IOTA wallet
- Support for ARDR wallet
- Use company node for querying BTC, NXT, ARDR
- Failover for BTC to use blockcypher.com
- Import specific currency wallet only on wallet screen
- Added Internet Address registration UI to support Masternode feature
- Added support for new transactions types - Internet Address registration, Atomic Multi Transfer
- Configurable URL of signaling server - ability to use separate (own, private) network of p2p messaging clients   
- Tiny fixes of user interface
- Fixed failover behavior - switching between servers requires stricter conditions, which reduces the number of switchings
- Fixed p2p messaging behavior on account switching on the Wallet page
- Fixed behavior and application state on account switching on the Wallet page
- Disallowed new account creation without pin code

Get the FULL Wallet here (that includes the server)
https://github.com/Heat-Ledger-Ltd/heatwallet/releases/tag/v3.0.0


Get the LIGHT Client here (no server included)
https://github.com/Heat-Ledger-Ltd/heat-ui/releases/tag/v3.0.0

HEAT SERVER 3.0.0 RELEASED

18 Million TeraByte of Blockchain capacity from now on.

Expect transaction fees to drop.

New Server Features

Note that this is a mandatory update. All nodes on the network must update to this new version.

• Enabled 18 million terabytes decentralized blockchain storage engine, in preparation for decentralized block slice hosting.
• New transaction type for registration of a node’s IP address or domain name to become Masternode. Only registered masternodes are eligible for POP rewards when forging a block. Masternode registration is valid for 311,040  blocks (~90 days) with a single registration transaction. Masternode registration fee (goes to next block finder) is 100 HEAT, and the minimum guaranteed balance checked at every block creation time is 1,000 HEAT. Masternode feature will be enabled at hard fork block height 2,700,000 (approx. August 10th).
• In preparation to the decentralized POP network where nodes are rewarded for archiving and distributing historic blockchain data, we are beginning to move to nodes being required to register as Masternodes. The first phase will start with the coming fork after which POP rewards are rewarded only to registered valid Masternodes. Registration is simple and is performed through the HEAT wallet user interface or API.
• New transaction type for sending multiple payments in one transaction - Atomic Multiple Transfer. This feature is for now accessible through the Heatwallet API only, not User Interface. Intended for use in external integrations and for the automation of processes on the HEAT network like microservices sending automated payments. Atomic Multiple Transfer feature will be enabled at hard fork height 2,700,000.
• P2P protocol update. Starting from block 2700000 all nodes will communicate with the newer, more efficient binary protocol instead of text based JSON. This will save bandwidth and makes things faster and more stable. CPU and memory usage of a node go down considerably especially when communicating larger pieces of data.
• Secure chat user interface improvements
• Configurable webrtc signaling server for local secure chat setup independent from 3rd party services. Create your own private messaging network by turn on signaling service in your server heat.properties using “heat.signalingServerEnabled=true” and specifying your signaling host in the client application fail-over config (failover-config.json). Ask your users to do the same in their client apps, and VOILA! There you have the world’s most secure messaging service where the encrypted messages are transmitted directly from sender ip address to receiver ip. Initiation of communication channel coordination goes through single “central” server only - your own!

Server version can be downloaded here:
https://github.com/Heat-Ledger-Ltd/heatledger/releases/tag/v.3.0.0

Check out our blog post on the new release to know more on all the improvements and new features - https://goo.gl/DKj58F


RELEASE NOTES

Heatwallet 2.9.0

Includes Heatledger 2.5.4

Notable Server Changes

Added signaling server to provide peer-to-peer messaging via WebRTC technology. The basic version of the signaling server supports central signaling host with the following features:

- Off-chain messaging, data transtmitted and stored encrypted on local device (sender & receiver) only
- P2P direct connect from client to client after signaling channel creation
- prevent MITM attacks via encryption signaling data (on client side) by users public/private keys. Server cannot recognize any client WebRTC data after signaling channel creation
- Online trigger with accept / decline confirmation for incoming connect requests
Other updates:
- discard chart and market updates when blockchain is downloading and height is far from peers height;
- fix sql select transactions

Notable Changes in Heatwallet Client

- Added company node data source and failover mechanism for Bitcoin client side wallet
- Added local payment message storage (encrypted)
- Removed trollbox
- Added NXT support for client side wallet
- Added certified NXT asset
- Enabled NXT deposits (delay of up to 24 hours for now)
- Standby readiness for ARDR client side wallet deployment
- improved failover config options
- fixed BTC send bug
- speedup of wallet screen handling
- enabled Ardor client side wallet
- enabled Ignis Chain DEX access. Access you ARDR account first, then DEX screen
- enabled BTC/ARDR market
- prepared BTC withdrawal automation system and NXT / ARDR deposit automation

RELEASE LINKS

Windows

HEAT Wallet: Heatwallet_Setup_2.9.0.exe - https://github.com/Heat-Ledger-Ltd/heatwallet/releases/download/v2.9.0/Heatwallet_Setup_2.9.0.exe

HEAT Client: Heatclient_Setup_2.9.0.exe - https://github.com/Heat-Ledger-Ltd/heat-ui/releases/download/v2.9.0/Heatclient_Setup_2.9.0.exe

Linux

HEAT Wallet: Heatwallet_Linux_2.9.0.zip - https://github.com/Heat-Ledger-Ltd/heatwallet/releases/download/v2.9.0/Heatwallet_Linux_2.9.0.zip

HEAT Client: Heatclient_Linux_2.9.0.zip - https://github.com/Heat-Ledger-Ltd/heat-ui/releases/download/v2.9.0/Heatclient_Linux_2.9.0.zip

Mac OS

HEAT Wallet: Heatwallet_MacOS_2.9.0.zip - https://github.com/Heat-Ledger-Ltd/heatwallet/releases/download/v2.9.0/Heatwallet_MacOS_2.9.0.zip

HEAT Client: Heatclient_MacOS_2.9.0.zip - https://github.com/Heat-Ledger-Ltd/heat-ui/releases/download/v2.9.0/Heatclient_MacOS_2.9.0.zip

 New Releases:
HEAT Server 2.5.2 | HEAT Wallet 2.7.0

These are optional but recommended updates.

Online wallet is here:

ONLINE WALLET

Wallet 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 who 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
• • https://heatwallet.com/api/#!/Transactions/checkApplicability
  • https://heatwallet.com/api/#!/Accounts/payments now returns transaction id
• New p2p/network health/node monitoring system with build in email reporter

Other notable updates:

HEAT-SDK (software development kit - browser+server) was promoted to version 1.0.1 recently and is becoming an ever more important part of our arsenal and a vital building block of our own and third party projects.

https://www.npmjs.com/package/heat-sdk
https://github.com/Heat-Ledger-Ltd/heat-sdk

We implemented a mini Paper Wallet utility which assists you to store and administer your private keys. It is functional as is with one drawback: the generated keys are old style HEAT keys which means you can’t derive Bitcoin or Ethereum addresses from them. You CAN however create paper wallets with your BIP44 compatible keys you created in the main HEAT wallet.

https://github.com/Heat-Ledger-Ltd/heat-paperwallet

Downloads:

HEAT Wallet (full version - includes HEAT p2p server)

• Windows https://github.com/Heat-Ledger-Ltd/heatwallet/releases/download/v2.7.0/Heatwallet_Setup_2.7.0.exe
• OSX https://github.com/Heat-Ledger-Ltd/heatwallet/releases/download/v2.7.0/Heatwallet_MacOS_2.7.0.zip
• Linux https://github.com/Heat-Ledger-Ltd/heatwallet/releases/download/v2.7.0/Heatwallet_Linux_2.7.0.zip

HEAT Client (light version)

• Windows https://github.com/Heat-Ledger-Ltd/heat-ui/releases/download/v2.7.0/Heatclient_Setup_2.7.0.exe
• OSX https://github.com/Heat-Ledger-Ltd/heat-ui/releases/download/v2.7.0/Heatclient_MacOS_2.7.0.zip
• Linux https://github.com/Heat-Ledger-Ltd/heat-ui/releases/download/v2.7.0/Heatclient_Linux_2.7.0.zip

HEAT Server

https://github.com/Heat-Ledger-Ltd/heatledger/releases/download/v2.5.2/heatledger-2.5.2.zip

BEWARE SCAMMERS ACTIVE..

FAKE WALLET REPLICA FOUND ONLINE.

Scammers have created at least one fake replica of the https://heatwallet.com site.
The replica consists of just one page in which you are supposed to enter your secret phrase, by doing that the scammers will be able to empty your funds.

How to protect yourself.

1. Only one online wallet exists which is available at https://heatwallet.com any other address is not the HEAT web wallet.
2. Use the desktop app for enhanced security, find the full wallet here https://github.com/Heat-Ledger-Ltd/heatwallet/releases or get the light version here https://github.com/Heat-Ledger-Ltd/heat-ui/releases



Always make sure the address is https://heatwallet.com



This is what the real site looks like.



This is a screenshot of the replica created by the scammers.

Please don't share the address of the scammer site if you run into it.
Also watch out not to visit the site which could potentially reveal your identity to the scammers or possibly infect your computer with malware.

A safe way to visit such a site for research purposes would be to use an online proxy such as https://www.hidemyass.com/en-eu/proxy

HEAT LEDGER 2.5.1 | Optional server only update.

This optional update brings us advancements to the fast-binary transaction broadcaster interface.
Sending transactions in prepared binary form over already opened (web)socket connections allows us to broadcast transactions from a client (mobile app or browser) to the HEAT network very fast!

In order to allow even greater speeds in our upcoming - record breaking -  over the internet benchmark competition we've made improvements to this protocol.

To ensure your blockchain and balances are in the best possible state at start up this version will perform a one time scan and validation of your blockchain.

Dont want to update

Updating to this version is not mandatory, but anyone who does will ensure themselves of the best possible state of their blockchain (data) through the process of the rescan + validation. Doing this reduces your chances of landing on a fork and increases your chance of receiving forging rewards.

Same benefits without the upgrade

Not doing the update, but you do want your blockchain and balances to be in the best possible condition?
Then do the following in order to rescan and validate your blockchain.

1. Locate or create a file at INSTALL DIR/conf/heat.properties
2. Place these two lines at the end of that file
    ```
    heat.forceValidate=true
    heat.forceScan=true
    ```
4. Now on startup your blockchain will be freshly re-scanned and fully validated

And there you have it, blockchain and balances are as good as they get.

Desktop app (HEAT Wallet)

Since this update only applies to the benchmark competition there is no need for a desktop update.

However, in order to perform a validation of your blockchain running in HEAT Wallet, please have a look at this short video on how to locate or create your INSTALL DIR/conf/heat.properties file. Same steps as above apply.

[Video was made on a Linux desktop but the same applies for Windows and MacOs]




DOWNLOAD:
 https://github.com/Heat-Ledger-Ltd/heatledger/releases/tag/v2.5.1

HEAT CLIENT 2.6.3

HEAT CLIENT 2.6.3

This is a light weight version of HEAT Wallet which does not include the HEAT server.

Installation:

Get your Windows, Linux or MacOS Desktop installers while they are hot...  

Downloads are here: https://github.com/Heat-Ledger-Ltd/heat-ui/releases/tag/v2.6.3

HEAT WALLET 2.6.3

HEAT goes Multi-Currency starting with Ethereum and ERC20 token support.

HEAT WALLET 2.6.3

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.

Installation:

Get your Windows, Linux or MacOS Desktop installers while they are hot...  

Downloads are here: https://github.com/Heat-Ledger-Ltd/heatwallet/releases/tag/v2.6.3

Updating/preserving your blockchain:

In order to preserve your blockchain from your previous installation so you dont have to download it, follow these steps.

Step 1. Backup your blockchain folder (video https://webmshare.com/play/EV4GR)

Step 2. Install HEAT WALLET 2.6.3

Step 3. Restore your blockchain folder (video https://webmshare.com/play/azwMO)

The steps are the same on Macs and Linux desktops.

The rewards will decrease at 1,250,000 + 4320.

So we'd have to wait a flew blocks still.

The reason is that the first rewards had been disabled during those first blocks since we were mining with company accounts to get the network stable.

The stage change for block 2,500,000 will be adjusted down to happen at block 2,500,000 again.

HEAT MAC OS Full Client

HEAT WALLET 2.5.0 now available for MAC OS.

All releases: https://github.com/Heat-Ledger-Ltd/heatwallet/releases/tag/v2.5.0

Direct download: https://github.com/Heat-Ledger-Ltd/heatwallet/releases/download/v2.5.0/Heatwallet_MacOS_2.5.0.EXPERIMENTAL.zip

Installation

- Download the zip
- Drag the Heatwallet App to your app bar

Contents

Fully functional HEAT wallet for Mac OS.
Will work as thin client the moment you start it.
Go to server section and click Start Server to run your own HEAT server, closing the App will stop your HEAT server.

To run a permanent server please look at https://github.com/Heat-Ledger-Ltd/heatledger/releases/tag/v2.5.0

Best practice is to always back up your wallet to disk. (Top right side menu -> Backup wallet)

Hi,

Thank you for your question.

We use Github's https://github.com/electron as a run time engine to host our custom built web client as desktop apps on Windows, Linux and Macs.

Before we build the client we make sure to always update and upgrade to the latest electron pre-built packages available for the major version against which we have build our client.
We did the same for this latest build.

Normally security issues and updates are always backported to each still supported Electron version and these are made available as an update which we are alerted by simply running the electron builder script. For this build and for any past build that was the case as well.

Unfortunately I believe it's close to impossible to always update all software against any zero-day exploit the day, week or month it comes out.

That said, parts like the FFmpeg and the pdf viewer that come standard with Electron are however by the nature of our client never touched or invoked. What I mean is you cant remotely play any video or audio file or open a pdf doc in HEAT client.

Your question did make us look better into keeping build dependencies up to date and its something we will be looking into in order to harden this aspect even more. So thank you for that!

HEAT 2.5.0 FULL CLIENT - WINDOWS & LINUX

Hard fork set for block 1,245,000 which is somewhere around next Friday (April 6th).

Download available:

https://github.com/Heat-Ledger-Ltd/heatwallet/releases/tag/v2.5.0

HEAT WALLET 2.5.0

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.

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
release.

### 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 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
nodes.

### 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.

HEAT 2.5.0 MANDATORY UPDATE - PLEASE EVERYONE UPDATE.

Hard fork set for block 1,245,000 which is somewhere around next Friday (April 6th).

Download available:

https://github.com/Heat-Ledger-Ltd/heatledger/releases/tag/v2.5.0

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.

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
release.

### 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 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
nodes.

### 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.