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

HEAT Forum

August 19, 2019, 08:28:10 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.

Topics - Eliphaz

Pages: [1] 2 3
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


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

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.

HEAT Markets and trading / IGNIS ICO available on
« on: August 07, 2017, 06:55:23 PM »
The first batch of 500k IGNS tokens (IGNIS ICO) are now available for purchase and trade on HEAT Decentralized Asset Exchange

Prices start from 1 HEAT (~2 NXT) each. Heat Ledger Ltd holds 4 Million NXT and will be receiving a minimum of 2 Million IGNIS when they're distributed. Those who purchase the token from the HEAT IGNS pre-sale will be able to withdraw their tokens shortly after the IGNIS blockchain is released.

Bitcoin Cash (BCH, Bitcoin fork) trading is now available on Heatwallet.

BCH Deposits and Withdrawals will be enabled during the next days / weeks.

General HEAT Discussion / HEAT sitrep July 2017
« on: July 11, 2017, 12:14:23 AM »
Brief HEAT sitrep:

A few days ago the Dutch bank ABN AMRO 3-month [disruption bonding] project was concluded. A fairly impressive MVP / demo was implemented by Heat Ledger Ltd for P2P forex trading and capital markets platform for a spinoff project on a sizable blockchain incubator department of ABN. During the closure party I remember seeing a slide about a study where ABN was ranked as the Europe's 1st disruptive / innovative bank. I don't doubt that, as the atmosphere during the program has been really outgoing indeed considering we're working with a large, traditional continental bank.

Short recap video from the event: (HEAT lead dev @verymuchso spotted at 0:42 and both of us cheering on stage at the end scene. :) )

During the project (which wasn't full time of course, as Heatwallet 2.0 was also released during it) we received excellent corporate banking contacts - further banking structures are now pursued for various token arrangements regarding the significant regulatory requirements that according to my knowledge will be affecting all cryptocurrency wallet operators and many cryptos as well within the EU during 2018. Wallets and cryptos not taking action already will likely be in trouble by then. I can't yet disclose exact details of what I know, but the info should be publicly available although not pushed by the media.

Commercialization of the ABN AMRO P2P forex trading platform will be pending for the next months while the bank's department goes through massive reorganization. This suits us well, as we need to now deploy resources to other parts of the HEAT roadmap.

Effort is now being put to the long overdue licensed EUR tokens on the HEAT blockchain for our major customer and JV partner, concurrently improving the scalabililty of the p2p network that was already under dire stress recently during 3rd party launch of the first, massively successful XEL token trading facility. On Heat Wallet, anyone can launch trading and gateways for any new cryptocurrencies, however be aware that we do take dire measures against scam assets to the extent possible within platform that's still semi-decentralized and for all practical purposes largely within the company's centralized control.

Messaging feature improvements (with off-chain FREE encrypted messaging), balance leasing and microservices mainnet release will certainly be the technical highlights of HEAT for the 2nd half of this year. Tokenized company options and real Heat Ledger Ltd share tokens on the HEAT platform will be our response as the next step for the ETH ICO vapor buzz that I expect to be gradually fading out during the the later half of 2017. For the stock sale we'll however be gladly accepting all the excess capitulated Eth that should be floating around by then. The timing for the share sale still needs to be considered - serious crypto consolidation and bear market isn't exactly the optimal time for such operation. At last our decided and criticized restraint in planning the exact times for phasing in various parts of the full HEAT plan is yielding fruit in form of major market timing flexibility.

HEAT Wallet discussion / New Heat Wallet user interface
« on: June 28, 2017, 05:19:37 PM » now has new UI design installed. Click CTRL+F5 to update your browser cache.

New Heatwallet release with improved server and client will follow soon.

General HEAT Discussion / HEAT Roadmap
« on: June 10, 2017, 09:50:13 AM »
Fresh HEAT roadmap below.

Heat Ledger Ltd / Heat Ledger at Moneyfintech 2017 Helsinki event
« on: May 17, 2017, 03:21:06 AM »
Presenting HEAT and cryptocurrencies for the bankers at

General HEAT Discussion / HEAT R&D Lab sneak peek
« on: May 03, 2017, 12:43:07 PM »
New HEAT aluminium badges from our new employee

(Old stuff, but unpublished, elsewhere in the photo) :)

