Please add database backup step during upgrade storage node. I see a lot of SNO have issues when storagenodes upgrade to the new versions. In most cases database is corrupted, and have possibility to recovery from backup is very ipmortant
Jul 11 2019
Enter a subject
Log in / Sign up
Identify yourself with your email address
You won't be notified about changes to this idea.
Distribute audits across storagenodes
Hash SNO errors. If the hash is unique, send the error to storj. Storj stores hash. Future SNOs check storj to see if it is known issue and whether SNO should be concerned about said issue
Don't keep storagnode offline because of brief HDD reconnect as it would result in DQ
Reward system to onboard new SNO´s
Use the given email address from the docker run command to send monthly reports with detailed information about your node (payout + surge payouts + held amount, storage, traffic, reputation, uptime, possible improvements and an overall score for example) and notify users when their node goes offline (without a third party service)
Use more threads when generating keys for a new node.
Allow for a storage node to perform planned maintenance
Email notification in case the node goes OFFLINE
A service that Satellite operators can sign up on to notify Storage Nodes who are on the market to work with more satellites