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

HEAT Forum

December 29, 2017, 04:15:59 PM
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
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

Hi, XLM is an uncertified asset, so you need to contact the asset issuer for any questions about it.

Heat Ledger Ltd doesn't have anything to do with uncertified assets in the decentralized HEAT peer-to-peer network. Anyone can create any kind of assets, named anything, on the network. It's buyer beware, as displayed prominently in the orange notification banned on the Asset info section.

Hi everyone,
I bought some Stellar Lumen (XLM) at the heat wallet exchange and now I got stuck. Suddenly there is no possibility anymore to exchange HEAT/XLM. So how do I get my XLM out of the wallet? Any chance to withdrawal?

HEAT Wallet discussion / Heatledger 2.0.0 with Heatwallet 2.2.0 released
« on: October 10, 2017, 12:02:20 AM »
HARDFORK AT BLOCK 777,777 (Around October 22nd)

Heatledger 2.0.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 777,777 which is approximately two weeks from
the moment we do this release (somewhere around 2017-10-22).


The following applies **ONLY** if you run in 'non-light' mode. (when you've added `heat.replicatorEnabled=true` to your configuration).

While you can re-use your existing `blockchain` which can be found in the `blockchain` directory in your previous 1.1.0 installation.

You now need to DELETE THE DIRECTORY CALLED `heat_db` before starting heat 2.0.0, doing this will force HEAT to rescan the blockchain and rebuild its replicator database model.

API Documentation

Please look here for API docs

Balance Leasing

By sending a LEASE transaction you transfer your forging power (so thats your
effective balance or stake) to a different account.

The amount you lease is always your full stake at any given moment, you also
provide a period expressed in blocks after which the lease ends. The period has
to be between 1,440 and 300,000 blocks. 

While your stake is leased you can still move your HEAT to another account or
receive HEAT in your account. The same rules that applied before for how to
calculate your effective balance apply now. Whenever you add HEAT to your account
those funds will add up to your leased balance after 1440 blocks. At the same
time whenever you transfer HEAT out of your account that will immediately be
deducted from your leased stake.

An account to which balances are leased can start forging as usual, when determining
the account stake during block creation and broadcasting we add up all leased
stakes to come to that account current forging power.

After sending a LEASE transaction and before that lease period is over you can
send any number of follow up LEASE transactions each one overwriting your 'next lease'
which takes effect automatically the moment your first lease ends.

Use case for balance leasing is two fold.

    1. It allows accounts with small stakes to group together to form forging
       pools. This way increasing your chance of forging blocks.
    2. It's a security measure where you lease your (large) stake to a proxy
       account. Meaning you no longer have to expose your secret phrase of
       your main account to the server you use for foring blocks.

As is the case with forging blocks without leasing your balance, we require a minimum of
1,000 HEAT in order for your stake to be counted as leased stake.
List of updates/fixes/features.

- fixed placeAsk, placeBid unknown asset bug
- replicator model schemas now support MYSQL
- new replicator schema version manager based on external property files, please
  see 'resources' directory for all sql schemas
- server side order book running total and sum calculations
- changed the default logger to daily rollovers, logs are archived for 30 days
  and automatically deleted
- forger rewards are traced by a new replictor
- forger rewards can be returned by the API
- order cancellations are now traced by a new replicator, now the UI can display
  order cancellation details including asset, currency, quantity and price
- blocks generated per account are now traced in a new replicator and are availble
  in the UI and from the API
- improvements/optimizations of replicator SQL and where needed combining SQL
  based solutions with custom caching solutions. this is an ongoing process,
  major updates to the way we deal with our rather unique replicator mechanism
  are to be expected
- thread safety improvements

When the hard fork happens only servers running this version or higher will be
able to connect.




General HEAT Discussion / HEAT sitrep Oct 2017
« on: October 02, 2017, 05:21:58 PM »
Update on the progress achieved during the 3rd quarter of 2017; Most work done during this period is still at this moment invisible outside the company and thus progress may seem slow. However several of our development routes are nearing completion / release phase. Q4 thus looks quite crowded on HEAT related news starting from approx. mid-October if not earlier.

- Microservices (DAPP - decentralized applications 100% complete) release pending preparation of functional samples (5% complete)
- HEAT SDK client side libraries were released at to help with applications and eg. microservices
- Certified Assets BCH and IGNIS were made available on the HEAT gateway during Q3. @gh2 added Bismuth although not certified, well usable and trusted. BTC/Renmimbi pair was added by a Chinese community member, implicating scaling up trading on Chinese market, however further info isn't available.
- Accounting for FY 2016-2017 ending July 31st is still in progress. Figures will be made available for the Heat Ledger Ltd options issuance and public equity sale, currently planned by the end of 2017.
- Balance leasing is 100% complete, pending server release until UI has been modified to accommodate for leasing data and block stats. Network wide mandatory hard fork will be scheduled to enable balance leasing.
- Updates of UI to v2.1.0, including ident data for orders and past trades, leasing
- Nearly half of Q3 was spent on EUR token gateway arrangements and software, now 90% complete, design and branding integration ongoing.
- Mobile HEAT Wallet app on Android prototype has been tested, feature limited alpha with Send HEAT, Create / Import account and Blockchain explorer functionality will be available shortly
- Joint Venture on interesting 3rd party use case should be announced pretty soon. Demo version of the app working on HEAT blockchain has been demonstrated to us
- Joint Venture with a small financial institution seeking to use HEAT blockchain as systems backend and source funding through ITO on HEAT has progressed to contract evaluation phase
- Crowdfunding licensing process has been entered into.
- Unified HEAT web portal is under development
- Improved BTC gateway with automated and more secure handling of user BTC, involving hardware setup and processes is approx. 70% complete. When complete, the model can be used for several crypto gateways including Eth.

The HEAT support email hasn't been able to cope well on serving requests. If you have urgent matters, please use private messaging directly to me on Bitcointalk, or Slack.

General HEAT Discussion / Re: Heat from Fimk
« on: September 21, 2017, 11:47:28 AM »
downloaded the new fimk wallet after i claime my heat in november 2016 ... i see the some HEAT which i get for my FIMK ... but there was a problem in the 0.1.1 wallet with the NXT redemption; i never get a small account of NXT to verify my address ... so some of my HEAT are still missing ... can you help me Eliphaz?
Please send me a private message with all the details including your account numbers, amounts, dates, transaction ids.

Pages: [1] 2 3 ... 12