Hi, a bit late to the game, had a spare 6Tb drive that i wasnt using and have a unraid server that is on 24/7 so thought i might as well try this. Have set the 6Tb in unassigned devices and setup a docker to use it.
have got it working and its currently collecting data
I have some questions:
Does it still do some vetting? if so, for how long? how would I know when it is done?
Once this node is set up and working, i plan to add another drive to Unraid and create another docker for node nunber 2. i assume I have to do the whole indentity process again? i cant use the same indentify files as node1?
EDIT: found the answer for this
Each node must have its own generated unique identity signed with a new authorization token. Using a copy of the same identity but different tokens will result in disqualification as it is the same identity but with missing data.
Is zkSync now the preferred method of payment? im using Eth right now, from Trust Wallet app
any best practices to follow?
Does Storj keep the hard drive spun at all times? or are there times of inactivity allowing the drive to spin down when not in use?
when setting up another node, i am right in saying i will need to use another DDNS address? or same addess but different port to point to second node on the same box?
Vetting is still a thing if that’s what you mean.
It usually takes a few weeks for a node to get vetted. There is no official way to know when it’s done, but @brightsilence’s excellent tool can be used to show vetting progress (among other things):
Kind of. Using ETH is fine but costs more to StorjLabs. For SNOs, the main difference is that there is a minimum amount threshold to be reached when getting paid in ETH (which changes every month, depending on ETH’s fees), which doesn’t apply to zkSync. Also so far, getting paid via zkSync grants you an extra 10% payment.
Nodes don’t do anything in particular to keep HDDs active. That said, even though a node’s disk can spin down from time to time when the node is brand new, the more data it gets, the more the disk gets used, so it quickly stays ON 24/7.
Both approach sound valid to me.
What’s important to note is that all nodes behind a /24 subnet are treated as a big single node by the Storj network.
Which means that if you have several nodes on the same IP, or on several IPs that share the same /24 subnet, they will all share ingress.
Hard to answer that, this forum is full of info, good practices, experience and tools ^^ Go explore
For me, the first thing to set up is a tool monitoring your node’s port, so you’re notified when it gets offline. A popular tool for that is uptimerobot.
Yes, it’s better to wait until the first node would be almost full or at least vetted, then you can start another one, otherwise the vetting process could take longer in two times for both nodes.
