HEAT Discussion and Technical info

[dance]

If you need to discuss refunds instead of waiting for the gateway that'll eventually come please message HEAT 9583431768758058558

Your message in Heat from 21th of February:

I've kindly waited until "early next week" and "reminded" you week after.
You ignored my message.

It's in progress.

I'm hearing this for years since Fimk.

Just put a buy order for 10 BCH at current market price, and I will fill it. It's a one-minute task.

[1715057497]

1715057497

[1715057497]

1715057497

[1715057497]

1715057497

[1715057497]

1715057497

[1715057497]

1715057497

[memberberry]

If you need to discuss refunds instead of waiting for the gateway that'll eventually come please message HEAT 9583431768758058558

Your message in Heat from 21th of February:

I've kindly waited until "early next week" and "reminded" you week after.
You ignored my message.

It's in progress.

I'm hearing this for years since Fimk.

Just put a buy order for 10 BCH at current market price, and I will fill it. It's a one-minute task.

OMFG don't you spot the scam? I tell you how they fucked you over... "In case we can't pay you BCH we will then purchase your BCH tokens back FOR THE PRICE YOU PAID FOR THEM." You see there are 2 outcomes to this. Either the price goes down they will give you the BCH and they had no risk. In case BCH goes up they keep your BCH and will only install the gateway in case BCH goes below the price it was when you purchase. They will not install it before but they will try to purchase back the BCH tokens for the PRICE YOU PAID FOR THEM and make a nice profit. See how this is a scam? They can only win and you can only lose! As I described before, they could set up the BCH gateway in a few minutes as they already have a BTC gateway...

[Scout Georgenson]

I dismissed all the small things, can you reply how this one can affect on the cryptocurrency?

[Jiihaa]

Nice.. So eliphaz bch gateway is coming soon?

And friendly reminder about who is memberberry?
- maniac who posts ower 100 fud posts per month.
- he does it3-4 diffrent sites. With 3 diffrent names.
- hawe done it already several years.
- look at her posts.

[airgonomike]

Nice.. So eliphaz bch gateway is coming soon?

And friendly reminder about who is memberberry?
- maniac who posts ower 100 fud posts per month.
- he does it3-4 diffrent sites. With 3 diffrent names.
- hawe done it already several years.
- look at her posts.

Dude, what the hell is wrong with the letter "V" on your keyboard? 

[Jiihaa]

Hahha.. Nothing wrong with my keyboard.. Problem is finnish school system      Not enough english.  We spend  years to practise Sweden. Total shit language used only in sweden. I think it would be better if we used that time practising english or some other big language

[airgonomike]

Hahha.. Nothing wrong with my keyboard.. Problem is finnish school system      Not enough english.  We spend  years to practise Sweden. Total shit language used only in sweden. I think it would be better if we used that time practising english or some other big language

Eheh, well you're doing well in English... It's also important to practice your native language I suppose. Wouldn't be fun if everybody spoke the same language... or would it? 

[verymuchso]

HEAT 2.5.0 MANDATORY UPDATE - PLEASE EVERYONE UPDATE.

Hard fork set for block 1,245,000 which is somewhere around next Friday (April 6th).

Download available:

https://github.com/Heat-Ledger-Ltd/heatledger/releases/tag/v2.5.0

Heatledger 2.5.0

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.

[dance]

HEAT 2.5.0 MANDATORY UPDATE - PLEASE EVERYONE UPDATE.
n sending transactions.

Return me my BCH.

[Jiihaa]

Wow.. Sounds really good 
Troll memberberry still alive. I already was little bit afraid something happend to you.. Y hawent made 1000 troll bs posts this month 

[spendawgs]

Can we please get a link to download the full client for Linux rather than just the upgrade. Thanks

[spendawgs]

This link >>>>>>>>>>>>> https://github.com/Heat-Ledger-Ltd/heatwallet/releases <<<<<<<<<< 
needs to be updated to version 2.5. Or some instructions on how to use the updater for linux.

[Kazadar]

