Let’s fork this ToS discussion thread into it’s own topic please. @Alexey [image] Node disk configuration question It’s not ok, and you know this. This is evading the protection rule for nodes selection from each /24 to do not store the pieces of the same segment in the same physical location. …

Seems you missing the main thing. Why did you ever want to use an unique public IP for each node, running on the same server even using the same ISP? Right, to bypass the /24 filter. So, you already know about the filter and already know, that it’s enabled by default on the satellite, it’s part of …

[image] JWvdV: Every storage node operator (SNO) must be identifiable by the same STORJ-wallet and/or email address across the whole network, in such a way that a single SNO always is to be determined to be the same if one of them are the same How would you enforce this? Some sort of Know Yo…

No, much simpler: Table SNOs: ID (auto-increment), … Table nodes: ID , SNOID. Table SNOEmailAddresses: SNOID, MailAddress . Table SNOWallets: SNOID, WalletNumber . Every time, when a node signs in with its credentials it also delivers the walletnumber and mailaddress besides the nodeID. This sc…

Some email provider have their own rule for alias, ie: yourusername@provider.com and any combination of yourusername+39@provider.com will also be your alias. You would have to learn all the rules for each email provider and filter it correctly. If it come to that, what prevent an SNO to create a new…

Enforcement is not that important. There will always be few who try to cheat in any system, there is no good reason to waste disproportionate amount of resources to make life of disproportionally small number of cheaters temporarily slightly more frustrating. It is, and always will be, possible to …

[image] JWvdV: There is no definition of the storage network in the ToS leave alone it’s default behaviour, so it’s ambiguous It should not be in ToS, because it’s a current implementation of the node selection, described in the whitepaper. The current implementation is described in the docum…

[image] Alexey: It should not be in ToS, because it’s a current implementation of the node selection, described in the whitepaper. The current implementation is described in the documentation and blueprints. You think practical but not juridical. At first, there is no reference to it (=whit…

[image] ToS are updated, how to get a notification? Sorry about closing the topic about breaking the rule of /24 subnet. Indeed, you should be. Because it broke a Western public rule: freedom of speech, without hurting people without any necessity. In my opinion it was a sane discussion, on …

[image] JWvdV: In my opinion it was a sane discussion, on ToS not being aligned with current practice aside from being malwritten and vague. I agree, however, I’m not in the place to make any legal statements. I use what I have and what’s discussed in many places. I still think, that making …

[image] Alexey: But we recently started to change RS settings (see Updates on Test Data - #281 by littleskunk ), and it makes me feel bad if we can lose data to greedy SNOs with lots of hardware that use any trick to get around the /24 filter and when their hardware dies, which it will if they ca…

[image] Alexey: I agree, however, I’m not in the place to make any legal statements. I see, but you’re the one who was advocating certain things to be in the ToS. Since it’s a legal document, that statement can’t be considered otherwise than legal. Especially, if you’re closing topics in whic…

Storj Community Forum (official)

Using multiple IPs on the same physical service

Node Operators getting started