I got my payout punctual as usual from storj. For me it was around 110$. When I looked into my MND for all nodes, it is now expecting a payout of around 50-60$ at the end of month. I know that there is a big load of TTL Data which might be the case for this cut regarding possible deletion. But for me it seems huge (50%). Is this cut real, or is it just a miscalculation of the MND?
Looks like this is missing reports again… @Alexey knows about this and has fed back to developers - this is only something dashboard side and wouldn’t affect actual payouts
We are making it extra hard for US1 to report any data. There is some issue going on with the repair queue. Nothing too dangerous since the repair queue is ordered by risk and the segments that are most at danger are getting repaired first. However a side effect of a bigger repair queue is that the hole meta info loop takes longer than usually. And in the meantime we deploy the satellite or restart it for other reasons. That restarts the clock and this time we had a few more of these events to the point that US1 hasn’t finished a run yet.
I believe the moment US1 reports some data the payout estimate should be correct again. The storage node dashboard will look strange but the payout estimate is based on TBh so far * estimate time to end of month. So it should work the moment US1 hands out some TBh values.
ATM, this is just a suspiction, because the payment data is not shown in the nodes yet but…
What about payments? Looks like in July we were paid the estimated amount, but the satellite did not report data for some days, so the estimated amounts were wrong (lower than actual). The amount paid should have been higher than the amount received. When will the missing amount be sent? Maybe as a second payment?
On the other hand, what will happen with August? The estimated figures now are quite low (-75%) for these days. Are they going to recalculate the satellites taking into account these last days or are they going to do like last month and skip these days, thus reducing the rewards that we SNOs should actually collect?
From what I have gathered of the payout process in the forum, no days are skipped when calculating the actual payouts. The values we see in the average space used in the dashboard are not part of how the payout amount is calculated at the end of the month, therefore having “bad” reports during the month should have no impact on the real payouts (assuming nothing else is going wrong).
Can we please stop this and lock the thread? The month just started and not all satellites did at least 1 complete report. How do you think the estimate could be correctly calculated?
The cause is known as missing and incomplete reports from the satellites. And there are enough threads about this already. And I ask you again, how do you expect correct calculations from incomplete/missing data? You will not get a different answer here.
It’s like the endless threads “Where is my payment !!!11!!!” in the past at the beginning of the month when the terms say you will be paid in the first two weeks.
Wait guys, maybe I’ve explained myself wrong, or maybe I’m mixing things up in this topic. I’m not talking about this month, but about last month’s payment.
I will check it on my own, but I would like to ask the Storj team to check it as well. My impressions are like:
One satellite failed for 15 days (just an example).
The “used” estimate dropped to 50% (logically, because the satellite has not recognized the storage used during those days).
At the end of the month, I was paid the estimate, instead of the actual storage used.
I hope it is now clear. July numbers are not yet posted on the nodes, but I would keep this post open until those numbers are public so we can confirm/reject my suspicions.
That could be an explanation. So summarising, we don’t get paid for the resources used because of a bug that is not on our side and that we can’t solve in any way without compromising the whole node?
This does not sound good at all. Is there an ETA for the resolution?
Yes you can fix the issue. You can debug the code, fix the error there and then open up a pull request for everything to fix the issue. In that way you can fix the error without compromising your node and get the code checked by others