Skip to content
  • v3.1.0
  • 3d73204
  • Compare
    Choose a tag to compare
    Search for a tag
  • v3.1.0
  • 3d73204
  • Compare
    Choose a tag to compare
    Search for a tag

@dmdeklerk dmdeklerk released this Oct 31, 2019 · 2 commits to master since this release

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

Assets 4
  • v3.0.1
  • ee492c8
  • Compare
    Choose a tag to compare
    Search for a tag
  • v3.0.1
  • ee492c8
  • Compare
    Choose a tag to compare
    Search for a tag

@dmdeklerk dmdeklerk released this Jul 19, 2019 · 3 commits to master since this release

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
Assets 5
  • v3.0.0
  • 6b40b35
  • Compare
    Choose a tag to compare
    Search for a tag
  • v3.0.0
  • 6b40b35
  • Compare
    Choose a tag to compare
    Search for a tag

@dmdeklerk dmdeklerk released this Jul 12, 2019 · 5 commits to master since this release

Heatwallet 3.0.0

Includes Heatledger 3.0.0

Notable server changes

See Heatledger 3.0.0 server release notes

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
Assets 5
  • v2.9.0
  • 2f66aef
  • Compare
    Choose a tag to compare
    Search for a tag
  • v2.9.0
  • 2f66aef
  • Compare
    Choose a tag to compare
    Search for a tag

@dmdeklerk dmdeklerk released this Apr 1, 2019 · 12 commits to master since this release

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
Assets 5
  • v2.8.1
  • 19f732a
  • Compare
    Choose a tag to compare
    Search for a tag
  • v2.8.1
  • 19f732a
  • Compare
    Choose a tag to compare
    Search for a tag

@resultingforce resultingforce released this Nov 21, 2018 · 17 commits to master since this release

HEAT Wallet 2.8.1

Optional but recommended update.

This is the full desktop wallet version with heatledger server 2.5.3 included.

To install and run the optional included heatledger server you need Java JDK 1.8 or higher installed. Note that JDK is different from standard java distributions.

To install JDK on Ubuntu 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.

Client changes from previous release:

  • Fixed erroneous failover host switching in desktop Heatwallet application.
  • Minor UI fixes
  • Added wallet support for FIMK cryptocurrency
  • Improved BTC wallet data display behavior
  • Added client failover settings file placed at the application home dir in file failover-config.json
  • Fixed icon to copy secret phrase to the clipboard at wallet creation
  • Showing version of embedded HEAT server in About dialogue

testnet

In order to connect to the heat testnet (this is used by developers mostly) add these properties to conf/heat.properties file.

heat.wellKnownPeersTest=176.9.102.212;95.85.4.150;146.185.154.55
heat.isTestnet=true

Recent Server updates:

The heatledger 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.
  • Server initialization is reorganized for embedded usage
  • Implemented more robust cross-OS server shutdown for desktop Heatwallet application using file signaling. Decreases or eliminates replicator db errors that contributed to long startup time in previous version
  • Removed extra console output about balances hash equality on blockchain scan and download.
Assets 5
Nov 6, 2018
Update README.md
  • v2.7.0
  • 509325f
  • Compare
    Choose a tag to compare
    Search for a tag
  • v2.7.0
  • 509325f
  • Compare
    Choose a tag to compare
    Search for a tag

@dmdeklerk dmdeklerk released this Sep 14, 2018 · 19 commits to master since this release

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
Assets 5
  • v2.6.3
  • 988c587
  • Compare
    Choose a tag to compare
    Search for a tag
  • v2.6.3
  • 988c587
  • Compare
    Choose a tag to compare
    Search for a tag

@dmdeklerk dmdeklerk released this May 30, 2018 · 20 commits to master since this release

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.

Assets 5
  • v2.5.0
  • 6e46a49
  • Compare
    Choose a tag to compare
    Search for a tag
  • v2.5.0
  • 6e46a49
  • Compare
    Choose a tag to compare
    Search for a tag

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

HEAT WALLET 2.5.0

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.

Includes

Windows, Linux and Mac OS versions.

Updates

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.

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.

Assets 5
  • v2.4.0
  • f4c7e28
  • Compare
    Choose a tag to compare
    Search for a tag
  • v2.4.0
  • f4c7e28
  • Compare
    Choose a tag to compare
    Search for a tag

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

HEAT WALLET 2.4.0

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.

Note

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

https://heatwallet.com/api/#/

HEAT SDK

https://www.npmjs.com/package/heat-sdk

Changes

  • 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
Assets 4
You can’t perform that action at this time.