Each section has Elders, these are 7 oldest (most trusted nodes). The have a DB of which Adults (up to 120 of these per section) hold the data. On any Fetch, the Eder can confirm the relevant Adults passed the data. Also on churn (node leave/join) the relevent data is copied to new locations. So churn in the section helps us maintain the data.
An important role is continualy checking nodes for malice, evan those we trust more as they may be in zombie mode bad guys.
Any code that can be linked to that already accomplishes all this or still to be implemented? And to be picky in language I see you say the "Elder can confirm" does this mean the "Elder will confirm", just a change in wording from a possibility to a certainty.
"An important role is continually checking nodes for malice, evan those we trust more as they may be in zombie mode bad guys." -> This is still to be implemented as well correct? And prior to implementation we need some sort of RFC that defines types of malice that can occur from a given node as well as appropriate and secure means to detect the various cases. Ones that come to my mind are forced sluggishness in an attempt to slow down the network, intentional loss of data to cause extra lookups elsewhere for a given chunk, forced intermittent connectivity, so maybe at L4 level it decides to throw connection reset/connection refused in an attempt to bottleneck traffic across the network.
An important role is continualy checking nodes for malice, evan those we trust more as they may be in zombie mode bad guys.