>So here are some possibilities: > >1. For the first say 3 hops, the data is routed as normal, but is not >cached. This is determined by a flag on the request, which is randomly >turned off with a probability of 33%.
Uhm... isn't this against the goal to increase a data chunk's presence around the keyspace it's supposed to be stored? If it isn't cached within the first hops won't this extemely harm keyspace specialization? Or perhaps - am I way off here?
