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

HEAT Forum

May 23, 2018, 10:01:51 PM
News: 2017-10-10 Heatledger 2.0 with Heatwallet 2.2.0 released! NOTE: Balance leasing and hard fork at block 777777 https://github.com/Heat-Ledger-Ltd/heatwallet/releases

Recent Posts

Pages: 1 ... 8 9 [10]
91
HEAT Server issues / Re: Stuck BTC withdrawal
« Last post by VonGraff on December 03, 2017, 08:29:21 PM »
The transaction you are referring to does not exist if I search for it on heatwallet. This could happen since it was done yesterday (December 2), when there was a minor issue on the blockchain (rounding off issue for a single transaction) which impacted the chain. This has been solved rather quickly by the devs. You could try withdrawing the BTC again.
92
HEAT Server issues / Re: Cannot sell HEAT or Withdraw BTC
« Last post by VonGraff on December 03, 2017, 08:27:29 PM »
I expect that this was caused by the issues which were happening throughout the full day of December 2. In the evening the devs released a new server version which fixed a minor issue screwing up the transactions on the chain. Can you check again whether there are still issues now?
93
General HEAT Discussion / Re: Heat server 2.2.0 - Mandatory update
« Last post by verymuchso on December 03, 2017, 04:37:56 PM »
Windows and Linux desktop client, with server..

HEAT Wallet 2.3.0

These are the desktop clients with updated server embedded.

https://github.com/Heat-Ledger-Ltd/heatwallet/releases/tag/v2.3.0
94
General HEAT Discussion / Heat server 2.2.0 - Mandatory update
« Last post by verymuchso on December 02, 2017, 11:59:40 PM »
Heatledger 2.2.0

This is a mandatory update, all nodes on the network need to run this version
or higher.

Nodes below 2.1.0 will automatically be blacklisted with this version.

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 https://heatwallet.com/api

List of updates/fixes/features.

- fixes bug involving the last hard fork and the way expired orders are handled

Download here:

https://github.com/Heat-Ledger-Ltd/heatledger/releases/tag/v2.2.0
95
HEAT Server issues / Stuck BTC withdrawal
« Last post by ragtag on December 02, 2017, 10:22:38 PM »
hey guys, why is it taking long to withdraw? I don't even see this transaction on the bitcoin blockchain? Could someone please look into it?

thanks
rt


Transaction: 9951321665214887115
 Object
signature: "b3ae2b006bce47eb8ce072f61f17d671fda6439754572584f90563574e1fb806594c479d90acdf406ae036a6b1575f74474e0e0b26d0a481cc5645439cca3ac3"
fee:  "1000000"
transactionIndex: -1
type: 2
ecBlockId:  "13305579258806670734"
signatureHash: "9fd6dd9f928ff7f6b4527ff4b07df5a7b461b6da7d64c4f05c8796e8b9484f11"
 attachment: Object
messageIsEncrypted: true
subtype: 2
messageIsText: true
block:  "0"
blockTimestamp: -1
deadline: 1440
timestamp: 126932297
height: 2147483647
senderPublicKey: "4a96dce5375a8f4e0ab12f1625da0d0e32690ab1630d123ac7337e1eb6437e05"
amount:  "0"
messageBytes: "4f488608d6b94ac6c12817b5a8f264e93d90371eae8b4b1fc3f578c09769d49e4af94bd1f9421c44c8afc66af46f4f0160755d8900652debb2dc39a188b614559c603b2f83d60ba85c7d134ee7e3d2b2ae0314d42b47041a0a90174bdf57dc301144777cf0158ed285f2ac34c24161cb"
recipientPublicKey: "2eb8137e3caefb6b14088107e96f02752b8e0ee685afea280587867119dff14d"
confirmations: -2146599615
fullHash: "cb34c88454321a8aaef89d8a409327381bbbb6486f3236d4cfb000a7ad119bba"
version: 1
recipientPublicName:  "Heat Ledger Ltd"
sender:  "3618719189254554333"
recipient:  "9583431768758058558"
ecBlockHeight: 883979
senderPublicName: null
transaction:  "9951321665214887115"
time:  "2017-12-02 08:58:17"
heightDisplay:  "*"
renderedInfo: "<b>TRANSFER ASSET</b> <b>BTC</b> from <a href="#/explorer-account/3618719189254554333/transactions">3618719189254554333</a> to <a href="#/explorer-account/9583431768758058558/transactions">Heat Ledger Ltd</a> amount <span>0.00719380 </span>"
messageText:  "1Nq8iPnQjrHwpXT1AYAHTM4mts1HqgpHC9"
messagePreview:  "1Nq8iPnQjrHwpXT1AYAHTM4mts1HqgpHC9"
96
HEAT Server issues / Re: Cannot sell HEAT
« Last post by ragtag on December 02, 2017, 08:35:24 PM »
Another BTC withdrawal that is stuck

Transaction: 9951321665214887115
 Object
signature: "b3ae2b006bce47eb8ce072f61f17d671fda6439754572584f90563574e1fb806594c479d90acdf406ae036a6b1575f74474e0e0b26d0a481cc5645439cca3ac3"
fee:  "1000000"
transactionIndex: -1
type: 2
ecBlockId:  "13305579258806670734"
signatureHash: "9fd6dd9f928ff7f6b4527ff4b07df5a7b461b6da7d64c4f05c8796e8b9484f11"
 attachment: Object
messageIsEncrypted: true
subtype: 2
messageIsText: true
block:  "0"
blockTimestamp: -1
deadline: 1440
timestamp: 126932297
height: 2147483647
senderPublicKey: "4a96dce5375a8f4e0ab12f1625da0d0e32690ab1630d123ac7337e1eb6437e05"
amount:  "0"
messageBytes: "4f488608d6b94ac6c12817b5a8f264e93d90371eae8b4b1fc3f578c09769d49e4af94bd1f9421c44c8afc66af46f4f0160755d8900652debb2dc39a188b614559c603b2f83d60ba85c7d134ee7e3d2b2ae0314d42b47041a0a90174bdf57dc301144777cf0158ed285f2ac34c24161cb"
recipientPublicKey: "2eb8137e3caefb6b14088107e96f02752b8e0ee685afea280587867119dff14d"
confirmations: -2146599615
fullHash: "cb34c88454321a8aaef89d8a409327381bbbb6486f3236d4cfb000a7ad119bba"
version: 1
recipientPublicName:  "Heat Ledger Ltd"
sender:  "3618719189254554333"
recipient:  "9583431768758058558"
ecBlockHeight: 883979
senderPublicName: null
transaction:  "9951321665214887115"
time:  "2017-12-02 08:58:17"
heightDisplay:  "*"
renderedInfo: "<b>TRANSFER ASSET</b> <b>BTC</b> from <a href="#/explorer-account/3618719189254554333/transactions">3618719189254554333</a> to <a href="#/explorer-account/9583431768758058558/transactions">Heat Ledger Ltd</a> amount <span>0.00719380 </span>"
messageText:  "1Nq8iPnQjrHwpXT1AYAHTM4mts1HqgpHC9"
messagePreview:  "1Nq8iPnQjrHwpXT1AYAHTM4mts1HqgpHC9"
97
HEAT Server issues / Cannot sell HEAT or Withdraw BTC
« Last post by ragtag on December 02, 2017, 04:29:54 PM »
hi,

 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

Object
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:  ""
98
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?
99
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.
100
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!
Pages: 1 ... 8 9 [10]