This link >>>>>>>>>>>>> https://github.com/Heat-Ledger-Ltd/heatwallet/releases <<<<<<<<<< 
needs to be updated to version 2.5. Or some instructions on how to use the updater for linux.

Its been a while since I used Linux, but I think you can do it the same way as on windows.
Stop the server, go the the heatledger folder that also contains the blockchain folder.
Delete everything but your heat.properties file (and blockchain if you dont want to resync).
Copy the new files to the heatledger folder and restart the server.

[alice.smith38]

 it's pretty interesting look no bad words for this thread 

[verymuchso]

HEAT 2.5.0 FULL CLIENT - WINDOWS & LINUX

Hard fork set for block 1,245,000 which is somewhere around next Friday (April 6th).

Download available:

https://github.com/Heat-Ledger-Ltd/heatwallet/releases/tag/v2.5.0

HEAT WALLET 2.5.0

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 and Linux versions.
Mac OS version will follow.

Updates

Apart from the all important embedded server update this release contains dozens of fixes and improvements among some of the more notable are:

• Visual warning when sending to non existing accounts
• Visual warning when sending to accounts without public key
• Correct display of virtual balance in account explorer (virtual balance includes trades based on unconfirmed transactions)
• Asset Exchange websocket order books updates got fixed, updates as well when no new order is added but just on trades
• You can switch to beta network from the about dialog now (beta net toolbar color is red) (for developers and beta net testers)
• Recipient auto complete includes all numeric account ids now

Heatledger 2.5.0

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.

[Flexatron]

Great work, installed like a breeze as always.

[blockaudit]

Question for the team regarding maintenance on the OSS dependencies shipping with Heat: ffmpeg, nodejs, etc.

Are you all keeping up to date with the latest versions, especially when one needs to be running the latest versions to be safe from attacks mitigated by their security fixes?

NodeJS for example drops details on releases containing security updates here:

https://groups.google.com/forum/#!topic/nodejs-sec/jGPlKJyLIxI

Quite a few bugs in there for March 2018.

And FFmpeg does similarly with this page:

https://www.ffmpeg.org/security.html

Where they list CVEs fixed in each release.

[spendawgs]

Thanks Dennis, saw the 2.5 full client.
awesome!
very excited about whats to come

[verymuchso]

Question for the team regarding maintenance on the OSS dependencies shipping with Heat: ffmpeg, nodejs, etc.

Are you all keeping up to date with the latest versions, especially when one needs to be running the latest versions to be safe from attacks mitigated by their security fixes?

NodeJS for example drops details on releases containing security updates here:

https://groups.google.com/forum/#!topic/nodejs-sec/jGPlKJyLIxI

Quite a few bugs in there for March 2018.

And FFmpeg does similarly with this page:

https://www.ffmpeg.org/security.html

Where they list CVEs fixed in each release.

Hi,

Thank you for your question.

We use Github's https://github.com/electron as a run time engine to host our custom built web client as desktop apps on Windows, Linux and Macs.

Before we build the client we make sure to always update and upgrade to the latest electron pre-built packages available for the major version against which we have build our client.
We did the same for this latest build.

Normally security issues and updates are always backported to each still supported Electron version and these are made available as an update which we are alerted by simply running the electron builder script. For this build and for any past build that was the case as well.

Unfortunately I believe it's close to impossible to always update all software against any zero-day exploit the day, week or month it comes out.

That said, parts like the FFmpeg and the pdf viewer that come standard with Electron are however by the nature of our client never touched or invoked. What I mean is you cant remotely play any video or audio file or open a pdf doc in HEAT client.

Your question did make us look better into keeping build dependencies up to date and its something we will be looking into in order to harden this aspect even more. So thank you for that!

[Jiihaa]

I hawe couple questions too.
Do y hawe any time schedule  fiat gateway, bch or some other  gateway?

I undrestand mobile wallet hawe some issues are they already fixed? And when we can wait it released?

And must say this project starting to look better day by day. Keep up the good work!