So we got a new server version, the inclusion as well of the BTC wallet into heatwallet, some new team members (Welcome to Mari and Fito!) and some interesting updates from the devs. Let’s hope Q4 will bring us even more!
In terms of forging, September was a kind of normal month. I write kind of, as the forging percentage seemed to have gone a bit down in the 2nd half of the month. Whether this is a result from the new server version, or just changes in the amount of people staking HEAT at the moment is as of yet unknown. For the full month the total ROI for HEATpool was 2,482%. If you would take only the last 15 days into account however, we would have ended up around 2.2%. Needless to say, that would also still be quite a nice ROI in my opinion 😉
Below the graph showing the fluctuations in the daily forging percentages, I’ve updated the visuals a bit to show the daily percentages this time:
A bit later than usual, due to the holiday season. Nevertheless, herewith the ROI updates for both July and August.
- The total ROI for July 2018 was 2,75%. Nicely in line with expectations. Overall as usual some variance in the month, with a spike caused at the moment Supernet wasn’t forging for about a day.
- The picture for August is very different, where the ROI ended up at 1,98%. The reason for this drop, was some forking which happened most likely due to the stake sizes of both this pool and Heatlegendspool. This was quickly resolved after Heatlegendspool created a split in 2 pools, but due to the fact that I was on holiday in France (which was great by the way!), I was unable to restart the server again… So consider it bad luck 🙁
- Disregarding the period in which no rewards were forged, also August seemed to be a rather stable month
And another month went by, with smooth forging results for HEATpool and a stable situation in general. There were only 2 occassions worth mentioning, as also shown in the graph below. In one case the Scaleway server got rebooted (security updated enforced by Scaleway), after which I could not restart forging being not at home… The days thereafter however, a major staker was not forging for a few days which nicely compensated the gap.
As the title says, we ended up with an ROI of 2,72%. Not bad at all!
To summarize what happened last month:
- Stability, check! No issues whatsoever, no server restarts needed, no weird ROI spikes… great stuff!
- The ETH wallet integration launched in Heatwallet, finally a great new major release. Now the first bugs have been sorted out, the feature works as intended, giving you a great possibility to securely store your ETH and ERC20 tokens in Heatwallet (both on the web and in the Desktop apps), with more to come in the future!
- For the pool, we ended up at 2.66% ROI in May, which is close to the 2.6% average I have been mentioning a few times.
- At the time of writing this post, there are in total 57 lessors in the pool, with a total stake of ~1.8M HEAT. Not as high as the HEATlegendspool (see the updated links section on this site for his pool info, and while you do also check out the one from Jeffmarco if you want to give them a try), but were still one of the biggest stakers out there!
The daily ROI % can be seen in the image below, did I already mention the stability of the HEAT server? 🙂
Overall, the ROI in April 2018 for HEATpool.org was just above 3% (3,05), mostly affected by the drop in rewards per block in the HEAT chain. At the same time the chain has been very stable with no forking behaviour or whatsoever, I haven’t had the need to restart my nodes once in the month!
As the time of writing (May 10), the ROI for May at this moment seems to head to approx. 2.6%. Note that May will be the first full month with 6 HEAT/block rewards hence the lower ROI compared to April is anyway expected.
So far so good, now all we need is some great new features and headlines related to the development of HEAT and we are all set!
Below the graph with daily returns in April:
As I could not find the time to create the overview for Feb 2018, I’ve now combined the rewards for Feb and March into one page.
- In February, the overall ROI (28 days only) was 4,12%.
- In March, the ROI was 4,67% in total.
- Like in previous months, there has been a moment of forking again in both Feb and March, which had a severe positive impact on the ROI, as shown in the graphs
- In the last days of March, the overall amount of HEAT being forged was back to a high level, and as a result the ROI currently is in the range of 3,4 – 3,8% (around 0,11 – 0,12% daily). Not bad at all, but certainly not as good as we’ve had in the last months.
Now let’s aim for a succesful Hard Fork with the 2.5.0 release of HEAT on Friday April 6, and onto the benchmarking feature!
With January now behind us, let me share the forging results for the full month. Overall I am happy to state that the HEAT network has proven to be very stable in the past few weeks. Only in the first week there were some hiccups still caused by legacy issues (from version 2.1.0), but for the pool this only has proven to be very beneficial as the pool node took the lead for about 1,5 day. If I would correct for this day, our ROI would not have reached 4.5%, but somewhere in the area of 3.8%. Still not bad at all right?!
Let me share some of the highlights, and check the graph below for the daily results:
- As mentioned, the overall ROI in January 2018 was 4.52%. When correcting for the major spike in the first week, the ROI would have been ~3.8%
- While daily returns vary a lot, the rest of the month has been very stable with daily returns between 0.10% and 0.15%. So if you’d like to calculate what you can expect in returns from joining HEATpool, you can use these stats.
- Somewhere in January, we aready achieved 200k HEAT rewards with the pool, which I consider quite impressive given that at that time the pool was not existing for longer than 3 months.
Let’s hope that the stability will continue in the future of HEAT, and for sure we can expect some nice new features from the HEAT team, they are working quite hard already on getting the things in place!
With some delay, find herewith the summary of forging status for December 2017.
In a nutshell:
- Overall an ROI of 7.65% was achieved, which is well above the average!
- As a rootcause to this high ROI, the forking issues in the HEAT network were the cause. There were some days where the pool almost was solo forging, and overall the amount of total HEAT being at stake was lower than in the months before.
- On average, the daily ROI was about 0.25%, heavily skewed by the solo forging day around Christmas (see the image below)
I am happy to confirm that the HEAT network is fully stable again in January. Unfortunately this will mean a lower ROI in January for sure, but let’s be honest: rather a great working product with a perfectly fine ROI, than a non-working product with a much higher ROI…
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!
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!