This implies that when you have a “private key” to create address A2333 you could become part of the group that has that address in it’s range. So it implies you could become part of group A23xx where you are now number 33. This is not correct. You can’t pick your own address on the network. You can’t insert or activate an address, even if you have the private key. It’s more like:
- I’m a brand new node and my public key is “ABCD”. I can sign whatever to prove I’m the owner of this public (and private) key.
- In Crust a request is sent to be accepted in a group somewhere.
- A group called “HBGG” has a spot open for you and you are allowed to join them.
- They all agree your address is: “HBGG12” and from now on that’s your address.
- If they want you to sign a message or anything they want you to use your private/public key “ABCD” to prove you are indeed “HBGG12”.
So even if you have the private key to create the right SHA256 = “HBGG12” you still can’t become it. The network has a different opinion about who is “HBGG12”. The network will tell you: “HBGG12”= node which can prove to be “ABCD” and there’s full consensus in group “HGBB” that this is the case as they applied that address to this node (GetNetworkName (response)). The routing table is also agreed on by the close groups of “HBGG” like “HBGGa” and “HBGGb”. That’s why I kept saying in this topic that computation is useless if you want to target a group. And I’m still convinced this is the case. Maybe I missed some details, but I stand by my claim.
Here it is in the bootstrap diagram:
There’s no part in the diagram that says: “Look at the SHA256 of the node and determine from that value where a node belongs in the network.” It says: “GetNetworkName (request)” which asks other nodes to provide an address in a group. Look a bit further and you’ll see the GetNetworkName (response). That’s the one you can’t target by POW or any other way. It is given to you.
This is where SAFE is far different from any Blockchain technology.