Next step of safecoin algorithm design

[tfa]

@mav

@jlpell

What about indirection [as a solution to full vault errors]?

Sorry for neglecting to put this in the list, my biases are showing! I don’t really see indirection as a viable solution, but am open to being convinced. Redirection delays the problem but doesn’t solve it. There’s still a need for more space in that part of the xor graph (and a need for reduced complexity in xor space by eventually removing redirects). Seems like it’s in the short-term-pain for long-term-gain basket along with price increases. Possible for sure, but imo not worth the extra complexity.

I agree with @mav.

Indirection is needed, but to solve another problem: prevent vault operators from gaming the reward system by issuing get requests on the chunks they own. The solution would be a constant indirection where the group managing the source id of the chunk re-encrypts the chunk and send it to another group (the one corresponding to new id of the chunk).

This was discussed at length in the topic about Data Density Attack. In my mind "constant indirection with encryption" was the final solution found for this problem in this topic, but since then I didn’t see any proposal from @maidsafe about this important security feature. Sorry to highjack this topic but is this going to be implemented?