Happy New Year and Updated calculation per Jan 1, 2018

First of all a happy new year to all of you!

Today I’ve changed the summary sheet as shown on this website, to incorporate my new and easier calculation I am using for the pool maintenance. I’ve simplified the way the calculations are included, and as a result the summary page now shows all open balances with already the fees being deducted. So what you see (as open balance) is what you get!

If you happen to have any feedback, don’t hesitate to contact me!

Note, December 2017 report still has to follow for the pool results!

Some forking on Dec 15

Earlier today some forking started to occur on the blockchain (around 10am GMT+1), and at the moment I am writing this I have not been able to get the pool node in sync with the chain. Somehow we ended up on our own chain, perhaps with a few others. Re-downloading the chain as we speak, hoping to be up and running again soon. So do expect the rewards for today to be slightly on the lower side.

Update 9.25PM: Forging is back on track, while some small glitches are still visible on heatwallet (some bad transactions which should leave the chain after 720 blocks). Actually the forging results now for today seem to become quite promising, as we currently are already at the level of where we would be for a complete day, so all in all no real impact for the pool!

Below an image of what you could observe if you did compare Heatwallet (on the “shorter” chain) vs running the server and the desktop app connected to Localhost (iso Heatwallet). Clearly shows what might go wrong, but also demonstrates the ease with which you can continue to use trading HEAT by using the server and pointing your desktop app to the localhost!

Rewards correction for Nov 27 HF

As you might have noticed, there recently have been 2 hardforks required for the HEAT network safety and stability. The first one happened on November 27 (v2.1.0 server release), after I observed and shared a potential safety issue with the devs. There was some more effective balance in the pool, than factually the lessors had as balance together… As a result, the pool forged close to 1400 HEAT more in a three day period.

Prior to the HF, I was asked by the devs to switch off the server for a while (1,5 day it turned out to be), to ensure that the HF went as smooth as possible. This was a success, at least for some days. However as a consequence we’ve missed out on some rewards (about 2500 HEAT for the total pool). I’ve checked in the community to see whether I could use the HEAT forged more in error as a bit of compensation and got no negative feedback. Hence I’ve used the stake % of each lessor on Nov 27 (the day of not-forging) to divide the rewards and added this balance to your accounts on the Dec 4 rewards. Note that the additional forging which was done with this 1400 HEAT is already incorporated in there, as I’ve set the 1385 in fact virtually apart and it ended up around 1400. See below your stake % and rewards for Nov 27, already included now in your open balance.

If any questions, let me know!

November 2017 HEATpool.org forging statistics

Just a view on the forging rewards accumulated by the HEAT pool on the total month of November 2017:

  • On average the reward percentage was 0.137% per day, which in total for the 30 days in November sums up to 4.10%
  • After starting the pool, the amount of lessors has grown to about 25 – 30 in total (some come, some go), including lessors having only very minimal HEAT (below 50), upto 1 lessor with even more than 650k HEAT!
  • Due to the Hard Fork around the release of server version 2.1.0, November 27 turned out to be quite a bad day for the pool

That’s it, so far it seems that the pool operations, though still manual of course, are working nicely as intended!

Update on recent Hard Fork (Nov 27, 2017)

Last Monday there was a mandatory server upgrade, due to a needed hard fork for additional stability and security of the HEAT network. The hard fork was required due to a bug found with the calculation of the effective balances which are relevant for staking. There was an account in the pool which was counted double in the total stake of the pool, which required a solution.

Due to the hard fork and the above mentioned issue, I switched off the node on Sunday and restarted shortly after the hard fork, after further alignment with the devs. This means that Sunday and Monday hardly no blocks were forged.

At the same time the pool did forge slightly more HEAT during the period in which the bug was happening. This is about 1100 HEAT more than what was supposed to be forged (over the course of about 3 days; regular forging rewards are about 2000 HEAT per day at the moment). I am considering whether these rewards can be used as compensation for the Sunday without the full forging power. All other nodes were having a slightly higher reward chance on Sunday due to the pool dropping out for 1.5 day, so I would expect that that balances things out a bit, with a small loss for the pool overall. Well, that’s life I guess…