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

HEAT Forum

March 19, 2018, 04:47:00 AM
News: 2017-10-10 Heatledger 2.0 with Heatwallet 2.2.0 released! NOTE: Balance leasing and hard fork at block 777777

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.

Messages - Eliphaz

Pages: [1] 2 3 ... 12
General HEAT Discussion / Re: Ignis Release Date?
« on: March 11, 2018, 11:49:29 PM »
We can now access our IGNIS tokens and are technically able to send IGNIS withdrawals. Heatwallet update and the official usage of the gateway will still take a while.

General HEAT Discussion / Re: CAN NOT buy any Heat coins
« on: March 11, 2018, 11:48:25 PM »
Seems you found the faucet :)

It was paid on Jan 15th. Because of the Bitcoin network congestion, very high fees when a small number of withdrawals is sent at once, and the need for longer periods on the HEAT network for transactions to settle, sometimes withdrawals still take longer than 1-2 days. Please allow 3-4 days until inquiries.

HEAT Server issues / Re: Network status
« on: December 27, 2017, 09:51:03 PM »
Unstable network occasionally shows a small number of forgers. This is remedied with automatic fork resolution, or as in this more serious case, server software update.

HEAT Server issues / Mandatory hard fork release 2.4.0
« on: December 27, 2017, 09:46:39 PM »


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



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

General HEAT Discussion / Re: Transferred BTC out
« on: December 27, 2017, 08:12:03 PM »
BTC withdrawals currently experience longer processing times due to network instability.

Normally withdrawals are processed once a day so 24 hours or 30 hours isn't unusual.

HEAT Server issues / Re: Cannot sell HEAT or Withdraw BTC
« on: December 07, 2017, 11:02:35 PM »
Hi, we do monitor however are short of staff, thus it takes time to attend.

Your withdrawal had been skipped for some reason, it has now been paid.

I don't see any issue with your account. You have a pending sell order that nobody has bought for 3300 satoshi. Just cancel it and the HEAT will be back on your account, after which you can submit a new sell order, transfer them to other account, forge etc.

If that's not the case and we're missing something please chime in again. Thanks.

HEAT Markets and trading / Re: My FIMK didn't show up after deposit
« on: December 05, 2017, 04:00:44 PM »
it's been more than 15 days since my FIMK deposit to HEAT, and there is still nothing on my account, is this issue going to be resolved?
Yes it's going to be. FIMK deposits clear very slowly for the time being due to human resources being scarcely available, unfortunately.


Heatledger 2.1.0

This is a mandatory update, all nodes on the network need to run this version
or higher.

A hard fork will happen at block 870,000 at which we will update the block
version number, after that block older versions will not accept blocks from the
new fork and vice versa.

Nodes below 2.0.0 will automatically be blacklisted with this version.


To install and run heatledger server you need Java JDK 1.8 or higher installed, note that JDK is different from standard java distributions.

On ubuntu:

sudo apt-get install default-jdk

For other platforms look here

UPGRADE INSTRUCTIONS [upgrade only, new installations can ignore]

This version will perform a full rescan of the blockchain upon first use, this
happens automatically.

API Documentation

Please look here for API docs

List of updates/fixes/features.
one critical and two lesser bugs are fixed with this release. details of which will be released when the fork is complete.
the custom memory mapped storage maps for storing things like account balances or block ids are reduced in size, this saves several Gigabytes of storage needed in the blockchain folder
in case storage maps grow too big they will now automatically be resized



Wallet/desktop specific changes:

Fixed Join Slack link
Orderbook alignment adjusted
Fixed history entries display bug

General HEAT Discussion / Re: How to certified a new market?
« on: November 06, 2017, 11:11:21 PM »
Currently only markets operated by Heat Ledger Ltd can be certified by the house. For other types of certification, you may wish to test with the HEAT API at (no documentation, other than the interactive API, available yet unfortunately).

General HEAT Discussion / Re: OrgiOrg Leasing Pool
« on: November 06, 2017, 01:14:16 PM »
Well done guys in getting that fixed - sorry for the absence on this forum, too many areas to work on...

General HEAT Discussion / Re: OrgiOrg Leasing Pool
« on: October 31, 2017, 03:42:25 PM »
Invalid effective balance leasing: recipient account 9634482525377050118 not found or no public key published
The account should make a single outgoing transaction which will easily fix that.

