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

HEAT Forum

March 19, 2018, 04:59:40 AM
News: 2017-10-10 Heatledger 2.0 with Heatwallet 2.2.0 released! NOTE: Balance leasing and hard fork at block 777777

Recent Posts

Pages: 1 ... 8 9 [10]
HEAT Server issues / Cannot sell HEAT or Withdraw BTC
« Last post by ragtag on December 02, 2017, 04:29:54 PM »

 I put in a request to sell and the Heat is not sold but it is also not showing up on my balance. Could you tell me why this is so? Is there a way to cancel the order? It shows as crossed out on the sellers list. What does this mean?

 Here is the info on the transaction

senderPublicKey: "4a96dce5375a8f4e0ab12f1625da0d0e32690ab1630d123ac7337e1eb6437e05"
amount:  "0"
signature: "ed3f841137e9c61a2ef015885db8078897b1af030451bd297efaec52d843c106a111b501a6e45ceae3a18de3612384c167ea0213df84ea35d858c87f15683b22"
fee:  "1000000"
transactionIndex: -1
type: 2
confirmations: -2146599707
fullHash: "f0c01c07d4d6e1664946392f0f025b05e10e2e9b73c252a8243022dfceb5cc2d"
version: 1
recipientPublicName: null
ecBlockId:  "540679016385846829"
signatureHash: "e3c6dfa7510ab7a1103bdadd456869ac5a9dcfadddbb43937910919d8063af61"
 attachment: Object
subtype: 3
sender:  "3618719189254554333"
recipient:  "0"
ecBlockHeight: 882681
block:  "0"
blockTimestamp: -1
senderPublicName: null
deadline: 1440
transaction:  "7413442667769282800"
timestamp: 126894609
height: 2147483647
time:  "2017-12-01 22:30:09"
heightDisplay:  "*"
renderedInfo: "<b>SELL ORDER</b> <a href="#/explorer-account/3618719189254554333/transactions">3618719189254554333</a> placed sell order <b>BTC</b>/<b>HEAT</b> amount <span>6,587.00000000 </span> price <span>0.00003300 </span>"
messageText:  ""
messagePreview:  ""
HEAT Markets and trading / Re: My FIMK didn't show up after deposit
« Last post by xartifex on December 02, 2017, 08:55:17 AM »
Guys, still, who can I contact regarding my FIMK deposit, which is stuck in limbo?
General HEAT Discussion / Core development update
« Last post by verymuchso on December 01, 2017, 12:19:20 PM »
The reason we needed the hard fork so badly was because of a bug.

It turned out through a not so obvious coding error that when you'd send HEAT to yourself it would incorrectly affect your forging stake. Not your spendable balance, only the amount of stake considered by the protocol.

What went wrong was that where a transaction comes in and is first processed two objects where instantiated, one for the sender account and one for the recipient account. These objects are passed on to lower level operations where depending on the transaction types these account objects are updated and these updates are recorded to a versioning mechanism.

What happened was that when the objects where first created some initial balance info was kept in object memory and when we first saved the sender object and later the recipient object, it turned out that updates to the first where not available to the second.

Solution was to check if sender and recipient are equal and simply instantiate a single object.

The fork was kindof difficult since we could not foresee if anyone would trigger this in between us releasing the update and the fork height. To deal with this at the fork height we had to make a scan of the blockchain (which luckily can do that in about a second) to search for offending transactions and correct the account stake for those accounts.

All in all the effect has been that just some of these payments have occurred and always with low amounts, the single large transfer was reported to us and we did the fork within the week.


Apart from this work has been progressing on finalizing the microservices, lets call it version 2. The main difference being that the usage has been greatly simplified, the api as published in heat-dev-kit will remain the same for the most part but some of the more difficult aspects are handled by the heat platform now and dont need any work on the part of the microservice author.

Its hard to describe this in a few words, but I'll try anyway..

Because of the nature of a decentralized consensus network, basically being decentralized, it can happen that the order of transactions differ at different points in the network. Since microservices are invoked through transactions a microservice had to be aware of this fact. Another aspect of a blockchain is that blocks get generated and accepted at some point, while at a later moment a better block could come along which required the old one to be undone and the new one to be applied, this also had to be handled by your microservice.

These two things are handled now by a transaction cache solution which is at the heat core, this cache ensures transactions are reported to your microservice only once and in case the order of transactions changes only the transaction that has shifted position is reported to your microservice.

The cache is also persisted to disk so that when you redownload the blockchain or rescan it, your microservices are not invoked again.

Off to slush now for the second day in a snowy Helsinki.
General HEAT Discussion / Re: slack invitation failed
« Last post by VonGraff on November 28, 2017, 10:07:42 PM »
guys, I'd like to join slack channel too.

There seem to be issues with the user cap in Slack as well as some other annoying stuff, hence some community members are currently looking into alternatives, such as Riot. Hoping that there will be proper updates soon!
HEAT Markets and trading / Re: My FIMK didn't show up after deposit
« Last post by VonGraff on November 28, 2017, 10:05:53 PM »
is the community dead?

No, the Slack is not. But that has issues with the user cap, hence alternatives are being checked as we speak.

If you refer to this forum: agree with you that the forum is hardly used...
General HEAT Discussion / Re: slack invitation failed
« Last post by xartifex on November 28, 2017, 04:53:06 PM »
guys, I'd like to join slack channel too.
HEAT Markets and trading / Re: My FIMK didn't show up after deposit
« Last post by xartifex on November 27, 2017, 08:50:32 PM »
is the community dead?

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 Markets and trading / Re: My FIMK didn't show up after deposit
« Last post by xartifex on November 26, 2017, 07:56:18 PM »
Previous deposit reached my wallet in 2 weeks, I hope the next one will be faster
Does anyone know who can address this issue with deposit delays?
HEAT Server issues / Re: Can't Forge From Windows GUI
« Last post by Miner2525 on November 26, 2017, 03:14:09 PM »
The invite limit for the Slack has been reached.  Can you fix?
Pages: 1 ... 8 9 [10]