Just a small update today. Storj seems to have switched to using 720 hour months to align with exactly 30 days, instead of the actual average hours per month of ~730. Effectively this means we get paid for $1.50 for storing data 30 days instead of for storing data an average calendar month. This means we’re making slightly more than the earnings calculator was displaying. This has now been fixed and numbers should better align with what’s shown on the web dashboard. In my case the numbers are now exactly the same across web dashboard and earnings calculator.
v9.3.1 - Change hours per month to 720
Storj has started to use 720 hours per month in calculating payout, this update changes the earnings calculator to use the same
Thanks for the heads up. Unfortunately my nodes are all on docker, so it’ll be a while until I get this update and can provide an update to the earnings calculator. Apologies for the slight delay, but I’ll get to it when I can.
This issue has now been fixed with todays release. I apologize for the inconvenience and the delay for those who got this node update earlier than I did. It sucks to have to wait for a fix. But to make up for it I implemented some new goodies. We now have uptime as recorded by the satellites with the new uptime tracking system. With more verbose warnings for different scenarios that may cause issues. I’ve also reshuffled the layout a little bit to make sure the longer status line doesn’t get in the way of the important stuff.
Please note that the warning for stefan-benten is likely because that satellite wasn’t updated and doesn’t report back uptime as it’s about to be phased out. You can safely ignore this for now. That’s the downside of reporting stats that haven’t been officially exposed to end users yet.
Here’s a few examples of the more detailed warning messages.
Please note, there is currently a bug that prevents the uptime to be updated in the first 30 days. This is on the storagenode end. So I don’t expect this will show correct information in the first month.
Additionally this new update requires node version v1.12 or later. The database changes made to the node were not backwards compatible.
Nice update. Good addition with the uptime scores. Also good to see that it’s showing to be expected results for the current month on Stefan-Benten satellite. Looks like it’s not communicating with the nodes anymore as my uptime is showing 0%
Is your node brand new? If not, is /home/dwr/storj where you store actual data for the network or is that where you placed your identity files? In my case, I have /opt/storj/identity for where my identity is stored and /opt/storj/data for the actual data hosting and all I type is “python earnings.py /opt/storj/data” (minus the quotes) and it works fine. If you’ve got your run command saved, post it here (you can redact the values for anything other than the bind points and I recommend that you do redact the other values).