--- Tom Kaitchuck <[EMAIL PROTECTED]> wrote: 
> Cancer nodes currently pose a serious threat to the network. However stopping 
> them is not simple, especially an anti-specialization attack, as discussed 
> previously. My previously proposed solution would not work, because someone 
> could find a hash that works and then start subtracting values until they 
> find XXX. Toad pointed this out as a problem with SSKs, but it is a problem 
> with CHKs too.
> 
> I have a better solution.
> Take the index key that things are located under now. Split it into two parts. 
> Hash each part. Then start incrementing one part and hashing it each time 
> until the last few digits are the same as the hash of the second part. Then 
> data is routed biased on the hash of the resulting two hashes. This is 
> basically the same as my previous proposal, except that by hashing the key 
> after it is split, someone cannot work backwards.

I think you've just gotten on the ah-ha idea from the last thread.  You make them pay 
first then
they know the routing key.

What I'm worried about with Cancer nodes, is that they can pick thier specialization 
by doing a
really good job in an area of hash space.  Then they can be 110% as good as the others 
but censor
10%.

Here's an idea:  It kind of goes against NGR and may start a flame war.  We could use 
what we've
learned for spreading an adversary's keys around hash space to assign him 
specialization.  Say
when you install your node you have to spend 1000 CPU*s on a hash cash for your ID.  
Your nodes
routing point is then the hash of that hash cash.  

All your nieghbors agree on what you're supposed to be specailized in, and they base 
their metrics
based on that.  So if you suck at what you're supposed to be good at "you suck".  If 
you suck at
stuff you're not supposed to be too good at you're forgiven more.

We could improve this by making your nodeID expire in something like a month.  We 
could also let
you run multiple of these routing points.  So a newbie can get his first point and 
wait until he's
got data for that before claiming any others.

Of coarse the key to it all is "pay first, then know your routing point".
 
FLAME on -- somebody has got to like this idea


PS. Thanks Tom for giving me an idea of what these TUKs are supposed to do.


__________________________________________________________________

Gesendet von Yahoo! Mail - http://mail.yahoo.de
Logos und Klingelt�ne f�rs Handy bei http://sms.yahoo.de
_______________________________________________
Devl mailing list
[EMAIL PROTECTED]
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl

Reply via email to