v4.3.0

Heatledger Server 4.3.0

Installation

We advise to use the new official Docker images to run HEAT server.

Please find the official Docker images here https://hub.docker.com/r/heatcrypto/heatledger

New Features:

• Provide live info about peers network state (using websocket)
• Reset blockchain to height using setting heat.rollbackBlockchainToHeight

Changes:

• Verbose check report comparing blockchain data to database state
• Optimisation: do not validate transaction in far past on scanning

Fixes:

• Fix download and upload volume counters
• Update (actualize) mysql sql
• Fix api doc annotation for path /messaging/message
• Add dependency jaxb-runtime for to provide compatibility from java 8 to java 17

v4.2.1

Heatledger Server 4.2.1

Installation

We advise to use the new official Docker images to run HEAT server.

Please find the official Docker images here https://hub.docker.com/r/heatcrypto/heatledger

New features

• Email notifying on incoming u2u message via mail service.

Changes

• Add explicity property "heat.isAnotherNet" to mark not mainnet blockchain.
• Add API function "Create offchain message".
• Add lessosrs balance to the api response.
• Pause forging while downloading blocks that are far to the blockchain end.
• Upgrading of resizing of storage files, now it doesn't require server restarting.
• Add ability to API to get bytes of transaction.
• Do not delete obsolete storage files by default.

Fixes

• Fix removing file on server when message is delivered but file is not delivered.
• Fix API function tools/aes/encrypt.
• Fix error handling on blockchain downloading.
• Prevent access to persistent store on shutdown.
• Fix U2U messaging removing message.
• Fix parsing API parameter "currency".
• Fix java startup parameters to be compatible with Chronicle libs for different JDK versions.

Heatledger Server 4.1.1

Heatledger Server 4.1.1

Installation

We advise to use the new official Docker images to run HEAT server.

Please find the official Docker images here https://hub.docker.com/r/heatcrypto/heatledger

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

Heatledger Server 4.0.0

Installation

We advise to use the new official Docker images to run HEAT server.

Please find the official Docker images here https://hub.docker.com/r/heatcrypto/heatledger

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 additions

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

Changes

• Masternode registration fee set to 50 HEAT, enhance validity period to 622080 blocks (180 days)
• New ways to set server properties (on command line)
• Support encrypted messaging through server when direct WebRTC is not allowed for endpoints.

Bug fixes and optimisations

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

Heatledger Server 3.1.0

Heatledger Server 3.1.0

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

HEAT Server 3.0.0

New Server Features

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

1. Enabled 18 million terabytes decentralized blockchain storage engine, in preparation for decentralized block slice hosting.
2. 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).
3. 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.
4. 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.
5. 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.
6. 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!

HEAT Server 2.5.4

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;

HEATLEDGER Version 2.5.3

The HEAT 2.5.3 Server is an optional update with improvements and some bug fixes.

Fixed errors on public name duplication in database at blockchain scanning. This improves blockchain scanning speed.

The server initialization is reorganized for embedded usage. Also implemented more robust (in different OS) server shutdown for desktop Heatwallet application using file signaling.

Eliminated extra console output about balances hash equality on blockchain scan and download.

HEATLEDGER Version 2.5.2

HEATLEDGER 2.5.2

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
  • 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

HEATLEDGER 2.5.1

HEATLEDGER 2.5.1

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
   

3. 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 (video was made on a Linux desktop but the same applies for Windows and MacOs).

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.