Brief technical situation update:

After negotiations and enrolling events during the past week with ABN AMRO bank, which is the 3rd largest bank in The Netherlands, they've chosen us for their disruptive high tech program embracing a fairly extensive yet carefully selected list of fintech companies with whom they intend to get ahead competition in the adoption of blockchain and other disruptive technologies closely related to the banking field.

That progression of events is highly desired and fits HEAT perfectly - in that our next step would've in any case been the deployment of microservices. Microservices is an unique feature of HEAT, as described by the lead developer Dennis in the following words in our many banking / fintech contact meetings:

The big issue with creating custom blockchain applications for your organisation is that in most cases you'll need skilled blockchain developers, which are hard to come by. With micro services all you need is one of your own programmers who is able to write one or more TypeScript scripts. The scripts are able to react to all the things that happen on the blockchain by simply registering an event listener, they can also do everything you can do on heat (send money, message, place order etc). Finally from a micro service you can connect to any other system or database in your organization through standard methods.

HEAT microservices, enhanced with our unique replicator model for external RDBMS such as Mysql, DB2, H2 or Berkeley, allow anyone to implement BaaS services in the HEAT public blockchain, and specifically they allow us Heat Ledger Ltd to deploy customized duplicates of the HEAT technology into corporate environments without dedicated personnel to service blockchain software in particular. This is the model we're going to develop into full fruitition while delivering the pilot solution for ABN AMRO's needs during the next 100 days, thus yielding us 3x leveraged benefit:

- Completion of the possibly highly lucrative bank co-op project
- Streamlined general corporate solution deployment model, and
- Considerable feature enhancement for the public HEAT blockchain

The high HEAT tps figures advertised are fit for HEAT blockchain internal corporate use already. Whereas even the highest speed data network lag between various continents of the earth AFAIK makes it impossible to disseminate p2p data globally at speeds higher than well under 20 tps in the best case scenario, the goal for the public HEAT chain of guaranteed 1000 tps 24/7 is actually designed to not be dependent on node communication lag.

Due to the replicator infrastructure as described in the HEAT White Paper we can use single node pre-matching and broadcast the bulk pre-matched tx batch to p2p network at regular intervals with sophisticated ordering automation handling any race conditions or frontrunning situations. This is some near future (~6-12 months) development that goes along with the restructuring of the p2p traffic to binary messaging (Akka). The current HEAT model allows us to deploy high speed pilot projects for organizations like ABN AMRO, as corporations use private blockchain configuration in closed environment with either single matching node or very high speed dedicated / cloud server network capable of reaching 50+ tps levels even on realtime p2p basis.

We've got to resolve some public key issues for full blockchain rescan before the new server release for enabling HEAT block rewards is made available. The block rewards are expected to be re-enabled when that's sorted out, which should happen during the weekend or shortly after. Interest towards HEAT and trading has been improving sharply during the past days and is expected to keep doing so when the block rewards are enabled.

Testnet only server release:

Please use the HEAT testnet to test trading, forging and asset related operations. The same data as your livenet account works, however if you need any test HEAT tokens just ping us with your testnet HEAT account number and we'll send some. You can access testnet on  -> top right menu -> About HEAT -> Go to test net. Making trades, cancelling orders etc. and reporting any bugs is of significant benefit to test network functionality, however it's even more useful for debugging to run your own testnet server from fresh testnet release from and do some forging and trading through your own testnet server node. You can use the downloadable heatwallet with your own testnet node by replacing the "heatledger" server installation with that of the github testnet zip package. We'll pay modest rewards for bugs reported (write up your reports so you'll be able to claim rewards later).

Thanks for any assistance in getting the live HEAT Decentralized Asset Exchange into working condition sooner with the community's help!

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

Pages: [1] 2 3