I’ll take this information to bring up my old thread again about full nodes not getting vetted.
I’ll referr to a situation a user has reported and that I have also experienced:
Audits can only complete successfully if a satellite can store data on a node. If a node is full, no data can be stored. When a new satellite comes up a full node cannot commence being audited.
The SNO would have to increase storage space to make room for new data but he does not have control over which satellites will use the increased space. If unlucky Storj starts a new round of testing, the additional storage could be filled with existing satellites data and non or almost non from a new satellite.
So my suggestion would be to create an (optional) process that makes sure that even a full node can receive data from a satellite it is not fully vetted on yet.
While I cannot suggest details how such a process must be designed, my idea would some kind of vetting space on a node that gets reserved for a new satellite once it appears online and the node appears to be not yet fully vetted on that satellite. For a full node it could mean that once a new satellite pops up, space gets reserved for data from this satellite like 1Gb-5Gb. This space could be on top of already allocated space or reserved when deletions happen. Until fully vetted on the new satellite, this space remains reserved to this satellite only.
I think such an implementation could be beneficial for SNOs as vetting could keep going even if a node is full of data. So once space becomes available on a node, SNO receives full amount of data without vetting restrictions much sooner.