Factomask



Offline



Activity: 108

Merit: 2







Jr. MemberActivity: 108Merit: 2 Re: HEAT Discussion and Technical info March 23, 2018, 06:47:53 PM #701 As I've encountered this project the other day from the other thread, I can say that it has positive vibes on me.

Checking the individuals who comprise the team and their partnerships will give you the impression that this will push through.

Though the supply is so huge but there's a valid reason on why such enormous amount.

Looking forward to another good project here.

Jiihaa



Offline



Activity: 104

Merit: 0







NewbieActivity: 104Merit: 0 Re: HEAT Discussion and Technical info March 23, 2018, 09:01:27 PM

Last edit: March 23, 2018, 09:14:41 PM by Jiihaa #705 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.





Jiihaa



Offline



Activity: 104

Merit: 0







NewbieActivity: 104Merit: 0 Re: HEAT Discussion and Technical info March 24, 2018, 10:44:10 AM #707 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 Hahha.. Nothing wrong with my keyboard.. Problem is finnish school systemNot 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



Offline



Activity: 69

Merit: 0







NewbieActivity: 69Merit: 0 Re: HEAT Discussion and Technical info March 26, 2018, 08:13:34 AM #708 Quote from: Jiihaa on March 24, 2018, 10:44:10 AM 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

Hahha.. Nothing wrong with my keyboard.. Problem is finnish school systemNot 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? 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



Offline



Activity: 418

Merit: 250





HEAT Ledger







Sr. MemberActivity: 418Merit: 250HEAT Ledger Re: HEAT Discussion and Technical info March 30, 2018, 03:38:39 PM #709 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



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



### 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. Hard fork set for blockwhich is somewhere around next Friday (April 6th).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 whena hardfork will take place.This version will perform a one time scan of the blockchain on startup.To install and run heatledger you need Java JDK 1.8 or higher installed, note thatJDK is different from standard java distributions.On ubuntu we use sudo apt-get install default-jdk package. For other platformsplease 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.First and foremost this release fixes the occasional forks that occurred and whichrequired node operators to do the regular rescans of the blockchain. Those rescansare not needed anymore as HEAT is now considered stable.HEAT is different from other crypto currencies because of its special custombuild storage engine. Our unique storage engine is what allows us to scale insize and speed. Building this engine however proved more difficult thanusing a one size fits all - off-the shelf - storage engine like every othercrypto out there.Our hard work however paid off which leads us to this stable and mature 2.5.0release.This version supports benchmark mode which allows you to participate in theupcoming HEAT Benchmark Competition. Instructions for this will follow butparticipating requires at the very least that you run a HEAT server. Once yourun a HEAT server on main net it will be easy to run a second HEAT serveron the same machine but on benchmark net.We are moving away from JSON as a transport mechanism and are instead adoptingthe binary AVRO encoding from HADOOP. One of the parts that makes it possibleto run a benchmark server which does many thousands of transactions a secondover 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 ourofficially supported HEAT-SDK https://www.npmjs.com/package/heat-sdk Transaction fees can be remotely raised or lowered by the developers without theneed to update the software. An incubation period of 24 hours is observed beforethe new fees take affect. This allows us to already lower the fees and raisethem again in case of misuse.This is a temporary measure. Once block file splitting is enabled we dont careabout this anymore since the chain can grow indefinitely from then on.We will start lowering the fees after the hard fork.While technically a part of the storage engine, it is worth mentioning that theunconfirmed transaction pool had a bug fixed which caused unconfirmed transactionsto be improperly rolled back. Leading to forks due to balance differences betweennodes.Use this setting to raise the number of rows returned from the various API's.This is enabled again by default, the virtual matcher matches orders and generatestrades in real-time based on unconfirmed transactions.Numeric account ids are included in account search and in every autocompletenow when sending transactions. https://heatwallet.com

Jiihaa



Offline



Activity: 104

Merit: 0







NewbieActivity: 104Merit: 0 Re: HEAT Discussion and Technical info March 30, 2018, 11:35:24 PM #711

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

verymuchso



Offline



Activity: 418

Merit: 250





HEAT Ledger







Sr. MemberActivity: 418Merit: 250HEAT Ledger Re: HEAT Discussion and Technical info April 03, 2018, 06:52:53 PM #716 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



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



### 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. Hard fork set for blockwhich is somewhere around next Friday (April 6th).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.Windows and Linux versions.Mac OS version will follow.Apart from the all important embedded server update this release contains dozens of fixes and improvements among some of the more notable are: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 whena hardfork will take place.This version will perform a one time scan of the blockchain on startup.To install and run heatledger you need Java JDK 1.8 or higher installed, note thatJDK is different from standard java distributions.On ubuntu we use sudo apt-get install default-jdk package. For other platformsplease 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.First and foremost this release fixes the occasional forks that occurred and whichrequired node operators to do the regular rescans of the blockchain. Those rescansare not needed anymore as HEAT is now considered stable.HEAT is different from other crypto currencies because of its special custombuild storage engine. Our unique storage engine is what allows us to scale insize and speed. Building this engine however proved more difficult thanusing a one size fits all - off-the shelf - storage engine like every othercrypto out there.Our hard work however paid off which leads us to this stable and mature 2.5.0release.This version supports benchmark mode which allows you to participate in theupcoming HEAT Benchmark Competition. Instructions for this will follow butparticipating requires at the very least that you run a HEAT server. Once yourun a HEAT server on main net it will be easy to run a second HEAT serveron the same machine but on benchmark net.We are moving away from JSON as a transport mechanism and are instead adoptingthe binary AVRO encoding from HADOOP. One of the parts that makes it possibleto run a benchmark server which does many thousands of transactions a secondover 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 ourofficially supported HEAT-SDK https://www.npmjs.com/package/heat-sdk Transaction fees can be remotely raised or lowered by the developers without theneed to update the software. An incubation period of 24 hours is observed beforethe new fees take affect. This allows us to already lower the fees and raisethem again in case of misuse.This is a temporary measure. Once block file splitting is enabled we dont careabout this anymore since the chain can grow indefinitely from then on.We will start lowering the fees after the hard fork.While technically a part of the storage engine, it is worth mentioning that theunconfirmed transaction pool had a bug fixed which caused unconfirmed transactionsto be improperly rolled back. Leading to forks due to balance differences betweennodes.Use this setting to raise the number of rows returned from the various API's.This is enabled again by default, the virtual matcher matches orders and generatestrades in real-time based on unconfirmed transactions.Numeric account ids are included in account search and in every autocompletenow when sending transactions. https://heatwallet.com

blockaudit



Offline



Activity: 34

Merit: 2



Helping the blockchain world build secure++ stuff!







Jr. MemberActivity: 34Merit: 2Helping the blockchain world build secure++ stuff! Re: HEAT Discussion and Technical info April 03, 2018, 11:33:54 PM #718



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:



!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. 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/jGPlKJyLIxIQuite a few bugs in there for March 2018.And FFmpeg does similarly with this page:Where they list CVEs fixed in each release. https://www.blockaudit.org