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

HEAT Forum

November 22, 2017, 11:21:44 AM
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
Pages: [1]   Go Down

Author Topic: Heatledger 2.0.0 with Heatwallet 2.2.0 released  (Read 263 times)

Eliphaz wrote Heatledger 2.0.0 with Heatwallet 2.2.0 released on October 10, 2017, 12:02:20 AM
HARDFORK AT BLOCK 777,777 (Around October 22nd)

Heatledger 2.0.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 777,777 which is approximately two weeks from
the moment we do this release (somewhere around 2017-10-22).

UPGRADE FROM 1.1.0

The following applies **ONLY** if you run in 'non-light' mode. (when you've added `heat.replicatorEnabled=true` to your configuration).

While you can re-use your existing `blockchain` which can be found in the `blockchain` directory in your previous 1.1.0 installation.

You now need to DELETE THE DIRECTORY CALLED `heat_db` before starting heat 2.0.0, doing this will force HEAT to rescan the blockchain and rebuild its replicator database model.

API Documentation

Please look here for API docs https://heatwallet.com/api

Balance Leasing

By sending a LEASE transaction you transfer your forging power (so thats your
effective balance or stake) to a different account.

The amount you lease is always your full stake at any given moment, you also
provide a period expressed in blocks after which the lease ends. The period has
to be between 1,440 and 300,000 blocks. 

While your stake is leased you can still move your HEAT to another account or
receive HEAT in your account. The same rules that applied before for how to
calculate your effective balance apply now. Whenever you add HEAT to your account
those funds will add up to your leased balance after 1440 blocks. At the same
time whenever you transfer HEAT out of your account that will immediately be
deducted from your leased stake.

An account to which balances are leased can start forging as usual, when determining
the account stake during block creation and broadcasting we add up all leased
stakes to come to that account current forging power.

After sending a LEASE transaction and before that lease period is over you can
send any number of follow up LEASE transactions each one overwriting your 'next lease'
which takes effect automatically the moment your first lease ends.

Use case for balance leasing is two fold.

    1. It allows accounts with small stakes to group together to form forging
       pools. This way increasing your chance of forging blocks.
    2. It's a security measure where you lease your (large) stake to a proxy
       account. Meaning you no longer have to expose your secret phrase of
       your main account to the server you use for foring blocks.

As is the case with forging blocks without leasing your balance, we require a minimum of
1,000 HEAT in order for your stake to be counted as leased stake.
       
List of updates/fixes/features.

- fixed placeAsk, placeBid unknown asset bug
- replicator model schemas now support MYSQL
- new replicator schema version manager based on external property files, please
  see 'resources' directory for all sql schemas
- server side order book running total and sum calculations
- changed the default logger to daily rollovers, logs are archived for 30 days
  and automatically deleted
- forger rewards are traced by a new replictor
- forger rewards can be returned by the API
- order cancellations are now traced by a new replicator, now the UI can display
  order cancellation details including asset, currency, quantity and price
- blocks generated per account are now traced in a new replicator and are availble
  in the UI and from the API
- improvements/optimizations of replicator SQL and where needed combining SQL
  based solutions with custom caching solutions. this is an ongoing process,
  major updates to the way we deal with our rather unique replicator mechanism
  are to be expected
- thread safety improvements

When the hard fork happens only servers running this version or higher will be
able to connect.

HEAT SERVER 2.0.0

https://github.com/Heat-Ledger-Ltd/heatledger/releases/tag/v2.0.0

HEAT WALLET 2.2.0 [DESKTOP WITH SERVER]

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

HEAT CLIENT 2.2.0 [DESKTOP LIGHT VERSION - NO SERVER]

https://github.com/Heat-Ledger-Ltd/heat-ui/releases/tag/v2.2.0

OrgiOrg wrote Re: Heatledger 2.0.0 with Heatwallet 2.2.0 released on October 10, 2017, 01:26:16 PM
after update from 2.0.0 to 2.2.0 i got a lot of errors in den server log


2017-10-10 12:26:11 [pool-5-thread-3] DEBUG c.heatledger.BlockchainProcessorImpl Didn't accept any blocks, pushing back my previous blocks
2017-10-10 12:26:11 [pool-5-thread-3] INFO c.heatledger.BlockchainProcessorImpl Pushed block 446739758241941207 at height 240935 received 2017-10-10 11:10:21 from 213.202.212.213 [0 39211344265355 77627616425]
2017-10-10 12:26:12 [pool-5-thread-4] INFO com.heatledger.peer.PeerImpl Unblacklisting 78.46.176.8
2017-10-10 12:26:14 [pool-5-thread-2] DEBUG c.heatledger.BlockchainProcessorImpl Will process a fork of 719 blocks
2017-10-10 12:26:14 [pool-5-thread-2] DEBUG c.heatledger.BlockchainProcessorImpl Rollback from 240935 to 240934
2017-10-10 12:26:14 [pool-5-thread-2] INFO com.heatledger.persist.Persist Persist rollback to 240934
2017-10-10 12:26:14 [pool-5-thread-2] INFO c.heatledger.BlockchainProcessorImpl Popped block 446739758241941207 with height 240935
"com.heatledger.BlockchainProcessor$TransactionNotAcceptedException: Double spending transaction: 14455434550905911531 transaction: {\"senderPublicKey\":\"63a881ad93a588b86440aca966fa571f38fb6fec4017c9e326a285fe6d96e670\",\"signature\":\"3a781f07ee6f20ae91b097025b8a25f0b1b4296c45550ea2eb86795badc1490fe49d727051c2448e2cf4ed81ddd3daccea63aa507b657f0d014bb994ec1bb430\",\"feeHQT\":1000000,\"type\":2,\"version\":1,\"ecBlockId\":\"9631288308767843541\",\"attachment\":{\"quantity\":6800000,\"encryptedMessage\":{\"data\":\"3ef0bae446876bed9831aa1119a545e9efc988e2cde5f4a290a283b2cf9b8e430cea87b922f391a4b1da27af5ccecc80317a33c5d234aa1297c09f266f20bc9dd74cb8e0cd7e5aa07e8c970962abb52e\",\"nonce\":\"e620ed8f06af65dcdbea42120e9587186012ecb61e5bc359d9900593a2e07aa2\",\"isText\":true},\"version.EncryptedMessage\":1,\"version.PublicKeyAnnouncement\":1,\"recipientPublicKey\":\"2eb8137e3caefb6b14088107e96f02752b8e0ee685afea280587867119dff14d\",\"version.AssetTransfer\":1,\"asset\":\"5592059897546023466\"},\"subtype\":2,\"recipient\":\"9583431768758058558\",\"ecBlockHeight\":240915,\"deadline\":1440,\"timestamp\":107616637,\"amountHQT\":0}"
"\tat com.heatledger.BlockchainProcessorImpl.accept(BlockchainProcessorImpl.java:944)"
"\tat com.heatledger.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:901)"
"\tat com.heatledger.BlockchainProcessorImpl$1.processFork(BlockchainProcessorImpl.java:442)"
"\tat com.heatledger.BlockchainProcessorImpl$1.downloadBlockchain(BlockchainProcessorImpl.java:401)"
"\tat com.heatledger.BlockchainProcessorImpl$1.run(BlockchainProcessorImpl.java:218)"
"\tat java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)"
"\tat java.util.concurrent.FutureTask.runAndReset(Unknown Source)"
"\tat java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)"
"\tat java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)"
"\tat java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)"
"\tat java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)"
"\tat java.lang.Thread.run(Unknown Source)"
2017-10-10 12:26:14 [pool-5-thread-2] DEBUG com.heatledger.peer.PeerImpl Bl

warmach wrote Re: Heatledger 2.0.0 with Heatwallet 2.2.0 released on October 14, 2017, 10:43:41 PM
For the new balance leasing, I am looking for an API call that will return the leased balances of an account for a specific block.  This is a basic need for pool operators.  Basically, I am looking for the HEAT version of the FIMK api call getAccountLessors


OrgiOrg wrote Re: Heatledger 2.0.0 with Heatwallet 2.2.0 released on October 25, 2017, 08:52:56 AM
any news?


after update from 2.0.0 to 2.2.0 i got a lot of errors in den server log


2017-10-10 12:26:11 [pool-5-thread-3] DEBUG c.heatledger.BlockchainProcessorImpl Didn't accept any blocks, pushing back my previous blocks
2017-10-10 12:26:11 [pool-5-thread-3] INFO c.heatledger.BlockchainProcessorImpl Pushed block 446739758241941207 at height 240935 received 2017-10-10 11:10:21 from 213.202.212.213 [0 39211344265355 77627616425]
2017-10-10 12:26:12 [pool-5-thread-4] INFO com.heatledger.peer.PeerImpl Unblacklisting 78.46.176.8
2017-10-10 12:26:14 [pool-5-thread-2] DEBUG c.heatledger.BlockchainProcessorImpl Will process a fork of 719 blocks
2017-10-10 12:26:14 [pool-5-thread-2] DEBUG c.heatledger.BlockchainProcessorImpl Rollback from 240935 to 240934
2017-10-10 12:26:14 [pool-5-thread-2] INFO com.heatledger.persist.Persist Persist rollback to 240934
2017-10-10 12:26:14 [pool-5-thread-2] INFO c.heatledger.BlockchainProcessorImpl Popped block 446739758241941207 with height 240935
"com.heatledger.BlockchainProcessor$TransactionNotAcceptedException: Double spending transaction: 14455434550905911531 transaction: {\"senderPublicKey\":\"63a881ad93a588b86440aca966fa571f38fb6fec4017c9e326a285fe6d96e670\",\"signature\":\"3a781f07ee6f20ae91b097025b8a25f0b1b4296c45550ea2eb86795badc1490fe49d727051c2448e2cf4ed81ddd3daccea63aa507b657f0d014bb994ec1bb430\",\"feeHQT\":1000000,\"type\":2,\"version\":1,\"ecBlockId\":\"9631288308767843541\",\"attachment\":{\"quantity\":6800000,\"encryptedMessage\":{\"data\":\"3ef0bae446876bed9831aa1119a545e9efc988e2cde5f4a290a283b2cf9b8e430cea87b922f391a4b1da27af5ccecc80317a33c5d234aa1297c09f266f20bc9dd74cb8e0cd7e5aa07e8c970962abb52e\",\"nonce\":\"e620ed8f06af65dcdbea42120e9587186012ecb61e5bc359d9900593a2e07aa2\",\"isText\":true},\"version.EncryptedMessage\":1,\"version.PublicKeyAnnouncement\":1,\"recipientPublicKey\":\"2eb8137e3caefb6b14088107e96f02752b8e0ee685afea280587867119dff14d\",\"version.AssetTransfer\":1,\"asset\":\"5592059897546023466\"},\"subtype\":2,\"recipient\":\"9583431768758058558\",\"ecBlockHeight\":240915,\"deadline\":1440,\"timestamp\":107616637,\"amountHQT\":0}"
"\tat com.heatledger.BlockchainProcessorImpl.accept(BlockchainProcessorImpl.java:944)"
"\tat com.heatledger.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:901)"
"\tat com.heatledger.BlockchainProcessorImpl$1.processFork(BlockchainProcessorImpl.java:442)"
"\tat com.heatledger.BlockchainProcessorImpl$1.downloadBlockchain(BlockchainProcessorImpl.java:401)"
"\tat com.heatledger.BlockchainProcessorImpl$1.run(BlockchainProcessorImpl.java:218)"
"\tat java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)"
"\tat java.util.concurrent.FutureTask.runAndReset(Unknown Source)"
"\tat java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)"
"\tat java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)"
"\tat java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)"
"\tat java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)"
"\tat java.lang.Thread.run(Unknown Source)"
2017-10-10 12:26:14 [pool-5-thread-2] DEBUG com.heatledger.peer.PeerImpl Bl

Eliphaz wrote Re: Heatledger 2.0.0 with Heatwallet 2.2.0 released on October 25, 2017, 09:31:29 AM
If the server keeps on going and pushing blocks, errors should be normal and expected.

any news?


after update from 2.0.0 to 2.2.0 i got a lot of errors in den server log


2017-10-10 12:26:11 [pool-5-thread-3] DEBUG c.heatledger.BlockchainProcessorImpl Didn't accept any blocks, pushing back my previous blocks
2017-10-10 12:26:11 [pool-5-thread-3] INFO c.heatledger.BlockchainProcessorImpl Pushed block 446739758241941207 at height 240935 received 2017-10-10 11:10:21 from 213.202.212.213 [0 39211344265355 77627616425]
2017-10-10 12:26:12 [pool-5-thread-4] INFO com.heatledger.peer.PeerImpl Unblacklisting 78.46.176.8
2017-10-10 12:26:14 [pool-5-thread-2] DEBUG c.heatledger.BlockchainProcessorImpl Will process a fork of 719 blocks
2017-10-10 12:26:14 [pool-5-thread-2] DEBUG c.heatledger.BlockchainProcessorImpl Rollback from 240935 to 240934
2017-10-10 12:26:14 [pool-5-thread-2] INFO com.heatledger.persist.Persist Persist rollback to 240934
2017-10-10 12:26:14 [pool-5-thread-2] INFO c.heatledger.BlockchainProcessorImpl Popped block 446739758241941207 with height 240935
"com.heatledger.BlockchainProcessor$TransactionNotAcceptedException: Double spending transaction: 14455434550905911531 transaction: {\"senderPublicKey\":\"63a881ad93a588b86440aca966fa571f38fb6fec4017c9e326a285fe6d96e670\",\"signature\":\"3a781f07ee6f20ae91b097025b8a25f0b1b4296c45550ea2eb86795badc1490fe49d727051c2448e2cf4ed81ddd3daccea63aa507b657f0d014bb994ec1bb430\",\"feeHQT\":1000000,\"type\":2,\"version\":1,\"ecBlockId\":\"9631288308767843541\",\"attachment\":{\"quantity\":6800000,\"encryptedMessage\":{\"data\":\"3ef0bae446876bed9831aa1119a545e9efc988e2cde5f4a290a283b2cf9b8e430cea87b922f391a4b1da27af5ccecc80317a33c5d234aa1297c09f266f20bc9dd74cb8e0cd7e5aa07e8c970962abb52e\",\"nonce\":\"e620ed8f06af65dcdbea42120e9587186012ecb61e5bc359d9900593a2e07aa2\",\"isText\":true},\"version.EncryptedMessage\":1,\"version.PublicKeyAnnouncement\":1,\"recipientPublicKey\":\"2eb8137e3caefb6b14088107e96f02752b8e0ee685afea280587867119dff14d\",\"version.AssetTransfer\":1,\"asset\":\"5592059897546023466\"},\"subtype\":2,\"recipient\":\"9583431768758058558\",\"ecBlockHeight\":240915,\"deadline\":1440,\"timestamp\":107616637,\"amountHQT\":0}"
"\tat com.heatledger.BlockchainProcessorImpl.accept(BlockchainProcessorImpl.java:944)"
"\tat com.heatledger.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:901)"
"\tat com.heatledger.BlockchainProcessorImpl$1.processFork(BlockchainProcessorImpl.java:442)"
"\tat com.heatledger.BlockchainProcessorImpl$1.downloadBlockchain(BlockchainProcessorImpl.java:401)"
"\tat com.heatledger.BlockchainProcessorImpl$1.run(BlockchainProcessorImpl.java:218)"
"\tat java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)"
"\tat java.util.concurrent.FutureTask.runAndReset(Unknown Source)"
"\tat java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)"
"\tat java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)"
"\tat java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)"
"\tat java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)"
"\tat java.lang.Thread.run(Unknown Source)"
2017-10-10 12:26:14 [pool-5-thread-2] DEBUG com.heatledger.peer.PeerImpl Bl

OrgiOrg wrote Re: Heatledger 2.0.0 with Heatwallet 2.2.0 released on October 25, 2017, 12:58:10 PM
how can i check if the server keeps pushing blocks?

Eliphaz wrote Re: Heatledger 2.0.0 with Heatwallet 2.2.0 released on October 27, 2017, 10:11:05 PM
how can i check if the server keeps pushing blocks?
Server log states for instance:

Pushed block 446739758241941207 at height 240935 received 2017-10-10 11:10:21 from 213.202.212.213

and you can see the latest blocks from your own server matching with https://heatwallet.com/#/explorer

OrgiOrg wrote Re: Heatledger 2.0.0 with Heatwallet 2.2.0 released on October 29, 2017, 07:16:48 AM
after deleting all heat-folders in %APPDATA% and reinstall new wallet all is fine!

Pages: [1]   Go Up