Quote from: AnonyMint on June 13, 2013, 02:52:53 AM

Quote from: digitalindustry on June 13, 2013, 02:49:03 AM

Quote from: Etlase2 on June 12, 2013, 08:44:20 PM

I have already stated that all it takes is a deterministic function to be applied to the current order of SHs. The only way to affect the outcome of this function is continually add or remove SHs from the equation. Adding costs significant amounts of money, subtracting has penalties in both power over the system and early withdrawals. There is no infinite possibility scenario for the attacker to perform. New joins will be added in a deterministic manner that has nothing to do with the public key.

Sor.rge, do not allow yourself to be derailed by what AnonyMint thinks is necessary due to his lack of competence.

+1 to that

before i slept i was thinking , why does he insist it has to be random .

thanks for the explanation Etlase, so now i know that , the doing of this , i'd like to contribute -

Your posts are meaningless, because you don't understand the technical issues. You are just adding noise here.

If you don't understand the critical importance of the random input entropy in cryptography, then you have no business posting here about this.

says the guy that i just read at least 9 pages worth of you saying the same thing... and wanted to try to educated me about the 78 year cycle or some other 1900's style economics.

Ok why not let the network randomize the order - ?

1. A join has been requested -

2. Signal sent to any online client - "please send a completely random function"

3. Base it on time one time and one the function another time.

4. Out of the response stream have that randomly generate a function.

plus i have s simple question for you, explain what the worst case scenario is if its not 100% random.