SafeNet needs a completely new communication protocol

[neo]

@Toivo

Somehow I was also thinking that the chunks are now downloaded straight from adults to clients.

It was being said that the Elder will do the sending from the section, there is the issue of ensuring the chunk is correct.

If the adult sends the chunk directly to the client then the adult could send garbage (after giving valid hash to elder as proof), if the client complains then how does the section (elders) know the client isn’t lying causing delays, extra work, etc for the elders as they punish the adult when the adult was correct.

Read the latest (that I’ve found) on this.

@maidsafe

The largest change therein is that registers are now stored at adults, along with chunks. Which makes elders pure relay nodes as things stand. (They will of course eventually have other more, DBCy duties)

@maidsafe

When someone makes a GET request, that kick starts a number of processes. First, the request is relayed to the elders in which section the chunk is stored. The elders then calculate which four adults store the chunk - the four XOR-closest to the chunk’s address - and each of those adults pass their copy of the chunk back to the elders, who then return them to the requesting client.