Please login or register.
Login with username, password and session length

HEAT Forum

March 15, 2017, 01:05:42 PM
News: 2017-02-08: New HEAT wallet is out! Download client + server from Github

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - Eliphaz

Pages: [1] 2
HEAT Server issues / Server update 0.9.21
« on: March 10, 2017, 10:05:47 PM »

Small bugfix release to resolve initial blockchain download issues

HEAT Server issues / Server 0.9.17 released
« on: March 06, 2017, 09:21:09 AM »
Heatledger 0.9.17

This is a mandatory update to get past block 97030 for fresh blockchain downloads.

Fixes a bug where two order cancellations for the same order were not properly handled.
The cancellation transaction was validated before the block was generated and both where
considered valid, but when the block was broadcasted to other nodes it was not accepted
since the first cancellation removed the order.

HEAT Wallet discussion / Wallet 1.0.10 and Server 0.9.14
« on: February 24, 2017, 11:12:48 PM »
Forging is enabled again for all. Rewards will be enabled when this proves stable.
Re-enabling rewards for blocks will require a hard fork.

New desktop release

New server release

HEAT Server issues / Mandatory update: Server 0.9.13
« on: February 21, 2017, 06:17:01 PM »
New server release 0.9.13

Heatledger 0.9.13

This is a mandatory update, all nodes should update.
In about 18 hours from the time of this release we will reach block 65,536 which is the moment the hardfork will be applied.

This release fixes the fact where we allowed order cancellations to exist for orders that have not yet been applied. This was most likely the main cause for earlier forks. This release also contains an addition to the legacy API, added was the GetBlock call.

This release also contains the preparations needed to better keep the replication database model (what is displayed in the AE) better in sync, it uses a new event dispatching mechanism which is directly bound to the binary balance, asset and order storage components which basically ensures that if something is written to or removed from the blockchain.
It is immediately updated in the optional replication database model, this should solve the wrong display of virtual (or real-time) balances.

HEAT Wallet discussion / Release: Heatwallet 1.0.1 with server embedded
« on: January 31, 2017, 10:35:20 PM »
A few minutes ago we've released the Client + Server Wallet package (preview) at

And new client at:

Asset exchange is preliminarily enabled for some asset types. Next version will enable all assets including the traditional ones of HEAT /Asset.

BTC/HEAT decentralized market should work.

Getting BTC in and out is centralized & experimental at this point and may incur delays.

Further release notes with instructions and more info will follow within some days.

The Forum / Trouble accessing the forum?
« on: January 30, 2017, 10:37:09 PM »
Does the forum load slowly for any of the users? Judging from the lack of posts today I figured that may be the case.

HEAT Server issues / Server 0.9.1 released - HARD FORK
« on: January 28, 2017, 08:51:44 PM »
Mandatory update

Heatledger 0.9.1

This is a mandatory update, nodes on 0.9.0 will be blacklisted.

Please update your versions to this new release.

During the start phase of heat you can expect a couple more of these mandatory
updates while we roll-out new functionality.

Couple of bug fixes in this release.

* heat.enableAPIServer=false was ignored, now the api server will not be
  enabled when you set this property to false
* fixed some strange behavior where the memory mapped hash map for the
  `whitelist-markets` was mapped against the file for the not yet enabled
  `whitelist-accounts`. account whitelisting will be enabled soon which
  allows an asset issuer to control which accounts are allowed to trade
  and receive privately issued assets.
* to ensure proper workings, at least during these first few versions we have
  made it the default that at startup the blockchain is scanned and validated
  by setting the configuration settings heat.forceValidate=true and
  heat.forceScan=true. a scan takes almost no time and guarantees all your
  blocks are in good shape when started. in case you have enabled the
  replication databases expect them to be cleared at the start of the
  scan an re-built. only the tables in the database that are managed by
  heat will be rebuilt if you are using the database for other purposes
  your own tables will be left alone.
* fixed a bug in the api, now it returns the real coinsupply
* fixed a bug where the blockchain could not be scanned successfully due to a test
  transaction we've sent at height 100.

HEAT Server issues / HEAT Server 0.9 released
« on: January 26, 2017, 10:25:21 PM »
The first downloadable server binary:

General HEAT Discussion / HEAT mainnet has been launched
« on: January 26, 2017, 06:25:19 PM »
We have the HEAT live mainnet now launched at

First blocks take time to come in as base target is normalized. This is standard for POS based releases.

POS + POP rewards are combined in the first release, disabled for the first 4320 blocks (1-2 days) to ensure p2p network stability and give time for people to set up servers for forging. We use one of the 500k dev accounts and a smaller one for initial forging (without rewards until block 4320) before which the dev accounts are removed from the forging power.

Client is unfinished but usable for transfers, messaging, and A2AE trading (technical prowess required until patches). It will begin to work much better when the blocks come in regularly and with some of the near future patch releases applied.

Client Github is currently being cleaned at - downloadables, servers & patches, release notes and more technical instructions will follow shortly.

The Forum / Forum Theme changed
« on: January 22, 2017, 08:23:48 PM »
The forum's default theme has been changed. Comments welcome.

Other Technical HEAT discussion / HEAT Genesis block data
« on: January 19, 2017, 02:24:15 AM »
The file in the following URL is going to be the genesis block data very soon unless nothing serious comes up. First column is the amount of HEATs the account will receive. Find your HEAT account and verify it's right. If you haven't made your HEAT account or it isn't present, it's possible to claim it after the HEAT tokens have been distributed.

General HEAT Discussion / HEAT Website makeup
« on: January 18, 2017, 09:16:19 PM »
Visual design for the website has been updated.

In preparations for HEAT token launch, Alcurex adjusted the 1.50x HEAT token multiplier yesterday Jan 17th.

Openledger 1.50x adjustment is imminent at 14.00 CET today.

C-CEX adjustment is still pending until further info.

Jobs / rewards / [BOUNTY 0.25 BTC] Comparison of HEAT vs. competitors
« on: December 05, 2016, 04:04:08 PM »
EDIT: Job completed - result visible at

We require a comparison chart of HEAT technology compared to some other crypto platforms, at least the following:

- Bitcoin
- Steem
- Ethereum
- Waves
- Ardor
- Bitshares

- Any others that promise to carry:

Asset-to-asset exchange
OR scalability of 100+ tps
OR sliced file blockchain

Required parameters for comparison: features, technology used (PoW, PoS, DPos etc.), actual tps max capacity, blockchain size, expected blockchain growth rate. We'll supply this info for HEAT.

Bounty: about 0.25 BTC or more, depending on the scale of work and paid after delivery, pdf invoice required

Written report / table needed within 7 days max. Reply to this thread to reserve the job.

General HEAT Discussion / HEAT Logo / Symbol advisory poll
« on: November 09, 2016, 04:36:19 PM »
Which of the following would you prefer to become the HEAT coin symbol and / or Heat Ledger Oy company logo? Please elaborate below. 2 votes allowed per participant. Poll results may or may not be used as advisory material by Heat Ledger Ltd when creating the company brand.

Symbols standardized to black and white and subject to changes.

Original suggestions in

Pages: [1] 2