how can i check if the server keeps pushing blocks?
Server log states for instance:

Pushed block 446739758241941207 at height 240935 received 2017-10-10 11:10:21 from

and you can see the latest blocks from your own server matching with

If the server keeps on going and pushing blocks, errors should be normal and expected.

any news?

after update from 2.0.0 to 2.2.0 i got a lot of errors in den server log

2017-10-10 12:26:11 [pool-5-thread-3] DEBUG c.heatledger.BlockchainProcessorImpl Didn't accept any blocks, pushing back my previous blocks
2017-10-10 12:26:11 [pool-5-thread-3] INFO c.heatledger.BlockchainProcessorImpl Pushed block 446739758241941207 at height 240935 received 2017-10-10 11:10:21 from [0 39211344265355 77627616425]
2017-10-10 12:26:12 [pool-5-thread-4] INFO com.heatledger.peer.PeerImpl Unblacklisting
2017-10-10 12:26:14 [pool-5-thread-2] DEBUG c.heatledger.BlockchainProcessorImpl Will process a fork of 719 blocks
2017-10-10 12:26:14 [pool-5-thread-2] DEBUG c.heatledger.BlockchainProcessorImpl Rollback from 240935 to 240934
2017-10-10 12:26:14 [pool-5-thread-2] INFO com.heatledger.persist.Persist Persist rollback to 240934
2017-10-10 12:26:14 [pool-5-thread-2] INFO c.heatledger.BlockchainProcessorImpl Popped block 446739758241941207 with height 240935
"com.heatledger.BlockchainProcessor$TransactionNotAcceptedException: Double spending transaction: 14455434550905911531 transaction: {\"senderPublicKey\":\"63a881ad93a588b86440aca966fa571f38fb6fec4017c9e326a285fe6d96e670\",\"signature\":\"3a781f07ee6f20ae91b097025b8a25f0b1b4296c45550ea2eb86795badc1490fe49d727051c2448e2cf4ed81ddd3daccea63aa507b657f0d014bb994ec1bb430\",\"feeHQT\":1000000,\"type\":2,\"version\":1,\"ecBlockId\":\"9631288308767843541\",\"attachment\":{\"quantity\":6800000,\"encryptedMessage\":{\"data\":\"3ef0bae446876bed9831aa1119a545e9efc988e2cde5f4a290a283b2cf9b8e430cea87b922f391a4b1da27af5ccecc80317a33c5d234aa1297c09f266f20bc9dd74cb8e0cd7e5aa07e8c970962abb52e\",\"nonce\":\"e620ed8f06af65dcdbea42120e9587186012ecb61e5bc359d9900593a2e07aa2\",\"isText\":true},\"version.EncryptedMessage\":1,\"version.PublicKeyAnnouncement\":1,\"recipientPublicKey\":\"2eb8137e3caefb6b14088107e96f02752b8e0ee685afea280587867119dff14d\",\"version.AssetTransfer\":1,\"asset\":\"5592059897546023466\"},\"subtype\":2,\"recipient\":\"9583431768758058558\",\"ecBlockHeight\":240915,\"deadline\":1440,\"timestamp\":107616637,\"amountHQT\":0}"
"\tat com.heatledger.BlockchainProcessorImpl.accept("
"\tat com.heatledger.BlockchainProcessorImpl.pushBlock("
"\tat com.heatledger.BlockchainProcessorImpl$1.processFork("
"\tat com.heatledger.BlockchainProcessorImpl$1.downloadBlockchain("
"\tat com.heatledger.BlockchainProcessorImpl$"
"\tat java.util.concurrent.Executors$ Source)"
"\tat java.util.concurrent.FutureTask.runAndReset(Unknown Source)"
"\tat java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)"
"\tat java.util.concurrent.ScheduledThreadPoolExecutor$ Source)"
"\tat java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)"
"\tat java.util.concurrent.ThreadPoolExecutor$ Source)"
"\tat Source)"
2017-10-10 12:26:14 [pool-5-thread-2] DEBUG com.heatledger.peer.PeerImpl Bl

Pages: [1] 2 3 ... 12