Thanks. I got this to work. Very helpful.
Like others I suspect, my actual and projected payouts are much lower than the Storj V3 earnings calculator suggested - even though I have a fast Internet connection. But that’s another discussion for elsewhere.
Thank’s for the good work and bring to us a tool that should be included in the dashboard.
There is a reason for start the node after the earnings script? I usualy start the node after the database copy for keep the downtime as low as possibile.
Starting after copy is fine too. The time difference is minimal though. But I changed it in my previous post.
I have a nice little update today. I noticed that the info.db actually stores storage data from previous months now. Last month it looked like it was there for one month only, but that likely was just because this way of storing the data was started that month. Long story short, starting with September 2019, historic data is now available, meaning that your historic totals should now reflect actual payouts!
Today’s update incorporates changes to actually display that storage information and adds a warning about the missing information for months prior to September 2019. There are some other tweaks as well. Enjoy!
It works like a charm!
Thank you so much for this very usefull tool! It would be great if Storj teams decided to inculde it natively 
Already suggested that and more on the Node Dashboard UI/UX Feedback topic 
Our Storj friends love to throw me curve balls with updates to the database structure for storagenodes. But they’re not getting me that easily! 
@Alexey you may want to update the reference to info.db at the bottom of this page as well.
It now requires bandwidth.db, storage_usage.db and piece_spaced_used.db to be copied.
btw… is that a typo in piece_spaced_used.db? That’s actually what the file is called.
Love this latest version, it rocks!
Maybe a stupid question: Why do we have some “NOT PAID” lines?
Because ingress traffic isn’t paid and storage is paid only once. I have multiple metrics for storage in there that basically descrive the same thing in different units. The currently stored amount is just what’s stored at this moment. And then there is the average over the entire months and GBh. Since payment is based on the average over the entire months, that line now lists the actual amount.
I have these 2 lines since version 7.0.0 at the top of the output when I run the script.
<sqlite3.Cursor object at 0x7fe9cea99570>
<sqlite3.Cursor object at 0x7fe9cea99570>
Are these error messages or what else do they mean?
No, they’re me being an idiot and leaving in some debug code in the version I put on github. Thanks for pointing it out. Fixed it with a minor release.
Do the estimated earnings take into account the surge payout (x4 for July, August, September, October)?
Thanks!
No, This is before surge. The surge payouts are different depending on how old your node is. I get 5x because my node existed prior to surge going into effect. I pondered including it but eventually decided against it since this is only temporary.
I have doubt when I ran the script I have received below output, When I saw Total in Disk usage it took only :Disk Average Month" only, let me know If I am wrong, Suppose it has to show 310.35 GBh
Note : I have started my node just 5 days back, my output as below :
the “m” stands for “month”, so it’s MegaByteMonth. Divide 310GBh by 24 and 30 and you will get almost exactly 431MBm.
That’s exactly right. GBh and MBm express the same storage, but in a different unit. MBm can be seen as the average amount stored for the entire calendar month. And since the payouts are expressed as $1.50 per TB per month, I figured for payout calculation purposes this number is more meaningful than GBh, which can go into massive numbers that don’t mean much to the average person.
Since I like being able to run stuff through Docker and avoid downloading scripts to the host machine, I’ve published a Docker image (source) that will run this script against /data. You can invoke it like so:
docker run --rm -v /path/to/storjdata/storage:/data cdhowie/storj_earnings:latest
@BrightSilence, I’ve subscribed to releases on your repo. If you make a Github release when you publish updates, I will be notified to update the Docker image – or you can feel free to merge my docker branch (linked above).
@cdhowie I think executing the script inside different folder is safer and Storj will incorporate earnings feature eventually. The time to download scripts < fixing a corrupted database.