Topic: HEAT Discussion and Technical info - page 19. (Read 61463 times)

The road map looks solid, but quite few people on the exchange and in social networks. Why so? The project looks really promising

The rewards will decrease at 1,250,000 + 4320.

So we'd have to wait a flew blocks still.

The reason is that the first rewards had been disabled during those first blocks since we were mining with company accounts to get the network stable.

The stage change for block 2,500,000 will be adjusted down to happen at block 2,500,000 again.

Correct, don't know why though.

No its still 8.

Wow already. Oh well I am very happy with my bag. Pretty sure i have added more than 10% to my total just from forging

Hard fork so far so good.

Heat block rewards decrease from 8 to 6 at block 1250000

https://heatwallet.com/#/explorer

The recent and ongoing changes in the regulatory landscape regarding tokens, share tokens in particular, have imposed further requirements to the whole business model of HEAT for which the HL share release on Heat Wallet is an entry case for the years to come. So we're working on the details of these corporate infrastructure and licensing arrangements. It's the most significant process affecting HEAT's business model and really needs careful design. If you've been following the scene you're aware of the changes in requirements, and the fact there exists no real leader with properly implemented structure for licensed crypto asset issuance in decentralized networks.

Fortunately the technology is being brought up to the required level meanwhile and 2.5.0 is a big step towards the rest of it on the tech side.

For visual layout not really, thanks. For modification of the current heatwallet.com design to responsive version, yes.
Apart from incompatibility with mobile devices, which parts of the Heatwallet.com exchange layout would you consider less than great?

Is there any updates regarding the IPO?

HEAT MAC OS Full Client

HEAT WALLET 2.5.0 now available for MAC OS.

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

Direct download: https://github.com/Heat-Ledger-Ltd/heatwallet/releases/download/v2.5.0/Heatwallet_MacOS_2.5.0.EXPERIMENTAL.zip

Installation

- Download the zip
- Drag the Heatwallet App to your app bar

Contents

Fully functional HEAT wallet for Mac OS.
Will work as thin client the moment you start it.
Go to server section and click Start Server to run your own HEAT server, closing the App will stop your HEAT server.

To run a permanent server please look at https://github.com/Heat-Ledger-Ltd/heatledger/releases/tag/v2.5.0

Best practice is to always back up your wallet to disk. (Top right side menu -> Backup wallet)

Do you guys need any help layouting your exchange?

I think a great design of the exchange could really help this project.

That's very good to know, thanks for the knowledgable response.

Sounds like you folks are ahead of the game in that way as many projects we come across either have no idea how up to date their dependencies are, let alone maintain a list of such dependencies to track and model their extended attack surface.

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!

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!

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

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.

Great work, installed like a breeze as always.

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.

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

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.