the ~perfect transcription of CRUST - Pastebin.com the unprecedented percentage of 98% for a complete CRUST transcription (probably slightly over-inflated, in parts, but was getting feelings of 100% for the first dozen paragraphs or something)
So when a CRUST node starts, itās going to have a list of protocols it knows it can deal with. So a CRUST node starts, it might know that itās got TCP and UTP. So on start, thatās going to have to connect at least one of each protocol. So at least one TCP and at least one UTP thing would have to be started there.
But itās a P2P networking solution. And a lot of P2P stuff will be happy with just one connection each. But, āTrust??ā Trust is the issue here.
And this is the Starbucks attack I was talking about. Where, if we know thereās a Beacon thing for instanceāand I start a Beacon node, and you come to the Starbucks that I happen to be sitting ināI know that youāll connect to me. I donāt know what I could do to you after that. But I know that youāll connect to me. So thatās, probably not good.
Thatās the beauty of CJDNS. You are putting TRUST on your friends/family router you choose to connect to. You know you trust that router, and the router knows it trusts you. You only need to know up to three routers. One of those three routers know other three routers. And so forth. Triangle connections, that leads to a hexagon shape networking. The rest of the network will not know anything about you except one of the two/three routers you send data to. This brings a much higher trust, with safe security.
-=============================================================================== - Pastebin.com slightly over 1/2 done, and lots of repetition in this talk, but Iāve split the paragraphs well. As for the dedicated thread, yeah probably. CRUST transcription I donāt think Iām going to look at again. I can definitely look at the other two again, and of course this Vaults one.