Please update your servers. Mandatory update!Heatledger 0.9.29 - The HEAT is on!Heatledger 0.9.29 This is a mandatory update, all nodes on older versions must update. While on [testnet]( https://github.com/Heat-Ledger-Ltd/heatledger-test) 7 other releases have come and gone please refer to testnet repo for details on those. This release fixes most if not all of the forking issues we experienced before plus it enables the new realtime websocket connectors already integrated in both the web and desktop clients. Forging rewards stay disabled. When this release proves to be stable we will put out another release which will enable forging rewards. This is to be expected by Friday 7'th of April. https://github.com/Heat-Ledger-Ltd/heatledger/releases/tag/v0.9.29
|
|
|
|
Server releasehttps://github.com/Heat-Ledger-Ltd/heatledger/releases/tag/v0.9.18Desktop releasehttps://github.com/Heat-Ledger-Ltd/heatwallet/releases/tag/v1.0.13Mandatory update will do a hard fork at 105,000. This release fixes several bugs and disables miner rewards at the fork height. In order to provide a better download experience when downloading the blockchain you will only download from the default wellknown peers, this way preventing you from ending on a fork again. Once the chain is downloaded in full you will connect to all peers on the network. A bug was fixed where unconfirmed bid order cancellations where not properly persisted to the data storage, causing both the virtual balance to be wrong and allowing a secondary order cancellation which would later not make it into a block but will mess with the replicator database model. The client now properly shows if an order is cancelled even if the cancellation is still unconfirmed, unconfirmed order cancellations are now shown with strike trough text until the next block fully removes them.
|
|
|
|
Heatledger 0.9.15 & Heatwallet 1.0.12 Mandatory update, this release will blacklist nodes that are on a version below heatldeger 0.9.15. Unconfirmed transactions in 0.9.15 and before (up to 0.9.14) where not removed properly when a block was generated. This release will properly remove these transactions. A bug some places referred to as the 50% bug was caused by this. Please update your nodes, especially if you are mining blocks. It will take some time for all 50% bug transactions to timeout before those are not seen anymore. We have seen that sometimes (probably due to network state) your blockchain download halts, we've found that if this is the case simply stopping and restarting will continue downloading the full chain. We'll be fixing this issue for the next release. Desktop:https://github.com/Heat-Ledger-Ltd/heatwallet/releases/tag/v1.0.12Server:https://github.com/Heat-Ledger-Ltd/heatledger/releases/tag/v0.9.16 |
|
|
|
How do I withdraw BTC from the wallet?
It says this... when you click the LOAD BTC button. BTC redemption (cashout) fee is 0.25%, minimum 0.001 BTC. Processing time 0-24 hours. To redeem your BTC asset for real Bitcoins, Click Transfer Asset from top right menu, choose Asset: BTC (5592059897546023466) Receiver: 9583431768758058558 and Amount: the desired cashout amount. Enter in payment message the desired Bitcoin address you want the Bitcoins to be sent. Do not enter anything else in the payment message. For any questions please contact support@heatledger.com |
|
|
|
Desktop releasehttps://github.com/Heat-Ledger-Ltd/heatwallet/releases/tag/v1.0.11Server releasehttps://github.com/Heat-Ledger-Ltd/heatledger/releases/tag/v0.9.15Contains heatledger 0.9.15. This is a mandatory update. Nodes below 0.9.14 will be blacklisted. We especially ask medium to large stake holders to switch to this version preferably also downloading the chain from the network. Heatledger server 0.9.15 will do a hard fork at block 87,000. The fork at 87,000 will change the way block generators validate order cancellations, the previous way that was done, in some cases, was a cause for forks. We've also changed the way public keys for accounts are stored and versioned, this was the other reason forks used to happen. With these two fixes combined we hope to have concluded the final solution for our forking issues. Given the expected stability of this version we also already have hard coded block height 100,000 at which forging rewards will start again. Work planned for these coming days might cause us to release another version before that but that will most likely be an optional release which only involves the replicator database parts. So installing this version should be enough to be able to start collecting block rewards again at block 100,000 which will be seen in about 5 days from now. The windows installer was switched to NSIS installer platform, it is highly advised that you uninstall any previous heat windows desktop software before installing this version.
|
|
|
|
We are ready to release 0.9.15 server and new (working) windows and linux desktop installs. Windows installer was changed to use NSIS which should give a better installation experience on windows. The order issues and public key problems have been fixed which will likely be the end of the forking woes. The planned release was about to enable miner rewards again at height 87,000 but this as you'll understand when reading on will need to be changed. Unfortunately the amazon cloud services are experiencing a major world wide outage at the moment which prevents us from uploading the installation files to github. Will retry in the morning. Track amazon cloud services status here https://twitter.com/awscloud |
|
|
|
New server release 0.9.13https://github.com/Heat-Ledger-Ltd/heatledger/releases/tag/v0.9.13Heatledger 0.9.13 This is a mandatory update, all nodes should update. In about 18 hours from the time of this release we will reach block 65,536 which is the moment the hardfork will be applied. - This release fixes the fact where we allowed order cancellations to exist for orders that have not yet been applied. This was most likely the main cause for earlier forks.
- This release also contains an addition to the legacy API, added was the GetBlock call.
This release also contains the preparations needed to better keep the replication database model ( what is displayed in the AE) better in sync, it uses a new event dispatching mechanism which is directly bound to the binary balance, asset and order storage components which basically ensures that if something is written to or removed from the blockchain. It is immediately updated in the optional replication database model, this should solve the wrong display of virtual (or real-time) balances.
|
|
|
|
Please read a properly formatted version here https://github.com/Heat-Ledger-Ltd/heatledger/releases/tag/v0.9.12Heatledger 0.9.12 This release fixes the proper handling of expired orders, for this a scan is required at start (which happens automatically) the scan will correctly release the locked unconfirmed asset and heat balances which should have been returned on order expiry. A fix has been applied to the unconfirmed balances storage, there is a built-in crash recovery mechanism which kicks in when heatledger suddenly shutsdown and is not allowed to properly write away all its data to the storage components. Although this happens rarely it is important for overall network consensus that even on lets say a power outage or hard exit on startup all the crash recovery parts function properly. It seemed the crash recovery for the unconfirmed transaction storage had a bug while parsing the binary recovery data. A fix to to the legacy API module (the extra NXT compat library) has been applied that fixes compatibility to the legacy getBlocks API call, results where in reverse order, not any longer. This is an intermediary release which is expected to be followed by one we're working on right now, during the 0.9.4 fork fixes, we had to drop a set of orders that could not pass the validation. Some of these orders however still hold unconfirmed asset and heat balances locked. The coming release will scan and correct these locked balances which should unlock affected balances. Until the 0.9.4 fix is complete and the unconfirmed transactions and network stabilization fixes in this release have proven to work correctly we are not enabling block generation and block or POP rewards. |
|
|
|
Skipping 0.9.10 here (since its only been some hours).. New server releaseBlacklist update (2) 0.9.11 Fixes one last instance of badly blacklisting overlooked in 0.9.10 https://github.com/Heat-Ledger-Ltd/heatledger/releases/tag/v0.9.11The release text for 0.9.10 was Heatledger 0.9.10.
Please update to this release.
It should solve the general blacklisting and misreported peer weight issues.
We need to see this one indeed fixes the blacklisting issues before we can enable forging for the public. |
|
|
|
My uncofirmed balances are not becoming confirmed still. For many days it is like this. Fixes doesn't fix that.
{"unconfirmedBalance":"30081395000","virtualBalance":"30081395000","balance":"330081395000","decimals":8,"id":"0","properties":""}
{"unconfirmedBalance":"92622170","virtualBalance":"92622170","balance":"117622170","decimals":8,"id":"5592059897546023466","properties":""}
So everything more than 300 HEAT and 0.92 BTC can't be moved, transfered, withdrawn, traded ("unsuffient balance" message).
"My Pending orders tab" is empty.
Now that transaction and blacklisting issues should be fixed. Balance display is up next. |
|
|
|
New server release.Heatledger 0.9.9 This is a mandatory update, all nodes on or below 0.9.8 will be blacklisted. This release fixes the issue with unconfirmed transactions not being accepted by other peers. Transactions can now be send and received over the network like before. We've introduced the Upgrader internal component, this helper component allows us to place version specific one time upgrade tasks in new releases. Mostly this will help in you keeping your blockchain and not needing to download it again. The upgrade function for this release will one time scan and validate your blockchain on startup. It could be you have been running 0.9.8 and are therefor blacklisted by other peers. This blacklisting should take no longer than 10 to 20 minutes. Forging has not yet been enabled for this release, if all goes well we'll enable forging and rewards again in the coming days. https://github.com/Heat-Ledger-Ltd/heatledger/releases/tag/v0.9.9New desktop versionsHeatwallet 1.0.8 contains heatledger 0.9.9 New desktop release to accompany the server release. https://github.com/Heat-Ledger-Ltd/heatwallet/releases/tag/v1.0.8
|
|
|
|
UPDATES!! Server and DesktopMinor update Now contains heatledger 0.9.7 which should improve log output and overall connectivity. We are aware of display issues with our real-time virtual balances in both the web and desktop clients, although the on-blockchain data is correct the virtual layer in some instances comes up with the wrong real-time balances which it displays for users. To overcome this issue instead of displaying the real-time virtual balance we now display the much slower 'real' blockchain balance. This however does not allow you to see the balance change as soon as you place an order, you'll have to wait for the next block for that. We hope to be able to fully analyze and fix the real-time virtual balance mechanism in the coming days. Serverhttps://github.com/Heat-Ledger-Ltd/heatledger/releases/tag/v0.9.7Full wallethttps://github.com/Heat-Ledger-Ltd/heatwallet/releases/tag/v1.0.6Thin client (no server included)https://github.com/Heat-Ledger-Ltd/heat-ui/releases/tag/v1.0.6
|
|
|
|
Minor update, includes 0.9.6 heatledger server Minor update, contains heatledger 0.9.6 which should improve network connectivity. Also a fix is applied so the load BTC button now works in the echange on the desktop version (the Windows version was giving problems). https://github.com/Heat-Ledger-Ltd/heatwallet/releases/tag/v1.0.5 |
|
|
|
Update, improves the network.. 0.9.6 Heatledger 0.9.6 Minor update, this version has the default configuration set to only connect to 0.9.5 nodes and higher. Also the standard practice of full rescan and validation is disabled since its probably not needed anymore. https://github.com/Heat-Ledger-Ltd/heatledger/releases/tag/v0.9.6 |
|
|
|
Heatledger 0.9.5 This is a mandatory update, all nodes on the network need to run this version or higher. * More forking fixes, we now better handle public key consensus height. Also added better checking for blocks received from peers that might lead to forks, blocks with transactions that dont explicitly include the sender public key are no longer accepted. * Enabled order cancelling again. * All nodes below 0.9.4 are automatically blacklisted * We advise to download the blockchain fully from the network. https://github.com/Heat-Ledger-Ltd/heatledger/releases/tag/v0.9.5Here we go |
|
|
|
|
Hi there.
We're putting out a new desktop and server version in the coming hour. Unfortunately we've had to hard fork again which given the current situation I've decided to not spend a week on again t o coordinate that in the most decentralized manner possible...
Gave this some thought and figured we are not yet the 7 year old bitcoin network with a world wide network of multi-billion dollar businesses connected to it.
We are in the super early stages of rolling a completely new consensus network that just needs fixes sometimes and they need to be applied fast.
To get it done quick we've decided to not built a lengthy migration solution like we did last time (and lost many days and other things because of that). Unfortunately because of this we had to roll back some blocks, the current network starts at 39652 and we are using the developer bonus account to mine on it.
Yes the same account, that is locked to block 1.250.000 and which i promised to donate all the forging awards back to the community.
Right now the hard fork is live and running on the company servers, to keep things fair i'll give a thirty minute heads up before we release the server code on github so everyone can start mining at the same time.
|
|
|
|
Heatledger 0.9.4This is a mandatory update, all nodes on the network need to run this version or higher. * Fixes have been applied that led to forks because of nodes not agreeing on what height a public key for an account was set. * We've also disabled cancelling of orders that have not yet been confirmed in a block. This functionality will come back but needs more work. * Public keys now have their own storage file which saves quite a lot of space since they dont need to be included in each account balance update (which caused one entry to be written to the account data version tracker file). Eventually we'll be able to get the accounts and account version tracker files to be much smaller (their size is so large because of pre- occupied space to hold at a minimum 250,000 accounts and all their versions over some 1400+ blocks, we expect to reduce the size of that by approximately 80%). * This release enables creating any kind of market as long as you own the asset for that market. * This release also enables the use of account email id's which you can register free of charge for new accounts created through either the web wallet or one of the downloadable desktop versions. * We've update the list of standard wellknown peers to almost 68 nodes now through the help of http://heatbrowser.com/report.html which is maintained by one of our community members (there is a donate address on that page!) Finally its advised to download the blockchain fully from the network. https://github.com/Heat-Ledger-Ltd/heatledger/releases/tag/v0.9.4
|
|
|
|
|
Announcement
We've completed the hardfork 0.9.4 version, Svante is in transit atm and when back tonight we'll go over it one final time. To be able to coordinate the update with everyone we'll put out the new 0.9.4 server version and the new desktop version tomorrow, we'll set the hard fork height some time in the future.
Svante will be coordinating with the biggest forgers on the network about update instructions.
The desktop version should come with account generator and if all goes well with the possibility to register your account name (which has the form of an email address).
These account names will be unique on the network, you have the choice to have your account name be public (so it will list in auto complete and all) or have it private and it will only show for people you've send a payment/message/txn to.
|
|
|
|
|
Show Posts
