Huh. I thought I saw in the documentation there are references to securing the master DHT, though I did see references to something called TomP2P. I'm no in a place where I can go back through the documentation for this though.
My original question I think still applies how every so I'll try and rephrase it: Is there a way to secure the Peer Discovery service in such a to secure against creating a secondary network of peers, then running a bookkeepers odds scheme. (Using the secondary marketplace as an options market for transactions on the first)
Which doc are you referring? We used a DHT in early days but that was long before the launch. Maybe I oversaw to update at some place...
There are 4 seed nodes to which you connect randomly at startup. They deliver you all known onion addresses in the network. From that list you select randomly peers until u have 8 connections. You also maintain your local peer list which will be used at follow up startups. I don't see a way how to partition the network. You get random incoming connections as well (e.g. if one takes your offer). The floodfill network architecture is very robust against eclipse attacks (dht problems) and partitioning. Thats why a floodfill architecture is used on Bitcoin as well.
My original question I think still applies how every so I'll try and rephrase it: Is there a way to secure the Peer Discovery service in such a to secure against creating a secondary network of peers, then running a bookkeepers odds scheme. (Using the secondary marketplace as an options market for transactions on the first)