Quote from: verymuchso on September 14, 2018, 12:51:31 PM

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 - weve 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 cant 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)

HEAT Client (light version)

HEAT Server

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

This function in the HEAT p2p server wallet, can I trade directly in the P2P wallet? but if P2P happens what will be the currency of exchange? BTC, ETH? Thanks Wink